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

random centos stream build failures on COPR environments #1191

Closed
lsm5 opened this issue Aug 22, 2023 · 2 comments
Closed

random centos stream build failures on COPR environments #1191

lsm5 opened this issue Aug 22, 2023 · 2 comments

Comments

@lsm5
Copy link

lsm5 commented Aug 22, 2023 •
edited
Loading

Short description of the problem

centos stream builds on copr flaking on podman pull quay.io/centos/centos:stream[8,9]

Output of rpm -q mock

Happens on copr environments and @FrostyX suspects it could be a mock problem

Steps to reproduce issue

  1. Happens randomly on centos stream build envs and goes away with a build retrigger
  2. See: https://download.copr.fedorainfracloud.org/results/packit/containers-podman-19683/centos-stream+epel-next-8-aarch64/06326478-podman/builder-live.log.gz for example

Occurred at least twice in centos stream copr builds triggered by packit. No mock command executed manually.
@lsm5 lsm5 changed the title centos stream build failures on COPR environments. random centos stream build failures on COPR environments Aug 22, 2023
@lsm5
Copy link
Author

lsm5 commented Aug 22, 2023

another example: centos-stream+epel-next-8-aarch64 failure at https://copr.fedorainfracloud.org/coprs/rhcontainerbot/podman-next/build/6267034/

@praiskup praiskup mentioned this issue Aug 28, 2023
Closed
praiskup added a commit to praiskup/mock that referenced this issue Aug 28, 2023
@praiskup
podman: better "podman pull / image mount" error reporting
12fee62 
Defining a new BootstrapError() exception covering the bootstrap chroot
preparation problems.

Make sure that stderr output is dumped into logs when some failure
happens.

When `podman pull` fails, we just throw a logger.error() message now,
and delay the fatal failure till the `podman image mount` attempt.
Users might have the image pre-downloaded (e.g. we can pull the
problematic container images when starting Copr builder machines).

Relates: rpm-software-management#1191
@praiskup praiskup mentioned this issue Aug 28, 2023
Closed
praiskup added a commit to praiskup/mock that referenced this issue Aug 28, 2023
@praiskup
podman: better "podman pull / image mount" error reporting
7947a72 
Defining a new BootstrapError() exception covering the bootstrap chroot
preparation problems.

Make sure that stderr output is dumped into logs when some failure
happens.

When `podman pull` fails, we just throw a logger.error() message now,
and delay the fatal failure till the `podman image mount` attempt.
Users might have the image pre-downloaded (e.g. we can pull the
problematic container images when starting Copr builder machines).

Relates: rpm-software-management#1191
praiskup added a commit that referenced this issue Aug 29, 2023
@praiskup
podman: better "podman pull / image mount" error reporting
4bc80c3 
Defining a new BootstrapError() exception covering the bootstrap chroot
preparation problems.

Make sure that stderr output is dumped into logs when some failure
happens.

When `podman pull` fails, we just throw a logger.error() message now,
and delay the fatal failure till the `podman image mount` attempt.
Users might have the image pre-downloaded (e.g. we can pull the
problematic container images when starting Copr builder machines).

Relates: #1191
@praiskup
Copy link
Member

Mock 5.1 will keep re-trying 395fc07, and then fallback to "normal boostrap" 79c36e8. Thank you for the report, @lsm5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lsm5 @praiskup