Bug 1649617

Summary: rolling-update - ubuntu - extra monitor service with fqdn getting enabled
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasishta <vashastr>
Component: Ceph-AnsibleAssignee: Dimitri Savineau <dsavinea>
Status: CLOSED ERRATA QA Contact: Ameena Suhani S H <amsyedha>
Severity: medium Docs Contact:
Priority: low    
Version: 3.2CC: amsyedha, aschoen, ceph-eng-bugs, ceph-qe-bugs, dsavinea, gabrioux, gmeno, hnallurv, jbrier, kdreyer, nthomas, shan, tchandra, tserlin
Target Milestone: z4Keywords: TestOnly
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.2.37-1.el7cp Ubuntu: ceph-ansible_3.2.37-2redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-06 08:27:04 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:
Attachments:
Description Flags
File contains playbook log
none
Ansible rolling update logs none

Description Vasishta 2018-11-14 04:48:06 UTC
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

Comment 3 Sébastien Han 2018-11-20 21:38:24 UTC
Can you share your group_var files?

Comment 6 Sébastien Han 2018-12-17 13:43:47 UTC
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 7 John Brier 2018-12-17 15:49:18 UTC
Okay. I removed it from the Release Notes tracker so we won't mention anything about it in the Release Notes.

Comment 8 Giridhar Ramaraju 2019-08-05 13:09:53 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 9 Giridhar Ramaraju 2019-08-05 13:11:04 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 13 Ameena Suhani S H 2019-10-29 08:43:10 UTC
Created attachment 1630042 [details]
Ansible rolling update logs

Comment 17 Ameena 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/

Comment 25 errata-xmlrpc 2020-04-06 08:27:04 UTC
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