Testcloud for current Fedora stable works fine for me:
testcloud instance -c qemu:///session create -u fedora:33 --ram 1024 test1
but with "fedora:34" or "fedora:rawhide" it fails:
DEBUG:create instance DEBUG:Starting new HTTPS connection (1): getfedora.org:443 DEBUG:https://getfedora.org:443 "GET /releases.json HTTP/1.1" 200 40948 Couldn't find the desired image...
Indeed https://getfedora.org/releases.json only has up to 33. But https://download.fedoraproject.org/pub/fedora/linux/development/ surely has cloud images for both 34 and rawhide, I suppose that's what packit/TF use for Fedora 34/rawhide tests.
Is there maybe a development.json? (It's not literally that or devel.json), or could testcloud use the cloud download URLs directly perhaps?
Metadata Update from @frantisekz: - Issue assigned to frantisekz
There is not an easy api-friendly way to get rawhide/branched urls as of now, I have asked Adam to expose json form of his latest nigthlies page ( https://pagure.io/fedora_nightlies/issue/10 ). The json exists, it's just not publicly accessible yet.
I'll implement this once the request above is completed.
Commit 513972e fixes this issue
F35 Cloud will be broken until https://src.fedoraproject.org/rpms/cloud-init/pull-request/19# gets merged.
That was fixed, new testcloud release will happen soon, pre-release build is in https://copr.fedorainfracloud.org/coprs/frantisekz/testcloud-wip/
Hmm, that cloud-init fix landed three months ago, testcloud packages in F34 are at version 0.6.1-1.fc34 (i.e. newer than the 0.5.0-7 that you did back then), and F35 is still broken:
tmt run --until report provision --how virtual --image fedora-35
fails with
Unable to get the full qcow name (https://kojipkgs.fedoraproject.org/compose/35/latest-Fedora-35/compose/Cloud/x86_64/images), retrying, 60 seconds left.
and eventually times out. However, it actually does work now for rawhide, which this issue was about:
tmt run --until report provision --how virtual --image fedora-rawhide
I also tried this with testcloud directly:
testcloud instance -c qemu:///session create -u fedora:35 --ram 1024 test1
but that seems to have to unlearned the session qemu fix, it says "Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro'". (Same for fedora:34)
Hmm, that cloud-init fix landed three months ago, testcloud packages in F34 are at version 0.6.1-1.fc34 (i.e. newer than the 0.5.0-7 that you did back then), and F35 is still broken: tmt run --until report provision --how virtual --image fedora-35 fails with Unable to get the full qcow name (https://kojipkgs.fedoraproject.org/compose/35/latest-Fedora-35/compose/Cloud/x86_64/images), retrying, 60 seconds left. and eventually times out. However, it actually does work now for rawhide, which this issue was about: tmt run --until report provision --how virtual --image fedora-rawhide
This is caused by Rawhide now being F36 and not F35. I've added support for handling branched Fedora releases to the master branch but didn't manage to cut the release before leaving for PTO (till 20th September).
I also tried this with testcloud directly: testcloud instance -c qemu:///session create -u fedora:35 --ram 1024 test1 but that seems to have to unlearned the session qemu fix, it says "Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro'". (Same for fedora:34)
And that shouldn't be happening. Could you try to launch testcloud without -u parameter (just type the "fedora:35" as the first arg and name after -n if you want to specify that manually)?
I am typing this from a phone at an airport, so sorry for being brief and possible formatting issues.
Great to hear that f35 is being fixed already!
Both of these fail due to trying to talk to system libvirt:
testcloud instance create fedora:34 testcloud instance -c qemu:///session create fedora:34
I filed issue #116 about the session qemu part. This really doesn't belong to this unrelated closed issue.
Log in to comment on this ticket.