Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Normal
Fix Version/s: 4.12.z
Affects Version/s: 4.12.0
Component/s: Cloud Compute / Other Provider
Labels:
None

Severity:
Important
Release Blocker:
Approved
Blocked:
False
Blocked Reason:

Hide

Regression introduced from 4.11 to 4.12

Show
Regression introduced from 4.11 to 4.12
Release Note Text:

Hide
* Previously, error messages for Azure clusters did not explain that it is not possible to create new machines with public IP addresses for a disconnected install that uses only the internal publish strategy. With this release, the error message is updated for improved clarity.
(link:https://issues.redhat.com/browse/OCPBUGS-519[*~~OCPBUGS-519~~*])

Show
* Previously, error messages for Azure clusters did not explain that it is not possible to create new machines with public IP addresses for a disconnected install that uses only the internal publish strategy. With this release, the error message is updated for improved clarity. (link: https://issues.redhat.com/browse/OCPBUGS-519 [* OCPBUGS-519 *])
Release Note Type:
Bug Fix
Release Note Status:
Done
Target Version:

4.12.0

SFDC Cases Counter:
SFDC Cases Links:

Description

For the disconnected installation , we should not be able to provision machines successfully with publicIP:true , this has been the behavior earlier till -
4.11 and around 17th Aug nightly released 4.12 , but it has started allowing creation of machines with publicIP:true set in machineset

Issue reproduced on - Cluster version - 4.12.0-0.nightly-2022-08-23-223922

It is always reproducible .

Steps :
Create machineset using yaml with
{"spec":{"providerSpec":{"value":{"publicIP": true}}}}

Machineset created successfully and machine provisioned successfully .

This seems to be regression bug refer - https://bugzilla.redhat.com/show_bug.cgi?id=1889620

Here is the must gather log - https://drive.google.com/file/d/1UXjiqAx7obISTxkmBsSBuo44ciz9HD1F/view?usp=sharing

Here is the test successfully ran for 4.11 , for exactly same profile and machine creation failed with InvalidConfiguration Error- https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/Runner/575822/console

We can confirm disconnected cluster using below there would be lot of mirrors used in those -

oc get ImageContentSourcePolicy image-policy-aosqe -o yaml 

apiVersion: operator.openshift.io/v1alpha1
kind: ImageContentSourcePolicy
metadata:
  creationTimestamp: "2022-08-24T09:08:47Z"
  generation: 1
  name: image-policy-aosqe
  resourceVersion: "34648"
  uid: 20e45d6d-e081-435d-b6bb-16c4ca21c9d6
spec:
  repositoryDigestMirrors:
  - mirrors:
    - miyadav-2408a.mirror-registry.qe.azure.devcluster.openshift.com:6001/olmqe
    source: quay.io/olmqe
  - mirrors:
    - miyadav-2408a.mirror-registry.qe.azure.devcluster.openshift.com:6001/openshifttest
    source: quay.io/openshifttest
  - mirrors:
    - miyadav-2408a.mirror-registry.qe.azure.devcluster.openshift.com:6001/openshift-qe-optional-operators
    source: quay.io/openshift-qe-optional-operators
  - mirrors:
    - miyadav-2408a.mirror-registry.qe.azure.devcluster.openshift.com:6002
    source: registry.redhat.io
  - mirrors:
    - miyadav-2408a.mirror-registry.qe.azure.devcluster.openshift.com:6002
    source: registry.stage.redhat.io
  - mirrors:
    - miyadav-2408a.mirror-registry.qe.azure.devcluster.openshift.com:6002
    source: brew.registry.redhat.io

Attachments

Issue Links

is cloned by

OCPBUGS-1500 publicIP is allowed in Azure disconnected installation for machines

Closed

links to

openshift/machine-api-operator#1068: OCPBUGS-519: update error message for disconnected installation validation

Activity

People

Assignee:: Mikhail Fedosin (Inactive)

Reporter:: Milind Yadav

QA Contact:: Milind Yadav

Doc Contact:: Jeana Routh

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2022/08/24 11:53 AM

Updated:: 2024/02/15 3:32 PM

Resolved:: 2023/01/17 7:40 PM