/etc/machine-id doesn't exist causing logs not to be populated.

[wes hayutin]

OVB jobs are not collecting the logs properly. See the blank logs below.
This does not seem to be an issue outside of ovb afaict atm.

http://logs.openstack.org/periodic/periodic-tripleo-ci-centos-7-ovb-ha-ocata-oooq/3f84978/logs/overcloud-controller-0/var/log/messages.txt.gz

http://logs.openstack.org/periodic/periodic-tripleo-ci-centos-7-ovb-ha-ocata-oooq/767c729/logs/overcloud-controller-2/var/log/messages.txt.gz

http://logs.openstack.org/periodic/periodic-tripleo-ci-centos-7-ovb-ha-ocata-oooq/4615cbf/logs/overcloud-controller-1/var/log/messages.txt.gz

[John Trowbridge (trown)]

Need to find some ocata gate logs and successful master/pike periodic jobs... it is not happening on master gate jobs:

http://logs.openstack.org/22/506922/9/check-tripleo/gate-tripleo-ci-centos-7-ovb-ha-oooq/a15082a/logs/overcloud-controller-0/var/log/messages.txt.gz

[John Trowbridge (trown)]

I think this bug is invalid. It is not that the job is not collecting logs properly. The logs just are not there.

ocata gate job:

http://logs.openstack.org/47/494947/6/check-tripleo/gate-tripleo-ci-centos-7-ovb-ha-oooq/2a4ad63/logs/overcloud-controller-0/var/log/messages.txt.gz

also the journal is also has no entries on one of the jobs above:

http://logs.openstack.org/periodic/periodic-tripleo-ci-centos-7-ovb-ha-ocata-oooq/3f84978/logs/overcloud-controller-0/var/log/journal.txt.gz

There seems to be a bug on ocata periodic, but I dont think it is quickstart related.

[Alfredo Moralejo (amoralej)]

I've reproduced that in a environment when i can access. The problem is that journald is failing to start because file /etc/machine-id doesn't exist. This file is created on boot by /usr/bin/systemd-machine-id-setup (in fact, running it manually, it started properly). I'm still trying to find out the root cause why this is happening using tripleo images (it works fine in undercloud)

[Alfredo Moralejo (amoralej)]

It may be related to https://review.openstack.org/#/c/493685

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/507495

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/507495
Committed: https://git.openstack.org/cgit/openstack/tripleo-puppet-elements/commit/?id=1eeaf432b7be2571ac53330c45d96f68ffae5a5d
Submitter: Jenkins
Branch: stable/ocata

commit 1eeaf432b7be2571ac53330c45d96f68ffae5a5d
Author: Alex Schultz <email address hidden>
Date: Tue Aug 1 08:22:20 2017 -0600

    Set remove-machine-id to executable

    We had previously added an element to remove the machine id from the
    images however the script is not executable so it wasn't actually being
    run as part of the image building process. This change sets
    70-remove-machine-id to be executable so that /etc/machine-id will
    actually be removed from the images during the building process.
    Additionally this changes the element to clear the file rather than
    delete it as if the file is missing, things may not work as expected.

    element remove-machine-id has been added to tripleo-common in stable/ocata
    and we are experiencing strange issues related to missing /etc/machine-id

    Closes-Bug: #1719421

    Change-Id: Id3f8c510801f8fcc1fc03415b0ebd23a2ff9da4c
    (cherry picked from commit ab7ac88006c6c26bbebbe6862792f89d34a65236)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-puppet-elements 6.2.3 release.