Bug 1295706 - puppet agent -t -v fails with "Error: Could not retrieve catalog from remote server: Error 400 on SERVER"
puppet agent -t -v fails with "Error: Could not retrieve catalog from remote ...
Product: Red Hat Satellite 6
Classification: Red Hat
Component: SCAP Plugin (Show other bugs)
All Linux
medium Severity medium (vote)
: Beta
: --
Assigned To: Katello Bug Bin
Kedar Bidarkar
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2016-01-05 05:13 EST by Kumudini Shirsale
Modified: 2016-07-27 05:22 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-27 05:22:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Comment 1 Marek Hulan 2016-01-05 05:22:02 EST
This was caused by wrong default value of policies puppet parameter. During previous failed saves it got wrongly escaped, a lot of \\\\" were part of the value. The solution was to change default value but the problem is that if we changed only default value, the record was not saved. A workaround was to change type as well (array to string), then the default value change was picked. After the save we reverted type back.
Comment 6 Kedar Bidarkar 2016-04-04 16:24:01 EDT
Can you please provide some verification steps for this bug.
Comment 7 Kedar Bidarkar 2016-04-04 16:27:48 EDT
sorry I asked needinfo for wrong bug.
Comment 8 Kedar Bidarkar 2016-04-04 16:37:22 EDT
followed the steps mentioned in the initial bug description, this issue is no longer seen with sat62-snap6

VERIFIED with sat62-snap6
Comment 10 errata-xmlrpc 2016-07-27 05:22:20 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.