I just repushed the 16.2.6 container with remoto 1.2.1 in it. On 9/22/21 4:19 PM, David Orman wrote: > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-4b2736a28c > > ^^ if people want to test and provide feedback for a potential merge > to EPEL8 stable. > > David > > On Wed, Sep 22, 2021 at 11:43 AM David Orman <ormandj@xxxxxxxxxxxx> wrote: >> >> I'm wondering if this was installed using pip/pypi before, and now >> switched to using EPEL? That would explain it - 1.2.1 may never have >> been pushed to EPEL. >> >> David >> >> On Wed, Sep 22, 2021 at 11:26 AM David Orman <ormandj@xxxxxxxxxxxx> wrote: >>> >>> We'd worked on pushing a change to fix >>> https://tracker.ceph.com/issues/50526 for a deadlock in remoto here: >>> https://github.com/alfredodeza/remoto/pull/63 >>> >>> A new version, 1.2.1, was built to help with this. With the Ceph >>> release 16.2.6 (at least), we see 1.1.4 is again part of the >>> containers. Looking at EPEL8, all that is built now is 1.1.4. We're >>> not sure what happened, but would it be possible to get 1.2.1 pushed >>> to EPEL8 again, and figure out why it was removed? We'd then need a >>> rebuild of the 16.2.6 containers to 'fix' this bug. >>> >>> This is definitely a high urgency bug, as it impacts any deployments >>> with medium to large counts of OSDs or split db/wal devices, like many >>> modern deployments. >>> >>> https://koji.fedoraproject.org/koji/packageinfo?packageID=18747 >>> https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/Packages/p/ >>> >>> Respectfully, >>> David Orman > _______________________________________________ > Dev mailing list -- dev@xxxxxxx > To unsubscribe send an email to dev-leave@xxxxxxx > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |