Canonical Juju

juju doesn't upgrade juju-db.service file

Bug #1907821 reported by John A Meinel
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

In https://bugs.launchpad.net/juju/+bug/1845350 we changed our systemd file to use "infinity" instead of "unlimited". However, the startup code in Juju checks to see if there is a juju-db service before it writes out a new service file. So it never cleans up the old service file.

I thought we had done an upgrade step in the past (when we changed the default value of memory limits).

The current workaround is to stop juju-db on each controller node, rewrite the /lib/systemd/system/juju-db/juju-db.service with infinity in place of unlimited, and then start juju-db again.

Revision history for this message
@les (alesstimec) wrote :

The customer had a HA enabled on their controller, 3 unit.

The controller was upgraded to 2.9.16, two units were upgraded properly, the third had somehow missed the upgrade step and its juju-db.service file still contained infinity in place of unlimited. Had to manually fix the service file, restart juju-db and machine services.

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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