| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-11-06 | |||
| 13:25:52 | efried | k, I'm running now. Cleaned first to get rid of compiled libvirt/qemu -- I needed that because of new compile flaggage, rite? | |
| 13:26:01 | efried | for apparmor | |
| 13:26:43 | sean-k-mooney | actully no i have not added that yet | |
| 13:27:07 | sean-k-mooney | but i found the bits i needed to set to disable the use of polkit | |
| 13:27:30 | sean-k-mooney | a clean does not hurt it just will be slower | |
| 13:27:35 | efried | ight. We'll see how this goes :) | |
| 13:29:04 | sean-k-mooney | by the way to go back to normal you just need to unstack then comment out the pluging. it should remove the libvirt and qemu it installed on unstack but wont delete the source in /opt/stack | |
| 13:29:19 | efried | cool | |
| 13:29:23 | efried | I'll never go back to normal | |
| 13:29:26 | efried | This is my new normal | |
| 13:29:41 | sean-k-mooney | :) | |
| 14:00:40 | efried | sean-k-mooney: no idea why this should be failing differently on my otherwise-identical VMs, but one is hitting the libvirt-python install failure again, and the other is hitting the /var/run/libvirt/libvirt-sock ENOENT again. | |
| 14:12:02 | sean-k-mooney | so the libvirt python failure is complaingin about the libvit.so right with pkg-config or somthing like that and the other case libvirt is not running? | |
| 14:13:12 | efried | sean-k-mooney: Maybe I'm not looking at the right patch set. I don't see a delta where you're purging qemu for instance. | |
| 14:14:17 | sean-k-mooney | its here https://review.opendev.org/#/c/693094/3/devstack/libs/libvirt@102 | |
| 14:14:30 | efried | ah, k | |
| 14:15:32 | efried | well, now I got both to fail the same way. The one that was failing with ENOENT is now failing on the libvirt-python thing. | |
| 14:15:52 | efried | I cut it over to USE_PYTHON3 | |
| 14:16:28 | sean-k-mooney | ok. am if you look in /usr/lib is there a libvirt.so | |
| 14:17:05 | efried | yes | |
| 14:17:20 | sean-k-mooney | ok if you unstack it should remove it | |
| 14:17:55 | efried | and that's what I want? | |
| 14:17:58 | sean-k-mooney | if it does not run " sudo rm -f /urs/lib/libvirt* | |
| 14:18:21 | sean-k-mooney | well we want to make sure its the libvirt.so you compiled for a start | |
| 14:18:28 | sean-k-mooney | it shoudl be | |
| 14:18:38 | efried | fwiw the date stamp implies that it is. | |
| 14:19:13 | efried | everything /usr/lib/libvirt* has a now-ish date stamp | |
| 14:19:35 | efried | and yes, unstacking removes everything /usr/lib/libvirt* | |
| 14:19:51 | sean-k-mooney | ok so if you run "pkg-config libvirt ; echo $?" | |
| 14:20:05 | sean-k-mooney | im guessin git now prints a non 0 value right | |
| 14:20:38 | sean-k-mooney | if so can you cd in /opt/stack/libvit and do sudo make install | |
| 14:20:42 | sean-k-mooney | then run it again | |
| 14:21:38 | efried | yes, confirm all of that. | |
| 14:22:10 | sean-k-mooney | so if you run it after you do make install is it 0 or non 0 | |
| 14:22:18 | efried | 0 | |
| 14:22:34 | sean-k-mooney | ok and if you manually to the pip install of libvirt-python? | |
| 14:22:35 | efried | and the checksum of the lib is the same as on the other system where I didn't unstack and manually `make install` | |
| 14:22:48 | sean-k-mooney | ya it should be | |
| 14:23:06 | efried | Found 0 functions in libvirt-override-api.xml | |
| 14:23:06 | efried | Found 475 functions in /usr/share/libvirt/api/libvirt-api.xml | |
| 14:23:06 | efried | /usr/bin/python generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml | |
| 14:23:06 | efried | /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt | |
| 14:23:06 | efried | same error: | |
| 14:23:07 | efried | virTypedParameterPtr:1 | |
| 14:23:07 | efried | Missing type converters: | |
| 14:23:07 | efried | Generated 385 wrapper functions | |
| 14:23:08 | efried | ERROR: failed virConnectSetIdentity | |
| 14:23:09 | efried | error: command '/usr/bin/python' failed with exit status 1 | |
| 14:24:13 | sean-k-mooney | if you do pip show libvirt-python | |
| 14:24:18 | sean-k-mooney | what version do you see | |
| 14:24:22 | sean-k-mooney | im using 5.7.0 | |
| 14:24:48 | efried | When we hit this yesterday, it went away magically by itself | |
| 14:24:57 | efried | 5.5.0 | |
| 14:25:18 | efried | it's trying to install 5.7.0 that breaks | |
| 14:25:46 | sean-k-mooney | if you try and install 5.5.0 does it work | |
| 14:25:56 | sean-k-mooney | e.g. if you remove it and add it | |
| 14:26:53 | efried | here's a thing: I'm running py2 pip | |
| 14:27:02 | sean-k-mooney | so am i | |
| 14:27:19 | sean-k-mooney | pip version 9.0.3 | |
| 14:27:25 | sean-k-mooney | the one devstack installs | |
| 14:28:16 | efried | if I uninstall 5.5.0 and try to reinstall, it fails (at 5.5.0 and at 5.7.0) the same way | |
| 14:28:44 | efried | also with pip3 | |
| 14:30:07 | efried | what if I tried setting the plugin to build libvirt 5.7.0? | |
| 14:30:18 | sean-k-mooney | oh... | |
| 14:30:29 | sean-k-mooney | yes you could do that | |
| 14:30:52 | sean-k-mooney | but its passing form me because its using the cached wheel | |
| 14:31:04 | sean-k-mooney | if i try to use 5.5.0 i get your error | |
| 14:31:15 | efried | like you already had 5.7.0 installed before you started? | |
| 14:31:18 | sean-k-mooney | actully i get | |
| 14:31:20 | sean-k-mooney | ERROR: failed virConnectSetIdentity | |
| 14:31:22 | sean-k-mooney | ERROR: failed virDomainGetGuestInfo | |
| 14:31:24 | sean-k-mooney | error: command '/usr/bin/python' failed with exit status 1 | |
| 14:31:26 | efried | yes, that's what I'm seeing. | |
| 14:31:40 | efried | it's slightly different with 5.5 vs 5.7 | |
| 14:32:02 | sean-k-mooney | so i proably had libvirt python 5.7 alredy install as that is the lates version | |
| 14:32:08 | sean-k-mooney | and i had previously stacked | |
| 14:32:20 | sean-k-mooney | ill ask downstream one sec | |
| 14:35:23 | sean-k-mooney | efried: it might be this? https://github.com/libvirt/libvirt-python/commit/873e0ca7db3ae43bd514354997cdfa7ea5b7f70a | |
| 14:36:23 | efried | you mean that's the fix for same | |
| 14:36:30 | efried | kinda looks that way, yeah. | |
| 14:36:44 | efried | It wouldn't surprise me that libvirt-python's version has to match that of libvirt itself. | |
| 14:36:56 | efried | lemme clean and try building 5.7.0 | |
| 14:38:19 | sean-k-mooney | efried: so apparently the libvirt python version needs to be newer or the same as the libvir tyou are compiling | |
| 14:38:22 | efried | I guess libvirt-python hasn't been published to pypi yet or something? Why wouldn't `pip install -U` pick up the latest? | |
| 14:39:19 | efried | tried asking explicitly for 5.8.0 and it bounces | |
| 14:39:49 | sean-k-mooney | ya let me check pypy you can install it from souce if you need too | |
| 14:40:06 | efried | nah, I'll just bust down to libvirt 5.7.0 | |
| 14:40:10 | efried | I only need 5.6.0 min | |
| 14:41:14 | efried | but I guess an improvement for your script would be a version qualifier on libvirt-python >= whatever version of libvirt you're compiling. | |
| 14:41:44 | sean-k-mooney | yep | |
| 14:41:45 | efried | I don't know if that failure ("can't find libvirt-python 5.8.0") would be more obvious or not. | |
| 14:43:00 | sean-k-mooney | i proably can also do a safty check or install it form souce. | |
| 14:43:13 | sean-k-mooney | it would not be hard to just clone it and check out the same tag | |
| 14:43:16 | sean-k-mooney | then pip install it | |
| 14:43:49 | efried | depends what the plugin user wants it for. If it's not available on pypi that means it's not released yet, right? | |
| 14:44:11 | efried | Though I thought tags don't move once they're set. | |
| 14:44:38 | sean-k-mooney | efried: no its released just talking to danpb he though it was released he is fixing it now | |
| 14:44:48 | efried | o | |
| 14:45:36 | sean-k-mooney | efried: its there now | |
| 14:46:42 | efried | cool. I've already got both of these stacking at 5.7.0; if they fail I'll bump one up. | |