SimulatedTemperatureSensor tutorial -> Module stop from Azure portal get exception into the module itself

ChumKiu commented 1 month ago

Expected Behavior

I'll expect that by changing the module from running to stopped the module on the device will stop.

Current Behavior

By using the sudo iotedge list the situation show that the SimulatedTemperatureSensor status is failed. The edgeAgent and edgeHub are still running.

Steps to Reproduce

Provide a detailed set of steps to reproduce the bug.

Follow the tutorial "Quickstart: Deploy your first IoT Edge module to a Windows device"
Show the status give all running without any trouble
From the portal try to change the status of the module from running to stopped and perform the creation so wait the portal update the IoT device
check the status by the sudo iotedge list command show failed(139) as status instead stopped as I've expected

Context (Environment)

IoT device on a tablet with Windows 11

Output of `iotedge check`

iotedge-user@WIN-11-EFLOW [ ~ ]$ sudo iotedge check --verbose

Configuration checks (aziot-identity-service)

√ keyd configuration is well-formed - OK √ certd configuration is well-formed - OK √ tpmd configuration is well-formed - OK √ identityd configuration is well-formed - OK √ daemon configurations up-to-date with config.toml - OK √ identityd config toml file specifies a valid hostname - OK √ aziot-identity-service package is up-to-date - OK √ host time is close to reference time - OK √ preloaded certificates are valid - OK √ keyd is running - OK √ certd is running - OK √ identityd is running - OK √ read all preloaded certificates from the Certificates Service - OK √ read all preloaded key pairs from the Keys Service - OK √ check all EST server URLs utilize HTTPS - OK √ ensure all preloaded certificates match preloaded private keys with the same ID - OK

Connectivity checks (aziot-identity-service)

√ host can connect to and perform TLS handshake with iothub AMQP port - OK √ host can connect to and perform TLS handshake with iothub HTTPS / WebSockets port - OK √ host can connect to and perform TLS handshake with iothub MQTT port - OK

Configuration checks

√ aziot-edged configuration is well-formed - OK √ configuration up-to-date with config.toml - OK √ container engine is installed and functional - OK √ configuration has correct URIs for daemon mgmt endpoint - OK √ aziot-edge package is up-to-date - OK √ container time is close to host time - OK ‼ DNS server - Warning Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub. Please see https://aka.ms/iotedge-prod-checklist-dns for best practices. You can ignore this warning if you are setting DNS server per module in the Edge deployment. caused by: Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub. Please see https://aka.ms/iotedge-prod-checklist-dns for best practices. You can ignore this warning if you are setting DNS server per module in the Edge deployment. ‼ production readiness: logs policy - Warning Container engine is not configured to rotate module logs which may cause it run out of disk space. Please see https://aka.ms/iotedge-prod-checklist-logs for best practices. You can ignore this warning if you are setting log policy per module in the Edge deployment. caused by: Container engine is not configured to rotate module logs which may cause it run out of disk space. Please see https://aka.ms/iotedge-prod-checklist-logs for best practices. You can ignore this warning if you are setting log policy per module in the Edge deployment. ‼ production readiness: Edge Agent's storage directory is persisted on the host filesystem - Warning The edgeAgent module is not configured to persist its /tmp/edgeAgent directory on the host filesystem. Data might be lost if the module is deleted or updated. Please see https://aka.ms/iotedge-storage-host for best practices. caused by: The edgeAgent module is not configured to persist its /tmp/edgeAgent directory on the host filesystem. Data might be lost if the module is deleted or updated. Please see https://aka.ms/iotedge-storage-host for best practices. ‼ production readiness: Edge Hub's storage directory is persisted on the host filesystem - Warning The edgeHub module is not configured to persist its /tmp/edgeHub directory on the host filesystem. Data might be lost if the module is deleted or updated. Please see https://aka.ms/iotedge-storage-host for best practices. caused by: The edgeHub module is not configured to persist its /tmp/edgeHub directory on the host filesystem. Data might be lost if the module is deleted or updated. Please see https://aka.ms/iotedge-storage-host for best practices. √ Agent image is valid and can be pulled from upstream - OK √ proxy settings are consistent in aziot-edged, aziot-identityd, moby daemon and config.toml - OK

Connectivity checks

√ container on the default network can connect to upstream AMQP port - OK √ container on the default network can connect to upstream HTTPS / WebSockets port - OK √ container on the default network can connect to upstream MQTT port - OK skipping because of not required in this configuration √ container on the IoT Edge module network can connect to upstream AMQP port - OK √ container on the IoT Edge module network can connect to upstream HTTPS / WebSockets port - OK √ container on the IoT Edge module network can connect to upstream MQTT port - OK skipping because of not required in this configuration 31 check(s) succeeded. 4 check(s) raised warnings. 2 check(s) were skipped due to errors from other checks. iotedge-user@WIN-11-EFLOW [ ~ ]$

Click here

``` ```

Device Information

Host OS [e.g. Ubuntu 22.04, Windows Server IoT 2019]: device host Windows 11 on tablet
Architecture [e.g. amd64, arm32, arm64]: linux/amd64
Container OS [e.g. Linux containers, Windows containers]: Linux containers on Window enviroments

Runtime Versions

aziot-edged [run iotedge version]: 1.4.33
Edge Agent [image tag (e.g. 1.0.0)]:
Edge Hub [image tag (e.g. 1.0.0)]:
Docker/Moby [run docker version]:

Note: when using Windows containers on Windows, run docker -H npipe:////./pipe/iotedge_moby_engine version instead

Logs

aziot-edged logs

``` ```

edge-agent logs

``` ```

edge-hub logs

``` ```

Additional Information

Please provide any additional information that may be helpful in understanding the issue.

nyanzebra commented 1 month ago

@ChumKiu thanks for bringing this up! I managed to repro the same thing and this doesn't match to what is expected to happen... will be investigating further and see what might be going wrong.

nyanzebra commented 3 weeks ago

Just to update here, the issue has been found, will post again here once this is fixed.

Azure / iotedge