Skip to content

Conversation

@dlom
Copy link
Contributor

@dlom dlom commented Nov 24, 2025

@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 24, 2025

@dlom: This pull request references HIVE-3014 which is a valid jira issue.

In response to this:

xref: HIVE-3014
/assign @2uasimojo

Depends on openshift/machine-api-operator#1438

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/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 24, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 24, 2025

@dlom: This pull request references HIVE-3014 which is a valid jira issue.

In response to this:

xref: HIVE-3014
/assign @2uasimojo

Depends on openshift/machine-api-operator#1438

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 requested review from 2uasimojo and suhanime November 24, 2025 21:40
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dlom

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 Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 24, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 24, 2025
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 24, 2025
@codecov
Copy link

codecov bot commented Nov 24, 2025

Codecov Report

❌ Patch coverage is 93.75000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 50.39%. Comparing base (6104f29) to head (1bc94c2).
⚠️ Report is 12 commits behind head on master.

Files with missing lines Patch % Lines
...ller/clusterrelocate/clusterrelocate_controller.go 0.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2796      +/-   ##
==========================================
+ Coverage   50.35%   50.39%   +0.03%     
==========================================
  Files         279      279              
  Lines       34180    34195      +15     
==========================================
+ Hits        17210    17231      +21     
+ Misses      15617    15604      -13     
- Partials     1353     1360       +7     
Files with missing lines Coverage Δ
pkg/controller/machinepool/awsactuator.go 77.86% <100.00%> (ø)
pkg/controller/machinepool/azureactuator.go 69.53% <100.00%> (-0.87%) ⬇️
pkg/controller/machinepool/nutanixactuator.go 84.28% <100.00%> (+0.22%) ⬆️
...ller/clusterrelocate/clusterrelocate_controller.go 40.96% <0.00%> (ø)

... and 4 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@2uasimojo
Copy link
Member

I'm going to hope that these validation budget checks were enabled by accident, temporarily.

/retest-required

@2uasimojo
Copy link
Member

Ugh. @JoelSpeed what are we supposed to do about this?

Also, why is it complaining about an int64 field? Or does that just happen to be the point at which the whole budget got pushed over the edge?

@dlom
Copy link
Contributor Author

dlom commented Nov 29, 2025

Failing on the same The CustomResourceDefinition "clusterdeployments.hive.openshift.io" is invalid:

I see we're patching CRDs already to remove some things, should we do the same here? @2uasimojo

@JoelSpeed
Copy link
Contributor

You need a max length on

Ingress []ClusterIngress `json:"ingress,omitempty"`

At the moment it's estimating the worst case as 3MiB over whatever the smallest object there is ({"name":"","domain":""} 23 chars) so approx 137k list entries. So every validation that exists in that list is 137k times larger than in o/api.

What's a sensible number of maximum ingresses you could retrofit to solve this without causing real world issues?

@2uasimojo
Copy link
Member

/test e2e-openstack

1 similar comment
@dlom
Copy link
Contributor Author

dlom commented Dec 1, 2025

/test e2e-openstack

@dlom
Copy link
Contributor Author

dlom commented Dec 2, 2025

/test e2e-azure

@dlom
Copy link
Contributor Author

dlom commented Dec 2, 2025

/retest

1 similar comment
@2uasimojo
Copy link
Member

/retest

@red-hat-konflux
Copy link
Contributor

Caution

There are some errors in your PipelineRun template.

PipelineRun Error
hive-mce-210-on-pull-request CEL expression evaluation error: expression "event == \"pull_request\"\n&& !body.pull_request.draft\n&& target_branch == \"master\"\n&& !files.all.all(x, x.matches('^docs/|\\\\.md$|^(?:.*/)?(?:\\\\.gitignore|OWNERS|PROJECT|LICENSE)$'))\n" failed to evaluate: no such key: pull_request
hive-mce-211-on-pull-request CEL expression evaluation error: expression "event == \"pull_request\"\n&& !body.pull_request.draft\n&& target_branch == \"master\"\n&& !files.all.all(x, x.matches('^docs/|\\\\.md$|^(?:.*/)?(?:\\\\.gitignore|OWNERS|PROJECT|LICENSE)$'))\n" failed to evaluate: no such key: pull_request
hive-mce-26-on-pull-request CEL expression evaluation error: expression "event == \"pull_request\"\n&& !body.pull_request.draft\n&& target_branch == \"master\"\n&& !files.all.all(x, x.matches('^docs/|\\\\.md$|^(?:.*/)?(?:\\\\.gitignore|OWNERS|PROJECT|LICENSE)$'))\n" failed to evaluate: no such key: pull_request
hive-mce-27-on-pull-request CEL expression evaluation error: expression "event == \"pull_request\"\n&& !body.pull_request.draft\n&& target_branch == \"master\"\n&& !files.all.all(x, x.matches('^docs/|\\\\.md$|^(?:.*/)?(?:\\\\.gitignore|OWNERS|PROJECT|LICENSE)$'))\n" failed to evaluate: no such key: pull_request
hive-mce-28-on-pull-request CEL expression evaluation error: expression "event == \"pull_request\"\n&& !body.pull_request.draft\n&& target_branch == \"master\"\n&& !files.all.all(x, x.matches('^docs/|\\\\.md$|^(?:.*/)?(?:\\\\.gitignore|OWNERS|PROJECT|LICENSE)$'))\n" failed to evaluate: no such key: pull_request
hive-mce-29-on-pull-request CEL expression evaluation error: expression "event == \"pull_request\"\n&& !body.pull_request.draft\n&& target_branch == \"master\"\n&& !files.all.all(x, x.matches('^docs/|\\\\.md$|^(?:.*/)?(?:\\\\.gitignore|OWNERS|PROJECT|LICENSE)$'))\n" failed to evaluate: no such key: pull_request
hive-on-pull-request CEL expression evaluation error: expression "event == \"pull_request\"\n&& !body.pull_request.draft\n&& target_branch == \"master\"\n&& !files.all.all(x, x.matches('^docs/|\\\\.md$|^(?:.*/)?(?:\\\\.gitignore|OWNERS|PROJECT|LICENSE)$'))\n" failed to evaluate: no such key: pull_request

@dlom
Copy link
Contributor Author

dlom commented Dec 2, 2025

/test e2e-openstack

@dlom
Copy link
Contributor Author

dlom commented Dec 3, 2025

/retest-required

1 similar comment
@2uasimojo
Copy link
Member

/retest-required

@dlom
Copy link
Contributor Author

dlom commented Dec 3, 2025

/test e2e-openstack

@dlom
Copy link
Contributor Author

dlom commented Dec 3, 2025

/test e2e-azure

4 similar comments
@dlom
Copy link
Contributor Author

dlom commented Dec 3, 2025

/test e2e-azure

@dlom
Copy link
Contributor Author

dlom commented Dec 4, 2025

/test e2e-azure

@dlom
Copy link
Contributor Author

dlom commented Dec 4, 2025

/test e2e-azure

@dlom
Copy link
Contributor Author

dlom commented Dec 4, 2025

/test e2e-azure

@dlom dlom force-pushed the HIVE-3014 branch 3 times, most recently from 0fd568b to 1bc94c2 Compare December 8, 2025 23:15
@dlom dlom marked this pull request as draft December 9, 2025 21:49
@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 Dec 9, 2025
@dlom
Copy link
Contributor Author

dlom commented Dec 9, 2025

/test e2e-azure

@dlom
Copy link
Contributor Author

dlom commented Dec 11, 2025

/test e2e-azure

@dlom
Copy link
Contributor Author

dlom commented Dec 11, 2025

/test e2e-azure

1 similar comment
@dlom
Copy link
Contributor Author

dlom commented Dec 11, 2025

/test e2e-azure

@dlom
Copy link
Contributor Author

dlom commented Dec 11, 2025

/test e2e-azure

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 11, 2025

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

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. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants