Description of problem: - 'glance control all start' does not seem to start the registry service. [root@ykaul-os-glance glance]# ps -ef |grep glance root 4853 2790 0 14:54 pts/0 00:00:00 grep glance [root@ykaul-os-glance glance]# glance-control all start Starting glance-api Starting glance-registry with /var/run/glance/all.pid Starting glance-scrubber with /var/run/glance/all.pid [root@ykaul-os-glance glance]# ps -ef |grep glance root 4860 1 4 14:55 ? 00:00:00 /usr/bin/python /usr/bin/glance-api root 4895 4860 15 14:55 ? 00:00:00 /usr/bin/python /usr/bin/glance-api root 4896 4860 15 14:55 ? 00:00:00 /usr/bin/python /usr/bin/glance-api root 4898 2790 0 14:55 pts/0 00:00:00 grep glance (note the use of /var/run/glance/all.pid file?!) Version-Release number of selected component (if applicable): openstack-glance-2012.2.1-1.el6ost.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I've reproduced the issue and it should be fixed, but direct use of glance-control would not be the recommended way of starting the glance services in RHOS, i.e. users would generally be directed to use something like: for svc in api registry ; do service openstack-glance-$svc start ; done
This has been fixed upstream but, since the recommended usage is not to use glance-control but starting each service individually, it doesn't make sense to backport this fix.