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

OCPBUGS-24199: Add client version in must-gather summary #1603

Merged
merged 1 commit into from Nov 28, 2023

Conversation

soltysh
Copy link
Member

@soltysh soltysh commented Nov 27, 2023

/assign @oarribas

Sample output looks like:

Reprinting Cluster State:
When opening a support case, bugzilla, or issue please include the following summary data along with any other requested information:
ClusterID: fc1339d9-8905-4353-ab48-30ba10b308b2
ClientVersion: v4.2.0-alpha.0-2063-g1d4a9af  <- this is new here
ClusterVersion: Stable at "4.15.0-0.nightly-2023-11-25-110147"
...

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 27, 2023
@soltysh
Copy link
Member Author

soltysh commented Nov 27, 2023

/label no-jira

Copy link
Contributor

openshift-ci bot commented Nov 27, 2023

@soltysh: The label(s) /label no-jira cannot be applied. These labels are supported: acknowledge-critical-fixes-only, 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/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label no-jira

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.

@soltysh soltysh changed the title Add client version in must-gather summary NO-JIRA: Add client version in must-gather summary Nov 27, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 27, 2023
@openshift-ci-robot
Copy link

@soltysh: This pull request explicitly references no jira issue.

In response to this:

/assign @oarribas

Sample output looks like:

Reprinting Cluster State:
When opening a support case, bugzilla, or issue please include the following summary data along with any other requested information:
ClusterID: fc1339d9-8905-4353-ab48-30ba10b308b2
ClientVersion: v4.2.0-alpha.0-2063-g1d4a9af  <- this is new here
ClusterVersion: Stable at "4.15.0-0.nightly-2023-11-25-110147"
...

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.

@oarribas
Copy link

This is related to https://issues.redhat.com/browse/RFE-3060

/lgtm

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

openshift-ci bot commented Nov 27, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: oarribas, soltysh

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 e2a6fd1 and 2 for PR HEAD 17c0df1 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 3b3f931 and 1 for PR HEAD 17c0df1 in total

@oarribas
Copy link

/retest

Copy link
Contributor

openshift-ci bot commented Nov 28, 2023

@soltysh: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security 17c0df1 link false /test security

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 f36933e into openshift:master Nov 28, 2023
12 of 13 checks passed
@oarribas
Copy link

@soltysh , can this be backported to 4.12+ releases?

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-cli-container-v4.15.0-202311282232.p0.gf36933e.assembly.stream for distgit openshift-enterprise-cli.
All builds following this will include this PR.

@soltysh soltysh deleted the must_gather_version branch November 29, 2023 12:38
@soltysh
Copy link
Member Author

soltysh commented Nov 29, 2023

/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

@openshift-cherrypick-robot

@soltysh: new pull request created: #1607

In response to this:

/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

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.

@oarribas
Copy link

@soltysh soltysh changed the title NO-JIRA: Add client version in must-gather summary OCPBUGS-24199: Add client version in must-gather summary Nov 29, 2023
@openshift-ci-robot
Copy link

@soltysh: Jira Issue OCPBUGS-24199: All pull requests linked via external trackers have merged:

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

In response to this:

/assign @oarribas

Sample output looks like:

Reprinting Cluster State:
When opening a support case, bugzilla, or issue please include the following summary data along with any other requested information:
ClusterID: fc1339d9-8905-4353-ab48-30ba10b308b2
ClientVersion: v4.2.0-alpha.0-2063-g1d4a9af  <- this is new here
ClusterVersion: Stable at "4.15.0-0.nightly-2023-11-25-110147"
...

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.

None yet

5 participants