Service not reliably active after install

Bug #2027954 reported by Christian Ehrhardt 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pcs (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hi,
the daily metric runs, among other things, install pcs.
In there I've had two days where in mantic the service did not come up.

Affected:
- 12th+13th of July
- Good before & after

What I see in the bad case is this:
08:05:59 Created symlink /etc/systemd/system/multi-user.target.wants/pcsd-ruby.service → /lib/systemd/system/pcsd-ruby.service.
08:05:59 Created symlink /etc/systemd/system/multi-user.target.wants/pcsd.service → /lib/systemd/system/pcsd.service.
08:06:02 Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.

Full logs:
good: https://jenkins.canonical.com/server-team/view/metrics/job/metric-server-simple-mantic-vm-c1-m1/68/consoleFull
bad: https://jenkins.canonical.com/server-team/view/metrics/job/metric-server-simple-mantic-vm-c1-m1/69/consoleFull

That seems to be the start call at the end of postinst
  deb-systemd-invoke $_dh_action 'pcsd-ruby.service' 'pcsd.service' >/dev/null || true
in
/var/lib/dpkg/info/pcs.postinst

Due to that

OTOH, a first thought might be "why isn't is failing the install then?"
Well that is easy, this has an || true (see above).
So is this expected?
Why?
Would then a retry mechanism make sense?

I've created (https://github.com/canonical/server-test-scripts/pull/185) to have the service status info next time, but for now all I can give is the info above.

Please have a look if you think this something we can improve with what we have so far.
If not close it as incomplete until it re-occurs or someone else chimes in having more data.

Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote :

Thanks for reporting this bug Christian.

As you may have anticipated, I was not able to reproduce this issue locally. That command in the postinst script you mentioned is autogenerated by dh_installsystemd so nothing manually crafted by the Debian maintainer. I think we shouldn't manually change this behavior right now, if you find any occurrence of that again we can revisit and re-asses the situation. Does that sound good to you?

Changed in pcs (Ubuntu):
status: New → Incomplete
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

> As you may have anticipated

Indeed

> Does that sound good to you?

Yes

:-)
The only problem I have now is that I'm not sure if I should hope it occurs (more data) or not (making me believe things are fine)

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for pcs (Ubuntu) because there has been no activity for 60 days.]

Changed in pcs (Ubuntu):
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.