Skip to content

Conversation

@jhixson74
Copy link
Member

When using a pre-existing network, save CIDR blocks for the virtual network and subnets

https://issues.redhat.com/browse/OCPBUGS-59105

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 28, 2025
@openshift-ci-robot
Copy link
Contributor

@jhixson74: This pull request references Jira Issue OCPBUGS-59105, which is invalid:

  • expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

When using a pre-existing network, save CIDR blocks for the virtual network and subnets

https://issues.redhat.com/browse/OCPBUGS-59105

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 openshift-ci bot requested review from rna-afk and sadasu October 28, 2025 17:43
@jhixson74 jhixson74 force-pushed the main-azure-OCPBUGS-59105 branch from 63e4167 to 451f37a Compare October 28, 2025 17:44
@jhixson74
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 28, 2025
@openshift-ci-robot
Copy link
Contributor

@jhixson74: This pull request references Jira Issue OCPBUGS-59105, which is valid. The bug has been moved to the POST state.

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

Requesting review from QA contact:
/cc @jinyunma

In response to this:

/jira refresh

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 openshift-ci bot requested a review from jinyunma October 28, 2025 17:46
@jhixson74
Copy link
Member Author

/retest-required

@rna-afk
Copy link
Contributor

rna-afk commented Oct 29, 2025

I am doing most of this in #9773 . Any chance we could merge this with that work?

@jinyunma
Copy link
Contributor

pre-merge tested, installation with pre-created vnet (network configuration was same with bug) succeeded.
Also did regression test, no issues were found.

/verified by jima

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 31, 2025
@openshift-ci-robot
Copy link
Contributor

@jinyunma: This PR has been marked as verified by jima.

In response to this:

pre-merge tested, installation with pre-created vnet (network configuration was same with bug) succeeded.
Also did regression test, no issues were found.

/verified by jima

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.

Copy link
Member

@tthvo tthvo left a comment

Choose a reason for hiding this comment

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

I just have a small question above ⬆️ and ci/prow/golint is current not happy 😓 Maybe it prefers make([]slice, len) and a bit other simplification.

There is also a comment from Aditya #10034 (comment) 👀

When using a pre-existing network, save CIDR blocks for the virtual
network and subnets

https://issues.redhat.com/browse/OCPBUGS-59105
@jhixson74 jhixson74 force-pushed the main-azure-OCPBUGS-59105 branch from 451f37a to 2d4fcd7 Compare November 13, 2025 04:36
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Nov 13, 2025
@jhixson74
Copy link
Member Author

I am doing most of this in #9773 . Any chance we could merge this with that work?

I haven't been following your work here very closely. I'll review it tomorrow. It does look quite a bit more involved than what I've done here though.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 13, 2025

@jhixson74: 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-azure-ovn-shared-vpc 2d4fcd7 link false /test e2e-azure-ovn-shared-vpc
ci/prow/e2e-azurestack 2d4fcd7 link false /test e2e-azurestack
ci/prow/okd-scos-e2e-aws-ovn 2d4fcd7 link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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.

Copy link
Member

@tthvo tthvo left a comment

Choose a reason for hiding this comment

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

/lgtm

Code looks good to me!

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 13, 2025
@patrickdillon
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 14, 2025
@jhixson74
Copy link
Member Author

/retest-required

@jinyunma
Copy link
Contributor

Retested with latest change, installation with pre-created vnet (network configuration was same with bug) succeeded, and regression tests also passed, no other issues were detected.

/verified by jima

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 17, 2025
@openshift-ci-robot
Copy link
Contributor

@jinyunma: This PR has been marked as verified by jima.

In response to this:

Retested with latest change, installation with pre-created vnet (network configuration was same with bug) succeeded, and regression tests also passed, no other issues were detected.

/verified by jima

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.

@jhixson74
Copy link
Member Author

/retest-required

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 5b7289b and 2 for PR HEAD 2d4fcd7 in total

@tthvo
Copy link
Member

tthvo commented Nov 17, 2025

/test gofmt golint

@openshift-merge-bot openshift-merge-bot bot merged commit 7c9b71a into openshift:main Nov 18, 2025
18 of 21 checks passed
@openshift-ci-robot
Copy link
Contributor

@jhixson74: Jira Issue Verification Checks: Jira Issue OCPBUGS-59105
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-59105 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

When using a pre-existing network, save CIDR blocks for the virtual network and subnets

https://issues.redhat.com/browse/OCPBUGS-59105

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
Copy link
Contributor

Fix included in accepted release 4.21.0-0.nightly-2025-11-22-193140

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. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants