charm-juju-controller

juju-db service is named wrong in focal

Bug #1922292 reported by Adam Dyess on 2021-04-01

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	charm-juju-controller	Fix Released	Low	Unassigned	charm-juju-controller 21.07

the nrpe check for juju-db service running is wrong b/c the service name is wrong

in focal:
juju-db is run as a snap:
`snap.juju-db.daemon.service`

the nrpe check looks for the service `juju-db` running.

Xav Paice (community): Approve on 2021-07-28

🤖 prod-jenkaas-bootstack: Approve (continuous-integration) on 2021-07-28

Paul Goins: Approve on 2021-07-27

Adam Dyess (addyess) on 2021-07-27

Changed in charm-juju-controller:
status:	New → In Progress
assignee:	nobody → Adam Dyess (addyess)

Revision history for this message

Xav Paice (xavpaice) wrote on 2021-07-28:

Change https://code.launchpad.net/~llama-charmers/charm-juju-controller/+git/charm-juju-controller/+merge/406258 was merged, but we still have an issue with charm upgrades, where the old, not working check for juju-db is left behind on charm upgrade.

I'll set this to low priority now, as the main fix has been implemented.

Changed in charm-juju-controller:
importance:	Undecided → Low
status:	In Progress → Triaged
assignee:	Adam Dyess (addyess) → nobody

Celia Wang (ziyiwang) on 2021-07-29

Changed in charm-juju-controller:
status:	Triaged → Fix Released
milestone:	none → 21.07

This report contains Public information

Everyone can see this information.

You are

Subscribing...

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