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 1715355 - Internal capsule not in Default organization and location on fresh install of Sat 6.6
Summary: Internal capsule not in Default organization and location on fresh install of...
Keywords:
Status: CLOSED DUPLICATE of bug 1709695
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-30 07:53 UTC by Peter Ondrejka
Modified: 2019-06-06 16:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-06 16:38:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot1 (22.95 KB, image/png)
2019-05-30 07:54 UTC, Peter Ondrejka 		no flags Details
screenshot2 (17.73 KB, image/png)
2019-05-30 07:55 UTC, Peter Ondrejka 		no flags Details
View All

Description Peter Ondrejka 2019-05-30 07:53:56 UTC 
Description of problem:

On freshly installed Satellite 6.6, the internal capsule does not appear under Infrastructure > Capsules under Default Org/Loc context.

When viewing it under any context, it doesn't appear to have org and loc assigned (see screenshot1). Though when editing a capsule, default org and loc are selected under respective tabs (see screenshot2). 

Note that when hitting Submit in the Capsule edit mode (without actually making any changes), the capsule is correctly assigned to default org and loc and the issue disappears.

Version-Release number of selected component (if applicable):
satellite-6.6.0-5.beta.el7sat.noarch

How reproducible:
always

Actual results:
Internal capsule not treated as belonging to a default context 

Expected results:
capsuel in def org/loc by default

Additional info:

This hurts us for example when testing remote execution on fresh satellite, all jobs fail with: "RuntimeError - Could not use any Capsule. Consider configuring remote_execution_global_proxy, remote_execution_fallback_proxy in settings" even though the setttings are correctly set
Comment 3 Peter Ondrejka 2019-05-30 07:54:35 UTC 
Created attachment 1575136 [details]
screenshot1
Comment 4 Peter Ondrejka 2019-05-30 07:55:10 UTC 
Created attachment 1575137 [details]
screenshot2
Comment 5 Brad Buckingham 2019-06-06 16:38:08 UTC 

*** This bug has been marked as a duplicate of bug 1709695 ***
Note You need to log in before you can comment on or make changes to this bug.