Bug 845321 - [RFE] - Suggested initial logging improvements for target_content.xml
[RFE] - Suggested initial logging improvements for target_content.xml
Status: NEW
Product: CloudForms Cloud Engine
Classification: Red Hat
Component: imagefactory (Show other bugs)
1.1.0
Unspecified Unspecified
low Severity low
: rc
: ---
Assigned To: Ian McLeod
Rehana
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-02 12:35 EDT by Justin Clift
Modified: 2015-07-13 00:36 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Justin Clift 2012-08-02 12:35:17 EDT
Description of problem:

  At present, although Imagefactory uses the contents of
  target_content.xml, it's hard to tell from the log file
  what actually happened when an image was built.

  The log output should also include:

    a) Which values were used when looking for a match.

         i.e. Target="rhevm", OS="RHEL", Version="6", etc.

       The SysAdmin can then create/update the
       target_content.xml file, to have those values.


    b) If a fragment of the target_content.xml file
       matched and is used, then output that to the log
       file.

       This is just because there's no other way to see
       what matched, and there needs to be. :)


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

  imagefactory-1.1.1-1.fc16.noarch
  imagefactory-jeosconf-ec2-fedora-1.1.1-1.fc16.noarch
  imagefactory-jeosconf-ec2-rhel-1.1.1-1.fc16.noarch


How reproducible:

  Every time.

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