Bug 1481443
Summary: | All nodes are sharing the same machine-id | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Alex Schultz <aschultz> |
Component: | openstack-tripleo-puppet-elements | Assignee: | RHOS Maint <rhos-maint> |
Status: | CLOSED ERRATA | QA Contact: | Gurenko Alex <agurenko> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 11.0 (Ocata) | CC: | achernet, agurenko, alan_bishop, arkady_kanevsky, aschultz, bnemec, cdevine, christopher_dearborn, dcain, derekh, evelu, gmeno, hbrock, jcoufal, jfenal, jjoyce, John_walsh, jschluet, jslagle, juwu, kurt_hey, lkocman, mburns, morazi, nbarcet, nthomas, randy_perryman, rghatvis, rhel-osp-director-maint, sclewis, smerrow, sreichar, tvignaud |
Target Milestone: | z5 | Keywords: | TestOnly, Triaged, ZStream |
Target Release: | 11.0 (Ocata) | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-puppet-elements-6.2.4-1.el7ost openstack-tripleo-common-6.1.4-1.el7ost | Doc Type: | Bug Fix |
Doc Text: |
The overcloud images provided and built using diskimage-builder included a static /etc/machine-id which was not automatically generated when nodes were booted. The /etc/machine-id was identical on all overcloud nodes and caused issues with other software. With this update, the /etc/machine-id is now cleared when images are built, and the provided overcloud-full image has an empty /etc/machine-id. The /etc/machine-id is now generated on initial boot when new nodes are added to the deployment or when new deployments are created.
Known Issue: Existing nodes that were deployed with the previous images may have the same /etc/machine-id and will not be updated. To give the node a unique /etc/machine-id, truncate the /etc/machine-id and reboot to have systemd generate a new one. Do not remove /etc/machine-id as systemd will only generate an ID if the file exists. The correct way to reset it is to have an empty /etc/machine-id and then reboot.
|
Story Points: | --- |
Clone Of: | 1270860 | Environment: | |
Last Closed: | 2018-05-18 17:08:29 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: | 1270860 | ||
Bug Blocks: | 1401639, 1476612, 1551603, 1555474, 1557046 |
Comment 1
Lon Hohberger
2018-03-07 13:51:39 UTC
According to our records, this should be resolved by openstack-tripleo-common-6.1.4-1.el7ost. This build is available now. Verified on puddle 2018-05-03.2 [stack@undercloud-0 ~]$ rpm -q openstack-tripleo-puppet-elements openstack-tripleo-puppet-elements-6.2.5-1.el7ost.noarch [stack@undercloud-0 ~]$ ansible overcloud -i /usr/bin/tripleo-ansible-inventory -a "cat /etc/machine-id" 192.168.24.15 | SUCCESS | rc=0 >> ed89bd36a18f49579a40587687324b2d 192.168.24.9 | SUCCESS | rc=0 >> 15701be78288461aa8b0726d9ab4df65 192.168.24.19 | SUCCESS | rc=0 >> 79febc6a6d694901928239e009682c1e 192.168.24.18 | SUCCESS | rc=0 >> 7ec440898ca74080be5f07ed43bcb513 192.168.24.16 | SUCCESS | rc=0 >> 9c3f612f7d504c45a339e23f9ae82cd2 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1622 |