Glance does not notify systemd when the services are up.

Bug #1438316 reported by Alberto Murillo
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Glance
In Progress
Undecided
Alberto Murillo

Bug Description

Unlike keystone, glance does not notify systemd when the api|registry|scrubber services are up.

root@controller:~# time systemctl start glance-api
Job for glance-api.service failed. See "systemctl status glance-api.service" and "journalctl -xe" for details.

real 1m30.310s
user 0m0.003s
sys 0m0.002s

The service actually starts but its status is not visible to systemd.

root@controller:~# systemctl status glance-api
● glance-api.service - OpenStack Image API Service
   Loaded: loaded (/usr/lib/systemd/system/glance-api.service; enabled; vendor preset: disabled)
   Active: activating (start) since Mon 2015-03-30 17:02:33 UTC; 41s ago
 Main PID: 810 (glance-api)
   CGroup: /system.slice/glance-api.service
           ├─810 /usr/bin/python2 /usr/bin/glance-api
           ├─829 /usr/bin/python2 /usr/bin/glance-api
           └─830 /usr/bin/python2 /usr/bin/glance-api

Mar 30 17:02:33 controller systemd[1]: Starting OpenStack Image API Service...
root@controller:~# echo $?
3

root@controller:~# ps aux |grep glance
glance 638 4.2 1.9 196948 78876 ? Rs 16:51 0:01 /usr/bin/python2 /usr/bin/glance-api

Attached is a patch that resolves this issue, tested against 2015.1.0b3

Tags: systemd
Revision history for this message
Alberto Murillo (powerbsd-o) wrote :
Revision history for this message
Alberto Murillo (powerbsd-o) wrote :

This is the sample glance-api.service file I used

[Unit]
Description=OpenStack Image API Service
After=syslog.target network.target

[Service]
Type=notify
NotifyAccess=all
Restart=always
User=glance
ExecStart=/usr/bin/glance-api

[Install]
WantedBy=multi-user.target

Changed in glance:
assignee: nobody → Alberto Murillo (powerbsd-o)
status: New → In Progress
Changed in glance:
status: In Progress → Fix Released
status: Fix Released → In Progress
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.