Open bit4man opened 2 years ago
looks like https://bugzilla.redhat.com/show_bug.cgi?id=2079361
Sure does. Thanks!
looks like https://bugzilla.redhat.com/show_bug.cgi?id=2079361
One small difference. I can query using follow=gluster_volumes just fine. This BZ seems to hint that this parameter is the problem; I don't use gluster-ovirt nodes, so it doesn't really matter - however it doesn't fail for me, when calling the API directly. Only through Ansible.
maybe @oliel can clarify if it's the same issue
looks like https://bugzilla.redhat.com/show_bug.cgi?id=2079361
One small difference. I can query using follow=gluster_volumes just fine. This BZ seems to hint that this parameter is the problem; I don't use gluster-ovirt nodes, so it doesn't really matter - however it doesn't fail for me, when calling the API directly. Only through Ansible.
per https://bugzilla.redhat.com/show_bug.cgi?id=2079361#c1 it is happening on Virt-only clusters.
per https://bugzilla.redhat.com/show_bug.cgi?id=2079361#c1 it is happening on Virt-only clusters.
I don't think so - they look different. https://bugzilla.redhat.com/show_bug.cgi?id=2079361#c1 talks about "not returned". That's incorrect. When I "curl" manually I do get a gluster_volume returned - just empty. Ie. this succeeds:
$ curl -H "Authorization: Bearer YIE2D......KYCDQ" https://ovirt.example.com/ovirt-engine/api/clusters/ccc53763-c479-410f-af0b-ec846929b46f?follow=gluster_volumes | grep gluster
<link href="/ovirt-engine/api/clusters/ccc53763-c479-410f-af0b-ec846929b46f/refreshglusterhealstatus" rel="refreshglusterhealstatus"/>
<link href="/ovirt-engine/api/clusters/ccc53763-c479-410f-af0b-ec846929b46f/glusterhooks" rel="glusterhooks"/>
<link href="/ovirt-engine/api/clusters/ccc53763-c479-410f-af0b-ec846929b46f/glustervolumes" rel="glustervolumes"/>
<skip_if_gluster_bricks_up>false</skip_if_gluster_bricks_up>
<skip_if_gluster_quorum_not_met>false</skip_if_gluster_quorum_not_met>
<gluster_service>false</gluster_service>
<gluster_volumes/>
So it doesn't fit the idea that "gluster_volumes doesn't work". It seems the call done from the ansible collection/python is not done according to required specs, but I'm having a hard time figuring out what the call actually looks like.
EDIT: Bad paste
4.5.0 upgrade from 4.4 is working, but cannot upgrade the cluster definitions to 4.5. The ansible playbook
/usr/share/ovirt-engine/ansible-runner-service-project/project/ovirt-cluster-upgrade.yml
fails very early withand the ovirt-engine.log shows large stackdumps with this as the initial cause:
I've uploaded the full stackdump log. I can call the the API directly:
And this does respond ok.