Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #955

/assign jpinsonneau

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 23, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: NETOBSERV-2023

In response to this:

This is an automated cherry-pick of #955

/assign jpinsonneau

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.

Copy link
Member

@jhadvig jhadvig left a comment

Choose a reason for hiding this comment

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

/lgtm
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jul 7, 2025
@jhadvig
Copy link
Member

jhadvig commented Jul 7, 2025

/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig, openshift-cherrypick-robot

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 7, 2025
@christoph-jerolimov
Copy link
Member

/retest

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 11, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 11, 2025

@jhadvig: This pull request references Jira Issue OCPBUGS-60304, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-60303 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-60303 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @yapei

This pull request references NETOBSERV-2023 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 story to target the "4.18.z" version, but no target version was set.

In response to this:

/jira refresh

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 requested a review from yapei August 11, 2025 13:53
@jhadvig
Copy link
Member

jhadvig commented Aug 11, 2025

/override ci/prow/okd-scos-e2e-aws-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 11, 2025

@jhadvig: Overrode contexts on behalf of jhadvig: ci/prow/okd-scos-e2e-aws-ovn

In response to this:

/override ci/prow/okd-scos-e2e-aws-ovn

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.

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

13 similar comments
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@yapei
Copy link
Contributor

yapei commented Aug 20, 2025

launched a cluster with command launch 4.18.0-0.nightly-2025-08-19-062444,openshift/console-operator#997 gcp
but didn't see netobserv consolequickstart

$ oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.18.0-0-2025-08-20-091903-test-ci-ln-s54bz72-latest   True        False         62m     Cluster version is 4.18.0-0-2025-08-20-091903-test-ci-ln-s54bz72-latest

$ oc get consolequickstart
NAME                             AGE
add-healthchecks                 70m
explore-pipelines                70m
host-inventory                   70m
install-cryostat                 70m
install-helmchartrepo-ns         70m
install-multicluster-engine      70m
install-serverless               70m
jboss-eap7-with-helm             70m
manage-helm-repos                70m
monitor-sampleapp                70m
node-with-s2i                    70m
odf-install-tour                 70m
quarkus-with-helm                70m
quarkus-with-s2i                 70m
rhdh-installation-via-helm       70m
rhdh-installation-via-operator   70m
sample-application               70m
spring-with-s2i                  70m
user-impersonation               70m

@yapei
Copy link
Contributor

yapei commented Aug 20, 2025

All Quick Starts in the testing cluster
Screenshot 2025-08-20 at 7 07 07 PM

@christoph-jerolimov
Copy link
Member

/uncc

@openshift-ci openshift-ci bot removed the request for review from christoph-jerolimov August 20, 2025 18:47
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fc9a3a2 and 2 for PR HEAD f59f5b9 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 21, 2025

@openshift-cherrypick-robot: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 60dd3f5 into openshift:release-4.18 Aug 21, 2025
12 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60304: All pull requests linked via external trackers have merged:

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

In response to this:

This is an automated cherry-pick of #955

/assign jpinsonneau

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-console-operator
This PR has been included in build openshift-enterprise-console-operator-container-v4.18.0-202508201440.p0.g60dd3f5.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.18.0-0.nightly-2025-08-27-065249

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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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.

10 participants