Apache PIDs should be monitored more precisely on restart
Bug #1795918 reported by
Andrey Grebennikov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Ceilometer Charm |
Triaged
|
High
|
Unassigned | ||
OpenStack Cinder Charm |
Triaged
|
High
|
Unassigned | ||
OpenStack Keystone Charm |
Fix Released
|
High
|
Andrey Grebennikov | ||
OpenStack Nova Cloud Controller Charm |
Triaged
|
High
|
Unassigned |
Bug Description
When config-changed hooks are running, the way keystone-charm monitors that Apache has been restarted is to execute "pgrep apache2".
In case the bundle defines Keystone on the host and any other service running under Apache inside LXD container - the command will always return PIDs of all Apache processes running on the host, consequently juju agent will be waiting for all them to be restarted.
Instead of "pgrep apache2" it should be executing "pgrep -f keystone", which only returns Keystone-related PIDs.
Changed in charm-keystone: | |
assignee: | nobody → Andrey Grebennikov (agrebennikov) |
Changed in charm-keystone: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 18.11 |
Changed in charm-keystone: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
We should look at all os-charms and evaluate for this impact.