yum groupinstall pulp-consumer-qpid upgrades default puppet
It was recently reported that yum groupinstall pulp-consumer-qpid upgraded puppet version (2.6.7 -> 2.7.x) on the clients. As a result of which puppet master(2.6.x) s communication with puppet clients. we are not using pulp for puppet deployment but only for rpm as of now. is there a way we remove pulp-puppet plugins on client so that rpm deployment still works?
#1 Updated by firstname.lastname@example.org almost 5 years ago
pulp version 2.5.1
As part of the pulp install, the puppet package is upgraded to 2.7.26. The puppet master is only at 2.6.7-1.
Because of this, we get the following error when puppet attempts to pull the latest catalog from the puppet master.
Could not retrieve catalog from remote server: Error 400 on SERVER: No support for http method POST
We are not using pulp for puppet deployment but only for rpm as of now. Is there a way we remove pulp-puppet plugins on client so that rpm deployment still works?
Can we safely remove pulp-puppet-consumer-extensions and pulp-puppet-handlers from pulp-consumer to avoid puppet upgrade without breaking rpm plugins?
Please register to edit this issue