search

OpenNebula / addon-context-linux

Linux VM Contextualization
Apache License 2.0
56 stars 73 forks source link

M #: Ensure proper network restart for alpine 3.16+ #296

Closed dann1 closed 1 year ago

dann1 commented 1 year ago

Fixes

375. Contextualization image Alpine 3.17 on KVM common (1) doesn't ping detached NIC alias [Alpine 3.17]
Frontends: alma8-context-kvm-6-7-jnks339-0.test

reached timeout, last state was false  while expected true
At ./spec/context/linux/network.rb:274

376. Contextualization image Alpine 3.17 on KVM common (1) doesn't have new NIC in guest [Alpine 3.17]
Frontends: alma8-context-kvm-6-7-jnks339-0.test

reached timeout, last state was false CLITester::VM(0) while expected true
At ./spec/context/linux/network.rb:283

377. Contextualization image Alpine 3.17 on KVM common (1) waits for contextualization [Alpine 3.17]
Frontends: alma8-context-kvm-6-7-jnks339-0.test

reached timeout, last state was false  while expected true
At ./spec/context/common.rb:214

378. Contextualization image Alpine 3.16 on KVM common (1) doesn't ping detached NIC alias [Alpine 3.16]
Frontends: alma8-context-kvm-6-7-jnks339-0.test

reached timeout, last state was false  while expected true
At ./spec/context/linux/network.rb:274

379. Contextualization image Alpine 3.16 on KVM common (1) doesn't have new NIC in guest [Alpine 3.16]
Frontends: alma8-context-kvm-6-7-jnks339-0.test

reached timeout, last state was false CLITester::VM(1) while expected true
At ./spec/context/linux/network.rb:283

380. Contextualization image Alpine 3.16 on KVM common (1) waits for contextualization [Alpine 3.16]
Frontends: alma8-context-kvm-6-7-jnks339-0.test

reached timeout, last state was false  while expected true
At ./spec/context/common.rb:214

Problem is after detaching the NIC alias, the parent interface doesn't get reconfigured and remains in DOWN state. Issuing a service networking restart does the trick.