Run k8sgpt as part of hypershift-dump chain - #68540
Conversation
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
|
/pj-rehearse ? |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@mgencur: job(s): ? either don't exist or were not found to be affected, and cannot be rehearsed |
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-conformance-cilium |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-conformance-cilium-k8sgpt |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
The k8sgpt returns this error: As can be seen here |
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-conformance-cilium-k8sgpt |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-conformance-cilium-k8sgpt |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-conformance-cilium-k8sgpt |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@mgencur, Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@mgencur, If the problem persists, please contact Test Platform. |
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-conformance-cilium-k8sgpt |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-conformance-cilium-k8sgpt |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-conformance-cilium-k8sgpt |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-conformance-cilium-k8sgpt |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-conformance-cilium-k8sgpt |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
95969ab to
b569d2f
Compare
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
|
/hold For rehearsal jobs to pass. |
openshift-ci
Bot
added
the
do-not-merge/hold
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aws-ovn-conformance |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@mgencur: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/unhold |
openshift-ci
Bot
removed
the
do-not-merge/hold
This commit adds k8sgpt integration to the hypershift-dump workflow by: - Adding k8sgpt step to the dump chain configuration - Creating new k8sgpt step registry files (commands, metadata, yaml config, and OWNERS)
ba76675 to
b9bfd7c
Compare
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aws-ovn-conformance |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
A total of 621 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LiangquanLi930, mgencur The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
|
/pj-rehearse ack |
|
@mgencur: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
| mkdir -p "${ARTIFACT_DIR}/namespaces" "${ARTIFACT_DIR}/hostedcluster" | ||
|
|
||
| CLUSTER_NAME="$(echo -n $PROW_JOB_ID|sha256sum|cut -c-20)" | ||
| HOSTED_CLUSTER_NS=$(oc get hostedcluster -A -ojsonpath='{.items[0].metadata.namespace}') |
There was a problem hiding this comment.
kubevirt presubmit job is failing here
* Run k8sgpt as part of hypershift-dump chain This commit adds k8sgpt integration to the hypershift-dump workflow by: - Adding k8sgpt step to the dump chain configuration - Creating new k8sgpt step registry files (commands, metadata, yaml config, and OWNERS) * Make sure the script doesn't fail if there's no guest cluster * Collect hypershift-related namespaces from mgmt cluster * Download k8sgpt binary directly to get latest version
* Run k8sgpt as part of hypershift-dump chain This commit adds k8sgpt integration to the hypershift-dump workflow by: - Adding k8sgpt step to the dump chain configuration - Creating new k8sgpt step registry files (commands, metadata, yaml config, and OWNERS) * Make sure the script doesn't fail if there's no guest cluster * Collect hypershift-related namespaces from mgmt cluster * Download k8sgpt binary directly to get latest version
4 participants
Adds k8sgpt integration to the hypershift-dump workflow by:
The step produces files under
hypershift-k8sgpt/artifacts/:See example with errors from the latest run. It shows an error in the HCP namespace and no errors in the hosted cluster.
The step currently doesn't run the analysis through AI (via
--explainflag for k8sgpt) as it is currently tied to an OpenShift OpenAI account that reached its limits. The plan is to change this to use Gemini (see slack thread). When this account is available we can enable AI analysis. Until that time, please see openshift/hypershift#6720 which adds a custom Claude command to analyze the output of these errors (instead of doing it directly by k8sgpt by calling AI).Note: The current usage of k8sgpt doesn't gather errors from Pod logs as it doesn't explicitly use the
Loganalyzer (available through--filter Log). This needs further investigation as there are usually errors that are "OK" such as some temporary reconciler error).