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

USHIFT-2080: configure-vm.sh: skip dnf update on demand #2762

Merged
merged 1 commit into from
Dec 19, 2023

Conversation

pmtk
Copy link
Member

@pmtk pmtk commented Dec 18, 2023

Goal is to speed up provisioning of MicroShift using cluster-bot

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 18, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 18, 2023

@pmtk: This pull request references USHIFT-2080 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.

In response to this:

Goal is to speed up provisioning of MicroShift using cluster-bot

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 18, 2023
@pmtk pmtk changed the title USHIFT-2080: Skip dnf update on demand USHIFT-2080: configure-vm.sh: skip dnf update on demand Dec 18, 2023
@ggiguash
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 18, 2023
Copy link
Contributor

openshift-ci bot commented Dec 18, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

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:

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

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9c8679c and 2 for PR HEAD 69a4df0 in total

@pmtk
Copy link
Member Author

pmtk commented Dec 19, 2023

/override ci/prow/microshift-metal-tests ci/prow/microshift-metal-tests-arm

unrelated failures

Copy link
Contributor

openshift-ci bot commented Dec 19, 2023

@pmtk: Overrode contexts on behalf of pmtk: ci/prow/microshift-metal-tests, ci/prow/microshift-metal-tests-arm

In response to this:

/override ci/prow/microshift-metal-tests ci/prow/microshift-metal-tests-arm

unrelated failures

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.

Copy link
Contributor

openshift-ci bot commented Dec 19, 2023

@pmtk: all tests passed!

Full PR test history. Your PR dashboard.

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-bot openshift-merge-bot bot merged commit 8d60e2b into openshift:main Dec 19, 2023
8 checks passed
@pmtk pmtk deleted the configure-vm-skip-update branch December 19, 2023 10:34
@ggiguash
Copy link
Contributor

/cherry-pick release-4.15

@openshift-cherrypick-robot

@ggiguash: new pull request created: #2802

In response to this:

/cherry-pick release-4.15

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.

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants