NO-ISSUE:rebase-4.13.0-0.nightly-2023-04-12-050538_amd64-2023-04-12_arm64-2023-04-11

[microshift-rebase-script]

amd64: 4.13.0-0.nightly-2023-04-12-050538
arm64: 4.13.0-0.nightly-arm64-2023-04-11-174952
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.13-rebase-on-nightlies/1646377819581714432

/label tide/merge-method-squash

[openshift-ci]

@microshift-rebase-script[bot]: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

rebase-4.13.0-0.nightly-2023-04-12-050538_amd64-2023-04-12_arm64-2023-04-11

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.

[openshift-ci]

@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.

[pacevedom]

/retitle NO-ISSUE:rebase-4.13.0-0.nightly-2023-04-12-050538_amd64-2023-04-12_arm64-2023-04-11

[pacevedom]

/label backport-risk-assessed
/label lgtm
/label cherry-pick-approved
/label bugzilla/valid-bug
/label approved

[openshift-ci]

@microshift-rebase-script[bot]: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

NO-ISSUE:rebase-4.13.0-0.nightly-2023-04-12-050538_amd64-2023-04-12_arm64-2023-04-11

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.

[openshift-ci-robot]

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

amd64: 4.13.0-0.nightly-2023-04-12-050538
arm64: 4.13.0-0.nightly-arm64-2023-04-11-174952
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.13-rebase-on-nightlies/1646377819581714432

/label tide/merge-method-squash

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.

[openshift-ci]

@pacevedom: Can not set label approved: Must be member in one of these teams: [openshift-release-oversight]

Details

In response to this:

/label backport-risk-assessed
/label lgtm
/label cherry-pick-approved
/label bugzilla/valid-bug
/label approved

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.

[openshift-ci]

@pacevedom: The label(s) /label lgtm cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, rebase/manual, approved, backport-risk-assessed, bugzilla/invalid-bug, bugzilla/valid-bug, cherry-pick-approved, jira/invalid-bug, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label backport-risk-assessed
/label lgtm
/label cherry-pick-approved
/label bugzilla/valid-bug
/label approved

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.

[pacevedom]

/approved

[pacevedom]

/label lgtm

[openshift-ci]

@pacevedom: The label(s) /label lgtm cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, rebase/manual, approved, backport-risk-assessed, bugzilla/invalid-bug, bugzilla/valid-bug, cherry-pick-approved, jira/invalid-bug, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label lgtm

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.

[pacevedom]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• OWNERS [pacevedom]

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