systemd: puppet duplicated resources for service restart

Bug #1747533 reported by Emilien Macchi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Emilien Macchi

Bug Description

In https://bugs.launchpad.net/tripleo/+bug/1741263, we wanted to make services restarted automatically with systemd but we have some duplicated resources now, like:

Error: Cannot alias File[/etc/systemd/system/mongod.service.d/] to [\"/etc/systemd/system/mongod.service.d\"] at /etc/puppet/modules/systemd/manifests/service_limits.pp:26; resource [\"File\", \"/etc/systemd/system/mongod.service.d\"] already declared at /etc/puppet/modules/tripleo/manifests/profile/base/database/mongodb.pp:52\u001b[0m\n", "deploy_status_code": 1}

Changed in tripleo:
milestone: none → queens-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to puppet-tripleo (stable/ocata)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on puppet-tripleo (stable/newton)

Change abandoned by Emilien Macchi (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/541045
Reason: we don't need on newton, my bad

Changed in tripleo:
status: Triaged → Won't Fix
status: Won't Fix → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to puppet-tripleo (stable/ocata)

Reviewed: https://review.openstack.org/541043
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=961a6fd0d4963853d1ee25e6faeed10fbf16f730
Submitter: Zuul
Branch: stable/ocata

commit 961a6fd0d4963853d1ee25e6faeed10fbf16f730
Author: Emilien Macchi <email address hidden>
Date: Mon Feb 5 14:28:14 2018 -0800

    mongodb: avoid duplicated resources in systemd config

    The unit directory for mongodb service in systemd is already managed by
    puppet-systemd. This patch will ensure that puppet-tripleo doesn't
    manage the resource anymore and actually rely on it for orchestration
    with a "require" statement.

    Change-Id: Id030896250117dcc0eb6c4f5a7b8d8aa4d265fa5
    Closes-Bug: #1747533

tags: added: in-stable-ocata
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-tripleo 6.5.9

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

Changed in tripleo:
status: In Progress → Fix Released
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.