Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1585903

Summary: Deployment of external ceph with UI: CephClusterFSID didn't get the right value.
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: rhosp-director-uiAssignee: Jason E. Rist <jrist>
Status: CLOSED DUPLICATE QA Contact: Arik Chernetsky <achernet>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: beth.white, jpichon, jtomasek, sasha
Target Milestone: gaKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-06 15:00:45 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
plan-environment.yaml none

Description Alexander Chuzhoy 2018-06-05 04:27:53 UTC 
Deployment of external ceph with UI: CephClusterFSID didn't get the right value.

Environment:
instack-undercloud-8.4.1-4.el7ost.noarch
openstack-tripleo-heat-templates-8.0.2-29.el7ost.noarch
openstack-tripleo-ui-8.3.1-2.el7ost.noarch

Attempted external ceph deployment with UI.

Included a yaml for external ceph deployment.

CephClientKey, CephExternalMonHost fields got the right values.

CephClusterFSID field didn't get the right value.
Comment 1 Julie Pichon 2018-06-06 08:07:49 UTC 
This sounds like https://bugs.launchpad.net/tripleo/+bug/1664521 (the fix is intricate and related to merging environments, and has been slowly worked on over the last few releases). In general when using the UI it's better to use the UI to set parameters. In OSP13, that would mean enabling the External Ceph environment in the overall settings (under Storage), and then modify CephClusterFSID in Parameters -> Externally Managed Ceph.
Comment 2 Jiri Tomasek 2018-06-06 13:02:51 UTC 
Can you please provide plan-environment.yaml and also check the parameter value in UI as Julie described above? I agree that most likely we're hitting the bug Julie referenced. Especially if you added custom environment file which carries the parameter value for CephClusterFSID (I can clearly ientify that if you provide plan-environment.yaml)
Comment 3 Alexander Chuzhoy 2018-06-06 13:34:46 UTC 
Created attachment 1448344 [details]
plan-environment.yaml
Comment 4 Jiri Tomasek 2018-06-06 15:00:45 UTC 
I am closing this as a duplicate of 1541721 as this issue was caused by incorrect order of environment files.

*** This bug has been marked as a duplicate of bug 1541721 ***