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

Increase TLS kuttl timeout #1121

Closed

Conversation

Deydra71
Copy link
Contributor

@Deydra71 Deydra71 commented Oct 9, 2024

After deleting TLS cert secrets, the ctlplane can take longer to become ready again. The timeout is increased to prevent false failures.

After deleting TLS cert secrets, the ctlplane can take longer to become ready again. The timeout is increased to prevent false failures.

Signed-off-by: Veronika Fisarova <[email protected]>
Copy link
Contributor

@stuggi stuggi left a comment

Choose a reason for hiding this comment

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

/lgtm

Copy link
Contributor

openshift-ci bot commented Oct 9, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Deydra71, stuggi

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 label Oct 9, 2024
@stuggi
Copy link
Contributor

stuggi commented Oct 9, 2024

timeout seen e.g. in #1104

timeout reported on nova, but from must-gather that is ok. but the latest cr state shows that ceilometer telemetry cert secret is missing,

status:
  conditions:
  - lastTransitionTime: "2024-10-08T21:49:29Z"
    message: 'TLSInput is missing: secrets "cert-ceilometer-internal-svc in namespace
      openstack-kuttl-tests" not found'
    reason: Requested
    severity: Info
    status: "False"
    type: Ready

but from the cert request at https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/opensta[…]tificaterequests/ceilometer-internal-svc-2.yaml it seems it was successful about 20s later

  conditions:
  - lastTransitionTime: "2024-10-08T21:49:41Z"
    message: Certificate request has been approved by cert-manager.io
    reason: cert-manager.io
    status: "True"
    type: Approved
  - lastTransitionTime: "2024-10-08T21:49:43Z"
    message: Certificate fetched from issuer successfully
    reason: Issued
    status: "True"
    type: Ready

Copy link

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/1471fff7e522451999d99f31f6643393

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 28m 11s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 15m 26s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 33m 50s
openstack-operator-tempest-multinode FAILURE in 2h 16m 34s

@stuggi
Copy link
Contributor

stuggi commented Oct 9, 2024

so the issue seems to be different. telemetry-operator is not reconciling ceilometer when the cert secret is there.

the ceilometer cert secret was created at creationTimestamp: '2024-10-09T08:51:37Z' and the controller at least recognized it. we see

2024-10-09T08:51:37Z	INFO	Controllers.Ceilometer	input source cert-ceilometer-internal-svc changed, reconcile: ceilometer - openstack-kuttl-tests

as the last message in https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/opensta[…]roller-manager-b67d96f56-qbhmg/logs/manager.log . but no further log message that it really reconciled.

@Deydra71
Copy link
Contributor Author

/test openstack-operator-build-deploy-kuttl

@Deydra71
Copy link
Contributor Author

Closing as the root cause of failures was not in too short timeout, but in telemetry-operator, which is fixed now.

@Deydra71 Deydra71 closed this Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants