Bug 852085

Summary: cannot launch deployable w/ <service> tag
Product: [Retired] CloudForms Cloud Engine Reporter: dgao
Component: aeolus-conductorAssignee: Jan Provaznik <jprovazn>
Status: CLOSED NOTABUG QA Contact: Rehana <aeolus-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.1.0   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-27 19:53:10 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 dgao 2012-08-27 15:07:55 UTC
Whenever launching a deployable w/ <services> tag, the status returned is "create_failed". No traceback from logs are observed.

[root@ibm-x3690x5-01 aeolus-conductor]# rpm -qa | grep "aeolus"
aeolus-conductor-0.13.0-0.20120824160007git202d4f9.fc16.noarch
aeolus-conductor-daemons-0.13.0-0.20120824160007git202d4f9.fc16.noarch
aeolus-configserver-0.4.10-1.el6cf.noarch
rubygem-aeolus-image-0.6.0-0.20120824120030git6801a52.fc16.noarch
aeolus-all-0.13.0-0.20120824160007git202d4f9.fc16.noarch
rubygem-aeolus-cli-0.7.0-0.20120824120026gitd64d64f.fc16.noarch
aeolus-conductor-doc-0.13.0-0.20120824160007git202d4f9.fc16.noarch
aeolus-configure-2.8.0-0.20120824120024gitbdcd549.fc16.noarch


deployable used:

<?xml version="1.0"?>
<deployable name="dgao_test" version="1.0">
  <description/>
  <assemblies>
    <assembly hwp="small-x86_64" name="Fedora-15-Audrey-Client">
      <image id="4ee653d4-ee26-11e1-8573-00215e5d12a0"/>
      <services>
        <service name='proxy'>
          <executable url='http://qeblade20.rhq.lab.eng.bos.redhat.com/pub/cloud-qe-script01.sh' />
        </service>
      </services>
    </assembly>
  </assemblies>
</deployable>

Comment 1 dgao 2012-08-27 19:53:10 UTC
This bug is caused by the oauth change in configserver. Without an additional patch on the conductor side, the communication breaks down and result in a 401 Unauthroized error. 

Closing this bz until the patch is applied to conductor, then retest.