CI: scenario002 job fails with "Error: Systemd start for systemd-resolved failed!"

Bug #1704160 reported by Sagi (Sergey) Shnaidman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Emilien Macchi

Bug Description

Scenario002 periodic jobs fails.

http://logs.openstack.org/39/481939/6/gate/gate-tripleo-ci-centos-7-scenario002-multinode-oooq-puppet/ee5228c/logs/undercloud/home/jenkins/failed_deployment_list.log.txt.gz

Error: Systemd start for systemd-resolved failed!
    journalctl log for systemd-resolved:
    -- No entries --
    Error: /Stage[main]/Systemd/Service[systemd-resolved]/ensure: change from stopped to running failed: Systemd start for systemd-resolved failed!
    journalctl log for systemd-resolved:
    -- No entries --
    Warning: /Stage[main]/Systemd/File[/etc/resolv.conf]: Skipping because of failed dependencies
    Error: Systemd start for systemd-networkd failed!
    journalctl log for systemd-networkd:
    -- No entries --
    Error: /Stage[main]/Systemd/Service[systemd-networkd]/ensure: change from stopped to running failed: Systemd start for systemd-networkd failed!
    journalctl log for systemd-networkd:
    -- No entries --

tags: added: promotion-blocker
Changed in tripleo:
milestone: none → pike-3
Revision history for this message
Emilien Macchi (emilienm) wrote :

Sounds like we got a new image in nodepool which contains new system packages: https://www.diffchecker.com/nLxGMUa1

Revision history for this message
Emilien Macchi (emilienm) wrote :
Revision history for this message
Emilien Macchi (emilienm) wrote :
Changed in tripleo:
assignee: nobody → Emilien Macchi (emilienm)
Revision history for this message
Emilien Macchi (emilienm) wrote :

so both commits in puppet-systemd enabled systemd-resolved and systemd-networkd by default, which means if you don't have the service deployed, Puppet will fail to run the services (obvious).

Revision history for this message
Alan Pevec (apevec) wrote :

@Emilien do we want to pin puppet-systemd in rdoinfo as a workaround in the meantime?

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to tripleo-heat-templates (master)

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

Changed in tripleo:
status: Triaged → Fix Released
tags: removed: alert
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to tripleo-heat-templates (master)

Reviewed: https://review.openstack.org/483946
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=0443e7a836d11f99639213e2f99538d47530f9b6
Submitter: Jenkins
Branch: master

commit 0443e7a836d11f99639213e2f99538d47530f9b6
Author: Emilien Macchi <email address hidden>
Date: Fri Jul 14 14:04:23 2017 +0000

    Revert "Disable systemd-networkd & systemd-resolved"

    https://github.com/camptocamp/puppet-systemd/pull/32 is disabling by default the services so we don't have to control them via TripleO.

    This reverts commit d24874c7b2625e25630534a86864a93050f661d3.

    Change-Id: I4044f0b28b636c7a022912f6f24707bce22c8b98
    Related-Bug: #1704160

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.