NO-JIRA: bug(metrics): fix typo in hypershift_cluster_waiting_initial_availability_duration_seconds metric

[joshbranham]

The metric hypershift_cluster_waiting_initial_availbility_duration_seconds had a typo in the word availabilty. This fixes that. Consumers will need to adjust their alerting as such.

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes

Special notes for your reviewer:

Checklist:

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

Walkthrough

Fixes a typographical error in the metric name constant WaitingInitialAvailabilityDurationMetricName, changing the metric identifier string from "hypershift_cluster_waiting_initial_avaibility_duration_seconds" to "hypershift_cluster_waiting_initial_availability_duration_seconds".

Changes

Cohort / File(s)	Summary
Metrics Constant Typo Fix hypershift-operator/controllers/hostedcluster/metrics/metrics.go	Corrects the metric name string: "hypershift_cluster_waiting_initial_avaibility_duration_seconds" → "hypershift_cluster_waiting_initial_availability_duration_seconds".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[csrwng]

The change looks good to me. However @joshbranham you would likely know better than the engineering team if this will impact dashboards or any other aggregation done on the service side.

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: csrwng, joshbranham

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [csrwng]

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

[joshbranham]

/verified
/lgtm

[openshift-ci]

@joshbranham: you cannot LGTM your own PR.

Details

In response to this:

/verified
/lgtm

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]

@joshbranham: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified
/lgtm

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.

[joshbranham]

/verified by @joshbranham

[openshift-ci-robot]

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

Details

In response to this:

/verified by @joshbranham

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]

@joshbranham: This pull request explicitly references no jira issue.

Details

In response to this:

The metric hypershift_cluster_waiting_initial_availbility_duration_seconds had a typo in the word availabilty. This fixes that. Consumers will need to adjust their alerting as such.

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes

Special notes for your reviewer:

Checklist:

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

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.

[enxebre]

/lgtm

[openshift-ci-robot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aks-4-21
/test e2e-aws-4-21
/test e2e-aks
/test e2e-aws
/test e2e-aws-upgrade-hypershift-operator
/test e2e-kubevirt-aws-ovn-reduced
/test e2e-v2-aws

[joshbranham]

/test e2e-aws-4-21
/test e2e-aks
/test e2e-aks-4-21

[openshift-ci]

@joshbranham: 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/e2e-aks	6b9eb30	link	true	/test e2e-aks
ci/prow/e2e-aws-4-21	6b9eb30	link	true	/test e2e-aws-4-21

Full PR test history. Your PR dashboard.

Details

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.