Info about openstack staging-ovirt driver connection not released
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-engine... 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
On Sun, Apr 26, 2020 at 1:19 PM Gianluca Cecchi <gianluca.cecchi@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-engine... 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?usp=s... 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
Hello Gianluca, did you tried contacting the RDO team which is responsible of that package? If is an easy fix, they can commit (or help you committing) directly in Openstack. Luca On Mon, Apr 27, 2020 at 10:33 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Sun, Apr 26, 2020 at 1:19 PM Gianluca Cecchi <gianluca.cecchi@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-engine... 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?usp=s...
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
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZIM2ZGJZ5VWIH4...
-- "E' assurdo impiegare gli uomini di intelligenza eccellente per fare calcoli che potrebbero essere affidati a chiunque se si usassero delle macchine" Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) "Internet è la più grande biblioteca del mondo. Ma il problema è che i libri sono tutti sparsi sul pavimento" John Allen Paulos, Matematico (1945-vivente) Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <lorenzetto.luca@gmail.com>
On Tue, Apr 28, 2020 at 11:18 AM Luca 'remix_tj' Lorenzetto < lorenzetto.luca@gmail.com> wrote:
Hello Gianluca,
did you tried contacting the RDO team which is responsible of that package? If is an easy fix, they can commit (or help you committing) directly in Openstack.
Luca
I was thinking about it, but I have not clear if I have to use https://bugs.launchpad.net/tripleo or https://bugzilla.redhat.com/buglist.cgi?quicksearch=openstack-ironic-staging... yum list of the package gives: Installed Packages openstack-ironic-staging-drivers.noarch 0.9.2-0.20190420093856.546ceca.el7 @delorean-queens and the repo contains: [delorean-queens] name=delorean-python-dracclient-f49840cfe014040134c1f9b6749acdc7e47d1c24 baseurl= https://trunk.rdoproject.org/centos7-queens/f4/98/f49840cfe014040134c1f9b674... enabled=1 gpgcheck=0 priority=1 So I should use the bugzilla one I think, correct? Gianluca
On Tue, Apr 28, 2020 at 11:40 AM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, Apr 28, 2020 at 11:18 AM Luca 'remix_tj' Lorenzetto < lorenzetto.luca@gmail.com> wrote:
Hello Gianluca,
did you tried contacting the RDO team which is responsible of that package? If is an easy fix, they can commit (or help you committing) directly in Openstack.
Luca
I was thinking about it, but I have not clear if I have to use https://bugs.launchpad.net/tripleo or
https://bugzilla.redhat.com/buglist.cgi?quicksearch=openstack-ironic-staging...
yum list of the package gives:
Installed Packages openstack-ironic-staging-drivers.noarch 0.9.2-0.20190420093856.546ceca.el7 @delorean-queens
and the repo contains:
[delorean-queens] name=delorean-python-dracclient-f49840cfe014040134c1f9b6749acdc7e47d1c24 baseurl= https://trunk.rdoproject.org/centos7-queens/f4/98/f49840cfe014040134c1f9b674... enabled=1 gpgcheck=0 priority=1
So I should use the bugzilla one I think, correct?
Gianluca
In the mean time I posted here: https://bugzilla.redhat.com/show_bug.cgi?id=1828757 as I see that also the Stein stable package has the problem: openstack-ironic-staging-drivers-0.11.1-0.20191023075755.ab5bb1d.el7.noarch.rpm Let's see if it is the correct point Gianluca
participants (2)
-
Gianluca Cecchi -
Luca 'remix_tj' Lorenzetto