That might also be a factor, but I think the actual reason is that I neglected to set the -release tags on the 16.2.14 builds. Give them a chance to propagate out to the mirrors and then the update to 16.2.14 should work now. On Mon, Oct 23, 2023 at 10:45 AM Francesco Pantano <fpantano at redhat.com> wrote: > Hi Luis, > I think the issue you've hit is basically related to the fact that for > Pacific we split the > cephadm package from the Ceph tree due to some bugs we experienced in the > OpenStack CI. > I've built and tagged the missing package (16.2.14) you were looking for > [0][1][2], and I > think from the next build we can re-add cephadm to the main Ceph tree. > /cc @Kaleb Keithley <kkeithle at redhat.com> > > > Thanks, > > [0] https://cbs.centos.org/koji/buildinfo?buildID=51357 > [1] https://cbs.centos.org/koji/buildinfo?buildID=51358 > [2] https://cbs.centos.org/koji/buildinfo?buildID=51359 > > On Mon, Oct 23, 2023 at 1:13 PM Luis Domingues via CentOS-devel < > centos-devel at centos.org> wrote: > >> Hello everyone. >> >> We sae ceph released ceph 16.2.14, and we want to upgrade to it. >> >> I can see on the build service that the build for el8 was done, but when >> I check the updates, I do not see any updates to 16.2.14. >> >> And if I look at: >> http://mirror.centos.org/centos-8/8/storage/x86_64/ceph-pacific/Packages/c/, >> I do not see them as well. >> >> Will 16.2.14 be pushed to el8 repos? >> >> Thanks, >> Luis Domingues >> Proton AG >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel at centos.org >> https://lists.centos.org/mailman/listinfo/centos-devel >> > > > -- > Francesco Pantano > GPG KEY: F41BD75C > -- Kaleb -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20231023/6d44f24c/attachment.html>