Bug #35192
closed
We shouldn't allow assigning hosts to import/export content views
Added by Jeremy Lenz over 2 years ago.
Updated about 2 years ago.
Category:
Inter Server Sync
|
|
Description
Does it make any sense for a host to be registered to
1) an import-only content view;
2) an 'Export-Library'content view
3) a "generated" content view?
I'm not 100% clear on which of these should and should not be allowed. But for the ones that should not,
a) The Katello registration API should prevent this
b) In the new host details CV selection screen, these CVs should not be listed as options
- Description updated (diff)
- Category set to Inter Server Sync
- Target version set to Katello 4.6.0
- Triaged changed from No to Yes
Re: `Does it make any sense for a host to be registered to`
1) an import-only content view; - YES
2) an 'Import-Library'content view - ? (may be what about users who already have it registered to the Import Library?. What if we want to compare versions of library snapshots (in the future...) )
3) a "generated" content view? - NO
- Target version changed from Katello 4.6.0 to Katello 4.7.0
- Target version changed from Katello 4.7.0 to Katello 4.8.0
- Target version deleted (
Katello 4.8.0)
- Triaged changed from Yes to No
- Target version set to Katello 4.9.0
- Triaged changed from No to Yes
- Status changed from New to Resolved
You cannot register to a generated content view, since Katello doesn't create the Candlepin environment:
[root@rhel8c vagrant]# subscription-manager register --org Default_Organization --environments Library/Export-Red_Hat_Satellite_Client_6_for_RHEL_8_x86_64_RPMs-3
Registering to: centos8-katello-devel-stable.example.com:443/rhsm
Username: admin
Password:
No such environment: Library/Export-Red_Hat_Satellite_Client_6_for_RHEL_8_x86_64_RPMs-3
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by