openstack undercloud install fails on upgrade during restart of systemd-journald on a file assertion error

Bug #1564471 reported by Marios Andreou
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

When upgrading the undercloud to stable/liberty and running

<setup repos>
sudo yum -y update
openstack undercloud install

^^ This fails and needs to be run a second time to succeed. The issue is originally discussed at https://bugzilla.redhat.com/show_bug.cgi?id=1315442

The undercloud install fails running:

2016-03-07 09:55:38,538 INFO: dib-run-parts Mon Mar 7 09:55:38 EST 2016 Running /tmp/tmp5t46Kc/pre-install.d/01-persistent-journal

which is at https://github.com/openstack/instack-undercloud/blob/master/elements/undercloud-install/pre-install.d/01-persistent-journal

A trace from journalctl looks like:

Mar 31 09:31:07 instack.localdomain systemd-journald[23175]: Failed to create new runtime journal: No such file or directory
Mar 31 09:31:07 instack.localdomain systemd-journald[23175]: Assertion 'f' failed at src/journal/journal-file.c:132, function journal_file_close(). Aborting.
Mar 31 09:31:07 instack.localdomain systemd-journal[23252]: Journal started

seems the assert failure is causing the install to fail. Weirdly, the journal is started fine. As above, running the undercloud install a second time succeeds. I am contemplating adding set +e for the restart waiting a second and checking that the journal is running fine.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to instack-undercloud (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/300051

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to instack-undercloud (master)

Reviewed: https://review.openstack.org/300051
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=cc41b7a1f9009a1dd24193b3a7e98a13496cbcc0
Submitter: Jenkins
Branch: master

commit cc41b7a1f9009a1dd24193b3a7e98a13496cbcc0
Author: marios <email address hidden>
Date: Thu Mar 31 18:55:56 2016 +0300

    Temporarily set +e on systemd-journald restart for +bug/1564471

    Though the restart of the systemd-journald service succeeds fine, an
    assertion error during the restart of the systemd-journald service
    causes the instack-undercloud install to fail (this is during an
    undercloud upgrade in fact, details in the bug).

    This review sets +e to allow the script to continue and then also
    checks that the service was indeed started OK, exiting otherwise.

    Related-Bug: 1564471
    Change-Id: I38c14a6b143b51dec6f6f88f2e1cb591e07a08b3

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to instack-undercloud (stable/liberty)

Related fix proposed to branch: stable/liberty
Review: https://review.openstack.org/300360

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to instack-undercloud (stable/mitaka)

Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/300363

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to instack-undercloud (stable/mitaka)

Reviewed: https://review.openstack.org/300363
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=a508ad7218cbc2064fc9f1316ab5afca85b25eda
Submitter: Jenkins
Branch: stable/mitaka

commit a508ad7218cbc2064fc9f1316ab5afca85b25eda
Author: marios <email address hidden>
Date: Thu Mar 31 18:55:56 2016 +0300

    Temporarily set +e on systemd-journald restart for +bug/1564471

    Though the restart of the systemd-journald service succeeds fine, an
    assertion error during the restart of the systemd-journald service
    causes the instack-undercloud install to fail (this is during an
    undercloud upgrade in fact, details in the bug).

    This review sets +e to allow the script to continue and then also
    checks that the service was indeed started OK, exiting otherwise.

    Related-Bug: 1564471
    Change-Id: I38c14a6b143b51dec6f6f88f2e1cb591e07a08b3
    (cherry picked from commit cc41b7a1f9009a1dd24193b3a7e98a13496cbcc0)

tags: added: in-stable-mitaka
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to instack-undercloud (stable/liberty)

Reviewed: https://review.openstack.org/300360
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=9f6e87809a892c4aae4f936ec46d2bbf828dfc8c
Submitter: Jenkins
Branch: stable/liberty

commit 9f6e87809a892c4aae4f936ec46d2bbf828dfc8c
Author: marios <email address hidden>
Date: Thu Mar 31 18:55:56 2016 +0300

    Temporarily set +e on systemd-journald restart for +bug/1564471

    Though the restart of the systemd-journald service succeeds fine, an
    assertion error during the restart of the systemd-journald service
    causes the instack-undercloud install to fail (this is during an
    undercloud upgrade in fact, details in the bug).

    This review sets +e to allow the script to continue and then also
    checks that the service was indeed started OK, exiting otherwise.

    Related-Bug: 1564471
    Change-Id: I38c14a6b143b51dec6f6f88f2e1cb591e07a08b3
    (cherry picked from commit cc41b7a1f9009a1dd24193b3a7e98a13496cbcc0)

tags: added: in-stable-liberty
Revision history for this message
Emilien Macchi (emilienm) wrote :

This bug is > 365 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in tripleo:
assignee: Marios Andreou (marios-b) → nobody
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for tripleo because there has been no activity for 60 days.]

Changed in tripleo:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.