Bug 837325 - [RFE] Do not require /etc/sysconfig/cloud-info to exist or create it upon installation
Summary: [RFE] Do not require /etc/sysconfig/cloud-info to exist or create it upon ins...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-audrey-agent
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
Assignee: Joe Vlcek
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-03 13:10 UTC by james labocki
Modified: 2013-01-04 13:10 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-04 13:10:31 UTC
Embargoed:


Attachments (Terms of Use)

Description james labocki 2012-07-03 13:10:07 UTC
Description of problem:
Currently, aeolus-audrey-agent requires /etc/sysconfig/cloud-info to exist in order to execute. The contents of the file must be one of the following:

For RHEVm:
CLOUD_TYPE="rhevm"

For EC2
CLOUD_TYPE=ec2

For vSphere
CLOUD_TYPE=vsphere

This file is created by imagefactory. If, however, the image is not created by imagefactory (for example, in the case of importing an existing image) then the installed audrey agent fails to execute and produced the following error message.

"failed accessing file /etc/sysconfig/cloud-info, retrying in X seconds ..."

This is a RFE to not require the cloud-info file or create it upon installation of aeolus-audrey-agent package. Without this functionality it will require those working in brown field environments who wish to import images to take extra measures before importing the images instead of just installing the aeolus-audrey-agent package and importing.

Comment 2 Joe Vlcek 2013-01-04 13:03:23 UTC
If an image is built using image factory the /etc/sysconfig/cloud-info
file will exist.

If an image is manually modified to include the Audrey Agent then
the /etc/sysconfig/cloud-info file must also be manually added in
the correct format.

Marking will not fix.


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