Skip to content

Conversation

@carbonin
Copy link
Member

@carbonin carbonin commented Jan 9, 2025

This indicates the container image that should be installed and booted for the installed host. It also indicates that we should install to the currently booted disk, in a new stateroot, rather than expecting a device path.

https://issues.redhat.com/browse/MGMT-19100

cc @tsorya @rccrdpccl @eranco74

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 9, 2025

@carbonin: This pull request references MGMT-19100 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 task to target the "4.19.0" version, but no target version was set.

Details

In response to this:

This indicates the container image that should be installed and booted for the installed host. It also indicates that we should install to the currently booted disk, in a new stateroot, rather than expecting a device path.

https://issues.redhat.com/browse/MGMT-19100

cc @tsorya @rccrdpccl @eranco74

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 9, 2025
@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 9, 2025
@openshift-ci openshift-ci bot requested review from danmanor and eliorerz January 9, 2025 21:25
@openshift-ci
Copy link

openshift-ci bot commented Jan 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: carbonin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Jan 9, 2025
@codecov
Copy link

codecov bot commented Jan 9, 2025

Codecov Report

Attention: Patch coverage is 33.92857% with 37 lines in your changes missing coverage. Please review.

Project coverage is 55.00%. Comparing base (e9ae12d) to head (2bde274).
Report is 1 commits behind head on master.

Files with missing lines Patch % Lines
src/ops/ops.go 24.39% 31 Missing ⚠️
src/installer/installer.go 57.14% 5 Missing and 1 partial ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1003      +/-   ##
==========================================
- Coverage   55.39%   55.00%   -0.39%     
==========================================
  Files          15       15              
  Lines        3318     3365      +47     
==========================================
+ Hits         1838     1851      +13     
- Misses       1297     1331      +34     
  Partials      183      183              
Files with missing lines Coverage Δ
src/config/config.go 70.58% <100.00%> (+0.43%) ⬆️
src/installer/installer.go 68.58% <57.14%> (-0.18%) ⬇️
src/ops/ops.go 41.92% <24.39%> (-1.33%) ⬇️

@carbonin carbonin force-pushed the image-install branch 2 times, most recently from eb0683a to 928a493 Compare January 10, 2025 18:29
src/ops/ops.go Outdated

func (o *ops) importOSTreeCommit(liveLogger io.Writer) (string, error) {
ostreeReleasePullSpec := fmt.Sprintf("ostree-unverified-registry:%s", o.installerConfig.CoreosImage)
out, err := o.ExecPrivilegeCommand(liveLogger, "ostree", "container", "unencapsulate", "--authfile", "/root/.docker/config.json", "--quiet", "--repo", "/ostree/repo", ostreeReleasePullSpec)
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: this is probably not gonna change often (or possibly never), however wouldn't the docker config file path be better in a constant? (there's already one in installer package, should we share such constant - in a different package of course - as we are relying that this file has been extracted there?)

@rccrdpccl
Copy link
Contributor

/retest
/lgtm

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

/retest-required

Remaining retests: 0 against base HEAD e9ae12d and 2 for PR HEAD cc87535 in total

This indicates the container image that should be installed and booted
for the installed host. It also indicates that we should install to the
existing root filesystem, in a new stateroot, rather than expecting a
device path.

https://issues.redhat.com/browse/MGMT-19100
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 21, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD e9ae12d and 2 for PR HEAD cc87535 in total

@openshift-ci
Copy link

openshift-ci bot commented Jan 22, 2025

@carbonin: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn 2bde274 link false /test okd-scos-e2e-aws-ovn
ci/prow/edge-e2e-oci-assisted-4-18 2bde274 link false /test edge-e2e-oci-assisted-4-18

Full PR test history. Your PR dashboard.

Details

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.

@rccrdpccl
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 22, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit e27ef9e into openshift:master Jan 22, 2025
19 of 21 checks passed
Copy link
Contributor

@eranco74 eranco74 left a comment

Choose a reason for hiding this comment

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

/lgtm

flagSet.BoolVar(&c.SkipInstallationDiskCleanup, "skip-installation-disk-cleanup", false, "Skip installation disk cleanup gives disk management to coreos-installer in case needed")
flagSet.BoolVar(&c.EnableSkipMcoReboot, "enable-skip-mco-reboot", false, "indicate assisted installer to generate settings to match MCO requirements for skipping reboot after firstboot")
flagSet.BoolVar(&c.NotifyNumReboots, "notify-num-reboots", false, "indicate number of reboots should be notified as event")
flagSet.StringVar(&c.CoreosImage, "coreos-image", "", "CoreOS image to install to the existing root")
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider renaming CoreosImage to OciImage

if i.Config.CoreosImage == "" {
return i.ops.WriteImageToDisk(liveLogger, ignitionPath, i.Device, i.Config.InstallerArgs)
} else {
return i.ops.WriteImageToExistingRoot(liveLogger, ignitionPath)
Copy link
Contributor

Choose a reason for hiding this comment

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

It should get the i.Config.CoreosImage, no?

@eranco74
Copy link
Contributor

@javipolo PTAL

@carbonin carbonin deleted the image-install branch January 22, 2025 16:02
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-agent-installer-orchestrator
This PR has been included in build ose-agent-installer-orchestrator-container-v4.19.0-202501221808.p0.ge27ef9e.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-agent-installer-csr-approver
This PR has been included in build ose-agent-installer-csr-approver-container-v4.19.0-202501221808.p0.ge27ef9e.assembly.stream.el9.
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.

7 participants