Skip to content

AGENT-1429: Add support for SNO IPV4 OVE#1897

Open
pawanpinjarkar wants to merge 1 commit into
openshift-metal3:masterfrom
pawanpinjarkar:ove-sno-ipv4
Open

AGENT-1429: Add support for SNO IPV4 OVE#1897
pawanpinjarkar wants to merge 1 commit into
openshift-metal3:masterfrom
pawanpinjarkar:ove-sno-ipv4

Conversation

@pawanpinjarkar
Copy link
Copy Markdown
Contributor

@pawanpinjarkar pawanpinjarkar commented May 20, 2026

Refactor wait/reload logic and improve SNO (IPV4) networking support

  • Adds required dns entries for SNO to also work with IPV4
  • Skips selecting virtualization bundle for SNO - Do not add api-int dns entries for SNO
  • Add wait() and reload() helper functions with duration logging
  • Increase and use consistent wait times for operators page and virtualization bundle
  • Add explicit IPv4 single-stack networking selection
  • Skip VIP configuration for SNO
  • Add missing wait for next button in verifyStorage step
  • Improve logging clarity throughout workflow

This improves automation reliability and adds proper support for single-node OpenShift deployments.

@openshift-ci openshift-ci Bot requested review from celebdor and rwsu May 20, 2026 16:28
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 20, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign bfournie for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/cc @bfournie @andfasano

@openshift-ci openshift-ci Bot requested review from andfasano and bfournie May 20, 2026 16:28
@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/hold

@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 May 21, 2026
@pawanpinjarkar pawanpinjarkar changed the title NO-ISSUE: SNO IPV4 OVE WIP NO-ISSUE: SNO IPV4 OVE May 21, 2026
@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 May 21, 2026
Refactor wait/reload logic and improve SNO (IPV4) networking support

- Adds required dns entries for SNO to also work with IPV4
- Skips selecting virtualization bundle for SNO - Do not add api-int dns entries for SNO
- Add wait() and reload() helper functions with duration logging
- Increase and use consistent wait times for operators page and virtualization bundle
- Add explicit IPv4 single-stack networking selection
- Skip VIP configuration for SNO
- Add missing wait for next button in verifyStorage step
- Improve logging clarity throughout workflow

This improves automation reliability and adds proper support for single-node OpenShift deployments.
@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/hold cancel

@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 May 21, 2026
@pawanpinjarkar pawanpinjarkar changed the title WIP NO-ISSUE: SNO IPV4 OVE AGENT-1429: Add support for SNO IPV4 OVE May 21, 2026
@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 May 21, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 22, 2026

@pawanpinjarkar: The following test 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-agent-bad-dns edb2481 link false /test e2e-agent-bad-dns

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-sigs/prow repository. I understand the commands that are listed here.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant