Self-hosted engine deploy failed
Hi, I have been trying to deploy the engine from cockpit of a ovirt node 4.5.2. The system is freshly installed from the iso. The deployment failed on step 3 Prepare VM. The last error in the /var/log/ovirt-hosted-engine-setup/*log said something about "SSO authentication access_denied : Cannot authenticate user Invalid user credentials." Has anyone seen this before? Thanks ``` 2022-08-18 18:57:20,334-0500 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "attempts": 50, "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_auth_payload_1t3ixb8c/ansible_ovirt_auth_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_auth.py\", line 287, in main\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 382, in authenticate\n self._sso_token = self._get_access_token()\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 627, in _get_access_token\n sso_error[1]\novirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials.\n", "invocation": { "module_args": { "ca_file": null, "compress": true, "headers": null, "hostname": null, "insecure": true, "kerberos": false, "ovirt_auth": null, "password": null, "state": "present", "timeout": 0, "token": null, "url": null, "username": null } }, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials." }, "ansible_task": "Obtain SSO token using username/password credentials", "ansible_type": "task", "status": "FAILED", "task_duration": 537 } ``` Static hostname: xxxxxxxxx Icon name: computer-server Chassis: server Machine ID: 6090168dcd724b04be97d57b01c2a11c Boot ID: 5fba59e1914e48a1aad23fc02641bf3c Operating System: oVirt Node 4.5.2 CPE OS Name: cpe:/o:centos:centos:8 Kernel: Linux 4.18.0-408.el8.x86_64 Architecture: x86-64
I am getting the same issue. Freshly installed ovirt-node same error. I can't seem to find a fix.
I finally gave up directly installing 4.5.2 and 4.5.1. I went back to freshly install 4.4.10 ovirt node and then deployed the 4.4.10 self-hosted engine using the workaround here https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SBCWNXLFLJBKTA3... to get the self-hosted to complete the installation. Once it's up I used the GUI to update it to 4.5.2.
Hi, On Mon, Aug 22, 2022 at 5:45 PM Henry Wong <dewongway@gmail.com> wrote:
I finally gave up directly installing 4.5.2 and 4.5.1. I went back to freshly install 4.4.10 ovirt node and then deployed the 4.4.10 self-hosted engine using the workaround here https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SBCWNXLFLJBKTA3... to get the self-hosted to complete the installation.
IIUC you refer to hosted-engine deployment via cockpit - the web ui - right? See also e.g. https://lists.ovirt.org/archives/list/users@ovirt.org/message/CBDUBBKLTCW4MM... As I wrote there, cockpit HE deployment is deprecated, please use the CLI. That said, I am not aware of a detailed bug report. Would you like to create one in bugzilla, and attach relevant logs? If it's easy to fix, someone might fix it...
Once it's up I used the GUI to update it to 4.5.2.
You mean, the engine's web admin ui, not cockpit, right? Also the engine itself can only be updated via the CLI, right now - or perhaps using the engine_setup ansible role from ovirt-ansible-collection - but I don't use it myself, nor am I aware of anyone that does - for *upgrades*. Best regards, -- Didi
Yes, I used cockpit to deploy the hosted-engine as I wasn't aware it's been deprecated. If you believe this issue is specific to the cockpit deployment method only, is there a need to open a bug since it should/will be removed from cockpit in the future, correct? Just need to update the documentation to point that out? To be honest, 4.5 has been a headache for me. I have been on 4.4 for over a year and never had so many issues. This all started from the upgrade of 4.4. to 4.5, which caused the engine failed to start, and later found out was related to the postgresql version incompatibility issue. But it was already too late as I decided to do a fresh install and thought it would be much cleaner and faster. In any way I have it back and it's on 4.5 but it will make me think twice next time before going for an update. Thanks for the help.
On Tue, Aug 23, 2022 at 8:01 PM Henry Wong <dewongway@gmail.com> wrote:
Yes, I used cockpit to deploy the hosted-engine as I wasn't aware it's been deprecated.
Sorry for that.
If you believe this issue is specific to the cockpit deployment method only,
Can't be certain, obviously, but it does look so - and for the CLI, unlike cockpit, we have automated testing, so at least for the common case we are likely to find bugs before actual users do.
is there a need to open a bug since it should/will be removed from cockpit in the future, correct?
If enough people want cockpit back, and enough of these people want to invest the time in maintaining it, it can live on... I didn't try cockpit myself recently, and frankly, hardly ever did overall - other than when trying to fix bugs in it. I personally find the CLI much better, main reason being that you can run it inside tmux and get back to it if the network went down in the middle. We had a bug asking to be able to return back to a running cockpit HE deploy, but eventually gave up on it - required too much work.
Just need to update the documentation to point that out?
I guess so, yes. Would you like to create a documentation bug/issue for this? Or send a patch? How to do this: Start with the page you followed when deciding to deploy - the point in which you'd expect such a note - then scroll down to the bottom press either 'Report an issue with this page' or 'Edit this page'. Thanks.
To be honest, 4.5 has been a headache for me. I have been on 4.4 for over a year and never had so many issues. This all started from the upgrade of 4.4. to 4.5, which caused the engine failed to start,
Was this resolved? Did you report a bug?
and later found out was related to the postgresql version incompatibility issue.
PG itself? Or postgresql-jdbc? We had problems around that during 4.4 time - I think in 4.5 they are all resolved.
But it was already too late as I decided to do a fresh install and thought it would be much cleaner and faster. In any way I have it back and it's on 4.5 but it will make me think twice next time before going for an update.
If this is a production setup, I definitely recommend trying an update on a test env beforehand. Not only for oVirt, BTW... Good luck and best regards, -- Didi
participants (3)
-
brad.breitenstein＠gmail.com -
Henry Wong -
Yedidyah Bar David