Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-22048 Client system registration with Capsule fails with a error message.
  3. SAT-22562

[QE] Client system registration with Capsule is successful with a error message.

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • stream
    • None
    • Hosts - Content
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • Phoenix - Content
    • Sprint 127, Sprint 133, Sprint 134, Sprint 135, Sprint 136, Sprint 137, Sprint 138, Sprint 139, Sprint 140, Sprint 141

      Description of problem:

      Registration of the client system with Capsule is successful with the below message:

      ~~~
      The system has been registered with ID: 9c0f3d6e-e60f-4950-913b-a5cfe6b452d7
      The registered system name is: client.example.com
      HTTP error code 422: Validation failed: Content view environment content facets is invalid
      ~~~

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

      Red Hat Satellite 6.15

      How reproducible:

      100%

      Steps to Reproduce:
      1. Register client system with Capsule with curl command generated on Satellite.
      2.
      3.

      Actual results:

      Client system registered but showing the below error:

      ~~~
      The system has been registered with ID: 9c0f3d6e-e60f-4950-913b-a5cfe6b452d7
      The registered system name is: client.example.com
      HTTP error code 422: Validation failed: Content view environment content facets is invalid
      ~~~

      Expected results:

      The client system should register without error messages.

      QE Tracker for https://issues.redhat.com/browse/SAT-22048
      Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2255276

              rhn-support-visawant Vijaykumar Sawant
              satellite-focaccia-bot Focaccia Bot
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: