Loading...

XML

Word

Printable

Severity:
Moderate
Regression:
No
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
*Cause*: What actions or circumstances cause this bug to present.
*Consequence*: What happens when the bug presents.
*Fix*: What was done to fix the bug.
*Result*: Bug doesn’t present anymore.

Show
*Cause*: What actions or circumstances cause this bug to present. *Consequence*: What happens when the bug presents. *Fix*: What was done to fix the bug. *Result*: Bug doesn’t present anymore.
Release Note Type:
Bug Fix
Release Note Status:
In Progress
Target Version:

4.16.z
Target Backport Versions:

4.16.0

This is a clone of issue ~~OCPBUGS-34978~~. The following is the description of the original issue:
—
Description of problem:

    When deploying a private cluster, if the VPC isn't a permitted network the installer will not add it as one

Version-Release number of selected component (if applicable):

How reproducible:

    Easily

Steps to Reproduce:

    1. Deploy a private cluster with CAPI in a VPC where the desired DNS zone is not permitted
    2. Fail
    3.

Actual results:

    Cluster cannot reach endpoints and deployment fails

Expected results:

    Network should be permitted and deployment should succeed

Additional info:

clones

OCPBUGS-34978 Power VS: VPC network is not permitted for private DNS

is blocked by

OCPBUGS-34978 Power VS: VPC network is not permitted for private DNS

relates to

OCPBUGS-36316 [Power VS] Private DNS zone cannot be used if no permitted network is added