-
Notifications
You must be signed in to change notification settings - Fork 197
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
MGMT-9682: fix default disk size requirement #3802
MGMT-9682: fix default disk size requirement #3802
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3802 +/- ##
==========================================
+ Coverage 66.29% 69.31% +3.02%
==========================================
Files 174 174
Lines 24209 26778 +2569
==========================================
+ Hits 16049 18561 +2512
+ Misses 6671 6644 -27
- Partials 1489 1573 +84
|
4c3f05d
to
c77e443
Compare
c77e443
to
8763016
Compare
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gamli75, osherdp 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 |
/unhold |
@osherdp: 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/test-infra repository. I understand the commands that are listed here. |
This change b9ec6db (openshift#3802) was incomplete. It didn't adjust the default hardware requirements set by the AgentServiceConfig controller in the default configmap. I made it so from now on code generation would make sure to keep them in sync. This caused us trouble when openshift/assisted-test-infra#1693 was merged because now the controller expects 120GB for the SNO control-plane node but it only has 100GB., as can be seen in (this)[https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-assisted-service-master-edge-e2e-metal-assisted-kube-api-late-binding-single-node-periodic/1537621678526304256] job failure
This change b9ec6db (openshift#3802) was incomplete. It didn't adjust the default hardware requirements set by the AgentServiceConfig controller in the default configmap. I made it so from now on code generation would make sure to keep them in sync. This caused us trouble when openshift/assisted-test-infra#1693 was merged because now the controller expects 120GB for the SNO control-plane node but it only has 100GB., as can be seen in [this](https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-assisted-service-master-edge-e2e-metal-assisted-kube-api-late-binding-single-node-periodic/1537621678526304256) job failure
This change b9ec6db (#3802) was incomplete. It didn't adjust the default hardware requirements set by the AgentServiceConfig controller in the default configmap. I made it so from now on code generation would make sure to keep them in sync. This caused us trouble when openshift/assisted-test-infra#1693 was merged because now the controller expects 120GB for the SNO control-plane node but it only has 100GB., as can be seen in [this](https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-assisted-service-master-edge-e2e-metal-assisted-kube-api-late-binding-single-node-periodic/1537621678526304256) job failure
This change b9ec6db (openshift#3802) was incomplete. It didn't adjust the default hardware requirements set by the AgentServiceConfig controller in the default configmap. I made it so from now on code generation would make sure to keep them in sync. This caused us trouble when openshift/assisted-test-infra#1693 was merged because now the controller expects 120GB for the SNO control-plane node but it only has 100GB., as can be seen in [this](https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-assisted-service-master-edge-e2e-metal-assisted-kube-api-late-binding-single-node-periodic/1537621678526304256) job failure
Seems like since OCP 4.6, disk requirements were set on 100GB for all nodes: https://docs.openshift.com/container-platform/4.6/installing/installing_bare_metal/installing-bare-metal.html#minimum-resource-requirements_installing-bare-metal Since we don't support installation of OCP <= 4.5 in any environment, it makes sense to change it for all OCP minor releases. This PR is not doing relevant changes for the operator (in the agentserviceconfig object), as it should follow BZ tickets instead of Jira ones. I've tested local environments of minikube and podman, trying to create envs with different disk sizes. I'll also follow up checking integration env preflight-requirements endpoint.
Seems like since OCP 4.6, disk requirements were set on 100GB for all nodes: https://docs.openshift.com/container-platform/4.6/installing/installing_bare_metal/installing-bare-metal.html#minimum-resource-requirements_installing-bare-metal Since we don't support installation of OCP <= 4.5 in any environment, it makes sense to change it for all OCP minor releases. This PR is not doing relevant changes for the operator (in the agentserviceconfig object), as it should follow BZ tickets instead of Jira ones. I've tested local environments of minikube and podman, trying to create envs with different disk sizes. I'll also follow up checking integration env preflight-requirements endpoint.
Seems like since OCP 4.6, disk requirements were set on 100GB for all nodes: https://docs.openshift.com/container-platform/4.6/installing/installing_bare_metal/installing-bare-metal.html#minimum-resource-requirements_installing-bare-metal Since we don't support installation of OCP <= 4.5 in any environment, it makes sense to change it for all OCP minor releases. This PR is not doing relevant changes for the operator (in the agentserviceconfig object), as it should follow BZ tickets instead of Jira ones. I've tested local environments of minikube and podman, trying to create envs with different disk sizes. I'll also follow up checking integration env preflight-requirements endpoint.
This change b9ec6db (openshift#3802) was incomplete. It didn't adjust the default hardware requirements set by the AgentServiceConfig controller in the default configmap. I made it so from now on code generation would make sure to keep them in sync. This caused us trouble when openshift/assisted-test-infra#1693 was merged because now the controller expects 120GB for the SNO control-plane node but it only has 100GB., as can be seen in [this](https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-assisted-service-master-edge-e2e-metal-assisted-kube-api-late-binding-single-node-periodic/1537621678526304256) job failure
This change b9ec6db (openshift#3802) was incomplete. It didn't adjust the default hardware requirements set by the AgentServiceConfig controller in the default configmap. I made it so from now on code generation would make sure to keep them in sync. This caused us trouble when openshift/assisted-test-infra#1693 was merged because now the controller expects 120GB for the SNO control-plane node but it only has 100GB., as can be seen in [this](https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-assisted-service-master-edge-e2e-metal-assisted-kube-api-late-binding-single-node-periodic/1537621678526304256) job failure
Seems like since OCP 4.6, disk requirements were set on 100GB for all nodes:
https://docs.openshift.com/container-platform/4.6/installing/installing_bare_metal/installing-bare-metal.html#minimum-resource-requirements_installing-bare-metal
Since we don't support installation of OCP <= 4.5 in any environment, it makes sense to change it for all OCP minor releases.
This PR is not doing relevant changes for the operator (in the
agentserviceconfig
object), as it should follow BZ tickets instead of Jira ones.I've tested local environments of minikube and podman, trying to create envs with different disk sizes. I'll also follow up checking integration env
preflight-requirements
endpoint.List all the issues related to this PR
What environments does this code impact?
How was this code tested?
Assignees
@gamli75 @eliorerz
Checklist
docs
, README, etc)Reviewers Checklist