OCPBUGS-73784: Release 4.17 azure byo vnet fix

[jhixson74]

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

https://issues.redhat.com/browse/OCPBUGS-59105
(cherry picked from commit 2d4fcd7) (cherry picked from commit 9d68847) (cherry picked from commit 3231408)

[openshift-ci-robot]

@jhixson74: No Jira issue with key OCPBUGS-74782 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

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
(cherry picked from commit 2d4fcd7) (cherry picked from commit 9d68847) (cherry picked from commit 3231408)

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]

[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 mtulio 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:

• pkg/asset/manifests/azure/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@jhixson74: 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-azurestack	b36edec	link	false	/test e2e-azurestack

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.

[jinyunma]

/retitle OCPBUGS-74784: Release 4.17 azure byo vnet fix

[openshift-ci-robot]

@jhixson74: No Jira issue with key OCPBUGS-74784 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

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
(cherry picked from commit 2d4fcd7) (cherry picked from commit 9d68847) (cherry picked from commit 3231408)

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.

[jinyunma]

/retitle OCPBUGS-73784: Release 4.17 azure byo vnet fix

[openshift-ci-robot]

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

• expected Jira Issue OCPBUGS-73784 to depend on a bug targeting a version in 4.18.0, 4.18.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

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

https://issues.redhat.com/browse/OCPBUGS-59105
(cherry picked from commit 2d4fcd7) (cherry picked from commit 9d68847) (cherry picked from commit 3231408)

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.

[jinyunma]

/payload-job periodic-ci-openshift-openshift-tests-private-release-4.17-multi-nightly-azure-ipi-fullyprivate-proxy-arm-f14

[openshift-ci]

@jinyunma: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-openshift-tests-private-release-4.17-multi-nightly-azure-ipi-fullyprivate-proxy-arm-f14

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/59397370-f1b4-11f0-8ba1-b7024c78aee1-0

[jinyunma]

/payload-job periodic-ci-openshift-openshift-tests-private-release-4.17-multi-nightly-azure-ipi-fullyprivate-proxy-amd-f28-destructive

[openshift-ci]

@jinyunma: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-openshift-tests-private-release-4.17-multi-nightly-azure-ipi-fullyprivate-proxy-amd-f28-destructive

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/00a19450-f1d6-11f0-9042-8838be05ef15-0

[jinyunma]

The job tested installation in existing vnet with customized vnet cidr and subnets which is different than the default values, installation passed and no need to run e2e test for this PR, abort the job.

/payload-abort

[openshift-ci]

@jinyunma: aborted 1 active payload job(s) for pull request #10218

[jinyunma]

pre-merge tested, installation with network configuration in bug description passed, and installation in e2e-azure-ovn-shared-vpc and periodic-ci-openshift-openshift-tests-private-release-4.17-multi-nightly-azure-ipi-fullyprivate-proxy-amd-f28-destructive also passed.

/verified by jima

[openshift-ci-robot]

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

Details

In response to this:

pre-merge tested, installation with network configuration in bug description passed, and installation in e2e-azure-ovn-shared-vpc and periodic-ci-openshift-openshift-tests-private-release-4.17-multi-nightly-azure-ipi-fullyprivate-proxy-amd-f28-destructive also passed.

/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.