From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: Daniele Buono <dbuono@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>
Subject: Re: [PATCH 0/1] tests/acceptance/boot_linux: Switch to Fedora 32
Date: Thu, 28 Jan 2021 17:19:01 -0300 [thread overview]
Message-ID: <20c6fbf7-3000-0ef4-cdb1-31d748878206@redhat.com> (raw)
In-Reply-To: <20210127010946.17370-1-dbuono@linux.vnet.ibm.com>
Hi,
On 1/26/21 10:09 PM, Daniele Buono wrote:
> Local acceptance tests run with "make check-acceptance" are now
> showing some cases canceled like the following:
>
> (01/39) tests/acceptance/boot_linux.py:BootLinuxX8664.test_pc_i440fx_tcg: CANCEL: Failed to download/prepare boot image (0.25 s)
>
> Turns out, every full-vm test in boot_linux.py is trying to use a
> Fedora 31 cloud image and is failing, with Avocado refusing to download
> it, presumably because Fedora 31 is EOL.
>
> This patch moves to Fedora 32, which is still supported. And seem to
> work fine
While ago it was discussed about updating the Fedora version which, in
my opinion, ended up without a conclusion. Please see the complete
thread in:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg763986.html
I'm CC'ing Daniel Berrrangé so that, perhaps, we could resume the
discussion.
Thanks!
- Wainer
>
> The script has the image checksums hardcoded. I downloaded and verified
> the checksums with the Fedora 32 GPG key, but I would feel more
> confident if someone else wants to verify it too.
>
> The checksum files are here:
> https://download-ib01.fedoraproject.org/pub/fedora-secondary/releases/32/Cloud/ppc64le/images/Fedora-Cloud-32-1.6-ppc64le-CHECKSUM
> https://download-ib01.fedoraproject.org/pub/fedora-secondary/releases/32/Cloud/s390x/images/Fedora-Cloud-32-1.6-s390x-CHECKSUM
> https://download-ib01.fedoraproject.org/pub/fedora/linux/releases/32/Cloud/aarch64/images/Fedora-Cloud-32-1.6-aarch64-CHECKSUM
> https://download-ib01.fedoraproject.org/pub/fedora/linux/releases/32/Cloud/x86_64/images/Fedora-Cloud-32-1.6-x86_64-CHECKSUM
> and the GPG keys are available here:
> https://getfedora.org/en/security/
>
> NOTE: I tried moving to Fedora 33, but the aarch64 VM cannot boot
> properly. May be worth investigating but I have no experience with ARM
> so I'll leave that to someone else, if interested.
>
> Daniele Buono (1):
> tests/acceptance/boot_linux: Switch to Fedora 32
>
> tests/acceptance/boot_linux.py | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
next prev parent reply other threads:[~2021-01-28 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 1:09 [PATCH 0/1] tests/acceptance/boot_linux: Switch to Fedora 32 Daniele Buono
2021-01-27 1:09 ` [PATCH 1/1] " Daniele Buono
2021-01-28 20:19 ` Wainer dos Santos Moschetta [this message]
2021-01-28 22:06 ` [PATCH 0/1] " Daniele Buono
2021-02-05 16:54 ` Philippe Mathieu-Daudé
2021-02-05 17:28 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20c6fbf7-3000-0ef4-cdb1-31d748878206@redhat.com \
--to=wainersm@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=dbuono@linux.vnet.ibm.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).