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 1706713

Summary: Ansible playbook is failing for ceph-osd task
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Uday kurundwade <ukurundw>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Uday kurundwade <ukurundw>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: aschoen, assingh, ceph-eng-bugs, ceph-qe-bugs, dsavinea, gmeno, nthomas, tchandra, tserlin, ymane
Target Milestone: rc   
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-ansible-4.0.0-0.1.rc7.el8cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-31 12:45:57 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:

Description Uday kurundwade 2019-05-06 06:56:09 UTC 
Description of problem:
Ansible playbook is failing for ceph-osd task

Version-Release number of selected component (if applicable):
ceph-ansible-4.0.0-0.rc3.10.ga718ddec.el8cp.noarch
ansible-2.8.0-0.8.rc1.el8ae.noarch

How reproducible:
Always

Steps to Reproduce:
1.run ansible-playbook site.yml 
2.
3.

Actual results:

ERROR! 'static' is not a valid attribute for a TaskInclude

The error appears to be in '/usr/share/ceph-ansible/roles/ceph-osd/tasks/main.yml': line 69, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


- name: include_tasks scenarios/lvm.yml
  ^ here



Expected results:
Playbook should complete successfully.

Additional info:
Comment 7 errata-xmlrpc 2020-01-31 12:45:57 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:0312