Skip to content

Conversation

@dustymabe
Copy link
Member

If a manifest previously exists then let's try to clean it up before continuing. We saw this in the pipeline where one run failed in the middle and then a later run failed because the manifest existed:

2024-11-19 14:29:26,184 INFO - Running command: ['podman', 'manifest', 'create', 'quay.io/coreos-assembler/coreos-assembler:main']
Error: creating manifest: image name "quay.io/coreos-assembler/coreos-assembler:main" is already associated with image "ffbb463bfb0e3bb0fb4c42856d2dca0ff985d1dd5d7b34f1b3ae0277287ad83d": that name is already in use

@dustymabe
Copy link
Member Author

This was partially exposed because of coreos/fedora-coreos-pipeline#1047 where we're now using the persistent builders for this task.

marmijo
marmijo previously approved these changes Nov 19, 2024
Copy link
Member

@marmijo marmijo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

manifest_info = runcmd(["podman", "manifest", "inspect", f"{repo}:{tag}"],
capture_output=True).stdout
return json.loads(manifest_info)

Copy link
Member

@aaradhak aaradhak Nov 19, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need an extra line here? CI test fails as two blank lines are required before every function.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

print(f" STDERR: {cp.stderr.decode()}")
raise Exception("Error encountered when checking if manifest exists")
return cp.returncode == 0

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

may be an extra line here too

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

If a manifest previously exists then let's try to clean it up before
continuing. We saw this in the pipeline where one run failed in the
middle and then a later run failed because the manifest existed:

```
2024-11-19 14:29:26,184 INFO - Running command: ['podman', 'manifest', 'create', 'quay.io/coreos-assembler/coreos-assembler:main']
Error: creating manifest: image name "quay.io/coreos-assembler/coreos-assembler:main" is already associated with image "ffbb463bfb0e3bb0fb4c42856d2dca0ff985d1dd5d7b34f1b3ae0277287ad83d": that name is already in use
```
@dustymabe dustymabe force-pushed the dusty-push-container-manifest branch from 7a53b49 to 9639525 Compare November 19, 2024 23:59
@dustymabe dustymabe enabled auto-merge (rebase) November 20, 2024 14:04
Copy link
Member

@aaradhak aaradhak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dustymabe dustymabe merged commit 01e4e55 into coreos:main Nov 20, 2024
5 checks passed
@dustymabe dustymabe deleted the dusty-push-container-manifest branch November 20, 2024 14:05
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