Managing static composite views


We want to manage static versions through different composite content views, ie: being able to re-install any composite v1, v2 or v3 with their respective package version.
We force the composite content view to specific version before publishing.
The question is:
When publishing child EPEL content view to version 6.0, it will remove version 5.0 from its environments (library and production in our case). The child EPEL content view 5.0 gets unpublished because version 6.0 is library and production. Is is safe to proceed that way ? In that case, will the composite v2 still being able to have access to the version 5.0 as it was created initialy ?


              | composite v1  | composite v2     | composite v3   |
| RHEL7Server | version 1.0 --|--> version 2.0 --|--> version 3.0 |
| Katello     | version 2.0 --|--> version 3.0 --|--> version 4.0 |
| EPEL        | version 4.0 --|--> version 5.0 --|--> version 6.0 |

Expected outcome:
Being able to install composite v2 as it was published.

Foreman and Proxy versions:
From Satelitte 6.3.5:

  • Katello 3.4.5-19.el7
  • Foreman

Foreman and Proxy plugin versions:

Other relevant data:

You speak of Foreman 1.15 and you speak of Satellite 6.3 in your post.

What system do you use actually?

Regarding Foreman…please update to at least 1.18., 1.15. is rather old and not really supported anymore.


I use Red Hat Satellite 6.3.5 and it is based on the versions I’ve
But the question is propably not related to a specific version.