Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Multi-arch support for images used during integration tests #6026

Open
feloy opened this issue Aug 16, 2022 · 4 comments
Open

Multi-arch support for images used during integration tests #6026

feloy opened this issue Aug 16, 2022 · 4 comments
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.

Comments

@feloy
Copy link
Contributor

feloy commented Aug 16, 2022

/kind bug

What versions of software are you using?

Operating System:

IBM Z architecture

Issue

During integration tests, some devfiles are using images that don't have multi-arch support and don't support Z arch.

For example:
https://github.com/redhat-developer/odo/blob/main/tests/examples/source/devfiles/nodejs/devfileCompositeBuildRunDebugInMultiContainersAndSharedVolume.yaml

is using quay.io/quay/busybox:latest which is not support by Z arch.

It would be better to use this one instead: https://quay.io/repository/openshifttest/busybox
@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Aug 16, 2022
@rm3l
Copy link
Member

rm3l commented Aug 16, 2022

cc @surenderky

@rm3l rm3l added this to odo Project Oct 3, 2022
@rm3l rm3l moved this to To Do 📝 in odo Project Oct 3, 2022
@rm3l rm3l removed the status in odo Project Oct 3, 2022
@github-actions
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 29, 2023
@rm3l rm3l added the area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering label Sep 29, 2023
@github-actions
Copy link
Contributor

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Oct 30, 2023
@github-project-automation github-project-automation bot moved this to Done ✅ in odo Project Oct 30, 2023
@rm3l
Copy link
Member

rm3l commented Oct 30, 2023

/remove-lifecyle rotten
/remove-lifecyle stale
/lifecycle frozen

Still relevant.

@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Oct 30, 2023
@rm3l rm3l reopened this Oct 30, 2023
@github-project-automation github-project-automation bot moved this from Done ✅ to To Do 📝 in odo Project Oct 30, 2023
@rm3l rm3l removed the status in odo Project Oct 30, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Oct 30, 2023
@rm3l rm3l added priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. and removed needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. labels Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
Projects
odo Project
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rm3l @feloy