This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2112040 - size of edge container .tar is shown as 0 GB
Summary: size of edge container .tar is shown as 0 GB
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: cockpit-composer
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jacob
QA Contact: Xiaofeng Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-28 17:36 UTC by Micah Abbott
Modified: 2023-09-18 12:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 12:42:02 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
finished image showing 0GB size (36.57 KB, image/png)
2022-07-28 17:36 UTC, Micah Abbott 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4586 0 None Migrated None 2023-09-18 12:41:56 UTC
Red Hat Issue Tracker RHELPLAN-129514 0 None None None 2022-07-28 17:38:03 UTC

Description Micah Abbott 2022-07-28 17:36:57 UTC 
Created attachment 1900015 [details]
finished image showing 0GB size

On a RHEL 9 system with Image Builder installed, after completing the creation of a "RHEL for Edge Container" image, the listing on the web UI shows the size as 0 GB

See attached screenshot.

Obviously, the tarball is not O GB as shown below using the CLI:

```
[root@localhost ~]# composer-cli compose list 
11bdcae5-1620-4c09-80da-1b7543d5b90b FINISHED edge 0.0.1 edge-container
[root@localhost ~]# composer-cli compose image 11bdcae5-1620-4c09-80da-1b7543d5b90b
11bdcae5-1620-4c09-80da-1b7543d5b90b-container.tar
[root@localhost ~]# ls -lh 11bdcae5-1620-4c09-80da-1b7543d5b90b-container.tar 
-rw-------. 1 root root 675M Jul 28 13:35 11bdcae5-1620-4c09-80da-1b7543d5b90b-container.tar
```

Relevant RPMs:

```
# rpm -qa | grep -e cockpit -e osbuild | sort
cockpit-264.1-1.el9.x86_64
cockpit-bridge-264.1-1.el9.x86_64
cockpit-composer-36-1.el9_0.noarch
cockpit-packagekit-264.1-1.el9.noarch
cockpit-system-264.1-1.el9.noarch
cockpit-ws-264.1-1.el9.x86_64
osbuild-53.1-1.el9_0.noarch
osbuild-composer-46.3-1.el9_0.x86_64
osbuild-composer-core-46.3-1.el9_0.x86_64
osbuild-composer-dnf-json-46.3-1.el9_0.x86_64
osbuild-composer-worker-46.3-1.el9_0.x86_64
osbuild-luks2-53.1-1.el9_0.noarch
osbuild-lvm2-53.1-1.el9_0.noarch
osbuild-ostree-53.1-1.el9_0.noarch
osbuild-selinux-53.1-1.el9_0.noarch
python3-osbuild-53.1-1.el9_0.noarch
subscription-manager-cockpit-1.29.26-3.el9_0.noarch
```
Comment 1 Yi He 2022-07-29 13:46:11 UTC 
Reproduced this bug in my rhel9.0 machine, and I tried more edge image types, here is the result:

1. For edge-commit, edge-container and edge-installer image type, the size is 0 GB, this is not correct.

2. For simplified-installer type, the size is 10 GB, this number is much more larger than the actual size, which is about 862M.
[root@yih-rhel90 rhel-edge]# ls -l
total 4703012
-rw-------. 1 root root  862976000 Jul 28 23:19 169e21a2-3be0-4752-987c-8620c874e745-simplified-installer.iso
Comment 2 Jacob 2022-08-23 10:39:58 UTC 
Not all image types support custom image size. Can you reverify this for release 39? The customizations better reflect what osbuild-composer supports now.
Comment 3 RHEL Program Management 2023-09-18 12:39:42 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-18 12:42:02 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.
Note You need to log in before you can comment on or make changes to this bug.