Bug 747380

Summary:	aeolus-configure does not restart qpidd after changing qpidd.conf
Product:	[Fedora] Fedora	Reporter:	James Laska <jlaska>
Component:	aeolus-configure	Assignee:	Mo Morsi <mmorsi>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	clalancette, jturner, mmorsi, morazi, whayutin
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-24 16:53:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description James Laska 2011-10-19 16:29:47 UTC

Description of problem:

Attempting to build an image failed with SASL errors (see below). The problem was easily fixed by restarting the qpidd service after running aeolus-configure.

This bug is to address either:
1) updating documentation so that the user restarts qpidd after running aeolus-configure, or ...
2) update aeolus-configure to conditionally restart qpidd after updating qpidd.conf?

Version-Release number of selected component (if applicable):

* rubygem-aeolus-cli-0.1.0-5.fc16
* aeolus-all-0.4.0-1.fc16
* aeolus-conductor-0.4.0-1.fc16
* rubygem-aeolus-image-0.1.0-3.fc16
* aeolus-configure-2.1.0-1.fc16

How reproducible:

Steps to Reproduce:
1. On a fresh Fedora 16 system, follow the install+setup instructions on the aeolus project site: http://aeolusproject.org/configuring_aeolus.html
2. Configure aeolus

$ /usr/sbin/aeolus-configure -p ec2

3. Set selinux to permissive
4. Open up the firewall
5. Login to web-ui as admin
6. Create a provider account for amazon EC2
7. Create an image template.xml file
8. Build an image using template.xml file

$ aeolus-image build --target ec2 --template template.xml

9. Upload the image to EC2

Actual results:

# aeolus-image build --target ec2 --template template.xml
2011-10-19 12:09:30 warning Closing connection due to internal-error: Sasl error: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Credentials cache file '/tmp/krb5cc_0' not found) (qpid/SaslFactory.cpp:280)
2011-10-19 12:09:33 warning Closing connection due to internal-error: Sasl error: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Credentials cache file '/tmp/krb5cc_0' not found) (qpid/SaslFactory.cpp:280)
2011-10-19 12:09:39 warning Closing connection due to internal-error: Sasl error: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Credentials cache file '/tmp/krb5cc_0' not found) (qpid/SaslFactory.cpp:280)
2011-10-19 12:09:51 warning Closing connection due to internal-error: Sasl error: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Credentials cache file '/tmp/krb5cc_0' not found) (qpid/SaslFactory.cpp:280)
2011-10-19 12:10:15 warning Closing connection due to internal-error: Sasl error: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Credentials cache file '/tmp/krb5cc_0' not found) (qpid/SaslFactory.cpp:280)

Expected results:

Target Image: fc1f00b0-72f4-4b09-8588-583d55929949
Image: 8cb512b0-998e-4636-a585-96bc8e771dfb
Build: 5d11243e-3b66-4142-9d58-3ec92332c46b
Status: COMPLETED
Percent Complete: 100

Additional info:

Comment 1 Mo Morsi 2011-12-13 20:11:11 UTC

At what point in steps 1-9 do you modify qpidd.conf?

Also I'm not fully sure about the scope of this issue. aeolus-configure makes sure that the underlying dependencies for aeolus are installed and running. 

Should a user make a change to one of these dependencies outside the scope of the aeolus framework, it doesn't make sense to require configure to auto-detect this and reinitialize the dependency. For example if a user changes his httpd configuration file, the result would be the same, aeolus-configure would simply see httpd as running and not require it to be restarted.

It just seems to me that there are too many underlying dependencies to detect configuration changes to each one of those in configure inorder to force restarts (/usr/sbin/aeolus-restart-services restarts all the services anyways, so you can just use that to restart everything)

Comment 2 Mo Morsi 2012-04-24 15:53:22 UTC

ping? Can this be closed? What would be best to mark this bug as when closing?

Comment 3 wes hayutin 2012-04-24 16:53:57 UTC

closing as not a bug.. qpidd is no longer part of the product