Hi,

the workflow changed in 8.7 - we are in the process of aligning the cockpit-composer UI to the one in the hosted service. You don't add packages in the page on your screenshot. You need to go to "Create Image", and select the packages in the (3) Packages section of the wizard. I will attach an image of it.

@jkozol Can we make it more obvious? Might be also worth connecting with @elpereir and document the changes.

Steve, can you verify that this works?

Thanks!

Created attachment 1926079 [details]
RHEL 8.7 - the new workflow for packages

@jcastran @sbarcomb Thank you for the feedback. 

We agree that the 8.7/9.1 state of blueprint creation is not as intuitive as it should be. This is all part of general update in cockpit-composer to simplify the process of blueprint and image creation. Ideally, for the 8.8/9.2 release there will be a single wizard to guide the user through creating a blueprint and optionally building an image. After creation, each blueprint can also be editted in its details page using single step modals identical to the step in the wizard. Also, the wizard will allow selection of an existing blueprint in case a user wants an expedited process of image creation.

This allows for three routes to image creation:

1) User creates an image from a predefined blueprint by selecting it in the wizard and using an "expedited" image create.
2) User enters all customizations for an image, saves this as a new blueprint, and creates the image.
3) User enters some or all customizations for an image, saves this as a new blueprint. Later, the User can edit the blueprint in the details page. Also, the User can follow steps 1 or 2 to create an image (with option 2 updating the blueprint instead of creating a new one).

This will match the workflow users would experience in Image Builder on consoledot while also supporting centralized blueprint creation.

I will be demoing our current progress towards this near the end of the quarter. Are you on the composer mailing list?

So is there a way to stop this change for RHEL 8 since it's fairly late in the game for RHEL 8. Customers who are used to things would much prefer changes in the from of new features, as opposed to "reorganizing" things for the sake of moving them around. I've already got one customer completely confused by the changes.

I would love to see this new feature as I've already got RFE's in mind for what I'd like to see get accomplished or included.

1. Creating a blueprint should be a full create blueprint, not just a title creation
2. You should be able to make edits in the various blueprint tabs. Allowing you to add a package or user without having to do a full wizard each time
3. The button "create image" should not be the only way to edit a blueprint
4. We should have a import blueprint function (if we have one, i've missed it) so that people can graphically import files without having to use a cli


Image Builder on consoledot is missing so many features that are possible in Image Builder. It doesn't allow you to import a blueprint, it doesn't allow you to add users, it doesn't allow you to review a blueprint. Everytyhing has to be done through a full wizard, and then you get almost no information in return. I would have hoped we intended to make consoledot more like a locally hosted image builder, as opposed to the opposite.

@jcastran I understand your concern about moving things around. This was a result of us doing a complete rewrite of the underlying data management system in cockpit-composer to meet modern standards. But, this update will allow all of the RFE's you mentioned. All 4 of these are already part of our 8.8 and 9.2 plans. Here are some of the epics tracking this work:

https://issues.redhat.com/browse/COMPOSER-1777
https://issues.redhat.com/browse/COMPOSER-1751
https://issues.redhat.com/browse/COMPOSER-1666

@jkozol It doesn't look like we've updated documentation to reflect this change either. 

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/composing_installing_and_managing_rhel_for_edge_images/composing-rhel-for-edge-images-using-image-builder-in-rhel-web-console_composing-installing-managing-rhel-for-edge-images

We will need to update any documentation that references how to use image builder in the Web UI

@jkozol Seems this bug is already well documented, can we close this bug?

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

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 "RHEL-" 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.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days