Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test #22

Open
wants to merge 23 commits into
base: main
Choose a base branch
from
Open

test #22

wants to merge 23 commits into from

Conversation

orenc1
Copy link
Owner

@orenc1 orenc1 commented May 19, 2022

Signed-off-by: orenc1 [email protected]

Reviewer Checklist

Reviewers are supposed to review the PR for every aspect below one by one. To check an item means the PR is either "OK" or "Not Applicable" in terms of that item. All items are supposed to be checked before merging a PR.

  • PR Message
  • Commit Messages
  • How to test
  • Unit Tests
  • Functional Tests
  • User Documentation
  • Developer Documentation
  • Upgrade Scenario
  • Uninstallation Scenario
  • Backward Compatibility
  • Troubleshooting Friendly

Release note:

test

tiraboschi and others added 23 commits August 24, 2021 14:49
Adda a flag to the csv-merger tool to optionally ignore
relatedImages from component operators generated CSV.

Signed-off-by: Simone Tiraboschi <[email protected]>
* Apply retry logic in check_defaults.sh

Apply retry logic in check_defaults.sh to prevent flakyness due
to conflicts by the validating webhook cause by side effects
from the previous changes.

Signed-off-by: Simone Tiraboschi <[email protected]>

* Update Community-Operators Publisher Workflow

Since we are now working with floating tags for hco-operator and hco-webhook in the CSV, there is no need to calculate their digests and re-commit to the CSV after building and pushing them.
Therefore, upon making a tag with a version, the publish action has been extended to:
1. Build and push the application images (hco-operator, hco-webhook).
2. Calculate and replace the floating tags of the application images with their digests, to be published on community-operators.
3. Build and push the bundle and index image in semver mode (remove 'replaces' field from the CSV).

Signed-off-by: orenc1 <[email protected]>

* minor unrelated fixes

Signed-off-by: orenc1 <[email protected]>

Co-authored-by: Simone Tiraboschi <[email protected]>
…rics (kubevirt#1309)

- Current alert misses the first increment. The new query fixes that issue.

- Current component_name label contains only the name of the operand but it is hard
to diagnose. This PR adds object type to label as well.

- Now, the operator doesn't update the metric for configmap/kubevirt-storage-class-defaults
and configmap/v2v-vmware. This PR fixes that issue as well.

Signed-off-by: Erkan Erol <[email protected]>
* Apply retry logic in check_defaults.sh

Apply retry logic in check_defaults.sh to prevent flakyness due
to conflicts by the validating webhook cause by side effects
from the previous changes.

Signed-off-by: Simone Tiraboschi <[email protected]>

* Update Community-Operators Publisher Workflow

Since we are now working with floating tags for hco-operator and hco-webhook in the CSV, there is no need to calculate their digests and re-commit to the CSV after building and pushing them.
Therefore, upon making a tag with a version, the publish action has been extended to:
1. Build and push the application images (hco-operator, hco-webhook).
2. Calculate and replace the floating tags of the application images with their digests, to be published on community-operators.
3. Build and push the bundle and index image in semver mode (remove 'replaces' field from the CSV).

Signed-off-by: orenc1 <[email protected]>

* minor unrelated fixes

Signed-off-by: orenc1 <[email protected]>

Co-authored-by: Simone Tiraboschi <[email protected]>
* WIP: default permitted devices

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>

* use go1.15.11

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>

* Add the `Disabled` field to the permitted host device objects

Add to the check_defaults test

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>

* Enforce default permitted host devices

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>

* fix code review comments

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>

* Change CRD to force unique permitted host devices

Remove the permitted host devices validation from the webhook.

Instead, change the PciHostDevices' annotation to:
"+listType=map"
"+listMapKey=pciVendorSelector"

And the MediatedDevices' annotation to:
"+listType=map"
"+listMapKey=mdevNameSelector"

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>

* rename PciHostDevice.PCIVendorSelector to PciHostDevice.PCIDeviceSelector

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
* Bump KUBEVIRT to v0.41.0-rc.1

Signed-off-by: HCO Bump Bot <[email protected]>

* Remove image pinned v0.40.0-nightly...

Signed-off-by: Simone Tiraboschi <[email protected]>

Co-authored-by: orenc1 <[email protected]>
Co-authored-by: Simone Tiraboschi <[email protected]>
* Enable eventual launcher updates by default

Add the workloadUpdateStrategy API to the HyperConverged CR. Propagate its fields to KubeVirt

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>

* add some unit tests to increase coverage

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
Remove descriptions from unstored versions of CRDs
to keep the bundle size < 1MiB.

Until operator-framework/enhancements#40
got implemented, a bundle should not exceed 1MiB
because its internally (in the opm tool) managed
with a configmap.

Signed-off-by: Simone Tiraboschi <[email protected]>
split writing HyperConverged's status and body (spec/metadata)

Since writing to the HyperConverged status must be a seperate write nad we can't write the whole custome resource as an automic operation, it caused several instbility and conflicts.

This PR split the right to two calls - if the code modified something in the body (should be with very low frequency, except for during upgrade), HCO will write only the body, and exit with requeue = true to force additional call, then we expect the body not to be modified again, letting HCO to write only the status this time.

This is WIP because the unit test can't fully check that in unit tests, as the client mock *does* write the status together with the body, so if there is a mistake here, it will not be found in unit tests, and we need the CI tests to validate.

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
Signed-off-by: HCO Bump Bot <[email protected]>

Co-authored-by: kubevirt-bot <[email protected]>
1. refactor tools/docgen/main.go to reduce Cognitive Complexity
2. refactor hack/strip_old_descriptions.py to reduce Cognitive Complexity
3. remove code duplecation from cmd/hyperconverged-cluster-operator/main.go

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
Openshift UI used the spec.version to present the operator version. That feature was removed, so there is no reason for this field anymore.

Placing the version in the spec was problematic for two reasons:
1. the user can get the wrong impression that it is possible to upgrade the HCO version by changing its version, because the spec is for the user to edit.
2. we need to sync the spec.version and the status version, but can't do that as an atomic write, but in two different update operation, and that leads to edge cases.

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
Signed-off-by: orenc1 <[email protected]>
Signed-off-by: orenc1 <[email protected]>
Signed-off-by: orenc1 <[email protected]>
@orenc1
Copy link
Owner Author

orenc1 commented May 19, 2022

/rebase

@hco-bot
Copy link

hco-bot commented May 19, 2022

Rebase Bot action has failed.
Action URL: https://github.com/orenc1/hyperconverged-cluster-operator/actions/runs/2350856622

@coveralls
Copy link

Pull Request Test Coverage Report for Build 2350842774

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 84.228%

Totals Coverage Status
Change from base Build 2350826152: 0.0%
Covered Lines: 4160
Relevant Lines: 4939

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants