Project

General

Profile

Bug #14834

Successful Capsule install when it is not registered with subscription manager to Satellite

Added by Ivan Necas about 6 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Installer
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1330072
Description of problem:
Capsule install documentation doesn't mention why capsule's subscription manager should be registered to Satellite. The katello-installer finish installation successfully without a warning. The leads the user to believe that everything is OK, and will able to use the capsule.
However, once the user will try publish new content view, it will get fail silently. The task will finish with a warning:
"Could not find Content Host with exact name 'abraverm-capsule-6-2.usersys.redhat.com', verify the Capsule is registered with that name."

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

How reproducible:
Always

Steps to Reproduce:
Install new Capsule (https://access.stage.redhat.com/documentation/en/red-hat-satellite/version-6.2-beta/installation-guide/#registering_capsule_to_satellite)
without:
  1. rpm -Uvh http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm
  2. subscription-manager register --org organization_label

Actual results:
foreman-installer will finish successfully without warning or errors.

Expected results:
Warning\Error in the installation log\output and in Web UI.

Additional info:

History

#1 Updated by Eric Helms about 6 years ago

  • Legacy Backlogs Release (now unused) set to 86

#2 Updated by Eric Helms about 6 years ago

  • Legacy Backlogs Release (now unused) changed from 86 to 144

#3 Updated by Eric Helms almost 6 years ago

  • Legacy Backlogs Release (now unused) changed from 144 to 168

#4 Updated by Eric Helms almost 6 years ago

  • Legacy Backlogs Release (now unused) changed from 168 to 171

#5 Updated by Eric Helms almost 6 years ago

  • Legacy Backlogs Release (now unused) deleted (171)

#6 Updated by Justin Sherrill almost 6 years ago

  • Status changed from New to Rejected
  • Legacy Backlogs Release (now unused) set to 166

This is no longer the case, it does not have to be registered to the katello server, fixed here: https://github.com/Katello/katello/pull/6104

Also available in: Atom PDF