Skip to content

OCPBUGS-31019: Compute Node to Nodes (Typo Fix) #76816

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 3, 2024
Merged

OCPBUGS-31019: Compute Node to Nodes (Typo Fix) #76816

merged 1 commit into from
Jun 3, 2024

Conversation

obrown1205
Copy link
Contributor

@obrown1205 obrown1205 commented Jun 3, 2024 •
edited
Loading

@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 3, 2024
@openshift-ci-robot
Copy link

@obrown1205: This pull request references Jira Issue OCPBUGS-31019, which is invalid:

  • expected Jira Issue OCPBUGS-31019 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Version(s):
4.12

Issue:
https://issues.redhat.com/browse/OCPBUGS-31019

Link to docs preview:

QE review:
N/A

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jun 3, 2024
@ocpdocs-previewbot
Copy link

🤖 Mon Jun 03 13:32:35 - Prow CI generated the docs preview:

https://76816--ocpdocs-pr.netlify.app/openshift-enterprise/latest/updating/understanding-openshift-update-duration.html

@obrown1205 obrown1205 changed the title OCPBUGS-31019: Compute Node to Nodes OCPBUGS-31019: Compute Node to Nodes (Typo Fix) Jun 3, 2024
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jun 3, 2024

@obrown1205: 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-sigs/prow repository. I understand the commands that are listed here.

@obrown1205
Copy link
Contributor Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Jun 3, 2024
@xenolinux
Copy link
Contributor

/label peer-review-in-progress

@openshift-ci openshift-ci bot added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Jun 3, 2024
xenolinux
xenolinux reviewed Jun 3, 2024
View reviewed changes
Copy link
Contributor

@xenolinux xenolinux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

/remove-label peer-review-needed
/remove-label peer-review-in-progress
/label peer-review-done

@openshift-ci openshift-ci bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Jun 3, 2024
@obrown1205
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Jun 3, 2024
@skopacz1 skopacz1 added merge-review-in-progress Signifies that the merge review team is reviewing this PR branch/enterprise-4.12 labels Jun 3, 2024
@skopacz1 skopacz1 added this to the Continuous Release milestone Jun 3, 2024
skopacz1
skopacz1 approved these changes Jun 3, 2024
View reviewed changes
Copy link
Contributor

@skopacz1 skopacz1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@skopacz1 skopacz1 merged commit b044b86 into openshift:enterprise-4.12 Jun 3, 2024
@openshift-ci-robot
Copy link

@obrown1205: Jira Issue OCPBUGS-31019: All pull requests linked via external trackers have merged:

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

In response to this:

Version(s):
4.12

Issue:
https://issues.redhat.com/browse/OCPBUGS-31019

Link to docs preview:
https://76816--ocpdocs-pr.netlify.app/openshift-enterprise/latest/updating/understanding-openshift-update-duration.html#machine-config-operator-node-updates_openshift-update-duration

QE review:
N/A

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

@skopacz1 skopacz1 removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@xenolinux xenolinux xenolinux left review comments

@skopacz1 skopacz1 skopacz1 approved these changes

Assignees

No one assigned

Labels

branch/enterprise-4.12 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. peer-review-done Signifies that the peer review team has reviewed this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Milestone

Continuous Release

Development

Successfully merging this pull request may close these issues.

5 participants

@obrown1205 @openshift-ci-robot @ocpdocs-previewbot @xenolinux @skopacz1