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
Created attachment 1575136 [details] screenshot1
Created attachment 1575137 [details] screenshot2
*** This bug has been marked as a duplicate of bug 1709695 ***