Bug 892300

Summary:	'glance control all start' does not work
Product:	Red Hat OpenStack	Reporter:	Yaniv Kaul <ykaul>
Component:	openstack-glance	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED WONTFIX	QA Contact:	Yaniv Kaul <ykaul>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.0 (Folsom)	CC:	eglynn, fpercoco, jkt
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-15 09:38:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yaniv Kaul 2013-01-06 12:57:53 UTC

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:

Comment 2 Eoghan Glynn 2013-01-10 16:20:06 UTC

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

Comment 3 Flavio Percoco 2013-02-15 09:38:06 UTC

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.