forked from linux/documentation
37 lines
1.3 KiB
Markdown
37 lines
1.3 KiB
Markdown
# Deployment Troubleshouting
|
|
|
|
## Failing Network Connection
|
|
|
|
Is the network MAC address correct and registered at PacketFence, e.g. for the office network?
|
|
|
|
## Failing Network Connection using Thunderbolt Dock
|
|
|
|
On a Thunderbolt dock the installation kernel may start fine, but the downloading the Kickstart file from the sysdb API may fail due to no network connection available.
|
|
This is due to Thunderbolt needing user authorization before it makes the functionality like networking available.
|
|
|
|
Depending on firmware/BIOS, you may change how Thunderbolt authorization behaves (temporarily) in the settings.
|
|
|
|
Another "easy" workaround is to use some other device, e.g. a USB network adapter for the installation as such.
|
|
|
|
If you really want to authorize the Thunderbolt dock before the installation starts, then you need to break the boot:
|
|
|
|
```bash
|
|
FQDN=...
|
|
bob node set-attr $FQDN 'kernel_cmdline=rd.break=cmdline'
|
|
```
|
|
|
|
after you start the installation you get first to the shell, where you need to run for Thunderbolt devize authorization:
|
|
```bash
|
|
for f in /sys/bus/thunderbolt/devices/*/authorized; do echo 1 > $f; done
|
|
exit
|
|
```
|
|
|
|
then the network connection should set up automatically and the installation should start.
|
|
|
|
After the installation has been successfully started undo the boot break:
|
|
```bash
|
|
bob node del-attr $FQDN kernel_cmdline
|
|
```
|
|
|
|
|