Skip to content

Conversation

@andfasano
Copy link
Contributor

The current patch allows the user to specify the content of the install-config networkConfig field directly as a yaml object. Content validation (for a generic yaml) is now carried on by the install config asset

/label platform/baremetal

@openshift-ci openshift-ci bot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Jan 18, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 18, 2022

@andfasano: This pull request references Bugzilla bug 2037813, 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.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.0) matches configured target release for branch (4.10.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

No GitHub users were found matching the public email listed for the QA contact in Bugzilla ([email protected]), skipping review request.

Details

In response to this:

Bug 2037813: [baremeta] networkConfig field now accepts yaml instead of string value

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.

@andfasano andfasano changed the title Bug 2037813: [baremeta] networkConfig field now accepts yaml instead of string value Bug 2037813: [baremetal] networkConfig field now accepts yaml instead of string value Jan 18, 2022
@openshift-ci openshift-ci bot added the platform/baremetal IPI bare metal hosts platform label Jan 18, 2022
@openshift-ci openshift-ci bot requested review from hardys and rna-afk January 18, 2022 14:33
Copy link
Contributor

@staebler staebler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current patch allows the user to specify the content of the install-config networkConfig field directly as a yaml object.

Hooray for this!

@staebler
Copy link
Contributor

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 18, 2022
@zaneb
Copy link
Member

zaneb commented Jan 18, 2022

Unfortunate that we can't allow a string as well, but it appears to me that would be banned by rule 3 of https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#specifying-a-structural-schema

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 18, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: staebler, zaneb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@staebler
Copy link
Contributor

Unfortunate that we can't allow a string as well, but it appears to me that would be banned by rule 3 of https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#specifying-a-structural-schema

/approve

You could have two separate fields--one that takes yaml and one that takes a string. The installer would fill out the one that is easier to use internally with the value from the other, if set. The installer would need to validate that if both are set that they are equivalent.

@sadasu
Copy link
Contributor

sadasu commented Jan 18, 2022

/lgtm

Nice improvement.

@andfasano
Copy link
Contributor Author

/hold

let's wait for the results of the pending jobs

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 18, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 18, 2022
@andfasano
Copy link
Contributor Author

/test e2e-metal-ipi-ovn-ipv6-required
/test e2e-metal-ipi-virtualmedia

@zaneb
Copy link
Member

zaneb commented Jan 19, 2022

You could have two separate fields--one that takes yaml and one that takes a string. The installer would fill out the one that is easier to use internally with the value from the other, if set. The installer would need to validate that if both are set that they are equivalent.

The main reason to support both would be so that we don't have to worry about users doing it wrong, so I think having two fields is just giving people twice as many ways to mess up :)

@andfasano
Copy link
Contributor Author

/hold cancel
metal-ipi jobs went fine

Agree also on just keeping one field for the sake of simplicity

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 19, 2022
@openshift-bot
Copy link
Contributor

/retest-required

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

6 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

5 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 20, 2022
@andfasano
Copy link
Contributor Author

There was a problem with the controller-gen, since interface{} type wasn't allowed, so I had to switch type.

@andfasano
Copy link
Contributor Author

/test verify-vendor

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess the plus side of this is that you could accept a string here as well. I don't know if we want to, but you could.

The current patch allows the user to specify the content of the install-config networkConfig field directly as a yaml object. Content validation (for a generic yaml) is now carried on by the install config asset
@sadasu
Copy link
Contributor

sadasu commented Jan 21, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 21, 2022
@andfasano
Copy link
Contributor Author

/hold
Checking ipv6 job failure

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 21, 2022
@andfasano
Copy link
Contributor Author

/hold cancel

/test e2e-metal-ipi-ovn-ipv6-required

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 21, 2022
@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 21, 2022

@andfasano: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-metal-ipi-ovn-ipv6 8b3d14d link false /test e2e-metal-ipi-ovn-ipv6
ci/prow/okd-e2e-aws-upgrade 8b3d14d link false /test okd-e2e-aws-upgrade
ci/prow/e2e-metal-ipi-ovn-dualstack 8b3d14d link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-azure-upi 8b3d14d link false /test e2e-azure-upi
ci/prow/e2e-aws-workers-rhel8 8b3d14d link false /test e2e-aws-workers-rhel8
ci/prow/e2e-metal-ipi-virtualmedia 8b3d14d link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-aws-single-node 8b3d14d link false /test e2e-aws-single-node
ci/prow/okd-e2e-aws 8b3d14d link false /test okd-e2e-aws
ci/prow/e2e-aws-workers-rhel7 8b3d14d link false /test e2e-aws-workers-rhel7
ci/prow/e2e-crc 8b3d14d link false /test e2e-crc
ci/prow/e2e-ibmcloud 8b3d14d link false /test e2e-ibmcloud

Full PR test history. Your PR dashboard.

Details

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-merge-robot openshift-merge-robot merged commit 969378d into openshift:master Jan 21, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 21, 2022

@andfasano: All pull requests linked via external trackers have merged:

Bugzilla bug 2037813 has been moved to the MODIFIED state.

Details

In response to this:

Bug 2037813: [baremetal] networkConfig field now accepts yaml instead of string value

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.

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. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. 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.

7 participants