Skip to content

Conversation

@Prashanth684
Copy link
Contributor

Following up on comment in #1700 to split the functionality to trigger the boot order
switch to metal.go making it generic.

Following up on comment in coreos#1700 to split the functionality to trigger the boot order
switch to metal.go making it generic.
Copy link
Member

@cgwalters cgwalters left a comment

Choose a reason for hiding this comment

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

From what I can tell we're sending the signal and switching the boot order unconditionally on the firstboot. If that's all we need I think we already can do that because e.g. the virtio journal connection also shows we booted successfully.

Hmm right but the virtio journal connection lives in testiso.go too. Maybe it makes sense to drain that whole thing into metal.go?

If you've tested this I'm ok to merge as is as well, we can always improve more on followups. And thanks for taking this on!

@darkmuggle
Copy link
Contributor

Interesting....I'm with @cgwalters on having this all in one place. But I would rather have the test in the first place.

LGTM

@Prashanth684
Copy link
Contributor Author

From what I can tell we're sending the signal and switching the boot order unconditionally on the firstboot. If that's all we need I think we already can do that because e.g. the virtio journal connection also shows we booted successfully.

Hmm right but the virtio journal connection lives in testiso.go too. Maybe it makes sense to drain that whole thing into metal.go?

If you've tested this I'm ok to merge as is as well, we can always improve more on followups. And thanks for taking this on!

that can be done - but i'll have to pull in adding the live signal and testiso completion units to metal too along with the journal connection..is that desirable ?

@Prashanth684
Copy link
Contributor Author

From what I can tell we're sending the signal and switching the boot order unconditionally on the firstboot. If that's all we need I think we already can do that because e.g. the virtio journal connection also shows we booted successfully.
Hmm right but the virtio journal connection lives in testiso.go too. Maybe it makes sense to drain that whole thing into metal.go?
If you've tested this I'm ok to merge as is as well, we can always improve more on followups. And thanks for taking this on!

that can be done - but i'll have to pull in adding the live signal and testiso completion units to metal too along with the journal connection..is that desirable ?

ok..never mind the above comment..i got it working by just checking for the virtio journal as suggested, but had to change the systemd unit to be similar to the live signal unit by adding dependency on coreos-installer target for the pxe case https://github.com/coreos/coreos-assembler/blob/master/mantle/cmd/kola/testiso.go#L102

I'm not sure we want to do that? is there any other way to make it run on first boot for the pxe case?

@Prashanth684
Copy link
Contributor Author

From what I can tell we're sending the signal and switching the boot order unconditionally on the firstboot. If that's all we need I think we already can do that because e.g. the virtio journal connection also shows we booted successfully.
Hmm right but the virtio journal connection lives in testiso.go too. Maybe it makes sense to drain that whole thing into metal.go?
If you've tested this I'm ok to merge as is as well, we can always improve more on followups. And thanks for taking this on!

that can be done - but i'll have to pull in adding the live signal and testiso completion units to metal too along with the journal connection..is that desirable ?

ok..never mind the above comment..i got it working by just checking for the virtio journal as suggested, but had to change the systemd unit to be similar to the live signal unit by adding dependency on coreos-installer target for the pxe case https://github.com/coreos/coreos-assembler/blob/master/mantle/cmd/kola/testiso.go#L102

I'm not sure we want to do that? is there any other way to make it run on first boot for the pxe case?

@cgwalters ^^ thoughts?

@cgwalters
Copy link
Member

/approve
@Prashanth684 I think I lean towards getting in your change as is and doing more work as a followup.
Still good to /lgtm here?

@Prashanth684
Copy link
Contributor Author

/approve
@Prashanth684 I think I lean towards getting in your change as is and doing more work as a followup.
Still good to /lgtm here?

thanks ! yeah this works. good to lgtm

@jlebon jlebon closed this Nov 10, 2020
@jlebon jlebon reopened this Nov 10, 2020
@jlebon
Copy link
Member

jlebon commented Nov 10, 2020

/lgtm

Restarted CI on this to be safe.

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cgwalters, jlebon, Prashanth684

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-merge-robot openshift-merge-robot merged commit 4fd4ae6 into coreos:master Nov 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants