Project

Profile

Help

Issue #1194

yum groupinstall pulp-consumer-qpid upgrades default puppet

Added by vijaykumar.jain@nomura.com almost 5 years ago. Updated about 2 months ago.

Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Category:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.5
Platform Release:
OS:
RHEL 6
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:

Description

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?

History

#1 Updated by vijaykumar.jain@nomura.com almost 5 years ago

wrote:

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?

#2 Updated by bcourt almost 5 years ago

  • Status changed from NEW to CLOSED - NOTABUG

The pulp puppet handler requires the newer version of puppet.

#3 Updated by bmbouter over 1 year ago

  • Tags Pulp 2 added

#4 Updated by bmbouter about 2 months ago

  • Category deleted (14)

We are removing the 'API' category per open floor discussion June 16, 2020.

Please register to edit this issue

Also available in: Atom PDF