On Sun, Apr 26, 2020 at 1:19 PM Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
Hello,
I'm setting up an Openstack Queens lab ( to best match OSP 13) using oVirt
VMs as nodes.
At this time only undercloud configured and 8 Openstack nodes (VMs) set as
available for provisioning.
I'm using staging-ovirt driver on director node in similar way as the vbmc
one.
I see from oVirt active user sessions page that every minute I have one
connection for node (in my case 8) of the designated user (in my case
ostackpm).
But it seems they are never released.
How can I check the problem?
Director is CentOS 7 server and the staging-ovirt driver is provided by
the package:
[root@director ~]# rpm -q python-ovirt-engine-sdk4
python-ovirt-engine-sdk4-4.3.2-2.el7.x86_64
[root@director ~]#
I didn't configure the oVirt repo but only installed the latest stable
available for 4.3.9:
wget
https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/x86_64/python-ovirt-eng...
sudo yum localinstall python-ovirt-engine-sdk4-4.3.2-2.el7.x86_64.rpm
Anyone with experience on this?
In the mean time any way to use a command using api to kill the stale (I
think) sessions?
Thanks,
Gianluca
Anyone?
It seems that the script involved for power management is
/usr/lib/python2.7/site-packages/ironic_staging_drivers/ovirt/ovirt.py, of
which you can find a copy here:
https://drive.google.com/file/d/1pC1TXuuc0Vks2UBwlmCHGP4oULVzK1_s/view?us...
It is part of package
openstack-ironic-staging-drivers-0.9.2-0.20190420093856.546ceca.el7.noarch
and it misses the "connection.close()" part.
Anyone more experienced in python can tell me where is it better to put the
connection close statement (and if more than one only, in case)?
Thanks,
Gianluca