Skip to content

[release-4.21] OCPBUGS-78580: Allow ProvisioningCIDR for unmanaged network#576

Open
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.21from
openshift-cherrypick-robot:cherry-pick-553-to-release-4.21
Open

[release-4.21] OCPBUGS-78580: Allow ProvisioningCIDR for unmanaged network#576
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.21from
openshift-cherrypick-robot:cherry-pick-553-to-release-4.21

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #553

/assign hroyrh

In c00ff0a, provisioningIPCIDR is used only for
managed network. Due to this, routes are not created for unmanaged network
during deployment, which leads to broken networking. So, we are allowing
provisioningCIDR for both managed and unmanaged networks.

Signed-off-by: Himanshu Roy <hroy@redhat.com>
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug OCPBUGS-69399 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message. request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":[],"errors":{"rankBeforeIssue":"expected Object","rankAfterIssue":"expected Object"}}

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.
/retitle [release-4.21] : Allow ProvisioningCIDR for unmanaged network

Details

In response to this:

This is an automated cherry-pick of #553

/assign hroyrh

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 changed the title [release-4.21] OCPBUGS-69399: Allow ProvisioningCIDR for unmanaged network [release-4.21] : Allow ProvisioningCIDR for unmanaged network Mar 17, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 17, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

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.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d70f7105-f0d1-4ed2-bf95-fb5956c16756

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

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci openshift-ci bot requested review from honza and zaneb March 17, 2026 05:42
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 17, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign dtantsur 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

@hroyrh
Copy link
Copy Markdown
Contributor

hroyrh commented Mar 17, 2026

/jira cherrypick OCPBUGS-78580

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@hroyrh: An error was encountered cloning bug for cherrypick for bug OCPBUGS-78580 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message. request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":[],"errors":{"rankBeforeIssue":"expected Object","rankAfterIssue":"expected Object"}}

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.
/retitle : [release-4.21] : Allow ProvisioningCIDR for unmanaged network

Details

In response to this:

/jira cherrypick OCPBUGS-78580

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 changed the title [release-4.21] : Allow ProvisioningCIDR for unmanaged network : [release-4.21] : Allow ProvisioningCIDR for unmanaged network Mar 17, 2026
@hroyrh
Copy link
Copy Markdown
Contributor

hroyrh commented Mar 17, 2026

/retitle : [release-4.21] OCPBUGS-78580: Allow ProvisioningCIDR for unmanaged network

@openshift-ci openshift-ci bot changed the title : [release-4.21] : Allow ProvisioningCIDR for unmanaged network : [release-4.21] OCPBUGS-78580: Allow ProvisioningCIDR for unmanaged network Mar 17, 2026
@openshift-ci-robot openshift-ci-robot added 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 Mar 17, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-78580, which is invalid:

  • expected the bug to target either version "4.21." or "openshift-4.21.", but it targets "4.22.0" instead
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-69399 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

Details

In response to this:

This is an automated cherry-pick of #553

/assign hroyrh

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.

@hroyrh
Copy link
Copy Markdown
Contributor

hroyrh commented Mar 17, 2026

/retitle [release-4.21] OCPBUGS-78580: Allow ProvisioningCIDR for unmanaged network

@openshift-ci openshift-ci bot changed the title : [release-4.21] OCPBUGS-78580: Allow ProvisioningCIDR for unmanaged network [release-4.21] OCPBUGS-78580: Allow ProvisioningCIDR for unmanaged network Mar 17, 2026
@hroyrh
Copy link
Copy Markdown
Contributor

hroyrh commented Mar 17, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@hroyrh: This pull request references Jira Issue OCPBUGS-78580, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-69399 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

Details

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.

@hroyrh
Copy link
Copy Markdown
Contributor

hroyrh commented Mar 23, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@hroyrh: This pull request references Jira Issue OCPBUGS-78580, which is invalid:

  • expected dependent Jira Issue OCPBUGS-69399 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

Details

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.

@hroyrh
Copy link
Copy Markdown
Contributor

hroyrh commented Mar 23, 2026

/retest-required

@hroyrh
Copy link
Copy Markdown
Contributor

hroyrh commented Mar 27, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@hroyrh: This pull request references Jira Issue OCPBUGS-78580, which is invalid:

  • expected dependent Jira Issue OCPBUGS-69399 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

Details

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.

@hroyrh
Copy link
Copy Markdown
Contributor

hroyrh commented Mar 27, 2026

/retest-required

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 27, 2026

@openshift-cherrypick-robot: all tests passed!

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.

sgoveas added a commit to sgoveas/release that referenced this pull request Mar 30, 2026
@hroyrh
Copy link
Copy Markdown
Contributor

hroyrh commented Mar 30, 2026

/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 Mar 30, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.z) matches configured target version for branch (4.21.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-69399 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-69399 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

Requesting review from QA contact:
/cc @sgoveas

Details

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 sgoveas March 30, 2026 11:38
@sgoveas
Copy link
Copy Markdown

sgoveas commented Mar 30, 2026

/verified by sgoveas link

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 30, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@sgoveas: This PR has been marked as verified by sgoveas [link](https://redhat.atlassian.net/browse/OCPBUGS-78580?focusedCommentId=16575431).

Details

In response to this:

/verified by sgoveas link

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.

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

Labels

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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants