-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 1936443: Revert "baremetal: send full ignition to masters" #4722
Bug 1936443: Revert "baremetal: send full ignition to masters" #4722
Conversation
/label platform/baremetal |
This doesn't work for IPI baremetal deployments driven via hive, because there are firewall rules that prevent access to the bootstrap MCS from the pod running the installer. This was implemented in: openshift#4427 But we ran into problems making the same approach work for worker machines ref: openshift#4456 We're now looking at other approaches to resolve the network-config requirements driving that work, so switching back to the pointer config for masters seems reasonable, particularly given this issue discovered for hive deployments. Conflicts: pkg/tfvars/baremetal/baremetal.go This reverts commit 98dc381.
47ea1ee
to
35c5089
Compare
/retitle Bug 1936443: Revert "baremetal: send full ignition to masters" |
@hardys: This pull request references Bugzilla bug 1936443, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (augol@redhat.com), skipping review 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. |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kirankt, stbenjam 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. |
5 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. |
3 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. |
@hardys: The following test 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. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@hardys: All pull requests linked via external trackers have merged: Bugzilla bug 1936443 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. |
/cherry-pick release-4.7 |
@hardys: #4722 failed to apply on top of branch "release-4.7":
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. |
The ACM team would like to test with this when it is available. Is this expected in 4.7.3? It doesn't look like the PR merged correctly ^^^^. Is there a nightly build we can test with now, or is it still to come? |
@blkingrh Its not merged yet. I'm waiting on 4.8 revert to get verified by QA before the 4.7 backport can move along... I'll update you when it shows up in the nightlies... Thanks. |
Just checking in to see if there is an ETA on when this will be available in 4.7? Thanks. |
Tagging so I can get updates as well. |
This 4.8 bug still need to be verified by QA before 4.7 gets any attention. Unfortunately this out of my control, but I'll make sure to bug the QA folks to look into the issue. |
@kirankt any new news on the QA verification? Thanks. |
@kirankt We have a major customer who we believe is going to be looking for this support in the near future. Can you put us in touch with the QA lead so that we can understand whether or not this is in plan and what the timeline is? |
Hi @blkingrh . The QA contact is in the bugzilla link. Let me update it and make it Urgent, especially if there is a customer waiting for it... Edit. BZ link: https://bugzilla.redhat.com/show_bug.cgi?id=1936443 |
The BZ bug was verified by Alexander Chuzhoy: Can we move forward with the 4.7 fix? |
The 4.7 bug is now in verified state and should move forward with the appropriate labels. |
Thank you @kirankt . When do you anticipate that we can pick this up in a 4.7 build? |
Can you let us know if the 4.7 fix is in any build that we can verify? |
@evelinec , @blkingrh Please pose the questions regarding when the patch gets into a release in the appropriate bugzillas. The right people will see and respond to it. On github, as a developer, I can only work on the fix and see it off to completion. I honestly don't know the workings of the release process and github isn't the place to pose questions related to the release. Please comment/reply on the BZ. |
Thank you @kirankt. Just fyi for others, here's the 4.7 BZ, https://bugzilla.redhat.com/show_bug.cgi?id=1940275. I requested some info there. |
This doesn't work for IPI baremetal deployments driven via hive,
because there are firewall rules that prevent access to the
bootstrap MCS from the pod running the installer.
This was implemented in:
#4427
But we ran into problems making the same approach work for
worker machines ref:
#4456
We're now looking at other approaches to resolve the
network-config requirements driving that work, so
switching back to the pointer config for masters seems
reasonable, particularly given this issue discovered for
hive deployments.
Conflicts:
pkg/tfvars/baremetal/baremetal.go
This reverts commit 98dc381.