Fail to install ondemand-release-web-4.0-1.el9.noarch
We rerun ansible-playbook controller.yml after some configuration changes with the login node (i.e. changing the fqdn for the login node)
but the playbook failed when it attempted to install ondemand-release-web-4.0-1.el9.noarch.rpm, and I believe ondemand-4.0.3 had been installed in my previous installation.
How can we skip this 4.0.1 version installation to by-pass this error?
Hi Chiensh. We did not encounter this problem before. I assume this is trix 15.1u1? The role just makes sure the required RPM-s are installed, not updated. It seems to be there...
The easiest way out for now is by commenting out the packages section inside the OOD role. in meantime we try to reproduce in our lab. Can you provide the OS distro, trix release you use and in a bit more detail, the steps you took to get here?
-Antoine
Here is the system information, I am not sure it is a 15.1 or 15.1u1, but I did a git pull just before running the playbook. Can you tell me where I can switch off the packages section? /root/trinityX/site/roles/trinity/ood/tasks/main.yml ?
After disabling the package section, I hit on another problem that I reported before, but it has not been taken care of so far: "Deprecation warning: The standalone 'grafana-cli' program is deprecated and will be removed in the future. Please update all uses of 'grafana-cli' to 'grafana cli'\nError"
After disabling the package section, I hit on another problem that I reported before, but it has not been taken care of so far: "Deprecation warning: The standalone 'grafana-cli' program is deprecated and will be removed in the future. Please update all uses of 'grafana-cli' to 'grafana cli'\nError"
![]()
I encountered the same problem after making a few changes to the login node and wanting to update the system. Any ideas on how to solve this would be great.
Hi
you can solve this problem by replacing all "grafana-cli" with "grafana cli" in ~/trinityX/site/roles/trinity/grafana/tasks/main.yml
Hi,
perfect, that solved it, thank you!
Officially resolved in upcoming 15.2. I thank you all for the collaboration!
-Antoine