iotedge check-list doesn't run
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 473
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 7
Description
## Expected Behavior
`sudo iotedge check-list` should display a list of the supported checks.
`sudo iotedge check --help` should display additional help for the check command.
## Current Behavior
Both behave identically to `sudo iotedge check`.
## Steps to Reproduce
Provide a detailed set of steps to reproduce the bug.
1. `sudo iotedge check-list`
2. `sudo iotedge check --help`
Also of note is that the `iotedge check` command appears to ignore other arguments, like `--help` and `--dont-run`.
## Context (Environment)
### Output of `iotedge check`
Not relevant.
### Device Information
* Host OS [e.g. Ubuntu 22.04, Windows Server IoT 2019]: Ubuntu 24.04.2
* Architecture [e.g. amd64, arm32, arm64]: amd64
* Container OS [e.g. Linux containers, Windows containers]: Linux containers
### Runtime Versions
* aziot-edged [run `iotedge version`]: iotedge 1.5.21
* Edge Agent [image tag (e.g. 1.0.0)]: 1.5.16
* Edge Hub [image tag (e.g. 1.0.0)]: 1.5.16
* Docker/Moby [run `docker version`]: 28.3.3-1
## Logs
Not relevant.
## Additional Information
The `aziotctl` command behaves as expected; `check-list` works and `check --help` shows help, and `check --dont-run` skips the requested checks.
Also, part of the reason why I want to skip certain checks is that the timeouts are insanely long; if you're in a heavily-firewalled environment that blocks `aka.ms` or AMQP/MQTT ports then you have to sit through multiple ~70s timeouts.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the iotedge check command handling and compare its argument behavior with the aziotctl command, especially for check-list, --help, and --dont-run. Done means these arguments produce their expected output or skip behavior instead of behaving like plain check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100