Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #29975

/assign openshift-ci-robot

@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-61663 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.19] OCPBUGS-61666: chore(test/extended/prometheus): bump the series limit of total series sent via telemetry from each cluster

Details

In response to this:

This is an automated cherry-pick of #29975

/assign openshift-ci-robot

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 openshift-ci bot changed the title [release-4.19] OCPBUGS-61663: chore(test/extended/prometheus): bump the series limit of total series sent via telemetry from each cluster [release-4.19] OCPBUGS-61666: chore(test/extended/prometheus): bump the series limit of total series sent via telemetry from each cluster Sep 12, 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 Sep 12, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-61666, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-61664 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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.

Details

In response to this:

This is an automated cherry-pick of #29975

/assign openshift-ci-robot

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 Sep 12, 2025
…s sent via telemetry from each cluster

In 4.20 techpreview, more series are to be sent to telemetry, compared
to a 4.19 techpreview:

ALERTS{}	12					      |	ALERTS{}	9
apiserver_list_watch_request_success_total:rate:sum{}	2	apiserver_list_watch_request_success_total:rate:sum{}	2
cco_credentials_mode{}	1					cco_credentials_mode{}	1
cluster:alertmanager_integrations:max{}	1			cluster:alertmanager_integrations:max{}	1
cluster:apiserver_current_inflight_requests:sum:max_over_time	cluster:apiserver_current_inflight_requests:sum:max_over_time
cluster:capacity_cpu_cores:sum{}	2			cluster:capacity_cpu_cores:sum{}	2
cluster:capacity_memory_bytes:sum{}	2			cluster:capacity_memory_bytes:sum{}	2
cluster:console_auth_login_failures_total:sum{}	1	      <
cluster:console_auth_login_requests_total:sum{}	1	      <
cluster:console_auth_login_successes_total:sum{}	3     <
cluster:console_auth_logout_requests_total:sum{}	1     <
cluster:console_customization_perspectives_info:max{}	1     <
cluster:console_plugins_info:max{}	2		      <
cluster:controlplane_topology:info{}	1			cluster:controlplane_topology:info{}	1
cluster:cpu_usage_cores:sum{}	1				cluster:cpu_usage_cores:sum{}	1
cluster:infrastructure_topology:info{}	1			cluster:infrastructure_topology:info{}	1
cluster:ingress_controller_aws_nlb_active:sum{}	1		cluster:ingress_controller_aws_nlb_active:sum{}	1
cluster:kube_persistentvolume_plugin_type_counts:sum{}	1	cluster:kube_persistentvolume_plugin_type_counts:sum{}	1
cluster:kube_persistentvolumeclaim_resource_requests_storage_	cluster:kube_persistentvolumeclaim_resource_requests_storage_
cluster:kubelet_volume_stats_used_bytes:provisioner:sum{}	cluster:kubelet_volume_stats_used_bytes:provisioner:sum{}
cluster:memory_usage_bytes:sum{}	1			cluster:memory_usage_bytes:sum{}	1
cluster:network_attachment_definition_enabled_instance_up:max	cluster:network_attachment_definition_enabled_instance_up:max
cluster:network_attachment_definition_instances:max{}	17	cluster:network_attachment_definition_instances:max{}	17
cluster:node_instance_type_count:sum{}	2			cluster:node_instance_type_count:sum{}	2
cluster:openshift_route_info:tls_termination:sum{}	3	cluster:openshift_route_info:tls_termination:sum{}	3
cluster:ovnkube_controller_admin_network_policies_db_objects:	cluster:ovnkube_controller_admin_network_policies_db_objects:
cluster:ovnkube_controller_admin_network_policies_rules:max{}	cluster:ovnkube_controller_admin_network_policies_rules:max{}
cluster:ovnkube_controller_baseline_admin_network_policies_db	cluster:ovnkube_controller_baseline_admin_network_policies_db
cluster:ovnkube_controller_baseline_admin_network_policies_ru	cluster:ovnkube_controller_baseline_admin_network_policies_ru
cluster:ovnkube_controller_egress_routing_via_host:max{}	cluster:ovnkube_controller_egress_routing_via_host:max{}
cluster:route_metrics_controller_routes_per_shard:avg{}	1	cluster:route_metrics_controller_routes_per_shard:avg{}	1
cluster:route_metrics_controller_routes_per_shard:max{}	1	cluster:route_metrics_controller_routes_per_shard:max{}	1
cluster:route_metrics_controller_routes_per_shard:median{}	cluster:route_metrics_controller_routes_per_shard:median{}
cluster:route_metrics_controller_routes_per_shard:min{}	1	cluster:route_metrics_controller_routes_per_shard:min{}	1
cluster:telemetry_selected_series:count{}	1		cluster:telemetry_selected_series:count{}	1
cluster:usage:containers:sum{}	1				cluster:usage:containers:sum{}	1
cluster:usage:ingress_frontend_bytes_in:rate5m:sum{}	1	cluster:usage:ingress_frontend_bytes_in:rate5m:sum{}	1
cluster:usage:ingress_frontend_bytes_out:rate5m:sum{}	1	cluster:usage:ingress_frontend_bytes_out:rate5m:sum{}	1
cluster:usage:ingress_frontend_connections:sum{}	1	cluster:usage:ingress_frontend_connections:sum{}	1
cluster:usage:kube_node_ready:avg5m{}	1			cluster:usage:kube_node_ready:avg5m{}	1
cluster:usage:kube_schedulable_node_ready_reachable:avg5m{}	cluster:usage:kube_schedulable_node_ready_reachable:avg5m{}
cluster:usage:openshift:ingress_request_error:fraction5m{}	cluster:usage:openshift:ingress_request_error:fraction5m{}
cluster:usage:openshift:ingress_request_total:irate5m{}	1	cluster:usage:openshift:ingress_request_total:irate5m{}	1
cluster:usage:openshift:kube_running_pod_ready:avg{}	1	cluster:usage:openshift:kube_running_pod_ready:avg{}	1
cluster:usage:resources:sum{}	335			      |	cluster:usage:resources:sum{}	331
cluster:usage:workload:capacity_physical_cpu_core_seconds{}	cluster:usage:workload:capacity_physical_cpu_core_seconds{}
cluster:usage:workload:capacity_physical_cpu_cores:max:5m{}	cluster:usage:workload:capacity_physical_cpu_cores:max:5m{}
cluster:usage:workload:capacity_physical_cpu_cores:min:5m{}	cluster:usage:workload:capacity_physical_cpu_cores:min:5m{}
cluster:usage:workload:ingress_request_error:fraction5m{}	cluster:usage:workload:ingress_request_error:fraction5m{}
cluster:usage:workload:ingress_request_total:irate5m{}	1	cluster:usage:workload:ingress_request_total:irate5m{}	1
cluster:usage:workload:kube_running_pod_ready:avg{}	1	cluster:usage:workload:kube_running_pod_ready:avg{}	1
cluster:virt_platform_nodes:sum{}	2			cluster:virt_platform_nodes:sum{}	2
cluster:volume_manager_selinux_volumes_admitted_total{}	1	cluster:volume_manager_selinux_volumes_admitted_total{}	1
cluster_feature_set{}	1					cluster_feature_set{}	1
cluster_infrastructure_provider{}	1			cluster_infrastructure_provider{}	1
cluster_installer{}	1					cluster_installer{}	1
cluster_legacy_scheduler_policy{}	1			cluster_legacy_scheduler_policy{}	1
cluster_master_schedulable{}	1				cluster_master_schedulable{}	1
cluster_operator_conditions{}	165			      |	cluster_operator_conditions{}	164
cluster_operator_up{}	36					cluster_operator_up{}	36
cluster_version_capability{}	17				cluster_version_capability{}	17
cluster_version_payload{}	2				cluster_version_payload{}	2
cluster_version{}	4					cluster_version{}	4
code:apiserver_request_total:rate:sum{}	16		      |	code:apiserver_request_total:rate:sum{}	17
console_url{}	1						console_url{}	1
count:up1{}	78					      |	count:up0{}	1
							      >	count:up1{}	77
csv_succeeded{}	2						csv_succeeded{}	2
imageregistry:imagestreamtags_count:sum{}	4		imageregistry:imagestreamtags_count:sum{}	4
imageregistry:operations_count:sum{}	4			imageregistry:operations_count:sum{}	4
insightsclient_request_send_total{}	1			insightsclient_request_send_total{}	1
instance:etcd_disk_backend_commit_duration_seconds:histogram_	instance:etcd_disk_backend_commit_duration_seconds:histogram_
instance:etcd_disk_wal_fsync_duration_seconds:histogram_quant	instance:etcd_disk_wal_fsync_duration_seconds:histogram_quant
instance:etcd_mvcc_db_total_size_in_bytes:sum{}	3		instance:etcd_mvcc_db_total_size_in_bytes:sum{}	3
instance:etcd_mvcc_db_total_size_in_use_in_bytes:sum{}	3	instance:etcd_mvcc_db_total_size_in_use_in_bytes:sum{}	3
instance:etcd_network_peer_round_trip_time_seconds:histogram_	instance:etcd_network_peer_round_trip_time_seconds:histogram_
instance:etcd_object_counts:sum{}	9			instance:etcd_object_counts:sum{}	9
monitoring:container_memory_working_set_bytes:sum{}	1	monitoring:container_memory_working_set_bytes:sum{}	1
monitoring:haproxy_server_http_responses_total:sum{}	2	monitoring:haproxy_server_http_responses_total:sum{}	2
namespace_job:scrape_samples_post_metric_relabeling:topk3{}	namespace_job:scrape_samples_post_metric_relabeling:topk3{}
namespace_job:scrape_series_added:topk3_sum1h{}	3		namespace_job:scrape_series_added:topk3_sum1h{}	3
node_role_os_version_machine:cpu_capacity_cores:sum{}	2	node_role_os_version_machine:cpu_capacity_cores:sum{}	2
node_role_os_version_machine:cpu_capacity_sockets:sum{}	2	node_role_os_version_machine:cpu_capacity_sockets:sum{}	2
olm_resolution_duration_seconds{}	3			olm_resolution_duration_seconds{}	3
openshift:cpu_usage_cores:sum{}	1				openshift:cpu_usage_cores:sum{}	1
openshift:memory_usage_bytes:sum{}	1			openshift:memory_usage_bytes:sum{}	1
openshift:openshift_network_operator_ipsec_state:info{}	1	openshift:openshift_network_operator_ipsec_state:info{}	1
openshift:prometheus_tsdb_head_samples_appended_total:sum{}	openshift:prometheus_tsdb_head_samples_appended_total:sum{}
openshift:prometheus_tsdb_head_series:sum{}	1		openshift:prometheus_tsdb_head_series:sum{}	1
os_image_url_override:sum{}	1				os_image_url_override:sum{}	1
profile:cluster_monitoring_operator_collection_profile:max{}	profile:cluster_monitoring_operator_collection_profile:max{}
subscription_sync_total{}	1				subscription_sync_total{}	1
workload:cpu_usage_cores:sum{}	1				workload:cpu_usage_cores:sum{}	1
workload:memory_usage_bytes:sum{}	1			workload:memory_usage_bytes:sum{}	1
@machine424
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link

@machine424: This pull request references Jira Issue OCPBUGS-61666, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-61664 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Not a Bug) 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.

Details

In response to this:

/jira refresh

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.

@machine424
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 12, 2025
@openshift-ci-robot
Copy link

@machine424: This pull request references Jira Issue OCPBUGS-61666, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.z) matches configured target version for branch (4.19.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-61664 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-61664 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
  • bug has dependents
Details

In response to this:

/jira refresh

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
Copy link
Contributor

openshift-ci bot commented Sep 12, 2025

@openshift-cherrypick-robot: 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-openstack-ovn 55ee9bd link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node-serial 55ee9bd link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-single-node 55ee9bd link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 55ee9bd link false /test e2e-aws-ovn-kube-apiserver-rollout

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.

@sdodson sdodson added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Sep 14, 2025
@sdodson
Copy link
Member

sdodson commented Sep 14, 2025

/verified by confirming techpreview job passes

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-cherrypick-robot

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:

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

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 14, 2025
@openshift-ci-robot
Copy link

@sdodson: This PR has been marked as verified by confirming techpreview job passes.

Details

In response to this:

/verified by confirming techpreview job passes

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.

@sdodson sdodson merged commit 6835ae8 into openshift:release-4.19 Sep 14, 2025
28 of 33 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-61666
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-61666 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This is an automated cherry-pick of #29975

/assign openshift-ci-robot

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.

@sdodson
Copy link
Member

sdodson commented Sep 14, 2025

/cherry-pick release-4.18

@openshift-cherrypick-robot
Copy link
Author

@sdodson: new pull request created: #30253

Details

In response to this:

/cherry-pick release-4.18

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.19.0-202509140337.p0.g6835ae8.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.19.0-0.nightly-2025-09-14-165440

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.