Skip to content

WIP: OCPBUGS-42087: Add metric for watch cache ready #2234

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

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

bertinatto
Copy link
Member

No description provided.

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Mar 5, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 5, 2025
Copy link

openshift-ci bot commented Mar 5, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Mar 5, 2025
Copy link

openshift-ci bot commented Mar 5, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto

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

@bertinatto
Copy link
Member Author

/test unit
/test verify

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 5, 2025
@bertinatto
Copy link
Member Author

/payload-job periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance

Copy link

openshift-ci bot commented Mar 5, 2025

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/02f89670-f9fe-11ef-9ec0-fbf3c911d7f8-0

@bertinatto bertinatto force-pushed the add-metric-watch-cache-ready branch from c554029 to c918fbd Compare March 5, 2025 21:26
@openshift-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@bertinatto
Copy link
Member Author

/test unit
/test verify

@bertinatto
Copy link
Member Author

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance 10

Copy link

openshift-ci bot commented Mar 5, 2025

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9632c640-fa12-11ef-8131-8a670409c226-0

@bertinatto
Copy link
Member Author

/test all

@bertinatto
Copy link
Member Author

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance 10

Copy link

openshift-ci bot commented Mar 6, 2025

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/34b8a8e0-fa66-11ef-9ce9-a0295b05f037-0

@bertinatto bertinatto changed the title WIP: Add metric for watch cache ready WIP: OCPBUGS-42087: Add metric for watch cache ready Mar 6, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 6, 2025
@openshift-ci-robot
Copy link

@bertinatto: This pull request references Jira Issue OCPBUGS-42087, which is invalid:

  • expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.z" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

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-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 6, 2025
@@ -46,6 +48,7 @@ type ready struct {
}

func newReady() *ready {
metrics.RecordWatchCacheReady(false)

Choose a reason for hiding this comment

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

I think I would add this metric somewhere here

metrics.WatchCacheInitializations.WithLabelValues(c.groupResource.String()).Inc()

and for the off scenario somewhere here

We could slightly change WatchCacheInitializations to be a gauge or depreciate it and create a new one. I think the latter is better.

@bertinatto bertinatto force-pushed the add-metric-watch-cache-ready branch from c918fbd to 8d16ff5 Compare March 6, 2025 18:15
@openshift-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@bertinatto bertinatto force-pushed the add-metric-watch-cache-ready branch from 8d16ff5 to ccee3e5 Compare March 6, 2025 18:31
@openshift-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@bertinatto bertinatto force-pushed the add-metric-watch-cache-ready branch from ccee3e5 to 4cb7ce0 Compare March 6, 2025 18:34
@openshift-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@bertinatto
Copy link
Member Author

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance 10

Copy link

openshift-ci bot commented Mar 6, 2025

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e6ceb6f0-fabb-11ef-97c5-bbe9b53996a1-0

@bertinatto
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance openshift/cluster-kube-apiserver-operator#1822

Copy link

openshift-ci bot commented Mar 7, 2025

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/43c75840-fb83-11ef-91e3-6f93d0dd99c7-0

@bertinatto
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance openshift/cluster-kube-apiserver-operator#1822

Copy link

openshift-ci bot commented Mar 9, 2025

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/60593840-fcfd-11ef-9307-680c8b7be18c-0

@bertinatto
Copy link
Member Author

/test all

Copy link

openshift-ci bot commented Mar 9, 2025

@bertinatto: The following tests 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/okd-scos-e2e-aws-ovn 4cb7ce0 link false /test okd-scos-e2e-aws-ovn
ci/prow/verify-commits 4cb7ce0 link true /test verify-commits

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.

@bertinatto
Copy link
Member Author

/test ?

Copy link

openshift-ci bot commented Mar 10, 2025

@bertinatto: The following commands are available to trigger required jobs:

/test artifacts
/test configmap-scale
/test e2e-aws-crun-wasm
/test e2e-aws-jenkins
/test e2e-aws-ovn-cgroupsv2
/test e2e-aws-ovn-crun
/test e2e-aws-ovn-downgrade
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-runc
/test e2e-aws-ovn-serial
/test e2e-aws-ovn-upgrade
/test e2e-azure-ovn-upgrade
/test e2e-gcp
/test e2e-gcp-ovn-upgrade
/test images
/test integration
/test k8s-e2e-conformance-aws
/test k8s-e2e-gcp-ovn
/test k8s-e2e-gcp-serial
/test perfscale-control-plane-6nodes
/test unit
/test verify
/test verify-commits

The following commands are available to trigger optional jobs:

/test e2e-agnostic-ovn-cmd
/test e2e-aws
/test e2e-aws-csi
/test e2e-aws-disruptive
/test e2e-aws-ovn
/test e2e-aws-single-node
/test e2e-azure
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-ipv6
/test e2e-openstack
/test e2e-openstack-csi-cinder
/test e2e-openstack-csi-manila
/test e2e-vsphere
/test k8s-e2e-aws
/test k8s-e2e-aws-ovn-serial
/test k8s-e2e-gcp-five-control-plane-replicas
/test okd-scos-e2e-aws-ovn
/test okd-scos-images

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-kubernetes-master-e2e-agnostic-ovn-cmd
pull-ci-openshift-kubernetes-master-e2e-aws-crun-wasm
pull-ci-openshift-kubernetes-master-e2e-aws-csi
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-cgroupsv2
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-crun
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-fips
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-hypershift
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-runc
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-serial
pull-ci-openshift-kubernetes-master-e2e-gcp
pull-ci-openshift-kubernetes-master-e2e-gcp-ovn-upgrade
pull-ci-openshift-kubernetes-master-images
pull-ci-openshift-kubernetes-master-integration
pull-ci-openshift-kubernetes-master-k8s-e2e-aws-ovn-serial
pull-ci-openshift-kubernetes-master-k8s-e2e-conformance-aws
pull-ci-openshift-kubernetes-master-k8s-e2e-gcp-ovn
pull-ci-openshift-kubernetes-master-k8s-e2e-gcp-serial
pull-ci-openshift-kubernetes-master-okd-scos-e2e-aws-ovn
pull-ci-openshift-kubernetes-master-unit
pull-ci-openshift-kubernetes-master-verify
pull-ci-openshift-kubernetes-master-verify-commits

In response to this:

/test ?

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.

@bertinatto
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance openshift/cluster-kube-apiserver-operator#1822

Copy link

openshift-ci bot commented Mar 10, 2025

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/26429e30-fdb6-11ef-92aa-4b9be638d605-0

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. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants