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 1804284: Revert "RHCOS: bump to 44.81.202002071430-0" #3117
Bug 1804284: Revert "RHCOS: bump to 44.81.202002071430-0" #3117
Conversation
This reverts commit 5654e02.
Thanks @miabbott - I've reproduced the issue and am attempting to get some clues as to what's going wrong - it seems the external network doesn't come up on the masters, so they get stuck trying to download the ignition config from the bootstrap VM - reverting to the previous image does solve that problem |
I tested a modified image, and can confirm that just reverting the ignition_network_kcmdline to ip=dhcp does fix the problem on ipv4 - obviously we then still have issues with ipv6 (not yet tested the latest image in an ipv6 setup yet) |
/test e2e-metal |
Makes sense to roll back for the moment ... but I'm a little confused as I would think this would have happened as well for "ipv4 only" based on the dracut documentation. |
/test e2e-aws |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sdodson 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 |
and
|
Seems to work 👍 |
Critical platforms have all passed, gcp, metal, aws. Azure is an e2e flake. |
@sdodson: No Bugzilla bug is referenced in the title of this pull request. 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. |
/refresh |
/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. |
|
|
@sdodson The original one or the large amount of CI issues? 😄 The former has a bug and we'll update the PR to denote it. Updated 👍 |
|
/bugzilla refresh |
@sdodson: No Bugzilla bug is referenced in the title of this pull request. 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. |
/test e2e-ovirt |
@miabbott: This pull request references Bugzilla bug 1803926, 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. 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. |
@miabbott: This pull request references Bugzilla bug 1803926, which is valid. 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. |
Eh sorry @sdodson, forgot the space. |
/retest Please review the full test history for this PR and help us cut down flakes. |
Err...I don't think we want to link this PR to that BZ. Merging this PR doesn't fix the root cause of that BZ, which we want to get to. I'm going to create a separate BZ to indicate we need to unblock CI and appease the BZ gods. |
/retitle Bug 1804284: Revert "RHCOS: bump to 44.81.202002071430-0" |
@miabbott: This pull request references Bugzilla bug 1804284, 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. 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. |
@miabbott: All pull requests linked via external trackers have merged. Bugzilla bug 1804284 has been moved to the MODIFIED state. 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. |
@miabbott: The following tests 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. |
This reverts commit 5654e02.
Seeing reports via Slack that networking is not coming up properly on masters. This is preventing bare metal installs from completing successfully.
See: https://bugzilla.redhat.com/show_bug.cgi?id=1803926
NOTE: This is not a fix for the issue but a return to a previously working state for ipv4 usage on bare metal.