-
Notifications
You must be signed in to change notification settings - Fork 159
Bug 1977319: cleanup orphaned Service 'controller-manager-service' #388
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
Bug 1977319: cleanup orphaned Service 'controller-manager-service' #388
Conversation
|
@joelddiaz: This pull request references Bugzilla bug 1977319, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
/assign @akhil-rane |
akhil-rane
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
gone are the days of cleanup controller
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/bugzilla refresh |
|
@joelddiaz: This pull request references Bugzilla bug 1977319, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
| kind: Service | ||
| metadata: | ||
| annotations: | ||
| release.openshift.io/delete: "true" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CVO will ignore this unless you set profile annotations. Checking your other manifests:
$ git grep -oh 'include.release.openshift.io/.*' manifests | sort | uniq -c
14 include.release.openshift.io/ibm-cloud-managed: "true"
20 include.release.openshift.io/self-managed-high-availability: "true"There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, our manifest is so old it predates all that stuff. Thanks for the quick catch. You saved us some QE time 🥇
Back in 4.1 we installed a Service named 'controller-manager-service'. That was subsequently dropped, but any cluster that has upgraded from 4.1 to present keeps the needless Service arround. Re-create the Service with the delete annotation so that the CVO can properly clean this up.
8aaf96f to
f0499a8
Compare
|
/label qe-approved test pass:
$ cat 01-service.yaml
apiVersion: v1
kind: Service
metadata:
labels:
control-plane: controller-manager
controller-tools.k8s.io: "1.0"
name: controller-manager-service
namespace: openshift-cloud-credential-operator
spec:
ports:
- port: 443
selector:
control-plane: controller-manager
controller-tools.k8s.io: "1.0"
$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0-rc.3 True False 7h34m Cluster version is 4.9.0-rc.3
$ oc get service -n openshift-cloud-credential-operator NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE cco-metrics ClusterIP 172.30.50.225 8443/TCP 7h55m controller-manager-service ClusterIP 172.30.67.51 443/TCP 18m pod-identity-webhook ClusterIP 172.30.37.210 443/TCP 7h47m
oc adm upgrade --to-image registry.build01.ci.openshift.org/ci-ln-tnfrvhb/release:latest --allow-explicit-upgrade --force warning: Using by-tag pull specs is dangerous, and while we still allow it in combination with --force for backward compatibility, it would be much safer to pass a by-digest pull spec instead warning: The requested upgrade image is not one of the available updates. You have used --allow-explicit-upgrade to the update to proceed anyway warning: --force overrides cluster verification of your supplied release image and waives any update precondition failures.
$ oc get service -n openshift-cloud-credential-operator NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE cco-metrics ClusterIP 172.30.50.225 8443/TCP 8h pod-identity-webhook ClusterIP 172.30.37.210 443/TCP 8h |
|
/test e2e-upgrade |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: akhil-rane, joelddiaz The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@joelddiaz: All pull requests linked via external trackers have merged: Bugzilla bug 1977319 has been moved to the MODIFIED state. DetailsIn response to this:
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. |
Bug 1977319: cleanup orphaned Service 'controller-manager-service'
Back in 4.1 we installed a Service named 'controller-manager-service'.
That was subsequently dropped, but any cluster that has upgraded from
4.1 to present keeps the needless Service arround. Re-create the Service
with the delete annotation so that the CVO can properly clean this up.