YUM Provider in 3.x

34 views
Skip to first unread message

Paul Seymour

unread,
May 16, 2014, 3:54:03 AM5/16/14
to puppet...@googlegroups.com
Hello,

Working through some issues with upgrading our environment from 2.x to 3.5 (now I should probably target 3.6 !) anyway we have a module which 
does basically.

package { 'openssh-server':
  ensure => 'absent',
}

package { '3rd-party-ssh':
  ensure => 'installed'
}

This 3rd party SSH package has a "provides" of openssh-server on it. As such if you issue a "yum remove openssh-server" manually it will try and remove
the 3rd party version. Which is the standard YUM behaviour I believe.

So therefore on the 3.x servers the package is being removed/installed every time and as there is no dependencies here it can leave us without an SSH
server running.

Which I guess is probably what we are actually telling it to do. But this never happens in the 2.x series.

Any ideas on why, and how we can stop this behaviour ?

Thanks
Paul

José Luis Ledesma

unread,
May 16, 2014, 4:06:09 AM5/16/14
to puppet...@googlegroups.com

Hi,

   I think someone said a workaround in this group that consisted in setting the arch. You can try with:

package { 'openssh-server.x86_64':

  ensure => 'absent',

}

Hth,

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/daba08fe-85bc-426d-90ee-a01d3bd91ec8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Paul Seymour

unread,
May 16, 2014, 4:52:23 AM5/16/14
to puppet...@googlegroups.com
It works. Thanks a lot my Google'ing turned up nothing....

Kylo Ginsberg

unread,
May 17, 2014, 7:47:34 PM5/17/14
to puppet...@googlegroups.com
On Fri, May 16, 2014 at 12:54 AM, Paul Seymour <paul.s...@ig.com> wrote:
Hello,

Working through some issues with upgrading our environment from 2.x to 3.5 (now I should probably target 3.6 !) anyway we have a module which 
does basically.

package { 'openssh-server':
  ensure => 'absent',
}

package { '3rd-party-ssh':
  ensure => 'installed'
}

This 3rd party SSH package has a "provides" of openssh-server on it. As such if you issue a "yum remove openssh-server" manually it will try and remove
the 3rd party version. Which is the standard YUM behaviour I believe.

Yes, 3.5 fixed puppet's behavior to match yum's with respect to virtual packages, a long requested feature. See https://tickets.puppetlabs.com/browse/PUP-897 for details.

However, it was a regression wrt *puppet* which took a number of people by surprise, so in 3.6.1, there's a fix to make the new (3.5-style, yum-matching) behavior opt-in via a new "allow_virtual" parameter (with the intent to change the default to be the yum-matching behavior in puppet 4). See https://tickets.puppetlabs.com/browse/PUP-2182 for discussion.

Kylo


So therefore on the 3.x servers the package is being removed/installed every time and as there is no dependencies here it can leave us without an SSH
server running.

Which I guess is probably what we are actually telling it to do. But this never happens in the 2.x series.

Any ideas on why, and how we can stop this behaviour ?

Thanks
Paul

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/daba08fe-85bc-426d-90ee-a01d3bd91ec8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Kylo Ginsberg

Join us at PuppetConf 2014September 23-24 in San Francisco - http://puppetconf.com 
Register by May 30th to take advantage of the Early Adopter discount save $349!

Reply all
Reply to author
Forward
0 new messages