-
Notifications
You must be signed in to change notification settings - Fork 95
Bug 1975539: delete hello-openshift in payload imagestream via CVO annotation #380
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 1975539: delete hello-openshift in payload imagestream via CVO annotation #380
Conversation
|
@gabemontero: This pull request references Bugzilla bug 1975539, 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. |
|
@gabemontero: An error was encountered querying GitHub for users with public email (xiuwang@redhat.com) for bug 1975539 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
non-200 OK status code: 403 Forbidden body: "{\n \"documentation_url\": \"https://docs.github.com/en/free-pro-team@latest/rest/overview/resources-in-the-rest-api#abuse-rate-limits\",\n \"message\": \"You have triggered an abuse detection mechanism. Please wait a few minutes before you try again.\"\n}\n"
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
|
upgrade failure https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-samples-operator/380/pull-ci-openshift-cluster-samples-operator-master-e2e-aws-upgrade/1408065065768194048 appears unrelated to this change ... failed due to a required secret problem |
|
ok nothing yet related to this change with some passing e2e's as well /retest |
|
/bugzilla refresh |
|
@xiuwang: This pull request references Bugzilla bug 1975539, 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gabemontero, jottofar 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 Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
thanks @jottofar |
|
other operators besides samples are what are failing the upgrade jobs |
|
/hold @jottofar - a question: I pulled up the must-gather from one of the e2e runs and I see the That is not the desired result - I was expecting to not see that, with the imagestream getting removed because of the new annotation. Can you explain? Here was the must gather I pulled: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-samples-operator/380/pull-ci-openshift-cluster-samples-operator-master-e2e-aws-operator/1408065065743028224/artifacts/e2e-aws-operator/gather-must-gather/artifacts/must-gather.tar the imagesream: |
The deletes only happen during an upgrade. So you would need to be upgrading to a build that includes this PR. I can't remember if the |
I see .... well, then I think we'll have to abandon this approach then, since we don't want to re-introduce that imagestream just so we can delete it on upgrade. I'll have to instead add some special case logic to clean up the hello-openshift imagestream to satisfy the report you generated. I will add a comment in the imagestream manifest that if anything is to be deleted in the future, we go with this annotation ... though there is still the use case of a fresh install at a given level vs. an upgrade. Interesting conundrum there. |
No, you're good. CVO will see the Delete annotation and does not create/reconcile the manifest contents so it will not be created on install. |
|
@jottofar and I have been chatting in slack and we have in fact found a CVO bug wrt imagestreams and the delete stuff he'll be addressing that ... once that is in, I'll retest, make sure the hello world imagestream is in fact NOT created and will then unhold |
|
/skip |
|
/retest |
1 similar comment
|
/retest |
|
/test e2e-aws-operator in case the e2e-aws-upgrade fails in such a way that I cannot check the openshift imagestreams to confirm hello-openshift is not present thanks @jottofar |
|
@gabemontero: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
ok hello-openshift was NOT installed in the https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-samples-operator/380/pull-ci-openshift-cluster-samples-operator-master-e2e-aws-operator/1409856204607328256 run /hold cancel /retest |
|
@gabemontero: All pull requests linked via external trackers have merged: Bugzilla bug 1975539 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. |
|
/cherrypick release-4.7 |
|
@gabemontero: #380 failed to apply on top of branch "release-4.7": 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. |
ART hasn't been building these images since 4.8's a6286e7 (rm hello-openshift, 2021-03-29), with the router/ingress folks pivoting away in openshift/cluster-ingress-operator@8332af2f56 (NE 484: Use ingress-operator subcommand instead of hello-openshift for canary server, 2021-03-18, openshift/cluster-ingress-operator#561). Samples had been installing a hello-openshift ImageStream, but they also got away from that in 2021 with openshift/cluster-samples-operator@d94ad97e49 (delete hello-openshift in payload imagestream via CVO annotation, 2021-06-24, openshift/cluster-samples-operator#380). Origin hasn't entirely gotten out of the hello-openshift business yet [1], but regardless of whether they still have an interest, neither ART nor ingress is involved anymore, and it's been a long time since 4.7 went end-of-life: $ curl -s 'https://access.redhat.com/product-life-cycles/api/v1/products?name=Openshift+Container+Platform+4' | jq -r '.data[].versions[] | select(.name == "4.7").phases[] | .date + " " + .name' 2021-02-24T00:00:00.000Z General availability 2021-10-27T00:00:00.000Z Full support 2022-08-24T00:00:00.000Z Maintenance support N/A Extended update support N/A Extended update support Term 2 N/A Extended life phase So I'm dropping those lines from the mapping. [1]: https://github.com/openshift/origin/tree/94a4d2a6f202f64f89a1b747b44484c358f8299d/examples/hello-openshift
/assign @jottofar
@jottofar please lgtm if I have interpreted https://github.com/openshift/cluster-version-operator/blob/master/docs/dev/object-deletion.md and this bz correctly
I'm guessing I don't need to update
image-referencesas well since this change is intended for deletion, but we'll see how the cluster install goes. If there are complaints from the CVO around samples operator then that is the most likely explanation.@dperaza4dustbit FYI ... these "in payload" imagestreams IIRC are also discussed in the skill xfer videos.