OCPQE-31264: update 80458's timeout to 180s #579

jianzhangbjz · 2025-12-08T02:37:07Z

The expected message costs time more than 90s. It started at 04:19:51, failed at 04:21:16. But, the expected message was generated at 04:21:21.

I1205 04:19:51.799640 16884 catalog.go:149] ========= check clustercatalog clustercatalog-80458 Progressing message expect is manifest unknown =========
I1205 04:19:56.801879 16884 client.go:729] Running 'oc --kubeconfig=/tmp/kubeconfig-636540072 get clustercatalog clustercatalog-80458 -o jsonpath={.status.conditions[?(@.type=="Progressing")].message}'
I1205 04:19:56.899309 16884 tools.go:343] output is , error is <nil>, and try next
...
I1205 04:21:16.909088 16884 catalog.go:158] got is source catalog content: error creating image source: pinging container registry my-route-e2e-test-olmv1-opecob0a65c1d-jtzpj.apps.ci-op-d8lmgqk8-dc43b.XXXXXXXXXXXXXXXXXXXXXX: Get "https://my-route-e2e-test-olmv1-opecob0a65c1d-jtzpj.apps.ci-op-d8lmgqk8-dc43b.XXXXXXXXXXXXXXXXXXXXXX/v2/": tls: failed to verify certificate: x509: certificate signed by unknown authority, not manifest unknown, and try next
I1205 04:21:21.800218 16884 client.go:729] Running 'oc --kubeconfig=/tmp/kubeconfig-636540072 get clustercatalog clustercatalog-80458 -o=jsonpath-as-json={.status}'
I1205 04:21:21.892813 16884 tools.go:348] $oc get [clustercatalog clustercatalog-80458 -o=jsonpath-as-json={.status}], the returned resource:[
    {
        "conditions": [
            {
                "lastTransitionTime": "2025-12-05T04:19:56Z",
                "message": "source catalog content: error creating image source: reading manifest v4.17 in my-route-e2e-test-olmv1-opecob0a65c1d-jtzpj.apps.ci-op-d8lmgqk8-dc43b.XXXXXXXXXXXXXXXXXXXXXX/redhat/redhat-operator-index: manifest unknown",
                "observedGeneration": 1,
                "reason": "Retrying",
                "status": "True",
                "type": "Progressing"
            }
        ]
    }
]
I1205 04:21:21.892908 16884 catalog.go:167] Cluster catalog debug status: [
    {
        "conditions": [
            {
                "lastTransitionTime": "2025-12-05T04:19:56Z",
                "message": "source catalog content: error creating image source: reading manifest v4.17 in my-route-e2e-test-olmv1-opecob0a65c1d-jtzpj.apps.ci-op-d8lmgqk8-dc43b.XXXXXXXXXXXXXXXXXXXXXX/redhat/redhat-operator-index: manifest unknown",
                "observedGeneration": 1,
                "reason": "Retrying",
                "status": "True",
                "type": "Progressing"
            }
        ]
    }
]
I1205 04:21:21.893197 16884 catalog.go:227] =========Delete clustercatalog clustercatalog-80458=========

openshift-ci-robot · 2025-12-08T02:37:10Z

@jianzhangbjz: This pull request references OCPQE-31264 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 sub-task to target the "4.21.0" version, but no target version was set.

In response to this:

The expected message costs time more than 90s. It started at 04:19:51, failed at 04:21:16. But, the expected message was generated at 04:21:21.

I1205 04:19:51.799640 16884 catalog.go:149] ========= check clustercatalog clustercatalog-80458 Progressing message expect is manifest unknown =========
I1205 04:19:56.801879 16884 client.go:729] Running 'oc --kubeconfig=/tmp/kubeconfig-636540072 get clustercatalog clustercatalog-80458 -o jsonpath={.status.conditions[?(@.type=="Progressing")].message}'
I1205 04:19:56.899309 16884 tools.go:343] output is , error is <nil>, and try next
...
I1205 04:21:16.909088 16884 catalog.go:158] got is source catalog content: error creating image source: pinging container registry my-route-e2e-test-olmv1-opecob0a65c1d-jtzpj.apps.ci-op-d8lmgqk8-dc43b.XXXXXXXXXXXXXXXXXXXXXX: Get "https://my-route-e2e-test-olmv1-opecob0a65c1d-jtzpj.apps.ci-op-d8lmgqk8-dc43b.XXXXXXXXXXXXXXXXXXXXXX/v2/": tls: failed to verify certificate: x509: certificate signed by unknown authority, not manifest unknown, and try next
I1205 04:21:21.800218 16884 client.go:729] Running 'oc --kubeconfig=/tmp/kubeconfig-636540072 get clustercatalog clustercatalog-80458 -o=jsonpath-as-json={.status}'
I1205 04:21:21.892813 16884 tools.go:348] $oc get [clustercatalog clustercatalog-80458 -o=jsonpath-as-json={.status}], the returned resource:[
   {
       "conditions": [
           {
               "lastTransitionTime": "2025-12-05T04:19:56Z",
               "message": "source catalog content: error creating image source: reading manifest v4.17 in my-route-e2e-test-olmv1-opecob0a65c1d-jtzpj.apps.ci-op-d8lmgqk8-dc43b.XXXXXXXXXXXXXXXXXXXXXX/redhat/redhat-operator-index: manifest unknown",
               "observedGeneration": 1,
               "reason": "Retrying",
               "status": "True",
               "type": "Progressing"
           }
       ]
   }
]
I1205 04:21:21.892908 16884 catalog.go:167] Cluster catalog debug status: [
   {
       "conditions": [
           {
               "lastTransitionTime": "2025-12-05T04:19:56Z",
               "message": "source catalog content: error creating image source: reading manifest v4.17 in my-route-e2e-test-olmv1-opecob0a65c1d-jtzpj.apps.ci-op-d8lmgqk8-dc43b.XXXXXXXXXXXXXXXXXXXXXX/redhat/redhat-operator-index: manifest unknown",
               "observedGeneration": 1,
               "reason": "Retrying",
               "status": "True",
               "type": "Progressing"
           }
       ]
   }
]
I1205 04:21:21.893197 16884 catalog.go:227] =========Delete clustercatalog clustercatalog-80458=========

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 · 2025-12-08T02:37:30Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jianzhangbjz

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:

~~DOWNSTREAM_OWNERS~~ [jianzhangbjz]

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

jianzhangbjz · 2025-12-08T02:37:35Z

Test passed.

jiazha-mac:tests-extension jiazha$ ./bin/olmv1-tests-ext run-test "[sig-olmv1][Jira:OLM] clustercatalog PolarionID:80458-[OTP][Level0][Skipped:Disconnected]clustercatalog get x509 error since it cannot get the custom CA automatically [Serial]"
  [INFO] [env] Using kubeconfig: /Users/jiazha/21-kubeconfig
  [INFO] [env] Cluster environment initialized (OpenShift: true)
  I1208 10:34:04.808952 21486 test_context.go:567] The --provider flag is not set. Continuing as if --provider=skeleton had been used.
  Running Suite:  - /Users/jiazha/goproject/operator-framework-operator-controller/openshift/tests-extension
  ==========================================================================================================
  Random Seed: 1765161241 - will randomize all specs

  Will run 1 of 1 specs
  ------------------------------
  [sig-olmv1][Jira:OLM] clustercatalog PolarionID:80458-[OTP][Level0][Skipped:Disconnected]clustercatalog get x509 error since it cannot get the custom CA automatically [Serial] [NonHyperShiftHOST, ClusterCatalog, original-name:[sig-olmv1][Jira:OLM] clustercatalog PolarionID:80458-[Skipped:Disconnected]clustercatalog get x509 error since it cannot get the custom CA automatically [Serial]]
  /Users/jiazha/goproject/operator-framework-operator-controller/openshift/tests-extension/test/qe/specs/olmv1_cc.go:46
    STEP: Creating a kubernetes client @ 12/08/25 10:34:04.81
  I1208 10:34:09.815703 21486 client.go:729] Running 'oc --kubeconfig=/Users/jiazha/21-kubeconfig explain template.apiVersion'
    STEP: 1) create a random namespace @ 12/08/25 10:34:12.694
  I1208 10:34:12.694466 21486 client.go:349] do not know if it is external oidc cluster or not, and try to check it again
  I1208 10:34:12.694728 21486 client.go:753] showInfo is true
  I1208 10:34:12.694751 21486 client.go:755] Running 'oc --kubeconfig=/Users/jiazha/21-kubeconfig get authentication/cluster -o=jsonpath={.spec.type}'
  I1208 10:34:13.656333 21486 clusters.go:568] Found authentication type used: 
  I1208 10:34:16.076576 21486 client.go:200] configPath is now "/var/folders/5n/w9ysf4w93jnfy7k19xxct31c0000gn/T/configfile2011623298"
  I1208 10:34:16.076656 21486 client.go:363] The user is now "e2e-test-default-r9v9j-user"
  I1208 10:34:16.076680 21486 client.go:366] Creating project "e2e-test-default-r9v9j"
  I1208 10:34:16.440146 21486 client.go:375] Waiting on permissions in project "e2e-test-default-r9v9j" ...
  I1208 10:34:17.684037 21486 client.go:436] Waiting for ServiceAccount "default" to be provisioned...
  I1208 10:34:18.072294 21486 client.go:436] Waiting for ServiceAccount "builder" to be provisioned...
  I1208 10:34:18.458637 21486 client.go:436] Waiting for ServiceAccount "deployer" to be provisioned...
  I1208 10:34:18.848917 21486 client.go:446] Waiting for RoleBinding "system:image-builders" to be provisioned...
  I1208 10:34:19.425833 21486 client.go:446] Waiting for RoleBinding "system:deployers" to be provisioned...
  I1208 10:34:20.064258 21486 client.go:446] Waiting for RoleBinding "system:image-pullers" to be provisioned...
  I1208 10:34:20.627117 21486 client.go:477] Project "e2e-test-default-r9v9j" has been fully provisioned.
    STEP: 2) create an image registry @ 12/08/25 10:34:20.627
  I1208 10:34:20.628266 21486 client.go:729] Running 'oc --kubeconfig=/var/folders/5n/w9ysf4w93jnfy7k19xxct31c0000gn/T/configfile2011623298 new-app --image quay.io/openshifttest/registry@sha256:1106aedc1b2e386520bc2fb797d9a7af47d651db31d8e7ab472f2352da37d1b3 -n e2e-test-default-r9v9j REGISTRY_STORAGE_DELETE_ENABLED=true --import-mode=PreserveOriginal'
  --> Found container image 1106aed (1 second old) from quay.io for "quay.io/openshifttest/registry@sha256:1106aedc1b2e386520bc2fb797d9a7af47d651db31d8e7ab472f2352da37d1b3"

      * An image stream tag will be created as "registry:latest" that will track this image

  --> Creating resources ...
      imagestream.image.openshift.io "registry" created
      deployment.apps "registry" created
      service "registry" created
  --> Success
      Application is not exposed. You can expose services to the outside world by executing one or more of the commands below:
       'oc expose service/registry' 
      Run 'oc status' to view your app.
  I1208 10:34:27.770352 21486 olmv1_cc.go:58] Get registry pods: [registry-6dbd6f66d8-mctkn]
  I1208 10:34:27.770673 21486 client.go:729] Running 'oc --kubeconfig=/var/folders/5n/w9ysf4w93jnfy7k19xxct31c0000gn/T/configfile2011623298 create route edge my-route --service=registry -n e2e-test-default-r9v9j'
  I1208 10:34:28.984940 21486 client.go:729] Running 'oc --kubeconfig=/var/folders/5n/w9ysf4w93jnfy7k19xxct31c0000gn/T/configfile2011623298 get route my-route -o=jsonpath={.spec.host} -n e2e-test-default-r9v9j'
  I1208 10:34:30.006336 21486 client.go:729] Running 'oc --kubeconfig=/var/folders/5n/w9ysf4w93jnfy7k19xxct31c0000gn/T/configfile2011623298 set volume deploy registry --add -t pvc --claim-size=30G -m /var/lib/registry --overwrite -n e2e-test-default-r9v9j'
  I1208 10:34:31.624432 21486 client.go:729] Running 'oc --kubeconfig=/Users/jiazha/21-kubeconfig extract secret/router-ca -n openshift-ingress-operator --to=/tmp --confirm'
  I1208 10:34:32.669462 21486 client.go:729] Running 'oc --kubeconfig=/Users/jiazha/21-kubeconfig create -n openshift-config configmap trusted-ca-80458 --from-file=my-route-e2e-test-default-r9v9j.apps.anlid821.qe.devcluster.openshift.com=/tmp/tls.crt'
  I1208 10:34:33.651122 21486 client.go:729] Running 'oc --kubeconfig=/Users/jiazha/21-kubeconfig patch image.config.openshift.io/cluster -p {"spec": {"additionalTrustedCA": {"name": "trusted-ca-80458"}}} --type=merge'
  image.config.openshift.io/cluster patched
    STEP: 2.1) Wait for CA bundle to propagate to catalogd @ 12/08/25 10:34:35.498
  I1208 10:34:41.674877 21486 olmv1_cc.go:102] catalogd-trusted-ca-bundle ConfigMap has CA data, CA bundle synced
    STEP: 3) create a ClusterCatalog @ 12/08/25 10:34:41.675
  I1208 10:34:44.691463 21486 client.go:753] showInfo is true
  I1208 10:34:44.691697 21486 client.go:755] Running 'oc --namespace=e2e-test-default-r9v9j --kubeconfig=/Users/jiazha/21-kubeconfig process --ignore-unknown-parameters=true -f /var/folders/5n/w9ysf4w93jnfy7k19xxct31c0000gn/T/fixture-testdata-dir3309380337/test/qe/testdata/olm/clustercatalog.yaml -p NAME=clustercatalog-80458 IMAGE=my-route-e2e-test-default-r9v9j.apps.anlid821.qe.devcluster.openshift.com/redhat/redhat-operator-index:v4.17'
  I1208 10:34:45.883089 21486 template.go:128] generated resource configuration file: /var/folders/5n/w9ysf4w93jnfy7k19xxct31c0000gn/T/e2e-test-default-r9v9j-91c88aa3config.json.stdout
  I1208 10:34:45.890440 21486 client.go:729] Running 'oc --kubeconfig=/Users/jiazha/21-kubeconfig apply -f /var/folders/5n/w9ysf4w93jnfy7k19xxct31c0000gn/T/e2e-test-default-r9v9j-91c88aa3config.json.stdout'
  clustercatalog.olm.operatorframework.io/clustercatalog-80458 created
  I1208 10:34:47.183692 21486 catalog.go:149] ========= check clustercatalog clustercatalog-80458 Progressing message expect is manifest unknown =========
  I1208 10:34:52.259456 21486 client.go:729] Running 'oc --kubeconfig=/Users/jiazha/21-kubeconfig get clustercatalog clustercatalog-80458 -o jsonpath={.status.conditions[?(@.type=="Progressing")].message}'
  I1208 10:34:53.325399 21486 tools.go:348] $oc get [clustercatalog clustercatalog-80458 -o jsonpath={.status.conditions[?(@.type=="Progressing")].message}], the returned resource:source catalog content: error creating image source: reading manifest v4.17 in my-route-e2e-test-default-r9v9j.apps.anlid821.qe.devcluster.openshift.com/redhat/redhat-operator-index: manifest unknown
  I1208 10:34:53.325554 21486 catalog.go:227] =========Delete clustercatalog clustercatalog-80458=========
  I1208 10:34:53.325590 21486 catalog.go:219] =========DeleteWithoutCheck clustercatalog clustercatalog-80458=========
  I1208 10:34:53.325863 21486 client.go:729] Running 'oc --kubeconfig=/Users/jiazha/21-kubeconfig delete clustercatalog clustercatalog-80458'
  I1208 10:34:58.622184 21486 client.go:729] Running 'oc --kubeconfig=/Users/jiazha/21-kubeconfig get clustercatalog clustercatalog-80458'
  I1208 10:34:59.748305 21486 client.go:739] Error running /usr/local/bin/oc --kubeconfig=/Users/jiazha/21-kubeconfig get clustercatalog clustercatalog-80458:
  Error from server (NotFound): clustercatalogs.olm.operatorframework.io "clustercatalog-80458" not found
  I1208 10:34:59.748468 21486 tools.go:410] the resource is delete successfully
  I1208 10:34:59.748762 21486 client.go:729] Running 'oc --kubeconfig=/Users/jiazha/21-kubeconfig patch image.config.openshift.io/cluster -p {"spec": {"additionalTrustedCA": {"name": ""}}} --type=merge'
  image.config.openshift.io/cluster patched
  I1208 10:35:01.657707 21486 client.go:729] Running 'oc --kubeconfig=/Users/jiazha/21-kubeconfig delete -n openshift-config configmap trusted-ca-80458'
  configmap "trusted-ca-80458" deleted
  I1208 10:35:03.353188 21486 client.go:522] Deleted {user.openshift.io/v1, Resource=users  e2e-test-default-r9v9j-user}, err: <nil>
  I1208 10:35:03.658500 21486 client.go:522] Deleted {oauth.openshift.io/v1, Resource=oauthclients  e2e-client-e2e-test-default-r9v9j}, err: <nil>
  I1208 10:35:03.949674 21486 client.go:522] Deleted {oauth.openshift.io/v1, Resource=oauthaccesstokens  sha256~Jvr_wYs76q9BoGkmaN5d_tfc54IIhQWtiyZZVe4iefU}, err: <nil>
    STEP: Destroying namespace "e2e-test-default-r9v9j" for this suite. @ 12/08/25 10:35:03.951
  • [59.392 seconds]
  ------------------------------

  Ran 1 of 1 Specs in 59.393 seconds
  SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped

jianzhangbjz · 2025-12-08T02:38:01Z

Hi @kuiwang02 @Xia-Zhao-rh , could you help approve it? Thanks!

Xia-Zhao-rh · 2025-12-08T03:25:34Z

/lgtm

openshift-ci · 2025-12-08T05:28:51Z

@jianzhangbjz: 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.

jianzhangbjz · 2025-12-08T07:02:20Z

/verified by @jianzhangbjz

openshift-ci-robot · 2025-12-08T07:02:31Z

@jianzhangbjz: This PR has been marked as verified by @jianzhangbjz.

In response to this:

/verified by @jianzhangbjz

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.

tmshort · 2025-12-08T18:43:07Z

I'm concerned that chasing timeouts is not a proper fix.Are we sure this is the problem, and not something else?

jianzhangbjz · 2025-12-09T02:50:27Z

Yes, this test case does not always fail. In this failure, based on the log, it finally returns the expected message: manifest unknown", but it took more than 90s.

I1205 04:21:21.892908 16884 catalog.go:167] Cluster catalog debug status: [
    {
        "conditions": [
            {
                "lastTransitionTime": "2025-12-05T04:19:56Z",
                "message": "source catalog content: error creating image source: reading manifest v4.17 in my-route-e2e-test-olmv1-opecob0a65c1d-jtzpj.apps.ci-op-d8lmgqk8-dc43b.XXXXXXXXXXXXXXXXXXXXXX/redhat/redhat-operator-index: manifest unknown",
                "observedGeneration": 1,
                "reason": "Retrying",
                "status": "True",
                "type": "Progressing"
            }
        ]
    }
]

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 8, 2025

openshift-ci bot requested review from anik120 and oceanc80 December 8, 2025 02:37

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 8, 2025

UPSTREAM: <carry>: update 80458's timeout to 180s

410181d

jianzhangbjz force-pushed the 80458 branch from ece33ca to 410181d Compare December 8, 2025 02:41

openshift-ci bot assigned Xia-Zhao-rh Dec 8, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 8, 2025

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 8, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

OCPQE-31264: update 80458's timeout to 180s #579

OCPQE-31264: update 80458's timeout to 180s #579

jianzhangbjz commented Dec 8, 2025

Uh oh!

openshift-ci-robot commented Dec 8, 2025 •

edited by openshift-ci bot

Loading

Uh oh!

openshift-ci bot commented Dec 8, 2025

Uh oh!

jianzhangbjz commented Dec 8, 2025

Uh oh!

jianzhangbjz commented Dec 8, 2025

Uh oh!

Xia-Zhao-rh commented Dec 8, 2025

Uh oh!

openshift-ci bot commented Dec 8, 2025

Uh oh!

jianzhangbjz commented Dec 8, 2025

Uh oh!

openshift-ci-robot commented Dec 8, 2025

Uh oh!

tmshort commented Dec 8, 2025

Uh oh!

jianzhangbjz commented Dec 9, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

OCPQE-31264: update 80458's timeout to 180s #579

Are you sure you want to change the base?

OCPQE-31264: update 80458's timeout to 180s #579

Conversation

jianzhangbjz commented Dec 8, 2025

Uh oh!

openshift-ci-robot commented Dec 8, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci bot commented Dec 8, 2025

Uh oh!

jianzhangbjz commented Dec 8, 2025

Uh oh!

jianzhangbjz commented Dec 8, 2025

Uh oh!

Xia-Zhao-rh commented Dec 8, 2025

Uh oh!

openshift-ci bot commented Dec 8, 2025

Uh oh!

jianzhangbjz commented Dec 8, 2025

Uh oh!

openshift-ci-robot commented Dec 8, 2025

Uh oh!

tmshort commented Dec 8, 2025

Uh oh!

jianzhangbjz commented Dec 9, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

openshift-ci-robot commented Dec 8, 2025 •

edited by openshift-ci bot

Loading