-
Notifications
You must be signed in to change notification settings - Fork 238
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
Update Progressing message for non-critical components #510
Update Progressing message for non-critical components #510
Conversation
/retest |
1 similar comment
/retest |
Statuses:
so this is not quite right. It shouldn't go back to "waiting for other operators" after it stops that. |
87508cc
to
5847a61
Compare
5847a61
to
092c87b
Compare
ok, now we get:
which is still a little weird, but it's consistent with our other reporting, which we ought to improve at some point. But (1) it stays at "waiting for other operators" until it starts being deployed, and (2) it doesn't go back to "waiting for other operators" after that. |
/retest |
/assign @dougbtv |
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, dcbw 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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
12 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@danwinship: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
I was backporting #474 and realized that it solves
DaemonSet "openshift-multus/multus-admission-controller" is not available ...
(ie, "your install failed after the worker nodes were created but before multus-admission-controller could be deployed") but notDaemonSet "openshift-multus/multus-admission-controller" is not yet scheduled on any nodes
(ie, "your install failed before the worker nodes were created").(WIP until I see it doing the right thing in a test run)