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.

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

Update CI VM images #420

Closed
wants to merge 1 commit into from
Closed

Conversation

inknos
Copy link
Contributor

@inknos inknos commented Aug 15, 2024

Copy link
Contributor

openshift-ci bot commented Aug 15, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: inknos
Once this PR has been reviewed and has the lgtm label, please assign vrothberg for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link

We were not able to find or create Copr project packit/containers-podman-py-420 specified in the config with the following error:

Cannot create a new Copr project (owner=packit project=containers-podman-py-420 chroots=['centos-stream-9-x86_64', 'centos-stream-10-x86_64']): Copr: 'packit/containers-podman-py-420' already exists. Copr HTTP response is 400 BAD REQUEST.

Unless the HTTP status code above is >= 500, please check your configuration for:

  1. typos in owner and project name (groups need to be prefixed with @)
  2. whether the project name doesn't contain not allowed characters (only letters, digits, underscores, dashes and dots must be used)
  3. whether the project itself exists (Packit creates projects only in its own namespace)
  4. whether Packit is allowed to build in your Copr project
  5. whether your Copr project/group is not private

@inknos
Copy link
Contributor Author

inknos commented Aug 15, 2024

/packit build

@inknos inknos force-pushed the update-ci-vm-images branch 2 times, most recently from ff1a380 to 43d76c5 Compare August 16, 2024 13:18
@inknos
Copy link
Contributor Author

inknos commented Aug 20, 2024

testing with this PR I was able to isolate the environments better. I found out that for py3.9/py3.11 the tests hang, for 3.12 the tests pass the failing one but have issues later with requests. some more work is needed and I guess these two prs will need to be considered together

@inknos inknos changed the title Update CI VM images [wip] Update CI VM images Aug 20, 2024
@inknos inknos changed the title [wip] Update CI VM images Update CI VM images Sep 17, 2024
Signed-off-by: Nicola Sella <[email protected]>
@inknos
Copy link
Contributor Author

inknos commented Sep 23, 2024

@edsantiago how can I re-trigger the tests? should I make a new PR?

Maybe it's worth mentioning that this PR was made initially for an image that was created a while ago, and then it was rebased on top of another image change.

@edsantiago
Copy link
Member

Usually there's a Rerun test button, but I don't see it here. Maybe you and I don't have the right privs on this repo. In that case, the only possible action you can take is to repush.

@inknos
Copy link
Contributor Author

inknos commented Sep 23, 2024

force pushed already, I'll make a new one and close this with the new link

@inknos
Copy link
Contributor Author

inknos commented Sep 23, 2024

New PR. #430

@inknos inknos closed this Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants