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.
DescriptionFrantišek Hrdina
2021-09-15 11:06:03 UTC
Description of problem:
/CoreOS/filesystem/Regression/Fail-to-update-filesystem-inside-systemd-nspawn is failing on rhel9. Upgrade of filesystem inside of container is failing. Log is in the Additional info section.
Not sure if expected.
Version-Release number of selected component (if applicable):
filesystem.x86_64 3.16-2.el9
How reproducible: always
Steps to Reproduce:
1. Run test
Actual results:
Upgrade of filesystem inside of container failed
Expected results:
Upgrade of filesystem inside of container should be successful
Additional info:
Test log:
Spawning container test-container on /var/lib/machines/test-container.
Press ^] three times within 1s to kill container.
Selected user namespace base 749273088 and range 65536.
Failed to correct timezone of container, ignoring: Value too large for defined data type
Failed to copy /etc/resolv.conf to /var/lib/machines/test-container/etc/resolv.conf, ignoring: Value too large for defined data type
Failed to create /var/log/journal: Value too large for defined data type
Spawning container test-container on /var/lib/machines/test-container.
Press ^] three times within 1s to kill container.
Selected user namespace base 749273088 and range 65536.
Failed to correct timezone of container, ignoring: Value too large for defined data type
Failed to copy /etc/resolv.conf to /var/lib/machines/test-container/etc/resolv.conf, ignoring: Value too large for defined data type
Failed to create /var/log/journal: Value too large for defined data type