Missing log files for Ceph iSCSI gateway

[Nobuto Murata]

In Ceph iSCSI gateway usage, there are some additional logs or config files for analyzing issues on top of what sosreport collects as of today for Ceph.
https://docs.ceph.com/en/latest/rbd/iscsi-overview/

Would be nice if the following files are collected for such a use case.

- /etc/ceph/iscsi/ceph.conf <- already collected as a part of ceph_common plugin
- /etc/ceph/iscsi-gateway.cfg <- already collected as a part of ceph_common plugin
- /etc/tcmu/tcmu.conf <- missing
- /var/log/ceph/ceph-client.iscsi.log <- missing
- /var/log/rbd-target-api/rbd-target-api.log <- missing
- /var/log/rbd-target-gw/rbd-target-gw.log <- missing
- /var/log/tcmu-runner.log <- missing

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: sosreport 4.4-1ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
Uname: Linux 5.4.0-135-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Dec 29 04:51:39 2022
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: sosreport
UpgradeStatus: No upgrade log present (probably fresh install)

[Nobuto Murata (nobuto)]

https://github.com/sosreport/sos/pull/3099

[Bryce Harrington (bryce)]

Thanks for letting us know of this issue you've reported upstream. I've added a link to the upstream project so hopefully this bug will get flagged when the fix is landed upstream.

I assume the logs will get included when just running plain `sosreport`? Or are there flags that need included to reproduce?

Hopefully if that gets taken upstream and a new release provided, Debian will package the new release and we can merge it in for 23.04. If you're interested in seeing this included as an SRU for 20.04 and 22.04, let us know; this looks eligible for SRU consideration, but there'll be some additional validation steps required.

[Nobuto Murata (nobuto)]

> Thanks for letting us know of this issue you've reported upstream. I've added a link to the upstream project so hopefully this bug will get flagged when the fix is landed upstream.

Thanks for linking, I wasn't sure how to do it :-)

> I assume the logs will get included when just running plain `sosreport`? Or are there flags that need included to reproduce?

Yes, the logic is if a package is installed, or systemd services are running, the new module gets automatically run.

> Hopefully if that gets taken upstream and a new release provided, Debian will package the new release and we can merge it in for 23.04. If you're interested in seeing this included as an SRU for 20.04 and 22.04, let us know; this looks eligible for SRU consideration, but there'll be some additional validation steps required.

I'm not in super hurry of this. Considering sosreport is a part of MRE, this new module will be available for stable releases eventually as usual.

[Christian Ehrhardt  (paelzer)]

Merged upstream, there are regular backport by SEG of the recent versions.
So this will show up over time and as Nobotu said it isn't urgent.

[Arif Ali (arif-ali)]

Hi Team,

This was released upstream with version 4.5.1.

The sosreport snap is currently available from the latest/stable channel with version 4.5.3

The sosreport 4.5.3 is currently going through the backport and will come in soon in [1]

[1] https://launchpad.net/bugs/2018270

[Lena Voytek (lvoytek)]

Looks like this has been fixed in mantic with the release of 4.5.4, marking as fix-released. This fix should arrive in other versions soon too as they are all marked as Fix Commited in (LP: #2022915)