-
Notifications
You must be signed in to change notification settings - Fork 343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vmimage utility can't fetch fedora image on s390x #6071
Comments
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 10, 2024
Fix of requestsing the correct image depending on arch e.g s390x Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 10, 2024
Fix of requestsing the correct image depending on arch e.g s390x Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 10, 2024
Fix of requestsing the correct image depending on arch e.g s390x Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 10, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 10, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 10, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 10, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 10, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
moved this from Short Term (Current Q) Backlog
to In progress
in Default project
Dec 10, 2024
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 11, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 11, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 12, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 12, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 12, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 12, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 13, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 13, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 13, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 16, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado
that referenced
this issue
Dec 16, 2024
Updated the image pattern in FedoraSecondaryImageProvider to match the available Fedora image file names for the s390x architecture. This resolves the issue where the vmimage utility could not download the correct image due to a pattern mismatch. Reference: avocado-framework#6071 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
Resolved in #6082 |
github-project-automation
bot
moved this from In progress
to Done 109
in Default project
Jan 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Fedora stores vmimages for x86 and s390x in different repositories. Therefore, Avocado vmimage utility has two Fedora providers.
Fedora
andFedoraSecondary
. When you want to fetch Fedora images on s390x system withavocado vmimage get --distro Fedora
the image won't be found. The reason for this is thatImage.from_parameters
method doesn't respect the current system architecture as default architecture.Based on my investigation, it looks like that the issue is in here.
The text was updated successfully, but these errors were encountered: