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

WINC-1040: Use Version annotation for service removal in WICD cleanup #1584

Merged

Conversation

saifshaikh48
Copy link
Contributor

This PR uses the version annotation instead of the desired version
as the source of truth when deconfiguring Windows services. This is
important to ensure there are no services left behind when upgrading,
if there is a change to the services CM spec between WMCO versions.

Using the desired version anno is kept as a backup operation if the node
does not have a version annotation (i.e. was not fully configured). This is
useful to recover when configuration fails and the instance needs to be reconciled.

This commit uses the version annotation instead of the desired version
as the source of truth when deconfiguring Windows services. This is important
to ensure there are no services left behind when upgrading, if there is a change
to the services CM spec between WMCO versions.

Using the desired version anno is kept as a backup operation if the node does
not have a version annotation (i.e. was not fully configured). This is useful
to recover when configuration fails and the instance needs to be reconciled.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 20, 2023
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 20, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 20, 2023

@saifshaikh48: This pull request references WINC-1033 which is a valid jira issue.

In response to this:

This PR uses the version annotation instead of the desired version
as the source of truth when deconfiguring Windows services. This is
important to ensure there are no services left behind when upgrading,
if there is a change to the services CM spec between WMCO versions.

Using the desired version anno is kept as a backup operation if the node
does not have a version annotation (i.e. was not fully configured). This is
useful to recover when configuration fails and the instance needs to be reconciled.

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 20, 2023

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@alinaryan
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 24, 2023
@saifshaikh48 saifshaikh48 changed the title WINC-1033: [cleanup] Use version annotation for WICD cleanup WINC-1044: Use Version annotation for service removal in WICD cleanup Apr 25, 2023
@openshift-ci-robot
Copy link

@saifshaikh48: No Jira issue with key WINC-1044 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

In response to this:

This PR uses the version annotation instead of the desired version
as the source of truth when deconfiguring Windows services. This is
important to ensure there are no services left behind when upgrading,
if there is a change to the services CM spec between WMCO versions.

Using the desired version anno is kept as a backup operation if the node
does not have a version annotation (i.e. was not fully configured). This is
useful to recover when configuration fails and the instance needs to be reconciled.

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.

@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 25, 2023
@saifshaikh48 saifshaikh48 changed the title WINC-1044: Use Version annotation for service removal in WICD cleanup WINC-1040: Use Version annotation for service removal in WICD cleanup Apr 25, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 25, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 25, 2023

@saifshaikh48: This pull request references WINC-1040 which is a valid jira issue.

In response to this:

This PR uses the version annotation instead of the desired version
as the source of truth when deconfiguring Windows services. This is
important to ensure there are no services left behind when upgrading,
if there is a change to the services CM spec between WMCO versions.

Using the desired version anno is kept as a backup operation if the node
does not have a version annotation (i.e. was not fully configured). This is
useful to recover when configuration fails and the instance needs to be reconciled.

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 26, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saifshaikh48, sebsoto

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 26, 2023
@saifshaikh48 saifshaikh48 marked this pull request as ready for review April 26, 2023 16:03
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 26, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 26, 2023

@saifshaikh48: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/nutanix-e2e-operator 7ba0459 link false /test nutanix-e2e-operator

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.

@openshift-merge-robot openshift-merge-robot merged commit 70e5e22 into openshift:master Apr 26, 2023
14 of 15 checks passed
@saifshaikh48
Copy link
Contributor Author

/cherry-pick release-4.13

@saifshaikh48
Copy link
Contributor Author

/cherry-pick release-4.12

@openshift-cherrypick-robot

@saifshaikh48: new pull request created: #1588

In response to this:

/cherry-pick release-4.13

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.

@openshift-cherrypick-robot

@saifshaikh48: new pull request created: #1589

In response to this:

/cherry-pick release-4.12

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants