OSASINFRA-4098: openstack: Remove mecha-az0#73963
OSASINFRA-4098: openstack: Remove mecha-az0#73963openshift-merge-bot[bot] merged 2 commits intoopenshift:masterfrom
Conversation
kuryr is dead. Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
This will free up hardware that we can use in the managed cloud. Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
|
/assign @mandre |
|
@stephenfin: GitHub didn't allow me to assign the following users: eshulman2. Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. 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-sigs/prow repository. |
openshift-ci-robot
added
the
rehearsals-ack
|
[REHEARSALNOTIFIER] |
mandre
left a comment
mandre
left a comment
There was a problem hiding this comment.
This effectively removes the ccpmso-zone job, which should be better downstream anyway, and the remaining kuryr jobs, for which the feature is no longer available since ocp 4.15. And we can repurpose the node to add to our shared pool, big +1 from me.
/approve
There was a problem hiding this comment.
Is it that CNO doesn't have e2e-openstack-kuryr on later versions post 4.14?
Just wondering why the removal stopped at 4.14 and if by doing this we are loosing coverage for something we should be testing
There was a problem hiding this comment.
@tssurya Yeah, it was removed in 4.15. While we lose coverage on 4.12 and 4.14, both of those are in EUS stage now and we would need a very serious issue to justify any changes to kuryr (serious enough to also warrant spinning up internal test capacity)
|
/lgtm |
openshift-ci
bot
added
the
approved
|
@stephenfin: all tests passed! 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-sigs/prow repository. I understand the commands that are listed here. |
All jobs using this cloud were removed in openshift#73963. Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
All jobs using this cloud were removed in openshift#73963. Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
|
/retitle OSASINFRA-4098: openstack: Remove mecha-az0 |
openshift-ci
bot
changed the title
All jobs using this cloud were removed in openshift#73963. Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
All jobs using this cloud were removed in #73963. Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Remove launch-kuryr cluster-bot cluster kuryr is dead. Signed-off-by: Stephen Finucane <stephenfin@redhat.com> * openstack: Remove mecha az0 + associated jobs This will free up hardware that we can use in the managed cloud. Signed-off-by: Stephen Finucane <stephenfin@redhat.com> --------- Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
All jobs using this cloud were removed in openshift#73963. Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
8 participants
This host is underutilized and the jobs are not important enough to justify keeping it separate rather than folding it into the existing managed cloud.