697909 – imagefactory daemon should not report start if qpid is down?

Bug 697909 - imagefactory daemon should not report start if qpid is down?

Summary: imagefactory daemon should not report start if qpid is down?

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	CloudForms Cloud Engine
Classification:	Retired
Component:	imagefactory
Sub Component:
Version:	1.0.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Assignee:	Steve Loranz
QA Contact:	wes hayutin
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	ce-ami
TreeView+	depends on / blocked

Reported:	2011-04-19 15:53 UTC by wes hayutin
Modified:	2015-08-03 00:02 UTC (History)
CC List:	7 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2012-05-15 20:06:01 UTC

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2012:0588	0	normal	SHIPPED_LIVE	new packages: imagefactory	2012-05-15 22:31:27 UTC

Description wes hayutin 2011-04-19 15:53:52 UTC

Description of problem:

[root@ip-10-243-114-79 rc3.d]# rpm -qa | grep factory
rubygem-image_factory_console-0.2.0-2.el6_0.20110401225248git6800ed8.noarch
rubygem-image_factory_connector-0.0.2-2.el6.20110414153545git257f8a3.noarch
imagefactory-0.1.6.2_8_gbcb427d-2.el6.noarch
[root@ip-10-243-114-79 rc3.d]# 


[root@ip-10-243-114-79 rc3.d]# /etc/init.d/imagefactory stop
Stopping imgfac.py:                                        [  OK  ]
[root@ip-10-243-114-79 rc3.d]# ps -ef | grep factory
root      3489  1999  0 11:33 pts/1    00:00:00 grep factory
[root@ip-10-243-114-79 rc3.d]# /etc/init.d/qpidd status
qpidd (pid  1122) is running...
[root@ip-10-243-114-79 rc3.d]# /etc/init.d/qpidd stop
Stopping Qpid AMQP daemon:                                 [  OK  ]
[root@ip-10-243-114-79 rc3.d]# 
[root@ip-10-243-114-79 rc3.d]# 
[root@ip-10-243-114-79 rc3.d]# 
[root@ip-10-243-114-79 rc3.d]# ps -ef | grep qpid
root      3511  1999  0 11:34 pts/1    00:00:00 grep qpid
[root@ip-10-243-114-79 rc3.d]# /etc/init.d/imagefactory start
Starting imgfac.py:                                        [  OK  ]
[root@ip-10-243-114-79 rc3.d]# cat /var/log/imagefactory.log 
2011-04-19 10:51:17,457 INFO root pid(2147) Message: Launched as daemon...
2011-04-19 11:34:14,442 INFO root pid(3523) Message: Launched as daemon...
[root@ip-10-243-114-79 rc3.d]#

Comment 1 wes hayutin 2011-04-19 17:37:09 UTC

documenting that qpid is not running or may not be fully functional at ami boot time.. 

Apr 19 09:35:11 ip-10-80-213-29 ntpd[1645]: Listening on interface #3 eth0, fe80::1031:3dff:fe1c:cad3#123 Enabled
Apr 19 09:35:11 ip-10-80-213-29 ntpd[1645]: Listening on interface #4 lo, 127.0.0.1#123 Enabled
Apr 19 09:35:11 ip-10-80-213-29 ntpd[1645]: Listening on interface #5 eth0, 10.80.213.29#123 Enabled
Apr 19 09:35:11 ip-10-80-213-29 ntpd[1645]: Listening on interface #6 virbr0, 192.168.122.1#123 Enabled
Apr 19 09:35:11 ip-10-80-213-29 ntpd[1645]: Listening on routing socket on fd #23 for interface updates
Apr 19 09:35:11 ip-10-80-213-29 ntpd[1645]: kernel time sync status 2040
Apr 19 09:35:53 ip-10-80-213-29 qpidd[1178]: 2011-04-19 09:35:53 warning Client closed connection with 501: internal-error: Sasl error: SASL(-1): generic failure:  (qpid/SaslFactory.cpp:311)
Apr 19 09:36:10 ip-10-80-213-29 qpidd[1178]: 2011-04-19 09:36:10 warning Client closed connection with 501: internal-error: Sasl error: SASL(-1): generic failure:  (qpid/SaslFactory.cpp:311)
Apr 19 09:36:13 ip-10-80-213-29 qpidd[1178]: 2011-04-19 09:36:13 warning Client closed connection with 501: internal-error: Sasl error: SASL(-1): generic failure:  (qpid/SaslFactory.cpp:311)
Apr 19 09:36:19 ip-10-80-213-29 qpidd[1178]: 2011-04-19 09:36:19 warning Client closed connection with 501: internal-error: Sasl error: SASL(-1): generic failure:  (qpid/SaslFactory.cpp:311)
Apr 19 09:36:31 ip-10-80-213-29 qpidd[1178]: 2011-04-19 09:36:31 warning Client closed connection with 501: internal-error: Sasl error: SASL(-1): generic failure:  (qpid/SaslFactory.cpp:311)
Apr 19 09:36:53 ip-10-80-213-29 qpidd[1178]: 2011-04-19 09:36:53 warning Client closed connection with 501: internal-error: Sasl error: SASL(-1): generic failure:  (qpid/SaslFactory.cpp:311)
Apr 19 09:36:55 ip-10-80-213-29 qpidd[1178]: 2011-04-19 09:36:55 warning Client closed connection with 501: internal-error: Sasl error: SASL(-1): generic failure:  (qpid/SaslFactory.cpp:311)
Apr 19 09:37:43 ip-10-80-213-29 qpidd[1178]: 2011-04-19 09:37:43 warning Client closed connection with 501: internal-error: Sasl error: SASL(-1): generic failure:  (qpid/SaslFactory.cpp:311)
Apr 19 09:37:53 ip-10-80-213-29 qpidd[1178]: 2011-04-19 09:37:53 warning Client closed connection with 501: internal-error: Sasl error: SASL(-1): generic failure:  (qpid/SaslFactory.cpp:311)
Apr 19 09:38:30 ip-10-80-213-29 ntpd[1645]: synchronized to 38.117.195.101, stratum 3
Apr 19 09:38:30 ip-10-80-213-29 ntpd[1645]: kernel time sync status change 2001
Apr 19 09:38:43 ip-10-80-213-29 qpidd[1178]: 2011-04-19 09:38:43 warning Client closed connection with 501: internal-error: Sasl error: SASL(-1): generic failure:  (qpid/SaslFactory.cpp:311)
Apr 19 09:38:53 ip-10-80-213-29 qpidd[1178]: 2011-04-19 09:38:53 warning Client closed connection with 501: internal-error: Sasl error: SASL(-1): generic failure:  (qpid/SaslFactory.cpp:311)

Comment 2 Mike Orazi 2011-04-26 14:49:36 UTC

We can only really reproduce this in the ami, correct?  

My understanding is that the dependency shouldn't exist (imagefactory is supposed to be able to start before qpidd), but maybe there's something special about the ami.  I can play around with service start up ordering a bit and see if I can figure anything out, but more eyes would probably be helpful.

Comment 3 wes hayutin 2011-06-16 20:30:48 UTC

ibm-hs22-02.lab.bos.redhat.com
[root@ibm-hs22-02 scratch]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.3.0-0.el6.20110616184910gita7515e1.noarch
aeolus-configure-2.0.1-0.el6.20110602110128git5cb9257.noarch
aeolus-conductor-devel-0.3.0-0.el6.20110616184910gita7515e1.noarch
aeolus-conductor-0.3.0-0.el6.20110616184910gita7515e1.noarch
aeolus-all-0.3.0-0.el6.20110616184910gita7515e1.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110616184910gita7515e1.noarch
[root@ibm-hs22-02 scratch]# less /var/log/iwhd.log 
[root@ibm-hs22-02 scratch]# /etc/init.d/imagefactory stop
Stopping imgfac.py: [  OK  ]
[root@ibm-hs22-02 scratch]# /etc/init.d/qpidd stop
Stopping Qpid AMQP daemon: [  OK  ]
[root@ibm-hs22-02 scratch]# /etc/init.d/imagefactory start
Starting imgfac.py: [  OK  ]
[root@ibm-hs22-02 scratch]#

Comment 4 wes hayutin 2011-06-29 14:35:24 UTC

[root@hp-ml370g5-01 ~]# rpm -qa | grep aeolus
aeolus-conductor-0.3.0-0.el6.20110628135944git2a88782.noarch
rubygem-aeolus-cli-0.0.1-1.el6.20110628165632git0dfe3ff.noarch
aeolus-all-0.3.0-0.el6.20110628135944git2a88782.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110628135944git2a88782.noarch
aeolus-conductor-doc-0.3.0-0.el6.20110628135944git2a88782.noarch
aeolus-configure-2.0.1-0.el6.20110628141215gitb8aaf85.noarch
[root@hp-ml370g5-01 ~]# /etc/init.d/qpidd stop
Stopping Qpid AMQP daemon: [  OK  ]
[root@hp-ml370g5-01 ~]# /etc/init.d/imagefactory restart
Stopping imgfac.py: [  OK  ]
Starting imgfac.py: [  OK  ]
[root@hp-ml370g5-01 ~]#

Comment 5 Mike Orazi 2011-07-01 19:53:47 UTC

imagefactory seems to run fine even when it comes up before qpid, except when this whole construct is shipped via ami, so I'm going to remove this from blocking beta, but leave it on ce-ami.

Comment 6 wes hayutin 2011-09-28 16:37:46 UTC

making sure all the bugs are at the right version for future queries

Comment 8 Aziza Karol 2011-10-12 10:24:39 UTC

imagefactory  starts even if qpidd is down.

[root@dell-pe1950-02 templates]# /etc/init.d/imagefactory status
imagefactory (pid  5043) is running...
[root@dell-pe1950-02 templates]# /etc/init.d/qpidd  status
qpidd (pid  4666) is running...


[root@dell-pe1950-02 templates]# /etc/init.d/imagefactory stop
Stopping imagefactory: [  OK  ]
[root@dell-pe1950-02 templates]# /etc/init.d/qpidd stop
Stopping Qpid AMQP daemon: [  OK  ]
[root@dell-pe1950-02 templates]# ps -ef | grep qpidd
root     13724  8991  0 06:02 pts/0    00:00:00 grep qpidd


[root@dell-pe1950-02 templates]# /etc/init.d/imagefactory start
Starting imagefactory: /usr/lib/python2.6/site-packages/oauth2/__init__.py:29: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
[  OK  ]
[root@dell-pe1950-02 templates]# ps -ef | grep factory
root     14174     1  0 06:19 ?        00:00:00 /usr/bin/python /usr/bin/imagefactory --qmf --debug
root     14205  8991  0 06:20 pts/0    00:00:00 grep factory



[root@dell-pe1950-02 templates]cat /var/log/imagefactory.log
2011-10-12 06:19:16,448 INFO root pid(14174) Message: Launched as daemon..



verified on:
[root@dell-pe1950-02 templates]# rpm -qa | egrep 'aeolus|factory'
rubygem-actionpack-3.0.9-1.aeolus.el6.noarch
aeolus-conductor-0.5.0-0.20111007200330gite77b251.el6.noarch
imagefactory-jeosconf-ec2-rhel-0.1.0-1.el6.noarch
rubygem-activerecord-3.0.9-1.aeolus.el6.noarch
rubygem-ZenTest-4.3.3-2.aeolus.el6.noarch
rubygem-actionmailer-3.0.9-1.aeolus.el6.noarch
aeolus-conductor-doc-0.5.0-0.20111007200330gite77b251.el6.noarch
imagefactory-jeosconf-ec2-fedora-0.1.0-1.el6.noarch
rubygem-activesupport-3.0.9-1.aeolus.el6.noarch
rubygem-arel-2.0.10-0.aeolus.el6.noarch
aeolus-configure-2.2.0-1.20111007151942git26136f2.el6.noarch
rubygem-imagefactory-console-0.5.0-4.20110824113238gitd9debef.el6.noarch
rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.el6.noarch
aeolus-all-0.5.0-0.20111007200330gite77b251.el6.noarch
rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.el6.noarch
aeolus-conductor-daemons-0.5.0-0.20111007200330gite77b251.el6.noarch
imagefactory-0.7.0-1.el6.noarch
rubygem-rack-mount-0.7.1-3.aeolus.el6.noarch


DeprecationWarning when imagafactory starts is tracked at https://bugzilla.redhat.com/show_bug.cgi?id=744908

Comment 10 errata-xmlrpc 2012-05-15 20:06:01 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0588.html

Note You need to log in before you can comment on or make changes to this bug.