Description of problem: Adding a new repository to existing content hosts is *very* time consuming and takes a lot of handwork: 1. Add (RH) repo to product 2. Sync repo 3. Add repo to content views 4. Add repo to activation keys (for new deployments) 5. Publish content views 6. Promote content views 7. Add/Enable new repository to each existing content host 8. auto-attach new repository to each content host Step 7 is the most pain-full step. I propose to add a bulk action for this step. Version-Release number of selected component (if applicable): How reproducible: Follow above steps Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
For what it is worth, this bug is related to our RHN case 01540344.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.