the yumrepo resource creates a *.repo file for every resource. The
redhat thing just puts all repos in one big file.
and if you remove the redhat.repo, on a subscribed system, this file
will be recreated depending on the subscribed channel.
I did not test it in puppet3.x, but maybe it could work : still on 2.7,
and reworking our rep module is just sitting on the todo.
in redhat.rep, set enabled to 0 for all repos (augeas ?)
manage the redhat subscribed repos/channels with puppet
we do mirror all subscribes RH repos with mrepo, and point all or RH to
the local repos.
also we register our systems using the subscription manager, to our
local SAM (subscription asset manager ...)
SAM does not work with rhn, so maybe moving to the subscription thing is
not a bad idea.
something to look at ... maybe ?
grts
jo
On 20/05/14 19:45, DjE wrote:
Le 20/05/2014 15:47, jcbollinger a écrit :
On Tuesday, May 20, 2014 3:38:51 AM UTC-5, DjE wrote:
Hi all,
We find that the yumrepo resource is flapping on RedHat 6
Enterprise with the redhat.repo file since Puppet 3.4.x version
(due to a change about attribute content control)
We have updated with the latest Puppet 3.6 server and agent,
because we saw this commit :
https://github.com/puppetlabs/puppet/commit/9c25f75febe4df7d900e553824c9379cb7367c76
<https://github.com/puppetlabs/puppet/commit/9c25f75febe4df7d900e553824c9379cb7367c76>,
but the resource continues to flap.
The resource we want to manage :
Yumrepo[rhel-6-server-optional-rpms]
The Puppet change : enabled changed ' 1' to '1'
RedHat want : *"enabled= 1"*
Puppet want : "enable=1"
As we can see, there is a white space on original state (RedHat
generated file).
The change occurs every 4 hour (with 30 minutes runtime interval
agent), i did not looking for the process which generate the
redhat.repo file.
rhsm (/etc/rhsm/rhsm.conf) manage the yum repo file :
# Manage generation of yum repositories for subscribed content:
manage_repos = 1
[rhsmcertd]
# Frequency of certificate refresh (in minutes):
certFrequency = 240
The certFrequency seems to match with the change which occurs
every 4 hours, i did not test it.
The problem is that you are managing the same resource via two
different services. You are lucky that you are just flapping between
two equivalent states. Choose one system or the other to manage the
configuration for that repo.
John
--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to puppet-users+unsubscr...@googlegroups.com
<mailto:puppet-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/903782c7-828c-4fcb-9076-479c28650901%40googlegroups.com
<https://groups.google.com/d/msgid/puppet-users/903782c7-828c-4fcb-9076-479c28650901%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
Hi,
I agree with you about this potential conflict, but it's a default
RedHat configuration with rhsm, and it does not manage exactly the
same thing.
Puppet enable the "rhel-6-server-optional-rpms" which is not by
enabled default, and we never said rhsm to enable it (redhat
subscription side), so rhsm respect the local decision made via Puppet
with the Yumrepo, so it's just a syntax conflict, it could be a nice
thing that Puppet use the same syntax.
Puppet manage the rhsm.conf file so i tried to disable the
manage_repos option, but the redhat.repo file has been destroyed by
the rhsmcertd service, and disabled all RedHat repositories.
Then Puppet creates the
/etc/yum.repos.d/rhel-6-server-optional-rpms.repo file with just the
"enabled=1" parameter currently define by the Yumrepo resource.
We don't want to (re)define all the redhat repository urls one by one
with the YumRepo resource, maybe there is a better solution.
Djé
--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to puppet-users+unsubscr...@googlegroups.com
<mailto:puppet-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/537B94C9.6000307%40nosbox.net
<https://groups.google.com/d/msgid/puppet-users/537B94C9.6000307%40nosbox.net?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
Johan De Wit
Open Source Consultant
Red Hat Certified Engineer (805008667232363)
Puppet Certified Professional 2013/2014 (PCP0000006)
_________________________________________________________
Open-Future Phone +32 (0)2/255 70 70
Zavelstraat 72 Fax +32 (0)2/255 70 71
3071 KORTENBERG Mobile +32 (0)474/42 40 73
BELGIUM http://www.open-future.be
_________________________________________________________
Next Events:
Linux Training | https://www.open-future.be/linux-training-5-till-9th-may
Puppet Introduction Course |
https://www.open-future.be/puppet-introduction-course-12th-may
Puppet Fundamentals Training |
https://www.open-future.be/puppet-fundamentals-training-13-till-15th-may
Zabbix Certified Specialist |
https://www.open-future.be/zabbix-certified-specialist-training-19-till-21th-may
Zabbix Certified Professional |
https://www.open-future.be/zabbix-certified-professional-training-22-till-23rd-may
Subscribe to our newsletter | http://eepurl.com/BUG8H
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/537BC7F1.8040207%40open-future.be.
For more options, visit https://groups.google.com/d/optout.
