Project

General

Profile

Actions

Bug #9883

closed

Updating client content view fails when client is registered to capsule

Added by Justin Sherrill about 9 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Client/Agent
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1204949
Description of problem:
Updating a client's content view fails when the client is registered to a capsule.

Version-Release number of selected component (if applicable):

Tested against:

  • A satellite running Satellite-6.1.0-RHEL-7-20150317.0
  • A capsule running RHEL 7.1
  • Clients running RHEL 5.11, 6.6 and 7.1.

The RHEL 5.11 and 7.1 clients are affected, but the RHEL 6.6 client was not affected.

How reproducible:
Unknown.

Steps to Reproduce:
1. Set up a satellite and capsule.
2. Register clients to the capsule with the usual commands:

1. rpm -Uvh http://capsule.example.com/pub/katello-ca-consumer-latest.noarch.rpm
2. subscription-manager register --org="Default_Organization" --environment="Library"
3. (not sure if required) subscription-manager attach --pool …

3. Create a content view and make it available to the clients. (Following the xample above, it should be in the Library lifecycle environment and the Default Organization organization.)
4. Log in to the satellite web UI. Go to Hosts → Content Hosts. Select a host, and change the "content view" field.

Actual results:
The task fails. The failed task is "Actions::Candlepin::Consumer::Update". The most interesting line from the exception is "caused by: (RestClient::BadRequest) Katello::Resources::Candlepin::Consumer: 400 Bad Request {"displayMessage":"Problem updating unit Consumer [id = null, type = null, getName() = null]","requestUuid":"a1a2b811-4ef2-4a0c-91eb-c7bd274b9d3f"} (PUT /candlepin/consumers/ddc94272-eb37-40ab-8d36-1d4380875f9f)".

Expected results:
The task succeeds.

Additional info:
No firewall was running on the capsule or clients when this bug was noticed. It is unknown if the presence of a firewall affects how hard it is to reproduce this bug.

Actions #1

Updated by The Foreman Bot about 9 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 68
  • Pull request https://github.com/Katello/katello/pull/5134 added
  • Pull request deleted ()
Actions #2

Updated by Justin Sherrill about 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #3

Updated by Eric Helms about 9 years ago

  • Category set to Client/Agent
  • translation missing: en.field_release set to 23
  • Triaged changed from No to Yes
Actions

Also available in: Atom PDF