-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Baremetal: Re-arrange validations for provisioning network at cluster creation time #3851
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
Baremetal: Re-arrange validations for provisioning network at cluster creation time #3851
Conversation
|
/cc @dhellmann, @yevgeny-shnaidman, @romfreiman |
stbenjam
left a comment
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.
Can you link the enhancement in the commit message/PR description? openshift/enhancements#388
Other than that just one question and a nit. Also I'm curious what @andfasano thinks since he did a lot of work on the validations code.
|
/label platform/baremetal |
|
@abhinavdahiya: we'll need an installer team approval on this one. This is an implementation of openshift/enhancements#388. |
|
/approve |
|
/hold Just holding for now so it doesn't merge until we get the right stakeholders to look. |
andfasano
left a comment
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.
From a general point of view, I think that if we had a validation system completely tag based then it would have been simpler to partition the applied rules by scope (through a custom validation rule and context). In this way the flow is a little bit more complex to follow
|
/test e2e-ovirt |
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, yevgeny-shnaidman 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 |
|
/hold cancel |
|
I did some testing on this -- it works great! All of the provisioning checks are deferred until I just wanted to get clarification on the BMC's. I apologize if we already discussed this, my brain is a bit foggy at the end of the sprint. However, I think we expected assisted-installer folks to provide hosts without BMC creds, right? Looks like those validations are still running during |
That's right, the assisted installer will create hosts without any BMC details. I think that means just their name and MAC address will be set. |
My mistake. I didn/t look closely inside the BMC struct. Will fix this in the next commit. |
|
/hold |
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
25 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. |
|
/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. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@kirankt: 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. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
This PR re-arranges all provisioning network validations until the
createtarget. This enables end users to run other targets such asignition-configs,manifestswithout specifying any config related to the provisioning network.This is an implementation of openshift/enhancements#388.
Co-Authored-By: @andfasano