Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-95717

[ostree]ostree fsck always failed

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • rhel-10.1, rhel-9.7
    • ostree
    • None
    • No
    • None
    • rhel-image-mode
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      What were you trying to do that didn't work?

      after run podman run \
          --rm \
          --tls-verify=false \
          --privileged \
          --pid=host \
          -v /:/target \
          -v /dev:/dev \
          -v /var/lib/containers:/var/lib/containers \
          --security-opt label=type:unconfined_t \
          localhost/bootc:beaker \
          bash -c "bootc install to-existing-root --target-transport containers-storage" and reboot. Wait system come back and run ostree fsck with error. 

      What is the impact of this issue to you?

      ostree fsck always show error

      Please provide the package NVR for which the bug is seen:

      images.paas.redhat.com/bootc/rhel-bootc:RHEL-10.1-20250603.1

      How reproducible is this bug?: 100%

      Steps to reproduce

      1. run below commands
      # podman run \
          --rm \
          --tls-verify=false \
          --privileged \
          --pid=host \
          -v /:/target \
          -v /dev:/dev \
          -v /var/lib/containers:/var/lib/containers \
          --security-opt label=type:unconfined_t \
          localhost/bootc:beaker \
          bash -c "bootc install to-existing-root --target-transport containers-storage" 
      # reboot 
      # ostree fsck
      Validating refs...
      Validating refs in collections...
      Enumerating commits...
      Verifying content integrity of 67 commit objects...
      fsck objects (1576/95667) [             ]   1%
      error: In commits 0fd37298f63f155ee59c84ab5bb036434321288216ece7462cc8757dabdc5524, 3c9737201890fb011c709b591fa35aa7a5b4c2b9717da807683d436d6a522c40: fsck content object 86ff96a4fb6718db6830933c041172d140b018425f3477e8bf147b71e61e285b: Corrupted file object; checksum expected='86ff96a4fb6718db6830933c041172d140b018425f3477e8bf147b71e61e285b' actual='350efd747b6c2f0dd1d52866cddc0b79ab0fc8ed4e19eb5ee7defd845bffe5ee'
      

      Expected results

      ostree fsck should no error raised.

      Actual results

      # ostree fsck
      Validating refs...
      Validating refs in collections...
      Enumerating commits...
      Verifying content integrity of 67 commit objects...
      fsck objects (1576/95667) [             ]   1%
      error: In commits 0fd37298f63f155ee59c84ab5bb036434321288216ece7462cc8757dabdc5524, 3c9737201890fb011c709b591fa35aa7a5b4c2b9717da807683d436d6a522c40: fsck content object 86ff96a4fb6718db6830933c041172d140b018425f3477e8bf147b71e61e285b: Corrupted file object; checksum expected='86ff96a4fb6718db6830933c041172d140b018425f3477e8bf147b71e61e285b' actual='350efd747b6c2f0dd1d52866cddc0b79ab0fc8ed4e19eb5ee7defd845bffe5ee'

              coreos-bot CoreOS Bot
              mhou@redhat.com HOU MINXI
              CoreOS Bot CoreOS Bot
              CoreOS QE Bot CoreOS QE Bot
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: