-
Notifications
You must be signed in to change notification settings - Fork 462
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
iotedge check
improvements
#926
Conversation
- Restructure list of checks per the new spec. - Allow the user to override the expected latest version of iotedged. If this is set, the command does not reach out to the aka.ms URL to fetch the expected latest version. - Allow the user to override the name of the diagnostics image. - Differentiate between checks with warnings and checks that were skipped because a previous check failed. - Hide skipped tests unless `--verbose` is set. - Add check that device will not run in quick start mode. - Downgrade error that Moby is not being used in Windows to a warning. - Fix check that the edge agent can reach the management URI to handle the case where the listening URI is an fd. - Downgrade error that iotedged is not the latest version to a warning. - Fix host local time check to handle the case where the host is too far behind the SNTP server. - Fix host local time check to report a warning instead of an error if the SNTP server is not reachable. - Remove checks for the versions of edge agent and edge hub, since these should be reported by the portal, etc. - Remove the check that the Azure IoT Hub AMQP and MQTT ports can be reached from the host. Instead check these from within a module container. - Add check that any ports that edge hub wants to bind to on the host are available. - Use colors when writing the success / warning / error results of the checks. - Add note to default config.yaml about how the connect URIs must match the file paths in the systemd socket files.
This comment has been minimized.
This comment has been minimized.
Some customers are known to have middleboxes that allow TCP connections on these ports but block TLS traffic.
edgelet/iotedge/src/check.rs
Outdated
}), | ||
("edge hub can bind to ports on host", edge_hub_ports_on_host), | ||
( | ||
"container runtime network allows name resolution", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this message correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Venkat suggests "modules on the container runtime network can resolve each other by name".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh wait. I thought this was related to the port binding check. You can disregard my comment.
c730d54
to
db07949
Compare
Restructure list of checks per the new spec.
Allow the user to override the expected latest version of iotedged.
If this is set, the command does not reach out to the aka.ms URL to
fetch the expected latest version.
Allow the user to override the name of the diagnostics image.
Differentiate between checks with warnings and checks that were skipped
because a previous check failed.
Hide skipped tests unless
--verbose
is set.Add check that device will not run in quick start mode.
Downgrade error that Moby is not being used in Windows to a warning.
Fix check that the edge agent can reach the management URI to handle
the case where the listening URI is an fd.
Downgrade error that iotedged is not the latest version to a warning.
Fix host local time check to handle the case where the host is too
far behind the SNTP server.
Fix host local time check to report a warning instead of an error if
the SNTP server is not reachable.
Remove checks for the versions of edge agent and edge hub, since
these should be reported by the portal, etc.
Remove the check that the Azure IoT Hub AMQP and MQTT ports can be reached
from the host. Instead check these from within a module container.
Add check that any ports that edge hub wants to bind to on the host are
available.
Use colors when writing the success / warning / error results of
the checks.
Add note to default config.yaml about how the connect URIs must match
the file paths in the systemd socket files.