rhel client setup with shortname that is subcription-manager subscribed to satellite causes backend problems
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1158139
Description of problem:
capsule and content name shortname and long name mismatch causing errors.
appears to be the result of shortname that comes in from subscription manager to content host.
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/action.rb:398:in `block (3 levels) in execute_plan'
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This seems to be caused by the fact that the capsule is named 'x123.acme.com', while the content host
that represents the registered system is named 'x123': renaming the content host to 'x123.acme.com'
should get us moving forward, as the names of the capsule and the content host, and adding the env to the capsule should start working again.
Also if customer is setup for shortname they can subscribe with full FQDN as such.
in subscription manager's help
--name=SYSTEMNAME name of the system to register, defaults to the
I believe the general right recommendation here is for customers to not use shortname configuration.
#2 Updated by Justin Sherrill almost 6 years ago
- Subject changed from rhel client setup with shortname that is subcription-manager subscribed to satellite causes backend problems to rhel client setup with shortname that is subcription-manager subscribed to satellite causes backend problems
- Status changed from New to Rejected
- Legacy Backlogs Release (now unused) set to 166
This was resolved by https://github.com/Katello/katello/pull/6104