Bug 1713511 - Upgrade from F30 to Rawhide fails due to podman problems (latest F31 build is older than latest F30 build, files conflict)
Summary: Upgrade from F30 to Rawhide fails due to podman problems (latest F31 build is...
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: podman
Version: rawhide
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lokesh Mandvekar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: openqa
Keywords:
Depends On:
Blocks: BetaBlocker, F31BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2019-05-23 22:55 UTC by Adam Williamson
Modified: 2019-05-24 15:08 UTC (History)
8 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2019-05-24 15:03:46 UTC


Attachments (Terms of Use)

Description Adam Williamson 2019-05-23 22:55:42 UTC
Upgrades of Fedora 30 Workstation to Fedora Rawhide currently fail due to podman packaging issues. The following error occurs when you try the update:

dnf.exceptions.Error: Transaction check error:
  file /usr/share/man/man1/podman-container.1.gz from install of podman-2:1.3.0-21.dev.gitb01fdcb.fc31.x86_64 conflicts with file from package podman-manpages-2:1.3.1-1.git7210727.fc30.noarch
  file /usr/share/man/man1/podman-cp.1.gz from install of podman-2:1.3.0-21.dev.gitb01fdcb.fc31.x86_64 conflicts with file from package podman-manpages-2:1.3.1-1.git7210727.fc30.noarch
  file /usr/share/man/man1/podman-create.1.gz from install of podman-2:1.3.0-21.dev.gitb01fdcb.fc31.x86_64 conflicts with file from package podman-manpages-2:1.3.1-1.git7210727.fc30.noarch
  file /usr/share/man/man1/podman-events.1.gz from install of podman-2:1.3.0-21.dev.gitb01fdcb.fc31.x86_64 conflicts with file from package podman-manpages-2:1.3.1-1.git7210727.fc30.noarch
  file /usr/share/man/man1/podman-generate.1.gz from install of podman-2:1.3.0-21.dev.gitb01fdcb.fc31.x86_64 conflicts with file from package podman-manpages-2:1.3.1-1.git7210727.fc30.noarch
  file /usr/share/man/man1/podman-info.1.gz from install of podman-2:1.3.0-21.dev.gitb01fdcb.fc31.x86_64 conflicts with file from package podman-manpages-2:1.3.1-1.git7210727.fc30.noarch
  file /usr/share/man/man1/podman-pod-top.1.gz from install of podman-2:1.3.0-21.dev.gitb01fdcb.fc31.x86_64 conflicts with file from package podman-manpages-2:1.3.1-1.git7210727.fc30.noarch
  file /usr/share/man/man1/podman-run.1.gz from install of podman-2:1.3.0-21.dev.gitb01fdcb.fc31.x86_64 conflicts with file from package podman-manpages-2:1.3.1-1.git7210727.fc30.noarch
  file /usr/share/man/man1/podman-system.1.gz from install of podman-2:1.3.0-21.dev.gitb01fdcb.fc31.x86_64 conflicts with file from package podman-manpages-2:1.3.1-1.git7210727.fc30.noarch
  file /usr/share/man/man1/podman-top.1.gz from install of podman-2:1.3.0-21.dev.gitb01fdcb.fc31.x86_64 conflicts with file from package podman-manpages-2:1.3.1-1.git7210727.fc30.noarch
  file /usr/share/man/man1/podman-varlink.1.gz from install of podman-2:1.3.0-21.dev.gitb01fdcb.fc31.x86_64 conflicts with file from package podman-manpages-2:1.3.1-1.git7210727.fc30.noarch
  file /usr/share/man/man1/podman.1.gz from install of podman-2:1.3.0-21.dev.gitb01fdcb.fc31.x86_64 conflicts with file from package podman-manpages-2:1.3.1-1.git7210727.fc30.noarch

Note that we're trying to go from 2:1.3.1-1.git7210727.fc30 to 2:1.3.0-21.dev.gitb01fdcb.fc31 - the F30 package is, or at least appears to be, newer than the Rawhide package.

Looking at the build history in koji:

https://koji.fedoraproject.org/koji/packageinfo?packageID=26289

we can see that the most recent Rawhide build attempt, podman-1.3.1-0.1.dev.git9ae3221.fc31 , failed, which is probably part of the problem.

BTW, we *also* see that it is lower-versioned than the most recent F30 build, podman-1.3.1-1.git7210727.fc30 . This is because the pre-release versioning has been corrected, but the correction was not accompanied by an epoch bump. That should be fixed too, i.e. the epoch for builds done with the 'corrected' pre-release versioning needs to be bumped to 3...

Comment 1 Adam Williamson 2019-05-23 22:56:44 UTC
Proposing as a Beta blocker as a violation of "For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from a fully updated, clean default installation of each of the last two stable Fedora releases with that package set installed" - because there's a file conflict here, even `--allowerasing` doesn't let the upgrade proceed.

Comment 2 Daniel Walsh 2019-05-24 09:26:54 UTC
Lokesh it looks like your automatic builds are failing in Rawhide.  I will force a build.

Comment 3 Daniel Walsh 2019-05-24 09:35:03 UTC
Building podman-1.3.1-1.1.dev.git5296428.fc31 which should fix this bugzilla, but we need to fix the automatic builder.

Comment 4 Lokesh Mandvekar 2019-05-24 10:13:38 UTC
Dan, the release tag bump should be -0.2.dev instead of 1.1 for unreleased builds. But I guess we can fix that when the next version goes out.

Comment 5 Lokesh Mandvekar 2019-05-24 10:16:14 UTC
(In reply to Daniel Walsh from comment #3)
> Building podman-1.3.1-1.1.dev.git5296428.fc31 which should fix this
> bugzilla, but we need to fix the automatic builder.

I had to disable automatic builds to fix release tags, I'll enable them as and when we have new versions going out.

Comment 6 Daniel Walsh 2019-05-24 11:55:26 UTC
Lokesh, I kicked off

https://koji.fedoraproject.org/koji/taskinfo?taskID=35028668

But I am not sure if this is going to build.  I am on PTO Today, so could you fix this, if it fails to build.
I was seeing issues with the installion of podman-remote for some reason.

Comment 8 Adam Williamson 2019-05-24 15:08:34 UTC
OK, so long as you don't do a '1.3.2-1.1.dev....' build in F30 or anything, this should be fine now. Thanks.


Note You need to log in before you can comment on or make changes to this bug.