Skip to content

rebase-4.12.0-0.nightly_amd64-2023-06-26-100619_arm64-2023-06-29-005130#1973

Merged
openshift-merge-robot merged 3 commits into
release-4.12from
rebase-4.12.0-0.nightly_amd64-2023-06-26-100619_arm64-2023-06-29-005130
Jun 29, 2023
Merged

rebase-4.12.0-0.nightly_amd64-2023-06-26-100619_arm64-2023-06-29-005130#1973
openshift-merge-robot merged 3 commits into
release-4.12from
rebase-4.12.0-0.nightly_amd64-2023-06-26-100619_arm64-2023-06-29-005130

Conversation

@microshift-rebase-script

Copy link
Copy Markdown
Contributor
amd64: 4.12.0-0.nightly-2023-06-26-100619
arm64: 4.12.0-0.nightly-arm64-2023-06-29-005130
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.12-rebase-on-nightlies/1674281727658299392

# ovn-kubernetes image-arm64 17f9ed57beb21648ed53e5c360a6ad35f3791091 to 3aa743ca58669d91cc7da29aa5157648a4241361

741a619f85104ad0b404996afc596e5652728cbb 2023-06-27T09:02:09+02:00 Add default deny acl externalID to avoid duplicate acls for namespaces with long names. every namespace has 4 default deny acls: ingress/egress and deny/allow. Direction was in the ExternalIDs before, but action was a suffix in acl name, that gets truncated for long namespace names, therefore deny and allow acls for the same direction would have the same name and ExternalIDs. New ExternalID should fix this case.

/label tide/merge-method-squash

@openshift-ci openshift-ci Bot requested review from fzdarsky and sallyom June 29, 2023 05:10
@dhellmann dhellmann added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 29, 2023
@dhellmann

Copy link
Copy Markdown
Contributor

/approve
/lgtm
/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci openshift-ci Bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jun 29, 2023
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 29, 2023
@openshift-ci

openshift-ci Bot commented Jun 29, 2023

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhellmann, microshift-rebase-script[bot]

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 29, 2023
@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 8b52659 and 2 for PR HEAD c9d7c85 in total

@openshift-ci

openshift-ci Bot commented Jun 29, 2023

Copy link
Copy Markdown
Contributor

@microshift-rebase-script[bot]: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit ac974f4 into release-4.12 Jun 29, 2023
@openshift-merge-robot openshift-merge-robot deleted the rebase-4.12.0-0.nightly_amd64-2023-06-26-100619_arm64-2023-06-29-005130 branch June 29, 2023 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants