*Deployed*... Does that mean activate/re-activate OR the installation of
the rpms did not get the files OR an rhncfg-client get failed?
Activate/re-activate should have pushed the files.
Installation of the rpms by themselves, will not push the files.
rhncfg-client get or a schedule through the UI, api, or spacecmd.
This are some of the options you can do in the kickstart:
1. Ensure that the rpms Avi gave are installed.
2. This has been part of our default kickstart for years.
# Per rhncfg-client documentation, the first get or deploy of files can
fail if this file does not exist.
# The work around is either reschedule, rerun, or touch the file
touch /var/log/rhncfg-actions
3. In a %post script, verify all of the files were deployed.
for myconfigs in `rhncfg-client list |egrep -v
"myspacewalk.server.domain|Config Channel" |awk '{print $3}'`; do
rhncfg-client get $myconfigs
done
- Thanks and good luck
From: Lachlan Musicman <[email protected]>
To: [email protected]
Date: 03/29/2016 07:19 PM
Subject: Re: [Spacewalk-list] Kickstart and Config management
Sent by: [email protected]
This email originated from outside of the company. Please use discretion
if opening attachments or clicking on links.
On 30 March 2016 at 10:43, Avi Miller <[email protected]> wrote:
> On 30 Mar 2016, at 10:30 AM, Lachlan Musicman <[email protected]> wrote:
>
>
> If this doesn't work, where should I look for information on why? I'm
not seeing anything in the log files.
Post-provisioning, check that you have the following RPMs installed:
rhncfg-management
rhncfg-client
rhncfg
rhncfg-actions
And check that configuration management is allowed:
# rhn-actions-control --report
deploy is enabled
diff is enabled
upload is enabled
mtime_upload is enabled
run is enabled
If you don't have the RPMs, the rhn-actions-control won't work. If you're
not installing the RPMs as part of the provisioning process (i.e. if
they're not available in any channel enabled for kickstart), then the
enabling options won't work.
Thanks Avi.
Here's the output on a machine that I *just* deployed:
[root@vmpr-res-head-node ~]# rpm -qa | grep rhncfg
rhncfg-5.10.85-1.el7.noarch
rhncfg-actions-5.10.85-1.el7.noarch
rhncfg-client-5.10.85-1.el7.noarch
rhncfg-management-5.10.85-1.el7.noarch
[root@vmpr-res-head-node ~]# rhn-actions-control --report
deploy is enabled
diff is enabled
upload is enabled
mtime_upload is enabled
run is enabled
So everything looks right from that perspective.
But, no file deployment?
Hmmm..
------
The most dangerous phrase in the language is, "We've always done it this
way."
- Grace Hopper
Cheers,
Avi
--
Oracle <http://www.oracle.com>
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
This email originated from outside of the company. Please use discretion
if opening attachments or clicking on links.
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
**
This email and any attachments may contain information that is confidential
and/or privileged for the sole use of the intended recipient. Any use, review,
disclosure, copying, distribution or reliance by others, and any forwarding of
this email or its contents, without the express permission of the sender is
strictly prohibited by law. If you are not the intended recipient, please
contact the sender immediately, delete the e-mail and destroy all copies.
**
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
