Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2218206

Summary: [RFE] RFE to include an option for ostree local system updates to upload .tar file and manage unzip process into a given location.
Product: Red Hat Enterprise Linux 9 Reporter: dialvare
Component: cockpitAssignee: Martin Pitt <mpitt>
Status: CLOSED MIGRATED QA Contact: Jan Ščotka <jscotka>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.2CC: release-test-team-automation, tgunders
Target Milestone: rcKeywords: FutureFeature, MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-15 14:15:13 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description dialvare 2023-06-28 13:00:23 UTC
When performing ostree local updates, users need to upload the .tar file generated with the Edge Commit to a server and then unpack them into an specific directory. The request is for including this functionality in the UI so the upload and unpackaging processes can be handled by cockpit.

Something like: adding a "upload commit" option in the UI, and when there's a new commit staged a "reboot into it" option.

Comment 2 Martin Pitt 2023-06-30 07:03:54 UTC
> the .tar file generated with the Edge Commit

Hmm, that feels like a sad user experience. You have to download a huge tarball from the system that builds the edge image to some laptop/workstation, and upload it again to the destination machine?

What other output options does your image build process offer? Is that the image builder on cloud.redhat.com (Sorry, I'm not very familiar with it), or a self-hosted instance?. In my experience, OSTree builds result in either some http-accessible OSTree repository (classic), or pushing it as OCI container image into some registry [1], which is relatively new, but super convenient. We are working on cockpit-ostree support for the latter [2].

CC'ing Tom as the image builder lead for your interest, maybe you also have some ideas about how this should look like.

[1] https://fedoraproject.org/wiki/Changes/OstreeNativeContainerStable
[2] https://issues.redhat.com/browse/COCKPIT-928

Comment 3 RHEL Program Management 2023-09-15 14:13:14 UTC
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.

Comment 4 RHEL Program Management 2023-09-15 14:15:13 UTC
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.