Description of problem: When running ovirt-engine-extension-aaa-ldap-setup with a config file with a bad profile name, there is no validation to inform the user that the profile does not match any of the existing. Version-Release number of selected component (if applicable): ovirt-engine-extension-aaa-ldap-setup-1.3.1-0.0.master.20170115190508.gitda48d9d.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Create a config file with the following contents: [environment:default] OVAAALDAP_LDAP/profile=str:bad_profile 2. Execute: ovirt-engine-extension-aaa-ldap-setup --config=setup.conf 3. Manually input following values Actual results: Setup tool is executed successfully Expected results: Setup tool reports bad profile Additional info: Valid profile names: ad 389ds isds ipa iplanet openldap rfc2307-generic rfc2307-389ds rfc2307-isds rfc2307-rhds rfc2307-edir rfc2307-openldap rfc2307-rhds
Fix is contained in ovirt-engine-extension-aaa-ldap-1.3.1
Verified with: ovirt-engine-extension-aaa-ldap-setup-1.3.1-1.el7ev.noarch [ ERROR ] Failed to execute stage 'Environment customization': Profile bad_profile was not found.