Skip to content
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-16332: fix validation for LVM multinode #5898

Merged

Conversation

eifrach
Copy link
Contributor

@eifrach eifrach commented Jan 21, 2024

Fixing requirements for LVM multinode deployment

  1. full cluster should require disk on worker nodes only
  2. full cluster shouldn't allow auto assign
  3. fixing requirment calculation
  4. adding tests for requirements resources

List all the issues related to this PR

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • None

How was this code tested?

  • assisted-test-infra environment
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested)
  • No tests needed

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 21, 2024

@eifrach: This pull request references MGMT-16332 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.16.0" version, but no target version was set.

In response to this:

List all the issues related to this PR

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • None

How was this code tested?

  • assisted-test-infra environment
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested)
  • No tests needed

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

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 Jan 21, 2024
Copy link

openshift-ci bot commented Jan 21, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 21, 2024
@eifrach
Copy link
Contributor Author

eifrach commented Jan 21, 2024

/test images
/test unit-tests

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 21, 2024
@eifrach
Copy link
Contributor Author

eifrach commented Jan 21, 2024

/test ?

Copy link

openshift-ci bot commented Jan 21, 2024

@eifrach: The following commands are available to trigger required jobs:

  • /test e2e-agent-compact-ipv4
  • /test edge-assisted-operator-catalog-publish-verify
  • /test edge-ci-index
  • /test edge-e2e-ai-operator-ztp
  • /test edge-e2e-ai-operator-ztp-sno-day2-workers
  • /test edge-e2e-ai-operator-ztp-sno-day2-workers-late-binding
  • /test edge-e2e-metal-assisted
  • /test edge-e2e-metal-assisted-4-11
  • /test edge-e2e-metal-assisted-4-12
  • /test edge-e2e-metal-assisted-cnv
  • /test edge-e2e-metal-assisted-lvm
  • /test edge-e2e-metal-assisted-odf
  • /test edge-images
  • /test edge-lint
  • /test edge-subsystem-aws
  • /test edge-subsystem-kubeapi-aws
  • /test edge-unit-test
  • /test edge-verify-generated-code
  • /test images
  • /test mce-images

The following commands are available to trigger optional jobs:

  • /test e2e-agent-ha-dualstack
  • /test e2e-agent-sno-ipv6
  • /test edge-e2e-ai-operator-disconnected-capi
  • /test edge-e2e-ai-operator-ztp-3masters
  • /test edge-e2e-ai-operator-ztp-capi
  • /test edge-e2e-ai-operator-ztp-compact-day2-masters
  • /test edge-e2e-ai-operator-ztp-compact-day2-workers
  • /test edge-e2e-ai-operator-ztp-disconnected
  • /test edge-e2e-ai-operator-ztp-hypershift-zero-nodes
  • /test edge-e2e-ai-operator-ztp-multiarch-3masters-ocp
  • /test edge-e2e-ai-operator-ztp-multiarch-sno-ocp
  • /test edge-e2e-ai-operator-ztp-node-labels
  • /test edge-e2e-ai-operator-ztp-sno-day2-masters
  • /test edge-e2e-ai-operator-ztp-sno-day2-workers-ignitionoverride
  • /test edge-e2e-metal-assisted-4-13
  • /test edge-e2e-metal-assisted-4-14
  • /test edge-e2e-metal-assisted-4-15
  • /test edge-e2e-metal-assisted-bond
  • /test edge-e2e-metal-assisted-bond-4-14
  • /test edge-e2e-metal-assisted-day2
  • /test edge-e2e-metal-assisted-day2-arm-workers
  • /test edge-e2e-metal-assisted-day2-single-node
  • /test edge-e2e-metal-assisted-external
  • /test edge-e2e-metal-assisted-external-4-14
  • /test edge-e2e-metal-assisted-ipv4v6
  • /test edge-e2e-metal-assisted-ipv6
  • /test edge-e2e-metal-assisted-kube-api-late-binding-single-node
  • /test edge-e2e-metal-assisted-kube-api-late-unbinding-ipv4-single-node
  • /test edge-e2e-metal-assisted-kube-api-net-suite
  • /test edge-e2e-metal-assisted-mce-4-11
  • /test edge-e2e-metal-assisted-mce-4-12
  • /test edge-e2e-metal-assisted-mce-4-13
  • /test edge-e2e-metal-assisted-mce-4-14
  • /test edge-e2e-metal-assisted-mce-4-15
  • /test edge-e2e-metal-assisted-mce-sno
  • /test edge-e2e-metal-assisted-metallb
  • /test edge-e2e-metal-assisted-none
  • /test edge-e2e-metal-assisted-onprem
  • /test edge-e2e-metal-assisted-single-node
  • /test edge-e2e-metal-assisted-static-ip-suite
  • /test edge-e2e-metal-assisted-static-ip-suite-4-14
  • /test edge-e2e-metal-assisted-tang
  • /test edge-e2e-metal-assisted-tpmv2
  • /test edge-e2e-metal-assisted-upgrade-agent
  • /test edge-e2e-nutanix-assisted
  • /test edge-e2e-nutanix-assisted-2workers
  • /test edge-e2e-nutanix-assisted-4-14
  • /test edge-e2e-oci-assisted
  • /test edge-e2e-oci-assisted-4-14
  • /test edge-e2e-oci-assisted-iscsi
  • /test edge-e2e-vsphere-assisted
  • /test edge-e2e-vsphere-assisted-4-12
  • /test edge-e2e-vsphere-assisted-4-13
  • /test edge-e2e-vsphere-assisted-4-14
  • /test edge-e2e-vsphere-assisted-umn
  • /test edge-push-pr-image
  • /test push-pr-image

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-assisted-service-master-e2e-agent-compact-ipv4
  • pull-ci-openshift-assisted-service-master-edge-ci-index
  • pull-ci-openshift-assisted-service-master-edge-e2e-ai-operator-ztp
  • pull-ci-openshift-assisted-service-master-edge-e2e-metal-assisted
  • pull-ci-openshift-assisted-service-master-edge-e2e-metal-assisted-cnv
  • pull-ci-openshift-assisted-service-master-edge-e2e-metal-assisted-lvm
  • pull-ci-openshift-assisted-service-master-edge-e2e-metal-assisted-odf
  • pull-ci-openshift-assisted-service-master-edge-images
  • pull-ci-openshift-assisted-service-master-edge-lint
  • pull-ci-openshift-assisted-service-master-edge-subsystem-aws
  • pull-ci-openshift-assisted-service-master-edge-subsystem-kubeapi-aws
  • pull-ci-openshift-assisted-service-master-edge-unit-test
  • pull-ci-openshift-assisted-service-master-edge-verify-generated-code
  • pull-ci-openshift-assisted-service-master-images
  • pull-ci-openshift-assisted-service-master-mce-images

In response to this:

/test ?

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.

@eifrach
Copy link
Contributor Author

eifrach commented Jan 21, 2024

/test edge-lint
/test edge-unit-test
/test edge-images
/test images

Copy link

codecov bot commented Jan 21, 2024

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (9f19758) 68.32% compared to head (e436abe) 68.27%.
Report is 6 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #5898      +/-   ##
==========================================
- Coverage   68.32%   68.27%   -0.05%     
==========================================
  Files         236      236              
  Lines       34943    35047     +104     
==========================================
+ Hits        23874    23929      +55     
- Misses       8997     9044      +47     
- Partials     2072     2074       +2     
Files Coverage Δ
internal/bminventory/inventory.go 71.31% <100.00%> (-0.22%) ⬇️
internal/operators/cnv/cnv_operator.go 79.65% <100.00%> (ø)
internal/operators/lvm/config.go 100.00% <ø> (ø)
internal/operators/lvm/manifest.go 72.88% <100.00%> (ø)
internal/operators/lvm/lvm_operator.go 80.20% <97.05%> (+8.63%) ⬆️
internal/operators/manager.go 77.64% <0.00%> (ø)
internal/host/hostutil/test_utils.go 11.39% <0.00%> (ø)

... and 13 files with indirect coverage changes

@eifrach
Copy link
Contributor Author

eifrach commented Jan 24, 2024

/test edge-lint
/test edge-unit-test
/test edge-images
/test images
/test edge-e2e-metal-assisted-lvm

@eifrach
Copy link
Contributor Author

eifrach commented Jan 25, 2024

/test edge-e2e-metal-assisted-lvm

@eifrach eifrach force-pushed the lvm_clustertype_deployment branch 3 times, most recently from 2a6b359 to 9dedc6f Compare January 28, 2024 11:56
@openshift-ci openshift-ci bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 28, 2024
@eifrach
Copy link
Contributor Author

eifrach commented Jan 28, 2024

/test edge-lint
/test edge-unit-test
/test edge-images
/test images
/test edge-e2e-metal-assisted-lvm

@eifrach
Copy link
Contributor Author

eifrach commented Jan 28, 2024

/test edge-lint
/test edge-unit-test
/test edge-images
/test images

@eifrach eifrach changed the title MGMT-16332: moving deployment type to common MGMT-16332: align LVM multi node requirements Jan 28, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 28, 2024

@eifrach: This pull request references MGMT-16332 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.16.0" version, but no target version was set.

In response to this:

Fixing requirments for LVM multinode deployment

  1. full cluster should require disk on worker nodes only
  2. full cluster shouldn't allow auto assign
  3. fixing requirment calculation
  4. adding tests for requirments resources

List all the issues related to this PR

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • None

How was this code tested?

  • assisted-test-infra environment
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested)
  • No tests needed

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

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

openshift-ci-robot commented Jan 28, 2024

@eifrach: This pull request references MGMT-16332 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.16.0" version, but no target version was set.

In response to this:

Fixing requirements for LVM multinode deployment

  1. full cluster should require disk on worker nodes only
  2. full cluster shouldn't allow auto assign
  3. fixing requirment calculation
  4. adding tests for requirements resources

List all the issues related to this PR

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • None

How was this code tested?

  • assisted-test-infra environment
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested)
  • No tests needed

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

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.

internal/operators/lvm/lvm_operator.go Outdated Show resolved Hide resolved
internal/operators/lvm/lvm_operator.go Outdated Show resolved Hide resolved
internal/operators/lvm/lvm_operator.go Outdated Show resolved Hide resolved
internal/operators/odf/odf_operator.go Outdated Show resolved Hide resolved
internal/operators/lvm/common.go Outdated Show resolved Hide resolved
internal/operators/lvm/common.go Outdated Show resolved Hide resolved
internal/operators/lvm/lvm_operator.go Outdated Show resolved Hide resolved
internal/operators/lvm/lvm_operator.go Outdated Show resolved Hide resolved
internal/common/common.go Outdated Show resolved Hide resolved
@eifrach eifrach force-pushed the lvm_clustertype_deployment branch 2 times, most recently from 24f4cbb to 1b39606 Compare January 29, 2024 14:04
@eifrach
Copy link
Contributor Author

eifrach commented Jan 29, 2024

/test edge-lint
/test edge-unit-test
/test edge-images
/test images

@eifrach
Copy link
Contributor Author

eifrach commented Feb 11, 2024

/test edge-subsystem-aws

@eifrach
Copy link
Contributor Author

eifrach commented Feb 11, 2024

/test edge-subsystem-aws

Copy link
Contributor

@osherdp osherdp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mainly syntactic comments

internal/operators/lvm/config.go Outdated Show resolved Hide resolved
internal/operators/lvm/lvm_operator.go Outdated Show resolved Hide resolved
internal/operators/lvm/lvm_operator.go Outdated Show resolved Hide resolved
internal/operators/lvm/lvm_operator.go Outdated Show resolved Hide resolved
internal/operators/lvm/lvm_operator.go Outdated Show resolved Hide resolved
internal/operators/lvm/lvm_operator.go Outdated Show resolved Hide resolved
@eifrach eifrach marked this pull request as ready for review February 12, 2024 12:09
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 12, 2024
@eifrach
Copy link
Contributor Author

eifrach commented Feb 12, 2024

/test images

@gamli75
Copy link
Contributor

gamli75 commented Feb 13, 2024

/retest-required

@avishayt
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 13, 2024
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 13, 2024
@eifrach
Copy link
Contributor Author

eifrach commented Feb 13, 2024

/test edge-e2e-metal-assisted-odf

1 similar comment
@eifrach
Copy link
Contributor Author

eifrach commented Feb 13, 2024

/test edge-e2e-metal-assisted-odf

@eifrach eifrach requested a review from osherdp February 13, 2024 15:11
@eifrach
Copy link
Contributor Author

eifrach commented Feb 13, 2024

/cc @osherdp
/cc @gamli75

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 13, 2024
Copy link

openshift-ci bot commented Feb 13, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eifrach, gamli75

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

@gamli75
Copy link
Contributor

gamli75 commented Feb 13, 2024

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 13, 2024
Copy link

openshift-ci bot commented Feb 13, 2024

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

@openshift-merge-bot openshift-merge-bot bot merged commit 5bf3f33 into openshift:master Feb 13, 2024
17 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-agent-installer-api-server-container-v4.16.0-202402140210.p0.g5bf3f33.assembly.stream.el8 for distgit ose-agent-installer-api-server.
All builds following this will include this PR.

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. 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. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants