-
Notifications
You must be signed in to change notification settings - Fork 58
ACM-21694: Static IP form for BMC host discovery flow #3044
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
base: releases/v2.16-cim
Are you sure you want to change the base?
ACM-21694: Static IP form for BMC host discovery flow #3044
Conversation
|
@jgyselov: This pull request references ACM-21694 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.20.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
Skipping CI for Draft Pull Request. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@jgyselov: This pull request references ACM-21694 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.20.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@jgyselov: This pull request references ACM-21694 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@jgyselov: This pull request references ACM-21694 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@jgyselov: This pull request references ACM-21694 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@jgyselov: This pull request references ACM-21694 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
6b28255 to
5ee0e5c
Compare
|
@jgyselov: This pull request references ACM-21694 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@jgyselov: This pull request references ACM-21694 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@jgyselov: This pull request references ACM-21694 which is a valid jira issue. 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 openshift-eng/jira-lifecycle-plugin repository. |
9242c91 to
66643e9
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jgyselov 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 |
|
@jgyselov: This pull request references ACM-21694 which is a valid jira issue. 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 openshift-eng/jira-lifecycle-plugin repository. |
| const addNmState = | ||
| infraEnv.metadata?.labels && infraEnv.metadata?.labels['networkType'] === 'static'; | ||
|
|
||
| const { initValues, validationSchema } = React.useMemo(() => { | ||
| const initValues = getInitValues(bmh, nmState, secret, isEdit, addNmState); | ||
| const validationSchema = getValidationSchema(usedHostnames, initValues.hostname, t); | ||
| return { initValues, validationSchema }; | ||
| }, [bmh, nmState, secret, isEdit, addNmState, usedHostnames, t]); |
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.
we dont have to memoize values & schema
| const addNmState = | |
| infraEnv.metadata?.labels && infraEnv.metadata?.labels['networkType'] === 'static'; | |
| const { initValues, validationSchema } = React.useMemo(() => { | |
| const initValues = getInitValues(bmh, nmState, secret, isEdit, addNmState); | |
| const validationSchema = getValidationSchema(usedHostnames, initValues.hostname, t); | |
| return { initValues, validationSchema }; | |
| }, [bmh, nmState, secret, isEdit, addNmState, usedHostnames, t]); | |
| const addNmState = infraEnv.metadata?.labels?.networkType === 'static'; | |
| const initValues = getInitValues(bmh, nmState, secret, isEdit, addNmState); | |
| const validationSchema = getValidationSchema(usedHostnames, initValues.hostname, t); |
| <GridItem span={5}> | ||
| <Text component={TextVariants.small}>MAC address</Text> | ||
| </GridItem> | ||
| <GridItem span={5}> | ||
| <Text component={TextVariants.small}>NIC</Text> | ||
| </GridItem> |
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.
should we i18n these texts ?
| <PopoverIcon noVerticalAlign bodyContent="The range of IP addresses of the hosts." /> | ||
| } | ||
| label="Machine network" |
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.
i18n
|
PR needs rebase. 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-sigs/prow repository. |
https://issues.redhat.com/browse/ACM-21694
Stolostron/console PR: stolostron/console#5075