Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1348166

Summary: 2.0: /api/v2/cluster/<fs-id>/server does not display fqdn correctly
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Harish NV Rao <hnallurv>
Component: CalamariAssignee: Christina Meno <gmeno>
Calamari sub component: Back-end QA Contact: Harish NV Rao <hnallurv>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: ceph-eng-bugs, gmeno, kdreyer
Version: 2.0   
Target Milestone: rc   
Target Release: 2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: calamari-server-1.4.3-1.el7cp Ubuntu: calamari-server_1.4.3-2redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-23 19:42:12 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
/api/v2/cluster/<fs-id>/server does not display fqdn correctly none

Description Harish NV Rao 2016-06-20 10:29:15 UTC
Created attachment 1169829 [details]
/api/v2/cluster/<fs-id>/server does not display fqdn correctly

Description of problem:

 fqdn is displayed properly for the mon where calamari-lite is running. For rest of the nodes, it displays only host shortname. 

output of  /api/v2/cluster/<fsid>/server will be attached.

Tested on:
calamari-server-1.4.1-1.el7cp.x86_64
ceph version 10.2.2-1.el7cp

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Christina Meno 2016-06-21 20:46:38 UTC
https://github.com/ceph/calamari/pull/470

Comment 10 errata-xmlrpc 2016-08-23 19:42:12 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://rhn.redhat.com/errata/RHBA-2016-1755.html