Just upgraded to 2.7.6 and the yumrepo type does not write out our yum
configs correctly, anyone experiencing this? Documentation hasn''t
changed
from what I can tell for this type.
# facter -version
1.6.2
# puppetd --version
2.7.6
# facter architecture
x86_64
# facter operatingsystem
Fedora
# facter operatingsystemrelease
14
==== My manifest ===
yumrepo {
''EWT-Base'':
descr => ''Base Repository'',
baseurl => "
http://repo:80/$operatingsystem-$operatingsystemrelease-$architecture",
gpgcheck => 0,
enabled => 1,
priority => 1;
===== What gets written out ===
[Base]
name=Base Repository
baseurl=http://repo:80/x86_64
enabled=1
gpgcheck=0
priority=1
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
You probably need to escape some of this, part of ours- .....repo/\$releasever/\$basearch puppet/factor shouldn''t resolve these variables, they go to the repo file and are resolved by yum or whatever. On Tue, Nov 1, 2011 at 10:45 AM, Christopher Johnston <chjohnst@gmail.com>wrote:> Just upgraded to 2.7.6 and the yumrepo type does not write out our yum > configs correctly, anyone experiencing this? Documentation hasn''t changed > from what I can tell for this type. > > # facter -version > 1.6.2 > # puppetd --version > 2.7.6 > # facter architecture > x86_64 > # facter operatingsystem > Fedora > # facter operatingsystemrelease > 14 > > ==== My manifest ===> > yumrepo { > ''EWT-Base'': > descr => ''Base Repository'', > baseurl => " > http://repo:80/$operatingsystem-$operatingsystemrelease-$architecture", > gpgcheck => 0, > enabled => 1, > priority => 1; > > ===== What gets written out ===> > [Base] > name=Base Repository > baseurl=http://repo:80/x86_64 > enabled=1 > gpgcheck=0 > priority=1 > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
It''s the "dashes at the end of variable names" problem. Try
"...${operatingsystem}-${operatingsystemrelease}-${architecture}"
instead.
On 2011-11-01 09:07 , Len Rugen wrote:> You probably need to escape some of this, part of ours-
> .....repo/\$releasever/\$basearch
>
> puppet/factor shouldn''t resolve these variables, they go to the
repo
> file and are resolved by yum or whatever.
>
> On Tue, Nov 1, 2011 at 10:45 AM, Christopher Johnston
> <chjohnst@gmail.com <mailto:chjohnst@gmail.com>> wrote:
>
> Just upgraded to 2.7.6 and the yumrepo type does not write out our
> yum configs correctly, anyone experiencing this? Documentation
> hasn''t changed from what I can tell for this type.
>
> # facter -version
> 1.6.2
> # puppetd --version
> 2.7.6
> # facter architecture
> x86_64
> # facter operatingsystem
> Fedora
> # facter operatingsystemrelease
> 14
>
> ==== My manifest ===>
> yumrepo {
> ''EWT-Base'':
> descr => ''Base Repository'',
> baseurl =>
>
"http://repo:80/$operatingsystem-$operatingsystemrelease-$architecture",
> gpgcheck => 0,
> enabled => 1,
> priority => 1;
>
> ===== What gets written out ===>
> [Base]
> name=Base Repository
> baseurl=http://repo:80/x86_64
> enabled=1
> gpgcheck=0
> priority=1
>
That worked, for some reason back referencing did not. My foolishness I was overlooking normal variable semantic (like in shell). Strange thing my prior setup worked fine in 2.6, 2.7 broke it. -Chris On Tue, Nov 1, 2011 at 12:40 PM, Jacob Helwig <jacob@puppetlabs.com> wrote:> It''s the "dashes at the end of variable names" problem. Try > "...${operatingsystem}-${operatingsystemrelease}-${architecture}" instead. > > On 2011-11-01 09:07 , Len Rugen wrote: > > You probably need to escape some of this, part of ours- > > .....repo/\$releasever/\$basearch > > > > puppet/factor shouldn''t resolve these variables, they go to the repo > > file and are resolved by yum or whatever. > > > > On Tue, Nov 1, 2011 at 10:45 AM, Christopher Johnston > > <chjohnst@gmail.com <mailto:chjohnst@gmail.com>> wrote: > > > > Just upgraded to 2.7.6 and the yumrepo type does not write out our > > yum configs correctly, anyone experiencing this? Documentation > > hasn''t changed from what I can tell for this type. > > > > # facter -version > > 1.6.2 > > # puppetd --version > > 2.7.6 > > # facter architecture > > x86_64 > > # facter operatingsystem > > Fedora > > # facter operatingsystemrelease > > 14 > > > > ==== My manifest ===> > > > yumrepo { > > ''EWT-Base'': > > descr => ''Base Repository'', > > baseurl => > > " > http://repo:80/$operatingsystem-$operatingsystemrelease-$architecture", > > gpgcheck => 0, > > enabled => 1, > > priority => 1; > > > > ===== What gets written out ===> > > > [Base] > > name=Base Repository > > baseurl=http://repo:80/x86_64 > > enabled=1 > > gpgcheck=0 > > priority=1 > > > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
There was a change in 2.7 to allow dashes in variable names. There''s an issue open in Redmine around this very issue[0] [0] http://projects.puppetlabs.com/issues/10146 On 2011-11-01 10:29 , Christopher Johnston wrote:> That worked, for some reason back referencing did not. My foolishness I > was overlooking normal variable semantic (like in shell). Strange thing > my prior setup worked fine in 2.6, 2.7 broke it. > > -Chris > > > On Tue, Nov 1, 2011 at 12:40 PM, Jacob Helwig <jacob@puppetlabs.com > <mailto:jacob@puppetlabs.com>> wrote: > > It''s the "dashes at the end of variable names" problem. Try > "...${operatingsystem}-${operatingsystemrelease}-${architecture}" > instead. >