Turns out that D675 relies on features in libvirt-python which weren't added until 1.2.15.
libvirt-python
While el7 has 1.2.17, f23 has 1.2.18 and rawhide has 1.2.21 at the time of this writing, f22 only has 1.2.13.
Consequently, if you try to launch an instance on f22, you get the following output:
$ testcloud instance create disktest -u file:///home/tflink/taskotron-cloud/f22/20151123-taskotron-f22-10G.qcow2 DEBUG:create instance DEBUG:Local downloads will be stored in /var/lib/testcloud/backingstores. DEBUG:successfully changed SELinux context for image /var/lib/testcloud/backingstores/20151123-taskotron-f22-10G.qcow2 DEBUG:Creating instance directories DEBUG:Generated user-data for instance disktest DEBUG:Generated meta-data for instance disktest DEBUG:creating seed image /var/lib/testcloud/instances/disktest/disktest-seed.img INFO:Seed image generated successfully Formatting '/var/lib/testcloud/instances/disktest/disktest-local.qcow2', fmt=qcow2 size=10737418240 backing_file='/var/lib/testcloud/backingstores/20151123-taskotron-f22-10G.qcow2' encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16 DEBUG:Creating domain disktest DEBUG:Polling domain for active network interface Traceback (most recent call last): File "/usr/bin/testcloud", line 9, in <module> load_entry_point('testcloud==0.1.5', 'console_scripts', 'testcloud')() File "/usr/lib/python2.7/site-packages/testcloud/cli.py", line 302, in main args.func(args) File "/usr/lib/python2.7/site-packages/testcloud/cli.py", line 96, in _create_instance tc_instance.start(args.timeout) File "/usr/lib/python2.7/site-packages/testcloud/instance.py", line 401, in start domif = dom.interfaceAddresses(0) AttributeError: 'virDomain' object has no attribute 'interfaceAddresses'
Are we OK with testcloud requiring libvirt-python >= 1.2.15 or do we need to refactor the code that waits for an instance to be somewhat created before exiting?
libvirt-python >= 1.2.15
This ticket had assigned some Differential requests: D675
libvirt-python >= 1.2.15, right? Not .13.
.13
I'd be OK with requiring just the necessary version, but what will happen to the testcloud packages we just pushed to F22? Will they be stuck to the current version and we will not support F22 images in taskotron?
Maybe it would be worth a try to contact libvirt maintainers and ask them if they can push latest libvirt to F22.
Thanks for catching the typo, I did indeed mean 1.2.15.
1.2.15
I canceled the f22 update, so it wasn't pushed and that's not an issue. The branches exist in dist-git but I don't see that as a huge issue
Since el7 has new enough libvirt-python, I don't see how not having testcloud in f22 is a huge issue and I'm tempted to just leave things as they are and focus on getting everything working in f23, wich we have been doing with taskotron-dev.
Works for me.
Works for me too.
F22 is going EOL in a week, closing.