Hi @zuzzas. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

@dcantah
The failed test does not look related at all.

/ok-to-test

(Though I think the Prow job is having issues now)

@zuzzas: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

ServiceException: 409 A Cloud Storage bucket named 'cri-containerd-staging' already exists. Try another name. Bucket names must be globally unique across all Google Cloud projects, including those outside of your organization.

>_<

The Prow failure looks completely unrelated. I'm going to merge this anyway.

Thanks!