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

Validate updates to the whole .spec stanza #912

Merged
merged 1 commit into from Nov 2, 2020
Merged

Validate updates to the whole .spec stanza #912

merged 1 commit into from Nov 2, 2020

Conversation

tiraboschi
Copy link
Member

@tiraboschi tiraboschi commented Nov 2, 2020

HCO is supposed to validate updates to its CR
also delegating to components operators the validation
of the changes it has to propagate (trying to apply
them in dry run mode first and committing only if all the
involved components accepted it).

This was done only for the .spec.worloads stanza,
applying the same strategy to the whole .spec stanza.

Fixes: https://bugzilla.redhat.com/1893646
Fixes: #911

Signed-off-by: Simone Tiraboschi stirabos@redhat.com

Release note:

Validate updates to the whole .spec stanza

@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/XS labels Nov 2, 2020
@ovirt-infra
Copy link

All tests passed

HCO is supposed to validate updates to its CR
also delegating to components operators the validation
of the changes it has to propagate (trying to apply
them in dry run mode first and committing only if all the
involved components accepted it).

This was done only for the .spec.worloads stanza,
applying the same strategy to the whole .spec stanza.

Fixes: https://bugzilla.redhat.com/1893646

Signed-off-by: Simone Tiraboschi <stirabos@redhat.com>
@ovirt-infra
Copy link

All tests passed

@nunnatsa
Copy link
Collaborator

nunnatsa commented Nov 2, 2020

/lgtm

/approve

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Nov 2, 2020
@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nunnatsa

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 2, 2020
@openshift-merge-robot
Copy link

@tiraboschi: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/hco-e2e-upgrade-azure f61c738 link /test hco-e2e-upgrade-azure

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nunnatsa
Copy link
Collaborator

nunnatsa commented Nov 2, 2020

/override-bot

@hco-bot
Copy link
Collaborator

hco-bot commented Nov 2, 2020

hco-e2e-upgrade-aws lane succeeded.
/override ci/prow/hco-e2e-upgrade-azure

@kubevirt-bot
Copy link
Contributor

@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-upgrade-azure

In response to this:

hco-e2e-upgrade-aws lane succeeded.
/override ci/prow/hco-e2e-upgrade-azure

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kubevirt-bot kubevirt-bot merged commit 6828b2a into kubevirt:master Nov 2, 2020
@tiraboschi tiraboschi deleted the dry_run_all branch November 2, 2020 14:39
@tiraboschi
Copy link
Member Author

/cherry-pick release-1.2

@kubevirt-bot
Copy link
Contributor

@tiraboschi: new pull request created: #913

In response to this:

/cherry-pick release-1.2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Pod placement API issue - dry run doesn't occur for all the stanza
6 participants