Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Add org.osbuild.dmverity stage patch" #3844

Merged
merged 2 commits into from
Aug 13, 2024

Commits on Aug 12, 2024

  1. Revert "Add org.osbuild.dmverity stage patch"

    This reverts commit 180be1b.
    
    That patch is in the latest osbuild in Fedora now.
    jlebon committed Aug 12, 2024
    Configuration menu
    Copy the full SHA
    f73ee35 View commit details
    Browse the repository at this point in the history

Commits on Aug 13, 2024

  1. cmdlib: workaround rofiles-fuse mounts leaking

    This started happening in CI:
    
    ```
    + mount -o remount,ro /srv/cache
    mount: /srv/cache: mount point is busy.
           dmesg(1) may have more information after failed mount system call.
    [  321.026584] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00002000
    ```
    
    Digging into it, it seems to be due to leftover rofiles-fuse mounts:
    
    ```
    + ps aux
    ...
    root       306  0.0  0.1 401092  3972 ?        Ssl  15:46   0:00 rofiles-fuse --copyup usr /tmp/rpmostree-rofiles-fuse0QroLi
    root       311  0.0  0.1 251564  2488 ?        Ssl  15:46   0:00 rofiles-fuse --copyup etc /tmp/rpmostree-rofiles-fuseANAAgx
    root       330  0.0  0.2 474828  4120 ?        Ssl  15:46   0:00 rofiles-fuse --copyup usr /tmp/rpmostree-rofiles-fuseioSZ7r
    root       334  0.0  0.1 251564  2712 ?        Ssl  15:46   0:00 rofiles-fuse --copyup etc /tmp/rpmostree-rofiles-fusePPGBR9
    ...
    ```
    
    For some reason, rpm-ostree is not able to unmount those.
    
    We should dig into this but as a brutal workaround, just kill them
    manually. There's no data loss concerns here; the commit has already
    been written and shipped out via virtiofs.
    
    The issue remains tracked at
    coreos#3848.
    jlebon committed Aug 13, 2024
    Configuration menu
    Copy the full SHA
    de27dc9 View commit details
    Browse the repository at this point in the history