Description of problem: Introduce a repository with Debug packages in addition to the repos introduced with the 2.0 release.
Is this because "debuginfo-install ceph" does not work in 2.0? The reason for this is that there is no longer a "ceph" package and therefore you need to specify the name of one of the ceph subpackages for debuginfo-install to check the "basename" (fuzzy on the specifics here so please take this with a grain of salt) of the package. "debuginfo-install ceph-osd" will install the ceph-debuginfo package from the rhel-7-server-rhceph-2-mon-debug-rpms channel. I'm not sure whether there is a way to set up an "alias" so we can run "debuginfo-install ceph" and have it find the correct package?
I see this was meant to be specific to the Ubuntu packages and their debuginfo but it brings to light the issue of the ceph-debuginfo package installation on rhel.
Brad, could you please add a separate bug for under target=2.2?
See https://bugzilla.redhat.com/show_bug.cgi?id=1375425 for the rhel specific debuginfo-install issue.
Current status: we generate debug info packages for both RHEL and Ubuntu, but only the RHEL ones are available to customers. The Ubuntu debug info packages are for some reason huge — 8GB worth of them. The solution of choice is to add this to the online repositories for Ubuntu in 2.2, adjusting bug accordingly.
https://github.com/red-hat-storage/rhcephcompose/pull/41 gets us half-way there, but needs more work to generate the apt repodata (and more testing).
PR 41 mentioned above is still in progress; re-targeting to the next release
(In reply to Ken Dreyer (Red Hat) from comment #11) > PR 41 mentioned above is still in progress; re-targeting to the next release Will this be fixed in 2.3?
This feature competes with other priorities in 2.3. Re-targeting to a future release.
Andrew, the CI composes we do for Ubuntu currently have debug repos disabled because it is so heavyweight. In other words, we dynamically inject "include_dbg = False" into the jenkins.conf file during each rcm-jenkins job run. rhcephcompose defaults "include_dbg" to True if it is unset in the config, and rhcs-metadata.git/ceph-3/ceph-3.0-ubuntu.conf does not have this option set. In other words, when you run rhcephcompose by hand for 3.0, it will create the -dbg repository. When you generate the RHCEPH 3.0 beta, would you please ensure that output for QE includes the -dbg repo? Then the QE team will have something to test here.
Sure. How should we organize the repository delivery? .../ubuntu/3-beta{,-dbg}?
Sure, that sounds good.
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-2017:3387