Skip to content
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

Merged
merged 25 commits into from
Mar 12, 2019
Merged

iotedge check improvements #926

merged 25 commits into from
Mar 12, 2019

Conversation

arsing
Copy link
Member

@arsing arsing commented Mar 6, 2019

  • 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.

- 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.
@arsing arsing requested a review from myagley March 6, 2019 23:11
@arsing

This comment has been minimized.

@arsing arsing requested a review from damonbarry March 11, 2019 20:05
}),
("edge hub can bind to ports on host", edge_hub_ports_on_host),
(
"container runtime network allows name resolution",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this message correct?

Copy link
Member Author

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".

Copy link
Contributor

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.

edgelet/iotedge/src/check.rs Outdated Show resolved Hide resolved
myagley
myagley previously approved these changes Mar 11, 2019
@arsing arsing merged commit f7e820f into Azure:master Mar 12, 2019
@arsing arsing deleted the iotedge-diagnose branch March 12, 2019 20:25
arsing added a commit to arsing/iotedge that referenced this pull request Apr 4, 2019
Cherry-pick of:

- 22ef977 Implement `iotedge check` to perform basic tests for common issues (Azure#777)
- f7e820f `iotedge check` improvements (Azure#926)
- 63dc883 `iotedge check` improvements part 2 (Azure#1018)
arsing added a commit to arsing/iotedge that referenced this pull request Apr 4, 2019
Cherry-pick from master of:

- 22ef977 Implement `iotedge check` to perform basic tests for common issues (Azure#777)
- f7e820f `iotedge check` improvements (Azure#926)
- 63dc883 `iotedge check` improvements part 2 (Azure#1018)
arsing added a commit that referenced this pull request Apr 5, 2019
…1051)

Cherry-pick from master of:

- 22ef977 Implement `iotedge check` to perform basic tests for common issues (#777)
- f7e820f `iotedge check` improvements (#926)
- 63dc883 `iotedge check` improvements part 2 (#1018)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants