Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When you create a capsule with the pulp feature there is no warning that it is wrong as you normally only need the pulp-node feature.
Then once you have the external capsule with the pulp feature enabled then synchronize is not working anymore as it errors with
"Action not allowed for the default capsule"
This is for the end-user a confusing error message and does not help the end-user to solve the problem.
After some googling the issue http://projects.theforeman.org/issues/9209 can be found making a remark that the feature "Pulp" is checked for the Synchronize feature to be enabled.
For the end-user this is all confusing.
Recommended improvements to not confuse the end-user:
- Rename feature "Pulp" to "Pulp-Master" to make it clear it is the master feature and not the node feature
- Rename capsule-installer option "--foreman-proxy-plugin-pulp-enabled=true" to "--foreman-proxy-plugin-pulp-master-enabled=true"
- Rename feature "--foreman-proxy-plugin-pulp-pulpnode-enabled" to --foreman-proxy-plugin-pulpnode-enabled" to make it clear it is a second feature indepenednt of the "Pulp-Master" feature
- Improved error message, stating that a Capsule with the feature "Pulp-Master" does not need to be synchronized as it is the master.
- Provide a warning that registering a second Capsule with the feature "Pulp-Master" is not allowed
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
In Sat6.3 looking at the help page of the satellite-installer for capsule i do not see any 'pulpnode' anymore:
----
[crash/LI] root@li-lc-1589:~# satellite-installer --help --scenario capsule | grep pulp
--clear-pulp-content This option will clear all Pulp content from disk located in '/var/lib/pulp/content/'. (default: false)
--[no-]enable-foreman-proxy-plugin-pulp Enable 'foreman_proxy_plugin_pulp' puppet module (default: true)
= Module foreman_proxy_plugin_pulp:
[crash/LI] root@li-lc-1589:~#
----
I think this BZ can be closed as being delivered in 6.3 already
On Sat6.4 i have the following options with pulp:
--------------
root@li-lc-2223:~# satellite-installer --help --scenario capsule | grep pulp
--clear-pulp-content This option will clear all Pulp content from disk located in '/var/lib/pulp/content/'. (default: false)
--[no-]enable-foreman-proxy-plugin-pulp Enable 'foreman_proxy_plugin_pulp' puppet module (default: true)
= Module foreman_proxy_plugin_pulp:
--------------
For me this is fixed in Sat6.4