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.
Bug 1278909 - Error during Content View publish or promote "Action not allowed for the default capsule"
Summary: Error during Content View publish or promote "Action not allowed for the defa...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.1.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Chris Duryee
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-06 17:49 UTC by Mike McCune
Modified: 2019-09-26 13:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-13 16:06:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike McCune 2015-11-06 17:49:00 UTC
This is caused by the Capsule having the '--pulp-master true' flag passed during installation, which enables the "Pulp" feature enabled on the Capsule.

This feature is for the Satellite only and should never be enabled on a Capsule. We need to block/remove this option from the capsule-installer.


** WORKAROUND **

If the user is experiencing this error message they should 

1) execute on each capsule:

# capsule-installer --pulp-master false

2) Login to the Satellite UI and navigate to Infrastructure -> Capsules

3) Click "Refresh Features" on each Capsule.

Comment 2 Stephen Benjamin 2016-10-13 16:06:16 UTC
Looks to be fixed.


Note You need to log in before you can comment on or make changes to this bug.