Skip to content

Conversation

@jgyselov
Copy link
Contributor

@jgyselov jgyselov commented Jul 14, 2025

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 14, 2025

@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:

issues.redhat.com/browse/

TODO:

  • clean up initial values
  • transitions between states (resetting default values, confirm modal)
  • form / yaml
  • ipv4 / dualstack
  • localisation of validation strings
  • disabling fields in readonly (for OCM)

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 14, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 14, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jul 14, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@coderabbitai
Copy link

coderabbitai bot commented Jul 14, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 14, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 14, 2025
@openshift-ci openshift-ci bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Jul 14, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 14, 2025

@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:

https://issues.redhat.com/browse/ACM-21694

TODO:

  • clean up initial values
  • transitions between states (resetting default values, confirm modal)
  • form / yaml
  • ipv4 / dualstack
  • localisation of validation strings
  • disabling fields in readonly (for OCM)

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.

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 14, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 23, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 7, 2025

@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:

https://issues.redhat.com/browse/ACM-21694

TODO:

  • clean up initial values
  • transitions between states (resetting default values, confirm modal)
  • form / yaml
  • ipv4 / dualstack
  • localisation of validation strings
  • disabling fields in readonly (for OCM)

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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 7, 2025

@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:

https://issues.redhat.com/browse/ACM-21694

TODO:

  • clean up initial values
  • transitions between states (resetting default values, confirm modal)
  • form / yaml
  • ipv4 / dualstack
  • localisation of validation strings
  • disabling fields in readonly (for OCM)

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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 7, 2025

@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:

https://issues.redhat.com/browse/ACM-21694

TODO:

  • clean up initial values
  • transitions between states (resetting default values, confirm modal)
  • form / yaml
  • ipv4 / dualstack
  • localisation of validation strings
  • disabling fields in readonly (for OCM)

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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 7, 2025

@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:

https://issues.redhat.com/browse/ACM-21694

TODO:

  • clean up initial values
  • transitions between states (resetting default values, confirm modal)
  • form / yaml
  • ipv4 / dualstack
  • localisation of validation strings
  • disabling fields in readonly (for OCM)

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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 8, 2025

@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:

https://issues.redhat.com/browse/ACM-21694

TODO:

  • clean up initial values
  • transitions between states (resetting default values, confirm modal)
  • form / yaml
  • ipv4 / dualstack
  • localisation of validation strings
  • disabling fields in readonly (for OCM)

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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 8, 2025

@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:

https://issues.redhat.com/browse/ACM-21694

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 jgyselov changed the base branch from master to releases/v2.16-cim October 8, 2025 08:31
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 8, 2025

@jgyselov: This pull request references ACM-21694 which is a valid jira issue.

In response to this:

https://issues.redhat.com/browse/ACM-21694

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 jgyselov marked this pull request as ready for review October 8, 2025 08:31
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 8, 2025
@openshift-ci openshift-ci bot requested review from asmasarw and batzionb October 8, 2025 08:32
@openshift-ci
Copy link

openshift-ci bot commented Oct 8, 2025

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

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 8, 2025
@jgyselov jgyselov added this to the v2.16-cim milestone Oct 8, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 8, 2025

@jgyselov: This pull request references ACM-21694 which is a valid jira issue.

In response to this:

https://issues.redhat.com/browse/ACM-21694

Stolostron/console PR: stolostron/console#5075

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.

Comment on lines +43 to +50
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]);
Copy link
Member

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

Suggested change
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);

Comment on lines +32 to +37
<GridItem span={5}>
<Text component={TextVariants.small}>MAC address</Text>
</GridItem>
<GridItem span={5}>
<Text component={TextVariants.small}>NIC</Text>
</GridItem>
Copy link
Member

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 ?

Comment on lines +49 to +51
<PopoverIcon noVerticalAlign bodyContent="The range of IP addresses of the hosts." />
}
label="Machine network"
Copy link
Member

Choose a reason for hiding this comment

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

i18n

@jgyselov jgyselov added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 10, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 10, 2025
@openshift-merge-robot
Copy link

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.

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants