bots icon indicating copy to clipboard operation
bots copied to clipboard

Image refresh for centos-9-bootc

Open github-actions[bot] opened this issue 1 year ago • 1 comments

Image refresh for centos-9-bootc

  • [ ] FAIL: image-refresh centos-9-bootc

github-actions[bot] avatar May 09 '24 22:05 github-actions[bot]

Failed. Log: https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-centos-9-bootc-69a94492-20240509-223727/log.html

cockpituous avatar May 09 '24 22:05 cockpituous

I can reproduce this locally. growpart /dev/vda 4 is failing, but without stderr output. Will investigate with --sit.

allisonkarlitskaya avatar May 13 '24 09:05 allisonkarlitskaya

Oh fun. --sit doesn't apply to the bootstrap step.

allisonkarlitskaya avatar May 13 '24 10:05 allisonkarlitskaya

The error is logged to stdout, which is why we don't get it. It's:

NOCHANGE: partition 4 is size 59787231. it cannot be grown

meanwhile, the partition table looks like

 252        0   31457280 vda
 252        1       1024 vda1
 252        2     513024 vda2
 252        3    1048576 vda3
 252        4   29893615 vda4
Device       Start      End  Sectors  Size Type
/dev/vda1     2048     4095     2048    1M BIOS boot
/dev/vda2     4096  1030143  1026048  501M EFI System
/dev/vda3  1030144  3127295  2097152    1G Linux filesystem
/dev/vda4  3127296 62914526 59787231 28.5G Linux filesystem

with

/dev/vda4        29G  1.7G   27G   6% /sysroot

allisonkarlitskaya avatar May 13 '24 10:05 allisonkarlitskaya

From the journal:

May 13 10:29:19 centos-9-bootczq42yjen-127-0-0-2 bootc-generic-growpart[789]: CHANGED: partition=4 start=3127296 old: size=17844191 end=20971486 new: size=59787231 end=62914526
May 13 10:29:19 centos-9-bootczq42yjen-127-0-0-2 systemd-growfs[791]: Successfully resized "/sysroot" to 28.5G bytes (3584 bytes lost due to blocksize).
○ bootc-generic-growpart.service - Bootc Fallback Root Filesystem Grow
     Loaded: loaded (/usr/lib/systemd/system/bootc-generic-growpart.service; static)
     Active: inactive (dead) since Mon 2024-05-13 10:29:19 UTC; 6min ago
   Duration: 2.723s
       Docs: https://gitlab.com/fedora/bootc/docs
    Process: 530 ExecStart=/usr/libexec/bootc-generic-growpart (code=exited, status=0/SUCCESS)
   Main PID: 530 (code=exited, status=0/SUCCESS)
        CPU: 160ms

May 13 10:29:16 localhost systemd[1]: Started Bootc Fallback Root Filesystem Grow.
May 13 10:29:16 localhost bootc-generic-growpart[530]: Backing device: /dev/vda4
May 13 10:29:19 centos-9-bootczq42yjen-127-0-0-2 bootc-generic-growpart[789]: CHANGED: partition=4 start=3127296 old: size=17844191 end=20971486 new: size=59787231 end=62914526
May 13 10:29:19 centos-9-bootczq42yjen-127-0-0-2 systemd-growfs[791]: Successfully resized "/sysroot" to 28.5G bytes (3584 bytes lost due to blocksize).
May 13 10:29:19 centos-9-bootczq42yjen-127-0-0-2 systemd[1]: bootc-generic-growpart.service: Deactivated successfully.

So it looks like the image does this automatically on startup now (as a result of us having increased the disk image size). I'll drop the explicit call.

allisonkarlitskaya avatar May 13 '24 10:05 allisonkarlitskaya

→ #6375

allisonkarlitskaya avatar May 13 '24 10:05 allisonkarlitskaya