reboot notification comes back after clear-notification action removes it

Bug #1997356 reported by Rahul
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-sysconfig
Fix Released
Medium
Aliaksandr Vasiuk

Bug Description

When the reboot of sysconfig in not required and the warning to reboot comes, then you can run clear-notification action to get rid of the warning and the status of machine becomes active. However, the warning message comes back after couple of minutes and the machine status is back to blocked.

Steps to recreate:
`juju deploy ubuntu`
`juju deploy sysconfig`
`juju add-relation sysconfig ubuntu`

The `juju status` will show blocked status on sysconfig unit with message 'update-grub and reboot required. Changes in: /etc/systemd/system.conf, /etc/default/grub.d/90-sysconfig.cfg'.

You can clear the above notification by running:
`juju run-action sysconfig/<unit> clear-notification --wait`
and the sysconfig status is active. However after couple of minutes, the status goes back to blocked with the same message. I believe the update-status hook runs and brings back the warning.

Tags: bseng-591

Related branches

Revision history for this message
Rahul (rahulsinghunsw) wrote :

Juju Crashdump

Eric Chen (eric-chen)
tags: added: bseng-591
Changed in charm-sysconfig:
importance: Undecided → Medium
status: New → Triaged
Changed in charm-sysconfig:
assignee: nobody → Aliaksandr Vasiuk (valexby)
Changed in charm-sysconfig:
status: Triaged → Fix Committed
Changed in charm-sysconfig:
milestone: none → 23.01
Changed in charm-sysconfig:
status: Fix Committed → 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.