Bug 688191 - Matahari Agent for configuration
Summary: Matahari Agent for configuration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: matahari
Version: 6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Adam Stokes
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks: 688204
TreeView+ depends on / blocked
 
Reported: 2011-03-16 14:42 UTC by Perry Myers
Modified: 2011-12-06 11:38 UTC (History)
3 users (show)

Fixed In Version: matahari-0.4.2-2.el6
Doc Type: Bug Fix
Doc Text:
Matahari now includes an agent for system configuration. It supports updating system configuration using both puppet and augeas.
Clone Of:
: 688204 (view as bug list)
Environment:
Last Closed: 2011-12-06 11:38:50 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1569 0 normal SHIPPED_LIVE matahari bug fix and enhancement update 2011-12-06 00:39:06 UTC

Description Perry Myers 2011-03-16 14:42:12 UTC
Description of problem:
provide a Config Agent that allows a puppet script to be passed as an argument and then uses the puppet client to process and configure the system

This agent can also act as a wrapper to the augeas functionality

Comment 2 Andrew Beekhof 2011-05-16 08:18:08 UTC
We have the basics written upstream, but need a puppet expert to complete it.

Comment 4 Dave Johnson 2011-09-12 18:15:42 UTC
sysconfig agent is there and working in v0.4.2-2

Comment 5 Russell Bryant 2011-11-16 21:07:58 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Matahari now includes an agent for system configuration.  It supports updating system configuration using both puppet and augeas.

Comment 6 errata-xmlrpc 2011-12-06 11:38:50 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1569.html


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