On Tue, Jul 11, 2023 at 6:07 AM Alfredo Moralejo Alonso amoralej@redhat.com wrote:

Hi,

I've observed that a new build has been created in CBS https://cbs.centos.org/koji/buildinfo?buildID=49831 but it has epoch 1 while a previous one has epoch 2 https://cbs.centos.org/koji/buildinfo?buildID=40574 so still the old one is pulled.

Apparently epoch was decreased in https://git.centos.org/rpms/ceph/c/0ca9b1baa36c3e1184535f619cf82909616d1012?...

sigh. that broke between 17.2.3 and 17.2.4, almost a year ago, and nobody has noticed.

(I'm not sure what to make of that. It kinda suggests — to me — that nobody, or very few people, are using storage sig packages.)

Packages with correct epoch are building now.

Regards,

Alfredo

On Mon, Jul 10, 2023 at 4:11 PM Alfredo Moralejo Alonso < amoralej@redhat.com> wrote:

...

Hi,

After the update of liburing in centos stream 9, we are having issues to install ceph and qemu-kvm together:

# dnf install ceph qemu-kvm Last metadata expiration check: 0:01:00 ago on Mon Jul 10 14:02:55 2023. Error: Problem: cannot install both liburing-2.3-2.el9.x86_64 and liburing-0.7-7.el9.x86_64

• package qemu-kvm-core-17:8.0.0-6.el9.x86_64 requires

liburing.so.2()(64bit), but none of the providers can be installed

• package qemu-kvm-core-17:8.0.0-6.el9.x86_64 requires

liburing.so.2(LIBURING_2.0)(64bit), but none of the providers can be installed

• package ceph-osd-2:17.2.3-2.el9s.x86_64 requires

liburing.so.1()(64bit), but none of the providers can be installed

• package ceph-osd-2:17.2.3-2.el9s.x86_64 requires

liburing.so.1(LIBURING_0.1)(64bit), but none of the providers can be installed

• package qemu-kvm-17:8.0.0-6.el9.x86_64 requires qemu-kvm-core =

17:8.0.0-6.el9, but none of the providers can be installed

• package ceph-2:17.2.3-2.el9s.x86_64 requires ceph-osd =

2:17.2.3-2.el9s, but none of the providers can be installed

• cannot install the best candidate for the job

Any help from storage sig will be appreciated.

Best regards,

Alfredo

---

CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel

Hi Kaleb,

RDO, which is part of the Cloud SIG, is also using Ceph to provide storage, and it's working well so far. The Epoch downgrade made us pull 17.2.3 until yesterday, we caught it in CI lastly because of the last promotion in CS Base repos, as Alfredo said. As it was a .Z update, that may explain the delay why it took time to catch it. But, better late than never I'd say.

In any case, thank you for your work. Joel

On Tue, Jul 11, 2023 at 3:58 PM Carlos Rodriguez-Fernandez < carlosrodrifernandez@gmail.com> wrote:

Hi Kaleb, Our company uses Ceph to provide storage to Kubernetes in all environments all the way to production. They are all on CentOS 7. We are currently getting ready to migrate to CS9 (which we have in many servers already) or RHEL9.

We haven't found this issue probably because we are still in CentOS 7, and I don't think we install qemu-kvm on them either.

I'm glad to hear that this was found.

Thank you, Carlos R.F.

On 7/11/23 04:45, Kaleb Keithley wrote:

...

On Tue, Jul 11, 2023 at 6:07 AM Alfredo Moralejo Alonso <amoralej@redhat.com mailto:amoralej@redhat.com> wrote:

Hi,

I've observed that a new build has been created in CBS
https://cbs.centos.org/koji/buildinfo?buildID=49831
<https://cbs.centos.org/koji/buildinfo?buildID=49831> but it has
epoch 1 while a previous one has epoch 2
https://cbs.centos.org/koji/buildinfo?buildID=40574
<https://cbs.centos.org/koji/buildinfo?buildID=40574> so still the
old one is pulled.

Apparently epoch was decreased in

https://git.centos.org/rpms/ceph/c/0ca9b1baa36c3e1184535f619cf82909616d1012?... < https://git.centos.org/rpms/ceph/c/0ca9b1baa36c3e1184535f619cf82909616d1012?...

...

sigh. that broke between 17.2.3 and 17.2.4, almost a year ago, and nobody has noticed.

(I'm not sure what to make of that. It kinda suggests — to me — that nobody, or very few people, are using storage sig packages.)

Packages with correct epoch are building now.

Regards,

Alfredo


On Mon, Jul 10, 2023 at 4:11 PM Alfredo Moralejo Alonso
<amoralej@redhat.com <mailto:amoralej@redhat.com>> wrote:

    Hi,

    After the update of liburing in centos stream 9, we are having
    issues to install ceph and qemu-kvm together:

    # dnf install ceph qemu-kvm
    Last metadata expiration check: 0:01:00 ago on Mon Jul 10
    14:02:55 2023.
    Error:
      Problem: cannot install both liburing-2.3-2.el9.x86_64 and
    liburing-0.7-7.el9.x86_64
       - package qemu-kvm-core-17:8.0.0-6.el9.x86_64 requires
    liburing.so.2()(64bit), but none of the providers can be

installed

...

       - package qemu-kvm-core-17:8.0.0-6.el9.x86_64 requires
    liburing.so.2(LIBURING_2.0)(64bit), but none of the providers
    can be installed
       - package ceph-osd-2:17.2.3-2.el9s.x86_64 requires
    liburing.so.1()(64bit), but none of the providers can be

installed

...

       - package ceph-osd-2:17.2.3-2.el9s.x86_64 requires
    liburing.so.1(LIBURING_0.1)(64bit), but none of the providers
    can be installed
       - package qemu-kvm-17:8.0.0-6.el9.x86_64 requires
    qemu-kvm-core = 17:8.0.0-6.el9, but none of the providers can be
    installed
       - package ceph-2:17.2.3-2.el9s.x86_64 requires ceph-osd =
    2:17.2.3-2.el9s, but none of the providers can be installed
       - cannot install the best candidate for the job

    Any help from storage sig will be appreciated.

    Best regards,

    Alfredo


_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org <mailto:CentOS-devel@centos.org>
https://lists.centos.org/mailman/listinfo/centos-devel
<https://lists.centos.org/mailman/listinfo/centos-devel>

--

Kaleb

---

CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel

---

CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel