Bug 1763918
| Summary: | Container build should include the k8sevents mgr module rpm | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Paul Cuzner <pcuzner> |
| Component: | Container | Assignee: | Dimitri Savineau <dsavinea> |
| Status: | CLOSED ERRATA | QA Contact: | Vasishta <vashastr> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.0 | CC: | bniver, branto, ceph-eng-bugs, dsavinea, gabrioux, kdreyer, tserlin, vashastr |
| Target Milestone: | rc | ||
| Target Release: | 4.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHCEPH-4.0-RHEL-8-20191127.ci.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-31 14:44:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Paul Cuzner
2019-10-21 22:47:27 UTC
No, the backport PR to nautilus about packaging isn't merged yet https://github.com/ceph/ceph/pull/30215 So there's no rpm packages available at this time. Also we will need to wait for the next Nautilus minor release upstream (probably 14.2.5) before integrate this to the container image. Then we will wait for downstream to resync to that minor release. Any update on this? 30215 merged last week - so when is this likely to land, so we can start testing in an OCS build? Normally the PR 30215 will be included in the next upstream Ceph Nautilus v14.2.5 release. Until this release isn't out then we can't make the change in ceph-container upstream because we need the associated rpm package. Finally this feature is unlikely to be present in RHCS 4.0 or in the following z streams because the current Ceph version in RHCS 4.0 is 14.2.4 This will probably be included in 4.1. Just trying to understand the process here. The feature is merged in master and backported to nautilus. I can see the rpm in shaman builds for nautilus - https://2.chacra.ceph.com/r/ceph/nautilus/9989c20373e2294b7479ec4bd6ac5cce80b01645/centos/7/flavors/default/noarch/ which shows it as a 14.2.4 based version not 14.2.5 so what needs to happen to include this rpm into the upstream and downstream containers. I'm unfamiliar with the process here - so please provide some guidance on how we can move this forward. OCS requires this feature The ceph-container project doesn't use builds from shaman for nautilus but stable release from download.ceph.com [1]. Shaman is used for unreleased ceph content which is only consume by ceph-container project for master branch. [2] is basically 14.2.4 + all the commits on the nautilus branch since that release. This should be included in 14.2.5 [1] https://download.ceph.com/rpm-nautilus/el7/noarch/ [2] https://2.chacra.ceph.com/r/ceph/nautilus/9989c20373e2294b7479ec4bd6ac5cce80b01645/centos/7/flavors/default/noarch/ Hi Dimitri, we have this feature/package back-ported downstream. In fact, we have had it back-ported donwstream for some time, now (even before the upstream nautilus PR was merged). You can see the package e.g. in the latest downstream ceph builds, here: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1018962 Can you make a ds-only change to the container that will pull the package to the container until upstream releases 14.2.5 (which should be fairly soon iirc)? Thanks, Boris Dimitry - what's the latest here? Is that going to be part of RHCS 4.0 (and sooner, for OCS 4.2 GA) ? $ ssh magna109 sudo docker exec ceph-mon-magna109 rpm -qa|grep k8sevents ceph-mgr-k8sevents-14.2.4-85.el8cp.noarch chacked container with tag ceph-4.0-rhel-8-containers-candidate-52417-20191217061816 Moving to VERIFIED state. Regards, Vasishta QE, Ceph Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0313 |