#9208 Rebuild fedora imgaes on r.fp.o after every `filesystem` package update
Closed: Invalid a month ago by cverna. Opened 2 months ago by cipherboy.

Describe what you would like us to do:


filesystem package breaks Fedora containers because dnf cannot successfully update the package. See:

Every time filesystem updates, it causes this problem. The solution is to rebuild Fedora containers with the new filesystem package upgrade, so dnf upgrade will already have the updated filesystem package.

Alternatively, the filesystem maintainer could make their package container friendly.

This is from the main Fedora registry:

[ascheel@ascheel-p50 ~]$ podman run -ti registry.fedoraproject.org/fedora:rawhide /bin/bash
[root@5808bc88f6ab /]# dnf update --refresh -y
Fedora 33 openh264 (From Cisco) - x86_64      6.9 kB/s | 5.1 kB     00:00    
Fedora - Modular Rawhide - Developmental pack 2.6 MB/s | 3.1 MB     00:01    
Fedora - Rawhide - Developmental packages for  17 MB/s |  73 MB     00:04    
Dependencies resolved.
==============================================================================
 Package                     Arch   Version                     Repo     Size
==============================================================================
Upgrading:

<snip>

 filesystem                  x86_64 3.14-3.fc33                 rawhide 1.1 M

<snip>

  Upgrading        : filesystem-3.14-3.fc33.x86_64                      3/341 
Error unpacking rpm package filesystem-3.14-3.fc33.x86_64

<snip>

Failed:
  filesystem-3.14-2.fc32.x86_64         filesystem-3.14-3.fc33.x86_64        

Error: Transaction failed

When do you need this to be done by? (YYYY/MM/DD)


Within a couple of days of filesystem updating would be nice. Upstream CIs running on Fedora Rawhide tend to break. Recurring.


Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: groomed, high-trouble, medium-gain

2 months ago

I couldn't replicate it as I got the latest filesystem when I pulled in the rawhide container.

$ podman run -ti registry.fedoraproject.org/fedora:rawhide /bin/bash
Trying to pull registry.fedoraproject.org/fedora:rawhide...
Getting image source signatures
Copying blob 212604468f72 done  
Copying config 2fb8781cfd done  
Writing manifest to image destination
Storing signatures
[root@70e6864d6419 /]# dnf update --refresh -y
Fedora 33 openh264 (From Cisco) - x86_64                                  7.0 kB/s | 5.1 kB     00:00    
Fedora - Modular Rawhide - Developmental packages for the next Fedora rel 3.5 MB/s | 3.1 MB     00:00    
Fedora - Rawhide - Developmental packages for the next Fedora release     4.8 MB/s |  73 MB     00:15    
Dependencies resolved.
Nothing to do.
Complete!
[root@70e6864d6419 /]# rpm -q filesystem
filesystem-3.14-3.fc33.x86_64

Metadata Update from @mohanboddu:
- Issue untagged with: groomed, high-trouble, medium-gain
- Issue priority set to: Needs Review (was: Waiting on Assignee)

2 months ago

Metadata Update from @pingou:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: groomed, high-trouble, medium-gain

2 months ago

The rawhide container image is updated nightly so you need to make sure that you have the latest image locally when running podman. You can use the --pull always flag to ask podman to always pull the image before running the container

podman run -ti --rm --pull always registry.fedoraproject.org/fedora:rawhide /bin/bash

Metadata Update from @cverna:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

a month ago

Login to comment on this ticket.

Metadata