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-16966: Problem creating extra partition on main disk in 4.15+ #787

Merged
merged 1 commit into from Feb 21, 2024

Conversation

ori-amizur
Copy link
Contributor

When skipping MCO reboot, the last partition is extended to fill the remaining free space in the disk. This may be undesirable since there are scenarios that a user adds a partition in the installation disk.

This change doubles the space occupied by the last disk partition instead of occupying all the remining space. The assumption is that doubling the space should be enough for image overwrite.

/cc @javipolo

When skipping MCO reboot, the last partition is extended to fill the
remaining free space in the disk. This may be undesirable since there
are scenarios that a user adds a partition in the installation disk.

This change doubles the space occupied by the last disk partition
instead of occupying all the remining space.  The assumption is that
doubling the space should be enough for image overwrite.
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 20, 2024

@ori-amizur: This pull request references MGMT-16966 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

When skipping MCO reboot, the last partition is extended to fill the remaining free space in the disk. This may be undesirable since there are scenarios that a user adds a partition in the installation disk.

This change doubles the space occupied by the last disk partition instead of occupying all the remining space. The assumption is that doubling the space should be enough for image overwrite.

/cc @javipolo

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 Feb 20, 2024
@openshift-ci openshift-ci bot requested a review from javipolo February 20, 2024 09:06
@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 20, 2024
@romfreiman
Copy link

what's the behavior in coreos-installer?

Copy link

codecov bot commented Feb 20, 2024

Codecov Report

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

Comparison is base (6b6c6ac) 56.27% compared to head (1f7a375) 56.43%.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #787      +/-   ##
==========================================
+ Coverage   56.27%   56.43%   +0.15%     
==========================================
  Files          15       15              
  Lines        3316     3358      +42     
==========================================
+ Hits         1866     1895      +29     
- Misses       1282     1289       +7     
- Partials      168      174       +6     
Files Coverage Δ
src/ops/ops.go 43.61% <73.46%> (+1.59%) ⬆️

@ori-amizur
Copy link
Contributor Author

what's the behavior in coreos-installer?

No change for coreos-installer regarding this change

@javipolo
Copy link
Member

/lgtm

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

openshift-ci bot commented Feb 21, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: javipolo, ori-amizur

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:
  • OWNERS [javipolo,ori-amizur]

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

@javipolo
Copy link
Member

/retest

@openshift-merge-bot openshift-merge-bot bot merged commit 7a2ea37 into openshift:master Feb 21, 2024
9 of 10 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-agent-installer-csr-approver-container-v4.16.0-202402211239.p0.g7a2ea37.assembly.stream.el8 for distgit ose-agent-installer-csr-approver.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-agent-installer-orchestrator-container-v4.16.0-202402211239.p0.g7a2ea37.assembly.stream.el8 for distgit ose-agent-installer-orchestrator.
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/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants