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

Try several times to build the become container #2467

Merged
merged 4 commits into from
Nov 13, 2023
Merged

Conversation

psss
Copy link
Collaborator

@psss psss commented Nov 8, 2023

Seems this is the only point where the podman tests are still failing with the random network errors tracked in #2063. Let's give several attempts to build the container to reduce the failures.

Pull Request Checklist

  • extend the test coverage

@psss psss added the test coverage Improvements or additions to test coverage of tmt itself label Nov 8, 2023
@psss psss added this to the 1.30 milestone Nov 8, 2023
@psss
Copy link
Collaborator Author

psss commented Nov 8, 2023

Issue reproduced here. Second attempt to create the image was successful. We'll just need to get rid of the rlRun asserts to make this a passing test.

:: [ 12:54:47 ] :: [  BEGIN   ] :: Running 'podman build -t become-container-test:latest .'
STEP 1/3: FROM quay.io/fedora/fedora:latest
Trying to pull quay.io/fedora/fedora:latest...
Error: creating build container: copying system image from manifest list: parsing image configuration: Get "https://cdn03.quay.io/sha256/ec/ec546109f8227b6cca3212bad13f50f3f3555455f51f0162776a43f160f60343?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAI5LUAQGPZRPNKSJA%2F20231108%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20231108T125448Z&X-Amz-Expires=600&X-Amz-SignedHeaders=host&X-Amz-Signature=1dd7ea45c2450ac6d367b1a60a073320d466900a78f939266dd22641e54f0919&cf_sign=F%2FQVIzT7xnL3ZDo3zGKWJW1wRUmotHNviitaUw1hgu3Q0G8gjeaoIK%2FJO2li7lR5WKu0Cq5jrcWaSy7n3maW2f17BrUjf06wv0oP1d3WaSqQbxMO%2Fw%2FioYhUsKH4xthUZJCKwoPbSZlZxnkQN4vyZFwz7Id67Kqd%2FvihaZQKWNw2rME1mwEgT2AgAgJgOsT9C19BRCPOKADQyTtGMQ0sKTIGC5o%2BF17xD1nINM9iJ4wbSs8Nu%2B4Rm8JczX7a3W%2Fj3pdgSdo0a8MdC4z5E%2FxOxcw%2FozpYUafnaAb7mjNV8z6qNWV0ZUF%2FwQH4rD7jb%2BANxxsnNsDzON9L7EnbqIPUCg%3D%3D&cf_expiry=1699448688&region=us-east-1": dial tcp: lookup cdn03.quay.io: no such host
:: [ 12:54:48 ] :: [   FAIL   ] :: Command 'podman build -t become-container-test:latest .' (Expected 0, got 125)
Attempt 1 unsuccessful.
:: [ 12:54:53 ] :: [  BEGIN   ] :: Running 'podman build -t become-container-test:latest .'
STEP 1/3: FROM quay.io/fedora/fedora:latest
Trying to pull quay.io/fedora/fedora:latest...
Getting image source signatures
Copying blob sha256:6eb6364132025ad55f6fcb77569eeda080231bd8b0afd82e508f3cb29c3adbec
Copying config sha256:ec546109f8227b6cca3212bad13f50f3f3555455f51f0162776a43f160f60343
Writing manifest to image destination
STEP 2/3: RUN useradd user; usermod -aG wheel user; echo -e 'user\tALL=(ALL)\tNOPASSWD: ALL' >> /etc/sudoers
--> 91182913579c
STEP 3/3: USER user
COMMIT become-container-test:latest
--> c745ebfc6328
Successfully tagged localhost/become-container-test:latest
c745ebfc63286ba815123c36b61ff927181fc9c6c2bfda201378dea9bf2596e0
:: [ 12:54:55 ] :: [   PASS   ] :: Command 'podman build -t become-container-test:latest .' (Expected 0, got 0)

Seems this is the only point where the podman tests are still
failing with the random network errors tracked in #2063. Let's
give several attempts to build the container to reduce the
failures.
@happz happz merged commit 74eb463 into main Nov 13, 2023
16 checks passed
@happz happz deleted the retry-podman-build branch November 13, 2023 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test coverage Improvements or additions to test coverage of tmt itself
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants