Skip to content

Conversation

@kirankt
Copy link
Contributor

@kirankt kirankt commented Jul 7, 2020

This PR re-arranges all provisioning network validations until the create target. This enables end users to run other targets such as ignition-configs, manifests without specifying any config related to the provisioning network.

This is an implementation of openshift/enhancements#388.

Co-Authored-By: @andfasano

@kirankt
Copy link
Contributor Author

kirankt commented Jul 7, 2020

/cc @dhellmann, @yevgeny-shnaidman, @romfreiman
/assign @stbenjam

Copy link
Member

@stbenjam stbenjam left a 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.

@stbenjam
Copy link
Member

stbenjam commented Jul 7, 2020

/label platform/baremetal

@openshift-ci-robot openshift-ci-robot added the platform/baremetal IPI bare metal hosts platform label Jul 7, 2020
@stbenjam
Copy link
Member

stbenjam commented Jul 7, 2020

@abhinavdahiya: we'll need an installer team approval on this one. This is an implementation of openshift/enhancements#388.

@abhinavdahiya
Copy link
Contributor

/approve

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 7, 2020
@stbenjam
Copy link
Member

stbenjam commented Jul 7, 2020

/hold

Just holding for now so it doesn't merge until we get the right stakeholders to look.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 7, 2020
Copy link
Contributor

@andfasano andfasano left a 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

@kirankt
Copy link
Contributor Author

kirankt commented Jul 8, 2020

/test e2e-ovirt
/test e2e-openstack
/test e2e-aws-scaleup-rhel7
/test e2e-metal-ipi

@kirankt
Copy link
Contributor Author

kirankt commented Jul 8, 2020

/retest

@openshift-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@stbenjam
Copy link
Member

stbenjam commented Jul 9, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 9, 2020
@stbenjam
Copy link
Member

stbenjam commented Jul 9, 2020

I did some testing on this -- it works great! All of the provisioning checks are deferred until create cluster -- except one.

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 create ignition-configs:

FATAL failed to fetch Kubeconfig Admin Client: failed to load asset "Install Config": invalid "install-config.yaml" file: [platform.baremetal.hosts[0].BMC.Username: Required value: missing Username, platform.baremetal.hosts[0].BMC.Password: Required value: missing Password, platform.baremetal.hosts[0].BMC.Address: Required value: missing Address, platform.baremetal.hosts[1].BMC.Username: Required value: missing Username, platform.baremetal.hosts[1].BMC.Password: Required value: missing Password, platform.baremetal.hosts[1].BMC.Address: Required value: missing Address, platform.baremetal.hosts[2].BMC.Username: Required value: missing Username, platform.baremetal.hosts[2].BMC.Password: Required value: missing Password, platform.baremetal.hosts[2].BMC.Address: Required value: missing Address] 

@dhellmann
Copy link
Contributor

I did some testing on this -- it works great! All of the provisioning checks are deferred until create cluster -- except one.

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 create ignition-configs:

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.

@kirankt
Copy link
Contributor Author

kirankt commented Jul 9, 2020

I did some testing on this -- it works great! All of the provisioning checks are deferred until create cluster -- except one.
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 create ignition-configs:

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.

@kirankt kirankt changed the title Baremetal: Re-arrange validations for provisioning network at cluster creationg time Baremetal: Re-arrange validations for provisioning network at cluster creation time Jul 9, 2020
@kirankt
Copy link
Contributor Author

kirankt commented Jul 9, 2020

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 9, 2020
@kirankt
Copy link
Contributor Author

kirankt commented Jul 10, 2020

/retest

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

25 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 11, 2020

@kirankt: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-openstack 80152b4 link /test e2e-openstack
ci/prow/e2e-ovirt 80152b4 link /test e2e-ovirt

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.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. platform/baremetal IPI bare metal hosts platform

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants