Satellite 6.10 Requesting this as well.

This write-up is a little terse, but my original request is driven by what I find to be very poor Satellite UI/UX - namely, there is _no_ reference at all to "Incremental Content View" anywhere in the Satellite UI. ICVs can only be generated as a side-effect of the "Content" / "Errata" / "Apply Errata" process. I believe that there should be an option on the "Content - > Content Views > [name of CV]" page to "create Incremental Content View" (in addition to the current button which is to "Publish New Version").

There is also a possibility here for improving Satellite capabilities in one significant way: currently, Incremental Content Views can _only_ be created based on an "Errata" published by Red Hat -- meaning, customers with locally-created Products and Repositories _cannot_ create Incremental Content Views to e.g. publish an urgent security update to a locally-written custom package because there is no supported way to create "Errata" for local/custom content. Allowing the user to select specific _packages_ at this point (in additional to "Errata") would enable creation of ICVs for locally-written content.

I agree that the web user interface for creating an incremental content view can be improved.

I was helping a customer with the web UI method versus hammer command method.  I found it confusing why the web UI instructions:

  Satellite 6.10
  _Content Management Guide_
  Chapter 11.5, "Adding Errata to an incremental Content View"
  https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/content_management_guide/managing_errata#Managing_Errata-Adding-Errata-To-An-Incremental-Content-View

...has one select content hosts for which the added errata should apply.  We are creating a incremental *content view*, thus it should affect all hosts in the lifecycle environment to which the starting content view has been promoted.  There should be no need to select content hosts.

One consequence of having to select content hosts is that one is then limited to adding only installable errata.  For example, all my content hosts are minimal-install RHEL machines.  Thus, none of them have java-11-openjdk installed on them.  I cannot follow the web UI instructions to create an incremental content view containing a java-11-openjdk erratum because when I go to that erratum's Content Hosts tab, no hosts are listed.  Yet, hammer can create an incremental content view with a non-installable erratum.

(Granted, the probability that someone would want to add a non-installable erratum to a content view is small, but the fact that the hammer command method can accomplish this while the web UI method cannot is a discrepancy.)

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.