Created attachment 1505539[details]
File contains playbook log
Description of problem:
After running rolling-update, monitor service with fqdn is getting enabled which due to which there will be a failed monitor service in the list. I think this induces confusion in user.
Version-Release number of selected component (if applicable):
3.2.0~rc1-2redhat1
How reproducible:
Always
Steps to Reproduce:
1. Configure a cluster and run rolling updated
Actual results:
Before rolling update -
$ ll /etc/systemd/system/ceph-mon.target.wants/
total 8
drwxr-xr-x 2 root root 4096 Nov 14 03:41 ./
drwxr-xr-x 14 root root 4096 Nov 14 03:42 ../
lrwxrwxrwx 1 root root 37 Nov 14 03:41 ceph-mon -> /lib/systemd/system/ceph-mon@.service
After rolling update -
$ ll /etc/systemd/system/ceph-mon.target.wants/
total 8
drwxr-xr-x 2 root root 4096 Nov 14 04:13 ./
drwxr-xr-x 14 root root 4096 Nov 14 03:42 ../
lrwxrwxrwx 1 root root 37 Nov 14 04:13 ceph-mon.redhat.com.service -> /lib/systemd/system/ceph-mon@.service
lrwxrwxrwx 1 root root 37 Nov 14 03:41 ceph-mon -> /lib/systemd/system/ceph-mon@.service
Expected results:
No extr services should get enabled
Additional info:
1) Hostnames were FQDN
2) $ sudo systemctl list-units |grep "ceph-mon"
* ceph-mon.redhat.com.service loaded failed failed Ceph cluster monitor daemon
ceph-mon loaded active running Ceph cluster monitor daemon
We haven't really qualified this bug, we don't know if it's valid or not. So I'm not sure what to write as a known issue, since we haven't really determined if this was actually a bug.
Comment 17Ameena Suhani S H
2019-11-06 02:50:30 UTC
Guillaume,
The log in c13 contains errors of this bz https://bugzilla.redhat.com/show_bug.cgi?id=1766499.
After rolling_update please execute [1] to reproduce the current bug issue
[1] $ll /etc/systemd/system/ceph-mon.target.wants/
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:1320
Created attachment 1505539 [details] File contains playbook log Description of problem: After running rolling-update, monitor service with fqdn is getting enabled which due to which there will be a failed monitor service in the list. I think this induces confusion in user. Version-Release number of selected component (if applicable): 3.2.0~rc1-2redhat1 How reproducible: Always Steps to Reproduce: 1. Configure a cluster and run rolling updated Actual results: Before rolling update - $ ll /etc/systemd/system/ceph-mon.target.wants/ total 8 drwxr-xr-x 2 root root 4096 Nov 14 03:41 ./ drwxr-xr-x 14 root root 4096 Nov 14 03:42 ../ lrwxrwxrwx 1 root root 37 Nov 14 03:41 ceph-mon -> /lib/systemd/system/ceph-mon@.service After rolling update - $ ll /etc/systemd/system/ceph-mon.target.wants/ total 8 drwxr-xr-x 2 root root 4096 Nov 14 04:13 ./ drwxr-xr-x 14 root root 4096 Nov 14 03:42 ../ lrwxrwxrwx 1 root root 37 Nov 14 04:13 ceph-mon.redhat.com.service -> /lib/systemd/system/ceph-mon@.service lrwxrwxrwx 1 root root 37 Nov 14 03:41 ceph-mon -> /lib/systemd/system/ceph-mon@.service Expected results: No extr services should get enabled Additional info: 1) Hostnames were FQDN 2) $ sudo systemctl list-units |grep "ceph-mon" * ceph-mon.redhat.com.service loaded failed failed Ceph cluster monitor daemon ceph-mon loaded active running Ceph cluster monitor daemon