search

openshift / image-registry

OpenShift cluster image registry
Apache License 2.0
45 stars 75 forks source link

OCPBUGS-102: Keep OCI image configs when hard prune #341

Closed dmage closed 2 years ago

openshift-ci-robot commented 2 years ago

@dmage: Jira Issue [OCPBUGS-102](https://issues.redhat.com//browse/OCPBUGS-102) is in a security level that is not in the allowed security levels for this repo. Allowed security levels for this repo are:

In response to [this](https://github.com/openshift/image-registry/pull/341): > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
dmage commented 2 years ago

/assign @flavianmissi

flavianmissi commented 2 years ago

/lgtm

are the tests just being flaky?

openshift-ci[bot] commented 2 years ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dmage, flavianmissi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[pkg/dockerregistry/OWNERS](https://github.com/openshift/image-registry/blob/master/pkg/dockerregistry/OWNERS)~~ [dmage] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
AlexNPavel commented 2 years ago

/jira refresh

openshift-ci-robot commented 2 years ago

@AlexNPavel: This pull request references Jira Issue [OCPBUGS-102](https://issues.redhat.com//browse/OCPBUGS-102), which is invalid:

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to [this](https://github.com/openshift/image-registry/pull/341#issuecomment-1219921545): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
dmage commented 2 years ago

@flavianmissi no, tests are broken (not by this PR) :(

dmage commented 2 years ago

/retest

dmage commented 2 years ago

/retest

dmage commented 2 years ago

/jira refresh

openshift-ci-robot commented 2 years ago

@dmage: This pull request references Jira Issue OCPBUGS-102, which is invalid:

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to [this](https://github.com/openshift/image-registry/pull/341#issuecomment-1230077560): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
dmage commented 2 years ago

/jira refresh

openshift-ci-robot commented 2 years ago

@dmage: This pull request references Jira Issue OCPBUGS-102, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.12.0) matches configured target version for branch (4.12.0) * bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
In response to [this](https://github.com/openshift/image-registry/pull/341#issuecomment-1230078696): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
dmage commented 2 years ago

/retest

dmage commented 2 years ago

/retest

dmage commented 2 years ago

/test e2e-aws

openshift-ci[bot] commented 2 years ago

@dmage: The specified target(s) for /test were not found. The following commands are available to trigger required jobs:

The following commands are available to trigger optional jobs:

Use /test all to run the following jobs that were automatically triggered:

In response to [this](https://github.com/openshift/image-registry/pull/341#issuecomment-1232788188): >/test e2e-aws Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
dmage commented 2 years ago

/override ci/prow/e2e-aws now it is called e2e-aws-ovn

openshift-ci[bot] commented 2 years ago

@dmage: Overrode contexts on behalf of dmage: ci/prow/e2e-aws

In response to [this](https://github.com/openshift/image-registry/pull/341#issuecomment-1232792551): >/override ci/prow/e2e-aws >now it is called e2e-aws-ovn Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
openshift-ci[bot] commented 2 years ago

@dmage: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
openshift-ci-robot commented 2 years ago

@dmage: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-102 has been moved to the MODIFIED state.

In response to [this](https://github.com/openshift/image-registry/pull/341): > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
dmage commented 2 years ago

/cherrypick release-4.11

openshift-cherrypick-robot commented 2 years ago

@dmage: new pull request created: #343

In response to [this](https://github.com/openshift/image-registry/pull/341#issuecomment-1232809378): >/cherrypick release-4.11 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.