Bug 1806822 - InfraID in metadata.json and .openshift_install_state.json is not consistent when repeating `create` commands
Summary: InfraID in metadata.json and .openshift_install_state.json is not consistent ...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.z
Assignee: aos-install
QA Contact: Yang Yang
URL:
Whiteboard:
Depends On: 1777224
Blocks: 1777803
TreeView+ depends on / blocked
 
Reported: 2020-02-25 05:27 UTC by Johnny Liu
Modified: 2020-08-25 02:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1777224
Environment:
Last Closed: 2020-08-25 02:26:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Scott Dodson 2020-02-26 20:25:03 UTC 
We do not consider this a blocker and until we have a master branch fix we don't know how far it's reasonable to backport the fixes. Without a 4.4.z target release available I'm marking this closed deferred.
Comment 2 Johnny Liu 2020-02-27 02:23:13 UTC 
The reason why I cloned this bug is because QE think this bug is very important for our testing. This issue make QE's have no automated way to clean up gcp resource, because resource created for cluster is using two different infra ID. This bring a big problem for our testing.

Pls re-consider to fix this in 4.4, actually QE wanted a fix when we was running 4.3 testing, but now it is deferred again, we really need this fix.
Comment 4 Abhinav Dahiya 2020-07-10 16:38:37 UTC 
Still blocked on the fix landing in master to backport. see bug https://bugzilla.redhat.com/show_bug.cgi?id=1777224
Comment 5 Scott Dodson 2020-08-25 02:26:32 UTC 
I'm not saying we won't fix this in 4.4, but without a committed fix in master it's premature to have this clone sitting. We can decide how far back we fix it once we have the fix in hand.
Note You need to log in before you can comment on or make changes to this bug.