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.

Title: Adding Lifecycle Environments to a Red Hat Satellite Capsule Server

Describe the issue:
In step 5: "Synchronize the content from the Satellite Server's environment to the Satellite Capsule Server:", the second example

hammer capsule content synchronize --id 1 --environment-id 1

is invalid. capsule with id 1 is everytime the internal one, and one can synchronize only external capsule servers. Synchronizing internal capsule is done via "hammer repository synchronize" command.


Suggestions for improvement:
Replace "--id 1" by either "--id <external_capsule_id>" (to express it is applicable to _external_ capsules only) or "--id 2" (to be in line with numeric id of environment).

Additional information:

FYI when one tries to execute that command, (s)he gets confusing error:

# hammer -u admin -p BLFqs2jM4WZoi9jn capsule content synchronize --id 1
Could not synchronize capsule content:
  Couldn't find SmartProxy with id=1 [WHERE "features"."name" IN ('Pulp Node')]
#

I requested to change that error string in bz164233.

Hi Pavel,

Thank you for the feedback. We'll add this into the prioritization list. Updating the ticket once we work on this.

Cheers,
Athene

This was published in the December Async. looks all good.