Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1899342

Summary: Ignition config fetch times out too early on OpenStack
Product: OpenShift Container Platform Reporter: Benjamin Gilbert <bgilbert>
Component: RHCOSAssignee: Benjamin Gilbert <bgilbert>
Status: CLOSED ERRATA QA Contact: Michael Nguyen <mnguyen>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.6CC: bbreard, dornelas, imcleod, jlebon, jligon, nstielau
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1899361 (view as bug list) Environment:
Last Closed: 2020-11-19 00:23:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1899361    

Description Benjamin Gilbert 2020-11-18 22:33:50 UTC
Ignition 2.6.0-5.rhaos4.6.git947598e.el8 times out fetching OpenStack userdata after 30 seconds, which may not be enough time for networking to come up.  This has been fixed upstream in Ignition 2.7.0 but the fixes need a backport to 4.6.x.

There are several related fixes; see https://github.com/coreos/ignition/issues/1081#issuecomment-696447611.  I think it'd be cleanest to mirror the behavior of upstream 2.7.0, which requires taking all the patches from:

- https://github.com/coreos/ignition/pull/1094
- https://github.com/coreos/ignition/pull/1095
- https://github.com/coreos/ignition/pull/1098

Comment 1 Benjamin Gilbert 2020-11-18 22:41:26 UTC
For clarity, 4.7 has a newer version of Ignition which is unaffected.

Comment 4 Benjamin Gilbert 2020-11-19 00:23:55 UTC
Repurposing as the 4.7-targeted parent of the 4.6 backport in bug 1899361, and closing because 4.7 does not have the bug.

Comment 6 Jonathan Lebon 2020-11-26 17:12:46 UTC
Automation doesn't like `CLOSED NOTABUG`, so switching to `CLOSED ERRATA` instead. See https://bugzilla.redhat.com/show_bug.cgi?id=1899361#c4.