Bug 1814667
Summary: | bootstrap.ing modifications not taken into account by OCP 4.3.5 on OSP 13 IPI installer | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Andreas Karis <akaris> |
Component: | Installer | Assignee: | Mike Fedosin <mfedosin> |
Installer sub component: | OpenShift on OpenStack | QA Contact: | David Sanz <dsanzmor> |
Status: | CLOSED DUPLICATE | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | m.andre, pprinett |
Version: | 4.3.z | Keywords: | UpcomingSprint |
Target Milestone: | --- | ||
Target Release: | 4.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-01 22:12:22 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: |
Description
Andreas Karis
2020-03-18 13:42:28 UTC
I also tried manually editing bootstrap.ign ... an even manually editing .openshift_install_state.json. This means that I opened file .openshift_install_state.json with a text editor, and changed the following content (which is part of the bootstrap ignition configuration which was already compiled into the installation instructions): ~~~ { "filesystem": "root", "path": "/etc/motd", "user": { "name": "root" }, "append": true, "contents": { "source": "data:text/plain;charset=utf-8;base64,VGhpcyBpcyB0aGUgYm9vdHN0cmFwIG5vZGU7IGl0IHdpbGwgYmUgZGVzdHJveWVkIHdoZW4gdGhlIG1hc3RlciBpcyBmdWxseSB1cC4KClRoZSBwcmltYXJ5IHNlcnZpY2UgaXMgImJvb3RrdWJlLnNlcnZpY2UiLiBUbyB3YXRjaCBpdHMgc3RhdHVzLCBydW4gZS5nLgoKICBqb3VybmFsY3RsIC1iIC1mIC11IGJvb3RrdWJlLnNlcnZpY2UK", "verification": {} }, "mode": 420 }, ~~~ Replaced it with: ~~~ { "filesystem": "root", "path": "/etc/motd", "user": { "name": "root" }, "append": true, "contents": { "source": "data:,%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%0AMODIFIED%20MOTD%20FILE%20-%20PUSHED%20CHRONY%20CONFIGURATION%0A%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%0A%0AThis%20is%20the%20bootstrap%20node%3B%20it%20will%20be%20destroyed%20when%20the%20master%20is%20fully%20up.%0A%0AThe%20primary%20service%20is%20%22bootkube.service%22.%20To%20watch%20its%20status%2C%20run%20e.g.%0A%0A%20%20journalctl%20-b%20-f%20-u%20bootkube.service%0A", "verification": {} }, "mode": 420 }, { "path": "/etc/chrony.conf", "filesystem": "root", "mode": 272, "contents": { "source": "data:,server%200.europe.pool.ntp.org%20iburst%0Adriftfile%20/var/lib/chrony/drift%0Amakestep%201.0%203%0Artcsync%0Alogdir%20/var/log/chrony%0A" } }, ~~~ After the modification, ran the content of that file through jq, just to be sure: ~~~ $ cat .openshift_install_state.json | jq | less ~~~ The problem is that bootstrap.ign is consume afterwards and that the file is being overwritten Setting severity on "medium" under the assumption that the bug is not a blocker for disconnected-install. If it is, we have to revise Andreas, can you please confirm these two assumptions: 1. the use-case is indeed a disconnected installation 2. this bug is not a blocker for the use-case Thank you! 1. the use-case is indeed a disconnected installation confirmed. but also more generally I'd like to push NFS server information into the bootstrap node so that it's synchronized with the master servers that it creates and connects to 2. this bug is not a blocker for the use-case absolutely not a blocker Thanks! The team considers this bug as valid. Considering this bug priority and our capacity, we are deferring this bug to an upcoming sprint. If there are reasons for us to reprioritise, please let us know. Planning on working this in the current sprint. Considering the priority assigned to this bug and our team capacity, we are deferring this bug to an upcoming sprint. Please let us know if there are reasons for us to reprioritize. Considering the priority assigned to this bug and our team capacity, we are deferring this bug to an upcoming sprint. Please let us know if there are reasons for us to reprioritize. Hello! This bug was fixed in 4.5 with this patch: https://github.com/openshift/installer/pull/3329 It was the fix for another another bug, but the cause is the same - we generated metadata after tfvars. I've tested this issue in ocp 4.5 and couldn't reproduce it. Now all bootstrap.ign modifications are considered before generating tfvars. Therefore I'm going to close this bug as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1812950 *** This bug has been marked as a duplicate of bug 1812950 *** |