Closed glamrock closed 10 years ago
Are you assigning an IP address to laptop-eth0 or node-eth0?
Does this still occur with 1.1 candidate images?
This issue didn't appear in v1.1rc1 testing after I overhauled the way that DHCP is handled in the scripts, so I'm closing this out.
On r1 builds, nodes will frequently not issue DHCP leases when connected over ethernet. When this happens, nodes will be stuck in a loop of disconnected/reconnecting until I manually assign an ip address to
eth0
.This happens both before running the setup wizard and after, but doesn't happen consistently. Hardware used was ubiquiti picostation.
When you're connecting after setup has been completed, it's always the case that the node AP will be accessible and give out DHCP leases. Rebooting the node fixes the issue.
This is fairly likely to be a race condition.