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

test odo with podman v4 #6583

Open
Tracked by #6991
anandrkskd opened this issue Feb 9, 2023 · 6 comments
Open
Tracked by #6991

test odo with podman v4 #6583

anandrkskd opened this issue Feb 9, 2023 · 6 comments
Assignees
@rm3l
Labels
area/odo-on-podman Issues or PRs related to running odo against Podman area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.

Comments

@anandrkskd
Copy link
Contributor

/area testing

As a QE I want to start testing odo against podman v4 on CI, as the podman tests are running only on podman v3, we need to make sure if odo works with podman v4.
@openshift-ci openshift-ci bot added the area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering label Feb 9, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Feb 9, 2023
@rm3l rm3l added this to odo Project Feb 9, 2023
@rm3l rm3l added the area/odo-on-podman Issues or PRs related to running odo against Podman label Feb 9, 2023
@rm3l rm3l mentioned this issue Apr 19, 2023
Merged
3 tasks
@valaparthvi valaparthvi removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label May 2, 2023
@valaparthvi
Copy link
Contributor

Scope for Sprint 237:
Research the work that needs to be done to setup CI for podman v4.

@valaparthvi
Copy link
Contributor

@ritudes This might be a good issue for you to learn GitHub Actions. You can collaborate on this with Armel.

@ritudes ritudes moved this to In Progress 🚧 in odo Project May 11, 2023
@rm3l rm3l added this to the v3.11.0 🚀 milestone May 12, 2023
@rm3l rm3l modified the milestones: v3.11.0 🚀, v3.12.0 🚀 May 30, 2023
@rm3l rm3l modified the milestones: v3.12.0 🚀, v3.13.0 🚀 Jun 27, 2023
This was referenced Jul 20, 2023
Closed
Open
@rm3l rm3l removed this from the v3.13.0 🚀 milestone Jul 24, 2023
@rm3l rm3l removed the status in odo Project Jul 24, 2023
@rm3l rm3l added this to the v3.14.0 🚀 milestone Aug 1, 2023
@rm3l rm3l removed this from the v3.14.0 🚀 milestone Aug 21, 2023
@github-actions 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 Nov 20, 2023
@github-actions 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 Dec 21, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 21, 2023
@github-project-automation github-project-automation bot moved this to Done ✅ in odo Project Dec 21, 2023
@rm3l
Copy link
Member

rm3l commented Jan 24, 2024

/reopen
/remove-lifecycle rotten
/remove-lifecycle stale
/lifecycle frozen

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jan 24, 2024

@rm3l: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten
/remove-lifecycle stale
/lifecycle frozen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot reopened this Jan 24, 2024
@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 24, 2024
@github-project-automation github-project-automation bot moved this from Done ✅ to To Do 📝 in odo Project Jan 24, 2024
@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. labels Jan 24, 2024
@rm3l rm3l removed the status in odo Project Jan 24, 2024
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rm3l rm3l

Labels
area/odo-on-podman Issues or PRs related to running odo against Podman area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
Projects
odo Project
Status: No status
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rm3l @valaparthvi @anandrkskd @ritudes