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 Jira Cloud for all bug tracking management.

Bug 1502841

Summary: Containerized deployment should not succeed if osd_scenario is unset
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: John Fulton <johfulto>
Component: Ceph-AnsibleAssignee: John Fulton <johfulto>
Status: CLOSED CURRENTRELEASE QA Contact: Vasishta <vashastr>
Severity: high Docs Contact:
Priority: high    
Version: 3.0CC: adeza, anharris, aschoen, ceph-eng-bugs, gfidente, gmeno, hnallurv, johfulto, jschluet, kdreyer, nthomas, sankarshan, tchandra, vashastr
Target Milestone: rc   
Target Release: 3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.1.0-0.1.beta3.el7cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-26 16:15:35 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:
Bug Depends On:    
Bug Blocks: 1548353    

Description John Fulton 2017-10-16 20:20:49 UTC
A ceph-ansible site-docker.yml run [1][2] produced a deployment with 0 failures and 0 OSDs because the osd_scenario variable was not set. I think this should have failed. 

As per the "make sure an osd scenario was chosen" task in check_mandatory_vars.yml [3] the deployment will fail if an osd_scenario is not chosen. However, the when condition does not do this check for a containerized deployment. Why should this check not be done for a containerized deployment? If the code to check this is somewhere else, why wasn't it executed? 

Additional info:
- The logs show that both scenarios were skipped [4]. 
- If you search the --extra-vars input to ansible-playbook it will show no scenario was passed. This is an error on part of the process calling the playbook, but ceph-ansible should have failed that deployment request. 


[1] Resulting run: http://paste.openstack.org/show/623760/
[2] Playbook command with --extra-vars http://paste.openstack.org/show/623752/
[3] https://github.com/ceph/ceph-ansible/blob/b685aceede71a2dc872ce140ac636a7301f471f6/roles/ceph-osd/tasks/check_mandatory_vars.yml

[4] 
2017-10-16 10:16:00,713 p=12340 u=mistral |  TASK [ceph-osd : include scenarios/collocated.yml] *****************************
2017-10-16 10:16:00,729 p=12340 u=mistral |  skipping: [192.168.24.15]
2017-10-16 10:16:00,735 p=12340 u=mistral |  TASK [ceph-osd : include scenarios/non-collocated.yml] *************************
2017-10-16 10:16:00,753 p=12340 u=mistral |  skipping: [192.168.24.15]

Comment 6 John Fulton 2017-10-24 16:55:51 UTC
Setting this to POST as the changes have merged upstream. 

 https://github.com/ceph/ceph-ansible/pull/2097

Comment 9 Ken Dreyer (Red Hat) 2018-03-19 15:57:03 UTC
John would you please confirm this is fixed in v3.1.0beta3 (or v3.1.0beta4)?

Comment 10 John Fulton 2018-03-23 03:07:50 UTC
(In reply to Ken Dreyer (Red Hat) from comment #9)
> John would you please confirm this is fixed in v3.1.0beta3 (or v3.1.0beta4)?

I confirm this is fixed. I tested with v3.1.0beta4.