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

WIP: NM in the initrd #259

Closed
wants to merge 1 commit into from
Closed

Conversation

cgwalters
Copy link
Member

@cgwalters cgwalters commented Jan 3, 2020

This seems not to run for me...I don't quite understand the
initqueue stuff, still debugging.

See also #200 (comment)

Blocked on: dracutdevs/dracut#694

This seems not to run for me...I don't quite understand the
initqueue stuff, still debugging.

See also coreos#200 (comment)
@cgwalters cgwalters added the hold label Jan 3, 2020
@cgwalters
Copy link
Member Author

@cgwalters
Copy link
Member Author

I've verified that we have the module code in the initrd, but it looks like the initqueue never executes /usr/lib/dracut/hooks/initqueue/settled/99-nm-run.sh (I added an echo statement to that code).

@thom311
Copy link

thom311 commented Jan 7, 2020

hm. Is there no further information here? Any logs?

What was the kernel command line?

If you don't even get 99-nm-run.sh to execute, then it's a dracut issue (or an issue in NM's dracut module).

@dustymabe
Copy link
Member

since I'm having networking in the initrd troubles myself, I can try testing this out to see if I get any different results.

@cgwalters
Copy link
Member Author

OK so...this is a bit obvious now, but entering emergency.target will kill other services - specifically it will kill dracut-initqueue.service. So to better replicate what's going on in the normal case, be sure to at least systemctl start dracut-initqueue.

@cgwalters
Copy link
Member Author

hm. Is there no further information here? Any logs?
What was the kernel command line?

rd.neednet ip=dhcp are the relevant bits.

I can paste the full journal if you want (it's also easy to do a FCOS build from this patch) but AFAICS there's nothing there of use because:

If you don't even get 99-nm-run.sh to execute, then it's a dracut issue (or an issue in NM's dracut module).

Right. That's as far as I got - it's not clear to me why that hook isn't being executed. I don't understand the initqueue really to be honest.

@cgwalters
Copy link
Member Author

xref dracutdevs/dracut#702

@cgwalters
Copy link
Member Author

As best I can tell what's happening is /usr/bin/dracut-initqueue is calling check_finished which looks for files in $hookdir/initqueue/finished/ - and since nothing is there, we exit before trying any of the other hooks.

It seems like other dracut initrd code is dropping files there, but the NM initrd code isn't.

Was this NM initrd code ever tested? If so, where?

@ryncsn
Copy link

ryncsn commented Jan 10, 2020

Hi, for the dracut problem I have filed an issue that is related to your problem sometime ago, maybe we can discuss there:
See dracutdevs/dracut#694

@cgwalters
Copy link
Member Author

@ryncsn Thank you, that looks exactly like the bug!

@jlebon
Copy link
Member

jlebon commented Mar 10, 2020

Blocked on: dracutdevs/dracut#694.

@LorbusChris
Copy link
Contributor

Hopefully this'll be unblocked with the next dracut build :)

@dustymabe
Copy link
Member

Now that dracutdevs/dracut#694 is fixed I'm picking this up and running with it. I'm going to close this out and open a new PR with more fixes in it.

@dustymabe
Copy link
Member

If you'd like to track progress on this you can follow coreos/fedora-coreos-tracker#394

@dustymabe dustymabe closed this Mar 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants