New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supervisord crashes when a second network interface has no gateway #4442
Comments
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. |
This is still broken. |
Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) hassio documentation |
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. |
This is reproducible on Supervisor 2023.08.1. It seems that also the frontend behaves a bit weird: At times the settings cannot be saved even though changes have been made. |
Can confirm, still broken. |
The problem
The problem is rather simple: Supervisord assumes that every network interface will have a set of an IP+CIDR and a gateway address. This is a flawed assumption, as with multiple network cards realistically only the primary one should have a default route gateway.
Attempting to save a config like following, with the
enp6s18
being set to DHCP:Results in an error:
What version of Home Assistant Core has the issue?
2023.2.2
What was the last working version of Home Assistant Core?
N/A
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Supervisord itself
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
I isolated the problem to this exception, produced in the
supervisord
container:Additional information
Putting a gateway on that second card seems to solve the issue. However, I'm not sure if it will not cause problems down the line as generally I don't want a gateway on that card.
The text was updated successfully, but these errors were encountered: