-
Notifications
You must be signed in to change notification settings - Fork 340
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
ONL installer gets unknown onie_platform in latest ONIE #283
Comments
I did a test on AS7712_32X having a revised ONIE keeping machine.conf in the initrd image which can install latest ONL normally. |
@david56 @carlroth Lets modify the platform detection logic to remove the chroot into ONIE. Environment override
Installing from ONIE Installing form ONL What do you think? cc @cbrune |
see #287 |
The latest ONL can be installed via latest ONIE normally now. Thank you. |
Hello @carlroth, @jnealtowns , @cbrune ,
In latest ONIE, I had removed machine.conf from the initrd image. i.e., machine.conf is generated at ONIE run-time dynamically rather than putting a static one in the image. ONL had been revised to use
onie-sysinfo
on Dec 27 (#280 ). We found ONL install failed because it unpacks the image to executeonie-sysinfo
to getonie_platform
. In the unpacked environment, machine.conf is not existent so thatonie-sysinfo
will replyunknown
to ONL installer. It will try to import a module namedunknown
:It looks that it is necessary to keep machine.conf in the image to make the installer go smoothly. But
onie-sysinfo
still lacks machine-live.conf (which is also generated dynamically at ONIE run-time) for calculating the realonie_platform
. We need to discuss how to fix the issue.I would appreciate your opinions. Thank you very much.
Cheers,
David
The text was updated successfully, but these errors were encountered: