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 part 2 #1018

Merged
merged 25 commits into from
Apr 1, 2019
Merged

Conversation

arsing
Copy link
Member

@arsing arsing commented Mar 27, 2019

  • Update user-friendly error messages according to new spec.

  • Only display error causes when --verbose is set.

  • Add causes to warning messages, and only display then when --verbose
    is set.

  • Also check expiry of quickstart device CA cert.

  • Print message reminding user to run as root if "Edge Hub can bind to ports"
    check fails with EPERM, since 443 is a privileged port.

  • Remove "container can resolve other container hostname" check, since it is
    not a reported issue.

  • Remove "container on default network can resolve IoT Hub" checks
    on Windows since the "module runtime network" checks already cover it.

  • Tweak colors on Windows to match default PowerShell colors.

  • Strip iotedge-diagnostics binary to reduce container image size.


TODO:

  • Get new aka.ms URLs from Venkat (marked <TODO: aka.ms URL>).

arsing added 5 commits March 27, 2019 13:54
- Update user-friendly error messages according to new spec.

- Only display error causes when `--verbose` is set.

- Also check expiry of quickstart device CA cert.

- Print message reminding user to run as root if "Edge hHb can bind to ports"
  check fails with EPERM, since 443 is a privileged port.

- Remove "container can resolve other container hostname" check, since it is
  not a reported issue.
@arsing arsing marked this pull request as ready for review March 28, 2019 20:25
@arsing arsing requested review from damonbarry and myagley March 28, 2019 20:25
myagley
myagley previously approved these changes Apr 1, 2019
dns: Option<Vec<String>>,
}

let daemon_config_file = File::open(CONTAINER_ENGINE_CONFIG_PATH)
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we make this configurable?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, might as well.

@arsing arsing merged commit 63dc883 into Azure:master Apr 1, 2019
@arsing arsing deleted the iotedge-diagnose branch April 1, 2019 22:20
@veyalla
Copy link
Contributor

veyalla commented Apr 2, 2019

🎉👏

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.

3 participants