Hide Forgot
Description of problem: When launching a deployable with more than one service a tooling tarball is generated that only contains the tooling for the first service, which I just happen to name "TopLevel": # tar -xvf cec409fa-fe87-11e0-aee6-525400797afe.tgz . katello TopLevel TopLevel/start Although both dirs, katello and TopLevel, are in the tarball the katello directory is empty. BTW: If I remove the TopLevel service and leave only the katello service the katello tooling is delivered in the tarball. So it seem the tarball is being populated with tooling for only one service. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Joe can we get some more information.. Can you post your template and any other relevant config
Created attachment 530102 [details] Example Deployable for launching an instance to be managed by Katello.
I've attached the deployable used to show the bug. Instructions for building an Audrey Enabled image can be found here: http://www.aeolusproject.org/page/Audrey_Audrey-Start-Setup#Building_Audrey_Enable_Images_with_Imagefactory_using_an_Imagefactory_TDL
I tested this same scenario with a different deployableXML: http://file.rdu.redhat.com/~gblomqui/deployables/bz748815.xml And I was unable to reproduce this problem. One of the Executable URLs in the Deployable XML is 404. https://www.aeolusproject.org/redmine/attachments/download/191/katello_start.bash Should be: https://www.aeolusproject.org/redmine/attachments/download/192/katello_start.bash