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

test: update ami image id #385

Merged
merged 1 commit into from
Mar 12, 2024
Merged

Conversation

henrywang
Copy link
Contributor

This PR is to update ami id to latest according to compose update.

Signed-off-by: Xiaofeng Wang <henrywangxf@me.com>
@henrywang
Copy link
Contributor Author

henrywang commented Mar 11, 2024

Hi @cgwalters! Test is runing into an error Failed to invoke skopeo proxy method FinishPipe. This error should be the same as issue coreos/rpm-ostree#4567.
I retired twice and can't make it green.

Log:

- podman
  - run
  - --rm
  - --privileged
  - --pid=host
  - -v
  - /:/target
  - -v
  - /var/lib/containers:/var/lib/containers
  - --security-opt
  - label=type:unconfined_t
  - quay.io/redhat_emp1/centos-bootc-dev-test:v8j3
  - bootc
  - install
  - to-existing-root
  delta: '0:00:47.628819'
  end: '2024-03-11 12:40:17.139642'
  msg: non-zero return code
  rc: 1
  start: '2024-03-11 12:39:29.510823'
  stderr: "\e[31mERROR\e[0m Installing to filesystem: Creating ostree deployment: Performing deployment: Importing: Parsing layer blob sha256:6238f7e3a90b3af82553597d6813548e81db1d12cba8872a820a68978c46522a: Failed to invoke skopeo proxy method FinishPipe: remote error: write |1: broken pipe"
  stderr_lines: <omitted>
  stdout: |-
    Mounting tmpfs /tmp
    Mounting efivarfs /sys/firmware/efi/efivars
    Mounting selinuxfs /sys/fs/selinux
    Initializing ostree layout
    Initializing sysroot
    ostree/deploy/default initialized as OSTree stateroot
    Creating initial deployment
  stdout_lines: <omitted>

@cgwalters
Copy link
Collaborator

It's always been a race condition AFAICS, but unfortunate we're seeing it here too.

@cgwalters
Copy link
Collaborator

As far as these AMI updates, I think we should probably configure renovate to do it.

@henrywang
Copy link
Contributor Author

As far as these AMI updates, I think we should probably configure renovate to do it.

This ami id will be used by at least two repos(bootc and bootc-workflow-test), I'll save ami id into AWS Systems Manager (SSM) Parameter Store. There's a CI in https://github.com/virt-s1/bootc-workflow-test/blob/main/.github/workflows/upload_rhel9_ami.yml. The CI includes a fully test for new ami. So I'll update this CI to deploy test passed ami id to AWS Systems Manager (SSM) Parameter Store instead of update the ami id in playbook.

@cgwalters cgwalters merged commit 268591f into containers:main Mar 12, 2024
16 of 17 checks passed
@henrywang henrywang deleted the update_amin branch June 9, 2024 05:26
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.

None yet

2 participants