search

home-assistant / supervisor

:house_with_garden: Home Assistant Supervisor
https://home-assistant.io/hassio/
Apache License 2.0
1.66k stars 607 forks source link

Supervisor create new connection interface when modified #4383

Open warshoot3r opened 1 year ago

warshoot3r commented 1 year ago

Describe the issue you are experiencing

If you use are using VLAN. This is not affected if you are using ethernet only or Wifi.

Few issues happening: Connection name is incorrect. It displays "Supervisor eth0.30.30" rather than it should be "Supervisor eth0.30".

The new UUID is being generated every time when you make a change on the vlan networks.

Supervisor creates a new connection in NetworkManager ending up with lots of duplicate connections. But they are not connected so it it not major issue.

What type of installation are you running?

Home Assistant Supervised

Which operating system are you running on?

Other (e.g., Raspbian/Raspberry Pi OS/Fedora)

Steps to reproduce the issue

  1. SSH to host
  2. Create VLAN with "ha network vlan eth0 20"
  3. Run "ha network reload" so that vlan is visible in Network Tab.
  4. http://:8123/config/network. Set it to disabled
  5. http://:8123/config/network. Set it to Enabled
  6. run "nmcli con" on the host. Supervisor creates another connection everytime it is modified ...

Anything in the Supervisor logs that might be useful for us?

Host logs:
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.3838] device (eth0.30): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.3880] audit: op="connection-add-activate" uuid="cf6be0f2-2c29-49a0-ac97-d9640fc4caa1" name="Supervisor eth0.30.30" pid=1693 uid=0 result="success"
Jun 15 15:38:51 hassio systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 15 15:38:51 hassio systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.4763] device (eth0.30): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.5329] device (eth0.30): Activation: starting connection 'Supervisor eth0.30.30' (cf6be0f2-2c29-49a0-ac97-d9640fc4caa1)
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.5457] device (eth0.30): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.5482] device (eth0.30): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.5540] device (eth0.30): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.5558] dhcp4 (eth0.30): activation: beginning transaction (timeout in 45 seconds)
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.6650] dhcp4 (eth0.30): state changed unknown -> bound, address=10.10.30.200
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.6691] device (eth0.30): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.6749] device (eth0.30): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.6756] device (eth0.30): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 15 15:38:51 hassio NetworkManager[24779]: <info>  [1686839931.6973] device (eth0.30): Activation: successful, device activated.

Supervisor logs:
CoreState.RUNNING
23-06-15 15:33:24 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
23-06-15 15:33:40 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token

23-06-15 15:38:51 INFO (MainThread) [supervisor.host.network] Updating local network information

System Health information

System Information

version core-2023.6.2
installation_type Home Assistant Supervised
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.11.4
os_name Linux
os_version 6.1.21-v8+
arch aarch64
timezone Europe/London
config_dir /config
Home Assistant Community Store GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.32.1 Stage | running Available Repositories | 1360 Downloaded Repositories | 18
AccuWeather can_reach_server | ok -- | -- remaining_requests | 39
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Debian GNU/Linux 11 (bullseye) -- | -- update_channel | stable supervisor_version | supervisor-2023.06.2 agent_version | 1.5.1 docker_version | 24.0.2 disk_total | 117.1 GB disk_used | 15.2 GB healthy | true supported | failed to load: supported supervisor_api | ok version_api | ok installed_addons | Mosquitto broker (6.2.1), Node-RED (14.2.2), AirCast (3.5.3), AirSonos (3.5.4), TasmoAdmin (0.24.4), ESPHome (2023.5.5), File editor (5.6.0), Home Assistant Google Drive Backup (0.110.4), Duck DNS (1.15.0), NGINX Home Assistant SSL proxy (3.5.0), Log Viewer (0.15.1), chrony (2.6.0), Advanced SSH & Web Terminal (15.0.2), Matter Server (4.6.0)
Dashboards dashboards | 3 -- | -- resources | 13 views | 15 mode | storage
Recorder oldest_recorder_run | 13 June 2023 at 22:03 -- | -- current_recorder_run | 15 June 2023 at 14:33 estimated_db_size | 64.85 MiB database_engine | sqlite database_version | 3.41.2

Supervisor diagnostics

No response

Additional information

No response

Particpant commented 11 months ago

I'd like to confirm that I can also repro this bug with vlans that were generated via nmcli. Enabling/disabling, or even turning ipv4/ipv6 on or off in the system UIs creates duplicated networks.

github-actions[bot] commented 10 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Particpant commented 10 months ago

Issue still present.

github-actions[bot] commented 9 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Particpant commented 9 months ago

Issue still present

github-actions[bot] commented 8 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Particpant commented 8 months ago

Not resolved.

Lumute commented 8 months ago

I just noticed this issue, manually deleted all duplicates using this command:

nmcli con show
nmcli con delete UUID

Anyway, just to confirm this is still present as of latest everything:

Home Assistant 2023.10.4 Supervisor 2023.10.0 Operating System 11.0 Frontend 20231005.0 - latest

github-actions[bot] commented 7 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Particpant commented 7 months ago

Not resolved.

github-actions[bot] commented 6 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Particpant commented 6 months ago

Not resolved.

linucks commented 5 months ago

I'm experiencing this too. It would be helpful to resolve this as it makes it hard to automate management of the network interfaces.

github-actions[bot] commented 4 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Particpant commented 4 months ago

Not resolved.

github-actions[bot] commented 3 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Particpant commented 3 months ago

👏 Thank you. @agners!

agners commented 2 months ago

@Particpant the naming fix is now on the stable channel. Can you check if this resolves the issue for you?

Particpant commented 2 months ago

Will do! Might be a day or so.

Particpant commented 2 months ago

Had some unexpected delays, still intending to verify the fix as soon as I can.

Particpant commented 1 month ago

seems to be fixed