No such file or directly: '/EULA' after answerfile installation

[pietrushnic]

I'm trying answerfile automated installation using xcp-ng-8.0 and after installation getting the following screen:

My answer file: https://gist.github.com/pietrushnic/6cd46cfc32d41be0f60bc65595649601

Answerfile documentation says nothing about EULA or licensing at all. If this is a bug I can try to fix it in answerfile.py.

[stormi]

Thanks for the feedback. This is a benign known bug. Just press Enter. It is fixed in XCP-ng 8.1.

[stormi]

By the way, if you can check the fix, the latest pre-release ISOs are available at https://updates.xcp-ng.org/isos/8.1/

[pietrushnic]

@stormi it doesn't boot and complains for the configuration that I'm using for booting (my grub.cfg):

echo "insmod efinet"
insmod efinet
sleep 2
echo "call net_dhcp"
net_dhcp
sleep 2

echo "tftp load xen.gz..."
multiboot2 (tftp,$net_efinet0_dhcp_next_server)/xen.gz dom0_mem=1024M,max:1024M watchdog dom0_max_vcpus=4 com1=115200,8n1 console=com1,vga
echo "tftp load vmlinuz..."
module2 (tftp,$net_efinet0_dhcp_next_server)/vmlinuz console=hvc0 console=tty0  answerfile=https://gist.githubusercontent.com/pietrushnic/6cd46cfc32d41be0f60bc65595649601/raw/a5a754e0927e553aeae27ff312763e0e1a5109b9/xpc-ng-answerfile install
#module2 (tftp,$net_efinet0_dhcp_next_server)/vmlinuz console=hvc0 console=tty0 install
echo "tftp load install.img..."
module2 (tftp,$net_efinet0_dhcp_next_server)/install.img
echo "booting..."
boot

I made picture of 2 "problems":

[pietrushnic]

@stormi finally I was able to boot 8.1, definitely, there was a problem with tftp, but then I tried GRUB 2.04 using its tftp and http support. Performance of GRUB TFTP and HTTP modules is terrible, I will get to address that with maintainer, maybe on GRUB and 3mdeb minisummit 2020. So I switched to ipxe, the problem here was that there is not multiboot2 support, so we applied some old patches (2017) and those worked if anyone interested iPXE multiboot2 UEFI suport - maybe we will be able to merge that upstream.

Finally, HTTP performance in iPXE is very good and I was able to boot XCP-ng 8.1 prefinal2. the problem mentioned in this issue no longer occurs, but I faced different message, which requires accepting:

So the situation was improved because we have no error, but we still need user interaction. Can I get some rationale behind that decision? Can we assume the system would be usable without accepting? Can we extend answerfile to cover that license?

[stormi]

This behaviour is inherited from Citrix. I guess it's a legal requirement. You could open an issue asking for an enhancement, or even contribute it. Please describe the context and try to give an idea of the value of such a change for users.

The text doesn't look good though, looks like the text is all mixed.

[stormi]

If I remember correctly, when the answerfile contains a password hash for the root user, then this screen is not displayed. Could be a workaround. You can still change the password afterwards.