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 2130237 - containers config.json gets empty after sudden power loss [rhel-8.6.0.z]
Summary: containers config.json gets empty after sudden power loss [rhel-8.6.0.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Alex Jia
URL:
Whiteboard:
Depends On: 2126697 2136270
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-27 15:19 UTC by RHEL Program Management Team
Modified: 2022-12-06 14:20 UTC (History)
12 users (show)

Fixed In Version: podman-4.1.1-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2126697
Environment:
Last Closed: 2022-10-25 09:33:30 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers podman pull 15982 0 None Merged [v4.1.1-rhel] Backport #15799 2022-09-30 06:56:09 UTC
Red Hat Issue Tracker RHELPLAN-135039 0 None None None 2022-09-27 15:38:18 UTC
Red Hat Product Errata RHBA-2022:7127 0 None None None 2022-10-25 09:33:45 UTC

Comment 1 Matthew Heon 2022-09-28 15:51:54 UTC 
Backport PR https://github.com/containers/podman/pull/15982
Comment 2 Matthew Heon 2022-09-28 17:51:14 UTC 
Merged
Comment 3 Tom Sweeney 2022-09-28 20:46:46 UTC 
Assigning to @jnovy for any further BZ or packaging needs.
Comment 7 Alex Jia 2022-10-13 10:57:05 UTC 
This bug has been verified on podman-4.1.1-7.module+el8.6.0+16889+9f154fa9 with netavark network backend.


[root@test-8-6-0-bz2130237 ~]# podman inspect foo | grep -iA2 args
WARN[0000] Error unmarshalling container 9afb33215d1e46cd37aba0940d276278c1a4d520cffe7fb5f93fea9412ef3db5 config: readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||... 
          "Args": [
               "infinity"
          ],


[root@test-8-6-0-bz2126697 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.6 (Ootpa)

[root@test-8-6-0-bz2126697 ~]# grep network_backend /usr/share/containers/containers.conf
#network_backend = ""
network_backend = "netavark"

[root@test-8-6-0-bz2126697 ~]# rpm -q podman runc netavark systemd kernel
podman-4.1.1-7.module+el8.6.0+16889+9f154fa9.x86_64
runc-1.1.3-2.module+el8.6.0+16771+28dfca77.x86_64
netavark-1.0.1-35.module+el8.6.0+15917+093ca6f8.x86_64
systemd-239-58.el8.x86_64
kernel-4.18.0-372.9.1.el8.x86_64
Comment 11 errata-xmlrpc 2022-10-25 09:33:30 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (container-tools:rhel8 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:7127
Note You need to log in before you can comment on or make changes to this bug.