Created attachment 1519066 [details] ovirt-hosted-engine-setup_log_files Description of problem: Deploymnet via ''ovirt-hosted-engine-setup'' fails with error "Error during SSO authentication access_denied : Cannot authenticate user 'None@N/A': No valid profile found in credentials.." Version-Release number of selected component (if applicable): [root@ovirt-node-01 ~]# rpm -qa |grep ovirt-hosted ovirt-hosted-engine-ha-2.2.18-1.el7.noarch ovirt-hosted-engine-setup-2.2.32-1.el7.noarch How reproducible: Deploy self hosted engine from CLI or cockpit Steps to Reproduce: 1. Download newest ovirt-node image from http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64/lastSuccessfulBuild/artifact/exported-artifacts/latest-installation-iso.html (in my case ovirt-node-ng-installer-4.2.0-2019010606.el7.iso) 2. Provision Host with iso 3. Deploy self hosted engine (via CLI or Cockpit) Actual results: [root@ovirt-node-01 ~]# grep ERROR /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20190107192908-kxbhqe.log 2019-01-07 19:53:45,906+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:98 AuthError: Error during SSO authentication access_denied : Cannot authenticate user 'None@N/A': No valid profile found in credentials.. 2019-01-07 19:53:46,007+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:98 fatal: [localhost]: FAILED! => {"changed": false, "deprecations": [{"msg": "The 'ovirt_vms_facts' module is being renamed 'ovirt_vm_facts'", "version": 2.8}], "msg": "Error during SSO authentication access_denied : Cannot authenticate user 'None@N/A': No valid profile found in credentials.."} 2019-01-07 19:53:46,410+0100 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Closing up': Failed executing ansible-playbook 2019-01-07 19:54:20,423+0100 ERROR otopi.plugins.gr_he_common.core.misc misc._terminate:248 Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Expected results: Successful deployment of ovirt manager Additional info:
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0. If you think this bug should block 4.3.0 please re-target and set blocker flag.
Moving to 4.3.2 not being identified as blocker for 4.3.1.
Are you able to reproduce with oVirt Node 4.3?
Closing as duplicate of bug #1660595 *** This bug has been marked as a duplicate of bug 1660595 ***
No, it is not reproducible anymore for me