Re: Respinning rawhide images every filesystem update?
On Thu, Aug 06, 2020 at 12:02:09PM -0400, Alex Scheel wrote: > - Original Message - > > From: "Stephen John Smoogen" > > To: "Development discussions related to Fedora" > > > > Sent: Thursday, August 6, 2020 10:55:51 AM > > Subject: Re: Respinning rawhide images every filesystem update? > > > > On Thu, 6 Aug 2020 at 10:05, Alex Scheel wrote: > > > > > > - Original Message - > > > > From: "Stephen John Smoogen" > > > > To: "Development discussions related to Fedora" > > > > , asch...@redhat.com > > > > Sent: Thursday, August 6, 2020 9:55:17 AM > > > > Subject: Re: Respinning rawhide images every filesystem update? > > > > > > > > On Thu, 6 Aug 2020 at 09:36, Alex Scheel wrote: > > > > > > > > > > I'm bumping this thread. This is still broken. > > > > > > > > > > > > > Please open a ticket at > > > > https://pagure.io/fedora-infrastructure/new_issue and open new issue > > > > with an explanation of what is broken and where you are pulling from. > > > > If it is a fedora registry then infrastructure can work on a fix. If > > > > it is from docker.io or quay or elsewhere we can try to find the > > > > people who fix it and let them know. > > > > > > Opened: > > > > > > https://pagure.io/fedora-infrastructure/issue/9208 > > > > > > This was also posted to devel to hopefully get the attention of the > > > filesystem maintainer. > > > > > > > > > They seem to have ignored 1548403 since 2018. :-) > > > > > > > > > > OK so this ticket clarifies the problem because I thought this was a > > problem with the filesystem in the container image with how it is spun > > or delivered. It is instead with the package filesystem. Here is the > > ticket contents (since most people don't follow links in emails). > > There's three ways to solve this: > > 1) Make the filesystem upgrade nicely in a container, or > 2) Have the container runtime/user namespace system/... support the > type of change that upgrading the filesystem package makes, or > 3) Just respin the container image quickly whenever this happens; this > hides the problem from users without solving the problem. > > 1 isn't happening because the maintainer isn't involved. > 2 isn't happening because the container runtime maintainers punted on it. > 3 is the easiest left to accomplish. But I am confused, because as far as I can tell this is already happening. > If I had a choice, I'd be really happy with 3. I don't know what > all is involved to respin container images with a new package. I'm > sure it takes time, but I'd imagine it'd be mostly automated. The > problem gets fixed eventually anyways. It is automated. It happens every compose of rawhide. I am not sure why you are not seeing the new images. Are you pulling from registry.fedoraproject.org? kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Respinning rawhide images every filesystem update?
- Original Message - > From: "Stephen John Smoogen" > To: "Development discussions related to Fedora" > > Sent: Thursday, August 6, 2020 10:55:51 AM > Subject: Re: Respinning rawhide images every filesystem update? > > On Thu, 6 Aug 2020 at 10:05, Alex Scheel wrote: > > > > - Original Message - > > > From: "Stephen John Smoogen" > > > To: "Development discussions related to Fedora" > > > , asch...@redhat.com > > > Sent: Thursday, August 6, 2020 9:55:17 AM > > > Subject: Re: Respinning rawhide images every filesystem update? > > > > > > On Thu, 6 Aug 2020 at 09:36, Alex Scheel wrote: > > > > > > > > I'm bumping this thread. This is still broken. > > > > > > > > > > Please open a ticket at > > > https://pagure.io/fedora-infrastructure/new_issue and open new issue > > > with an explanation of what is broken and where you are pulling from. > > > If it is a fedora registry then infrastructure can work on a fix. If > > > it is from docker.io or quay or elsewhere we can try to find the > > > people who fix it and let them know. > > > > Opened: > > > > https://pagure.io/fedora-infrastructure/issue/9208 > > > > This was also posted to devel to hopefully get the attention of the > > filesystem maintainer. > > > > > > They seem to have ignored 1548403 since 2018. :-) > > > > > > OK so this ticket clarifies the problem because I thought this was a > problem with the filesystem in the container image with how it is spun > or delivered. It is instead with the package filesystem. Here is the > ticket contents (since most people don't follow links in emails). There's three ways to solve this: 1) Make the filesystem upgrade nicely in a container, or 2) Have the container runtime/user namespace system/... support the type of change that upgrading the filesystem package makes, or 3) Just respin the container image quickly whenever this happens; this hides the problem from users without solving the problem. 1 isn't happening because the maintainer isn't involved. 2 isn't happening because the container runtime maintainers punted on it. 3 is the easiest left to accomplish. If I had a choice, I'd be really happy with 3. I don't know what all is involved to respin container images with a new package. I'm sure it takes time, but I'd imagine it'd be mostly automated. The problem gets fixed eventually anyways. - Alex (Arguably there is 4, quit rebuilding the filesystem package needlessly, but we seem to like mass-rebuilds of all packages, and it might set a weird precedence if we special case things). > filesystem package breaks Fedora containers because dnf cannot > successfully update the package. See: > > https://bugzilla.redhat.com/show_bug.cgi?id=1548403 > https://bugzilla.redhat.com/show_bug.cgi?id=1708249 > > 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: > > > > filesystem x86_64 3.14-3.fc33 rawhide 1.1 M > > > > Upgrading: filesystem-3.14-3.fc33.x86_64 3/341 > Error unpacking rpm package filesystem-3.14-3.fc33.x86_64 > > > > Failed: > filesystem-3.14-2.fc32.x86_64 filesystem-3.14-3.fc33.x86_64 > > Error: Transaction failed > > > -- > Stephen J Smoogen. > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidel
Re: Respinning rawhide images every filesystem update?
On Thu, 6 Aug 2020 at 10:05, Alex Scheel wrote: > > - Original Message - > > From: "Stephen John Smoogen" > > To: "Development discussions related to Fedora" > > , asch...@redhat.com > > Sent: Thursday, August 6, 2020 9:55:17 AM > > Subject: Re: Respinning rawhide images every filesystem update? > > > > On Thu, 6 Aug 2020 at 09:36, Alex Scheel wrote: > > > > > > I'm bumping this thread. This is still broken. > > > > > > > Please open a ticket at > > https://pagure.io/fedora-infrastructure/new_issue and open new issue > > with an explanation of what is broken and where you are pulling from. > > If it is a fedora registry then infrastructure can work on a fix. If > > it is from docker.io or quay or elsewhere we can try to find the > > people who fix it and let them know. > > Opened: > > https://pagure.io/fedora-infrastructure/issue/9208 > > This was also posted to devel to hopefully get the attention of the > filesystem maintainer. > > > They seem to have ignored 1548403 since 2018. :-) > > OK so this ticket clarifies the problem because I thought this was a problem with the filesystem in the container image with how it is spun or delivered. It is instead with the package filesystem. Here is the ticket contents (since most people don't follow links in emails). filesystem package breaks Fedora containers because dnf cannot successfully update the package. See: https://bugzilla.redhat.com/show_bug.cgi?id=1548403 https://bugzilla.redhat.com/show_bug.cgi?id=1708249 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: filesystem x86_64 3.14-3.fc33 rawhide 1.1 M Upgrading: filesystem-3.14-3.fc33.x86_64 3/341 Error unpacking rpm package filesystem-3.14-3.fc33.x86_64 Failed: filesystem-3.14-2.fc32.x86_64 filesystem-3.14-3.fc33.x86_64 Error: Transaction failed -- Stephen J Smoogen. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Respinning rawhide images every filesystem update?
- Original Message - > From: "Stephen John Smoogen" > To: "Development discussions related to Fedora" > , asch...@redhat.com > Sent: Thursday, August 6, 2020 9:55:17 AM > Subject: Re: Respinning rawhide images every filesystem update? > > On Thu, 6 Aug 2020 at 09:36, Alex Scheel wrote: > > > > I'm bumping this thread. This is still broken. > > > > Please open a ticket at > https://pagure.io/fedora-infrastructure/new_issue and open new issue > with an explanation of what is broken and where you are pulling from. > If it is a fedora registry then infrastructure can work on a fix. If > it is from docker.io or quay or elsewhere we can try to find the > people who fix it and let them know. Opened: https://pagure.io/fedora-infrastructure/issue/9208 This was also posted to devel to hopefully get the attention of the filesystem maintainer. They seem to have ignored 1548403 since 2018. :-) - Alex > > Without that information, it is very likely it will stay broken unless > fixed by accident because no one knows what is meant by 'still broken' > > > - Original Message - > > > From: "Alex Scheel" > > > To: "Development discussions related to Fedora" > > > > > > Sent: Monday, August 3, 2020 2:36:40 PM > > > Subject: Respinning rawhide images every filesystem update? > > > > > > Hey list, > > > > > > > > > How do Fedora rawhide images get respun? Every time filesystem updates, > > > it causes `dnf update` to fail in a podman container because filesystem > > > can't be updated in a container. We either need to make sure filesystem > > > updates cause rawhide containers to be rebuilt, or figure out how to > > > ship a container-friendly filesystem package. > > > > > > > > > See: > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1548403 > > > https://bugzilla.redhat.com/show_bug.cgi?id=1708249 > > > > > > > > > And I'm sure many other discussions. > > > > > > - Alex > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > > > -- > Stephen J Smoogen. > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Respinning rawhide images every filesystem update?
On Thu, 6 Aug 2020 at 09:36, Alex Scheel wrote: > > I'm bumping this thread. This is still broken. > Please open a ticket at https://pagure.io/fedora-infrastructure/new_issue and open new issue with an explanation of what is broken and where you are pulling from. If it is a fedora registry then infrastructure can work on a fix. If it is from docker.io or quay or elsewhere we can try to find the people who fix it and let them know. Without that information, it is very likely it will stay broken unless fixed by accident because no one knows what is meant by 'still broken' > - Original Message - > > From: "Alex Scheel" > > To: "Development discussions related to Fedora" > > > > Sent: Monday, August 3, 2020 2:36:40 PM > > Subject: Respinning rawhide images every filesystem update? > > > > Hey list, > > > > > > How do Fedora rawhide images get respun? Every time filesystem updates, > > it causes `dnf update` to fail in a podman container because filesystem > > can't be updated in a container. We either need to make sure filesystem > > updates cause rawhide containers to be rebuilt, or figure out how to > > ship a container-friendly filesystem package. > > > > > > See: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1548403 > > https://bugzilla.redhat.com/show_bug.cgi?id=1708249 > > > > > > And I'm sure many other discussions. > > > > - Alex > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- Stephen J Smoogen. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Respinning rawhide images every filesystem update?
I'm bumping this thread. This is still broken. - Original Message - > From: "Alex Scheel" > To: "Development discussions related to Fedora" > > Sent: Monday, August 3, 2020 2:36:40 PM > Subject: Respinning rawhide images every filesystem update? > > Hey list, > > > How do Fedora rawhide images get respun? Every time filesystem updates, > it causes `dnf update` to fail in a podman container because filesystem > can't be updated in a container. We either need to make sure filesystem > updates cause rawhide containers to be rebuilt, or figure out how to > ship a container-friendly filesystem package. > > > See: > > https://bugzilla.redhat.com/show_bug.cgi?id=1548403 > https://bugzilla.redhat.com/show_bug.cgi?id=1708249 > > > And I'm sure many other discussions. > > - Alex ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Respinning rawhide images every filesystem update?
On Mon, Aug 03, 2020 at 02:36:40PM -0400, Alex Scheel wrote: > Hey list, > > > How do Fedora rawhide images get respun? Every time filesystem updates, They are rebuild in every rawhide nightly compose. Here's the one from last night/this morning: https://koji.fedoraproject.org/koji/taskinfo?taskID=48713559 They are then pushed into our registry. > it causes `dnf update` to fail in a podman container because filesystem > can't be updated in a container. We either need to make sure filesystem > updates cause rawhide containers to be rebuilt, or figure out how to > ship a container-friendly filesystem package. Where are you pulling from? Our registry? docker.io? quay? kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Respinning rawhide images every filesystem update?
Hey list, How do Fedora rawhide images get respun? Every time filesystem updates, it causes `dnf update` to fail in a podman container because filesystem can't be updated in a container. We either need to make sure filesystem updates cause rawhide containers to be rebuilt, or figure out how to ship a container-friendly filesystem package. See: https://bugzilla.redhat.com/show_bug.cgi?id=1548403 https://bugzilla.redhat.com/show_bug.cgi?id=1708249 And I'm sure many other discussions. - Alex ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
