Fixing double ip assignment
This commit is contained in:
@@ -128,6 +128,16 @@ boot LAN.
|
||||
- `nvme_tcp`/`nvme_fabrics` must be loaded before `/dev/nvme-fabrics` exists
|
||||
(dracut's `nvmf` module does this in a normal boot; at `rd.break` modprobe
|
||||
manually).
|
||||
- **Don't double-configure the NIC in test mode.** With `ip=dhcp` on the
|
||||
cmdline, dracut's network module brings the NIC up AND emits the "online"
|
||||
event that the `nvmf` module's `initqueue/online` hook waits on to run
|
||||
`nvme connect-all`. The `rd.dot1x=0` bypass used to *also* `ifup $NIC`,
|
||||
which (a) raced dracut → `Error: ipv4: Address already assigned`, and (b)
|
||||
didn't fire the nvmf online hook, so the namespace never auto-connected and
|
||||
boot spun on `/dev/mapper/root` forever (manual `connect-all` worked, which
|
||||
is what masked it). **Fixed:** the bypass branch no longer touches the NIC;
|
||||
`ip=dhcp` owns networking and triggers nvmf autoconnect. (The secure path
|
||||
still addresses macsec0 itself — dracut doesn't know about that interface.)
|
||||
- The target Rocky 9 kernel's erofs is built **without
|
||||
`CONFIG_EROFS_FS_ZIP`** — mounting a compressed image fails `erofs: lz4
|
||||
algorithm isn't enabled`, which silently blocks the root mount. **Fixed:**
|
||||
|
||||
Reference in New Issue
Block a user