+++ This bug was initially created as a clone of Bug #2153523 +++

Description of problem:
Promoting a composite content view to environment with registry name as "<%= lifecycle_environment.label %>/<%= repository.name %>" on Red Hat Satellite 6 fails with "'undefined method '#label' for NilClass::Jail (NilClass)'"

Version-Release number of selected component (if applicable):
6.11.4

How reproducible:
Always

Steps to Reproduce:
Create product

1. hammer product create --description "Product Busybox Container" --name Product_Busybox_Container --label "Product_Busybox_Container" --organization myorg
   Create repository and sync to source

1. hammer repository create \
   --content-type "docker" \
   --organization myorg \
   --product "Product_Busybox_Container" \
   --url "https://registry-1.docker.io" \
   --name "library/busybox" \
   --docker-upstream-name "library/busybox" \
   --label "library_busybox" \
   --include-tags "stable, 1.35.0"

1. hammer repository synchronize --name "library/busybox" --product "Product_Busybox_Container" --organization myorg

Create content view

1. hammer repository list --product Product_Busybox_Container --organization myorg
2. hammer content-view create --label ContentView_Busybox --name ContentView_Busybox --organization-label myorg --repository-ids 1225
   Replace 1225 with the id from above command

Content view creation

1. hammer content-view publish --organization myorg --name ContentView_Busybox

Now assign this created content-view to a composite-content-view

Create an environment test with registry name as "<%= lifecycle_environment.label %>/<%= repository.name %>"

promote composite-content-view to test environment

ERROR: 'undefined method '#label' for NilClass::Jail (NilClass)'

— Additional comment from on 2022-12-15T15:19:45Z

Can the full stack trace from the production.log? Thanks!

— Additional comment from on 2022-12-15T15:35:42Z

Created attachment 1932868
requested traceback from production.log

— Additional comment from on 2022-12-15T15:37:30Z

If interested, reproducer is also be available but only for the next 3-4days:

https://dhcp131-85.gsslab.pnq2.redhat.com
root | redhat
admin | RedHat1!

--Soham

— Additional comment from on 2023-09-25T15:19:28Z

Created redmine issue https://projects.theforeman.org/issues/36776 from this bug

— Additional comment from on 2023-10-02T16:02:14Z

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36776 has been resolved.

— Additional comment from on 2023-10-27T15:52:48Z

• • • Bug 2237999 has been marked as a duplicate of this bug. ***

— Additional comment from on 2023-11-01T16:00:11Z

Fix in snap 35.

— Additional comment from on 2024-01-23T16:38:02Z

Verified on 6.15 - Snap 5

Steps to Verify:
1.Create a product:

• hammer product create --description "Product Busybox Container" --name Product_Busybox_Container --label "Product_Busybox_Container" --organization myorg
  2.Create a repository and sync it:
• hammer repository create \
  --content-type "docker" \
  --organization myorg \
  --product "Product_Busybox_Container" \
  --url "https://registry-1.docker.io/" \
  --name "library/busybox" \
  --docker-upstream-name "library/busybox" \
  --label "library_busybox" \
  --include-tags "stable, 1.35.0"
• hammer repository synchronize --name "library/busybox" --product "Product_Busybox_Container" --organization myorg (For future reproducers, you might need to find a different registry for use here, docker.io refuses connection often)
  3. Create a content view with this repo and publish it:
• hammer content-view create --label ContentView_Busybox --name ContentView_Busybox --organization-label myorg --repository-ids <repo_id>
• hammer content-view publish --organization myorg --name ContentView_Busybox
  4. Create a CCV
  5. Add the CV to this composite CV.
  6. Create an LCE. Modify the registry name pattern to <%= repository.name %>.
  7. Create another LCE. Modify the registry name pattern to <%= lifecycle_environment.label %>/<%= repository.name %>
  8. Promote the CV to the first LCE.
  9. Promote the CV to the second LCE.

Expected Results:
The CCV can successfully be promoted to both LCEs without error.

Actual Results:
The CCV can successfully be promoted to both LCEs without error.

QE Tracker for https://issues.redhat.com/browse/SAT-23583
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2266144