Description of problem: When the user mis-configures variables they will sometimes wait 10s of minutes before discovering the error and many times the error is not clear. Version-Release number of selected component (if applicable): stable-3.1 How reproducible: 100% Steps to Reproduce: 1. Enable non-default config and skip a step 2. invoke playbook 3. observe description Actual results: playbook runs for more than a minute and appears to be working. then the playbook halts due to misconfig in step 2. Expected results: playbook invocation runs for a minute or less and fails with mis-configurations before making changes to the system Additional info: https://github.com/ceph/ceph-ansible/pull/2555
For the initial v3.2.0beta2 ceph-ansible builds, I forgot to add the python-notario dependency to ceph-ansible.spec and debian/control downstream. I'll fix that after the next ceph-ansible upstream tag (probably 3.2.0beta3).
Hi, While trying to bring up containerized cluster though playbook is failing in step ceph-validate : validate provided configuration trying to validate ceph_repository_type. msg- Validation failed for variable: ceph_repository_type\n[magna024] Reason: ceph_repository_type must be either 'cdn' or 'iso'\n[magna024] Given value for ceph_repository_type: dummy" I think we don't need to validate the repository type when user wants containerized scenario. Please let me know your views. Moving back to ASSIGNED state. Regards, Vasishta Shatsry QE, Ceph
Upstream pull request opened at https://github.com/ceph/ceph-ansible/pull/3287
https://github.com/ceph/ceph-ansible/releases/tag/v3.2.0rc2
All planned testcases are completed. Issue found during testing > Bug 1648168 - ceph-validate : devices are not validated in non-collocated and lvm_batch scenario is being release noted as known issue. Moving this RFE to VERIFIED state.
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-2019:0020