Bug 2096376: [openstack] Remove limitation on single node deployments #5997
Conversation
openshift-ci
bot
added
bugzilla/severity-low
|
@stephenfin: This pull request references Bugzilla bug 2096376, which is invalid:
Comment In 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. |
|
/bugzilla refresh |
openshift-ci
bot
added
bugzilla/valid-bug
|
@stephenfin: This pull request references Bugzilla bug 2096376, 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: In 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 |
There was a problem hiding this comment.
/hold
Let's make the UPI job work and exercise this change before merging.
We should at least have:
- openstack: Add a UPI workflow release#29672
- and a change that enables the new workflow on the installer repo for UPI-related changes.
openshift-ci
bot
added
do-not-merge/hold
|
@stephenfin: PR needs rebase. 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. |
|
@mandre it appears that we can remove the hold? |
|
/retitle Bug 2096376: [openstack] Remove limitation on single node deployments |
openshift-ci
bot
changed the title
|
/hold cancel |
openshift-ci
bot
removed
the
do-not-merge/hold
There should no longer be any issues running router pods on control plane nodes (i.e. kubernetes/kubernetes#65618 which was resolved in kubernetes/enhancements#1144). Remove this limitation from the docs. Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
openshift-merge-robot
removed
the
needs-rebase
|
New changes are detected. LGTM label has been removed. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test e2e-openstack-upi |
|
Not sure why, but we're missing the must-gather for the UPI job, making it difficult to debug. Let's try one more time. |
|
We should now be gathering the logs thanks to openshift/release#32676. |
|
From the logs, it looks like a timeout. From the authentication cluster operator, one of the pods was not ready: /test e2e-openstack-upi |
|
A timeout again. But this time it went further, and only /test e2e-openstack-upi |
|
This time, authentication co is available, but console co is not. We should understand if the long time it takes for the cluster to converge to a healthy state is caused by the patch or not before merging. |
|
/retest-required |
|
/test e2e-openstack-upi |
|
@stephenfin: The following tests failed, say
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. |
|
/hold |
openshift-ci
bot
added
the
do-not-merge/hold
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
the
lifecycle/stale
|
@stephenfin is this still a thing? |
|
Probably not. I've lost the context here. |
|
@stephenfin: This pull request references Bugzilla bug 2096376. The bug has been updated to no longer refer to the pull request using the external bug tracker. In 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. |
There should no longer be any issues running router pods on control plane nodes (i.e. kubernetes/kubernetes#65618 which was resolved in kubernetes/enhancements#1144). Remove this limitation from the docs.