-
Notifications
You must be signed in to change notification settings - Fork 253
HIVE-3014: Revendor installer to v1.4.21-pre #2796
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
Conversation
|
@dlom: This pull request references HIVE-3014 which is a valid jira issue. DetailsIn 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. |
|
@dlom: This pull request references HIVE-3014 which is a valid jira issue. DetailsIn 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. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2796 +/- ##
=======================================
Coverage 50.40% 50.40%
=======================================
Files 279 279
Lines 34194 34194
=======================================
+ Hits 17235 17236 +1
- Misses 15595 15597 +2
+ Partials 1364 1361 -3
🚀 New features to boost your workflow:
|
|
I'm going to hope that these validation budget checks were enabled by accident, temporarily. /retest-required |
|
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? |
|
Failing on the same I see we're patching CRDs already to remove some things, should we do the same here? @2uasimojo |
|
You need a max length on hive/apis/hive/v1/clusterdeployment_types.go Line 138 in 140ebad
At the moment it's estimating the worst case as 3MiB over whatever the smallest object there is ( What's a sensible number of maximum ingresses you could retrofit to solve this without causing real world issues? |
54b7e89 to
6a927e3
Compare
|
/test e2e-openstack |
1 similar comment
|
/test e2e-openstack |
|
/test e2e-azure |
|
/retest |
1 similar comment
|
/retest |
|
Caution There are some errors in your PipelineRun template.
|
|
/test e2e-openstack |
|
/retest-required |
1 similar comment
|
/retest-required |
|
/test e2e-openstack |
|
/unhold |
2uasimojo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to understand what our previous support stance was on multi-zone pools, because it looks like we might have a gap now. If there's no regression, I'm happy to land this now and worry about that in a fup.
| }, | ||
| } | ||
|
|
||
| if pool.Spec.Platform.Azure.ComputeSubnet != "" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like we may be inheriting some tech debt here to support multiple subnets? Do we have a card for this already?
| workerUserDataName, | ||
| capabilities, | ||
| useImageGallery, | ||
| []string{}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure I'm following the upstream code correctly, but it looks like, whereas the contents of this list are not used, the length of it needs to match that of pool.Spec.Azure.Zones for a multi-zone pool? (The list ends up here.) Can we run this by the installer team?
| if [[ $0 == */e2e-pool-test.sh ]]; then | ||
| # TODO: set this back to 148 when we figure out how to make the *test script* | ||
| # timeout something other than 2h. | ||
| timeout_minutes=118 | ||
| timeout_minutes=148 | ||
| else | ||
| timeout_minutes=118 | ||
| timeout_minutes=148 | ||
| fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like we can collapse this now?
Perhaps the comment should indicate that this timeout needs to be shorter than the test timeout configured in the release repo? I think the purpose is to give our script a chance to clean up, since the generic overarching test timeout doesn't give us enough of a chance to do so?
|
@dlom: This pull request references HIVE-3014 which is a valid jira issue. DetailsIn 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. |
1 similar comment
|
@dlom: This pull request references HIVE-3014 which is a valid jira issue. DetailsIn 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. |
|
/test hive-mce-29-on-pull-request hive-mce-210-on-pull-request |
|
/override "Red Hat Konflux" 🙄 |
|
@2uasimojo: Overrode contexts on behalf of 2uasimojo: Red Hat Konflux DetailsIn 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 kubernetes-sigs/prow repository. |
2uasimojo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 2uasimojo, dlom The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test hive-mce-210-on-pull-request |
|
/hold for moar testing |
|
/test e2e-openstack |
|
/override "Red Hat Konflux" |
|
@dlom: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. DetailsIn 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 kubernetes-sigs/prow repository. |
|
/test e2e-azure |
|
/hold cancel |
|
/test security |
|
/override ci/prow/security Systemic. Addressing via HIVE-3053. |
|
@2uasimojo: Overrode contexts on behalf of 2uasimojo: ci/prow/security DetailsIn 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 kubernetes-sigs/prow repository. |
|
@dlom: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
78f50cd
into
openshift:master
xref: HIVE-3014
xref: HIVE-3051
/assign @2uasimojo
Depends on openshift/machine-api-operator#1438