Ubuntu
ubiquity package

subiquity network event _send_update: CHANGE ETH0

Asked by Neagu

Questions:
- Does someone knows what is triggering this message?
- Is there a way to have more details about that is causing it(debugging mode)?

I have an issue with the installation of Ubuntu 20.04 using autoinstall (manual installation doesn't have this issue). I'm receiving a lot of event messages on console: 'ubuntu-server subiquity_event.1890[1890]: subiquity/Network/_send_update: CHANGE eth0' and I'm not able to track the issue down.

Environment:
- Virtualization: Hyper-V
- Build tool: Packer
- Hyper-V Switch: external(bridge mode)

Log: https://pastebin.com/ELxy361r
Packer template: https://pastebin.com/sM30Ktdk
User-data: https://pastebin.com/GQPsZTbc

Note:
The issue with the above event message is that I'm not able to track the issue down and it is polluting the console log and sometimes the build fails but without being able to catch the error due to the message above.

The strange issue is that using a NAT switch (Default Switch) this error is not triggered.

I have built the previous Ubuntu version(Debian installer) without any issues on the same environment, therefore I think there is something that subiquity require from the bridge networking that I have but the event doesn't provide enough information.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu ubiquity Edit question
Assignee:
No assignee Edit question
Solved by:
Neagu
Solved:
Last query:
Last reply:
Revision history for this message
Neagu (neaguali) said : 		#1

After more debuging, I think the issue is caused by the IPv6:

In /var/log/installer/subiquity-server-debug.log the following piece of log is the one that is triggering the console event from what I can understand.

2021-08-15 08:10:42,509 DEBUG subiquitycore.utils:48 run_command called: ['udevadm', 'settle', '-t', '0']
2021-08-15 08:10:42,524 DEBUG subiquitycore.utils:61 run_command ['udevadm', 'settle', '-t', '0'] exited with code 0
2021-08-15 08:10:42,524 DEBUG probert.network:586 event for addr_change: CHANGE {'ifindex': 2, 'flags': 768, 'family': 10, 'scope': 0, 'local': b'fd00:c47:3dfa:d382:215:5dff:fe00:ed6/64'}
2021-08-15 08:10:42,524 DEBUG probert.network:718 addr_change CHANGE {'ifindex': 2, 'flags': 768, 'family': 10, 'scope': 0, 'local': b'fd00:c47:3dfa:d382:215:5dff:fe00:ed6/64'}
2021-08-15 08:10:42,524 DEBUG root:39 start: subiquity/Network/_send_update: CHANGE eth0
2021-08-15 08:10:42,525 DEBUG subiquity.server.controllers.network:269 dev_info eth0 {'dhcp4': True}
2021-08-15 08:10:42,525 DEBUG root:39 finish: subiquity/Network/_send_update: SUCCESS: CHANGE eth0

Revision history for this message
Neagu (neaguali) said : 		#2

After disabling the IPV6 using boot parameters the event is no longer triggered.

The issue is solved now.