---- On Tue, 19 Nov 2024 22:34:07 -0800 Dmitriy Rabotyagov wrote ---
Hey,
This looks like some issue with Horizon itself. Though, Wallaby has reached the End Of Maintenance state, so I would not expect much on fixing the issue for W. I would suggest try upgrading Horizon to some maintained release and see if that fixes the issue. As there were a series of issues with scopes (including system and domain scopes) which were addressed in Horizon since Wallaby (ie https://bugs.launchpad.net/horizon/+bug/2054799)
ср, 20 нояб. 2024 г. в 07:16, Danish Khan danish52.jmi@gmail.com>:
Dear All,
I have upgraded one of my test openstack cluster from victoria to Wallaby. After upgrading, the hypervisor is not showing correct numbers of VMs on compute nodes from browser.
But openstack CLI is giving correct number of VMs.
I am getting below error in horizon container when I click on "hypervisor" from browser:
Nov 20 11:17:29 horizon-container-2b244cbd apache2[43317]: [wsgi:error] [pid 43317:tid 139897181898496] [remote x.x.x.151:37180] /openstack/venvs/horizon-23.3.1.dev4/lib/python3.8/site-packages/oslo_policy/policy.py:1065: UserWarning: Policy os_compute_api:os-migrate-server:migrate failed scope check. The token used to make the request was domain scoped but the policy requires ['system', 'project'] scope. This behavior may change in the future where using the intended scope is required
I did try few thing but that did not work.
We had the system scope things in Nova in wallaby but those were disabled by default. I think that is why you are getting correct result via CLI. If system scope error is raised from Horizon then check if "[oslo.policy] enforce_scope and enforce_new_defaults"[1] is enabled in the horizon. Those can be done in horizon side conf or in nova.conf. I would also check the oslo.policy version here in case you end up with the 4.4.0 in your env. I enabled those configs by default in oslo.policy 4.4.0, so if you are using the latest oslo.policy with Wallaby, then also the same issue can occur. But as you saying CLI is working fine, then I think the Nova server and olso.policy is fine and it seems issue on Horizon side. [1] https://github.com/openstack/oslo.policy/blob/unmaintained/wallaby/oslo_poli... -gmann
Regards, Danish Khan