-
Notifications
You must be signed in to change notification settings - Fork 456
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
EdgeAgent module is not able to authenticate during reprovisioning #4458
Comments
@alaendle Thanks for reporting this issue. We're investigating. |
iotedge/edgelet/edgelet-core/src/watchdog.rs Lines 179 to 197 in e4c6eae
It's a bug. We only recreate the EA module identity in Hub if the EA container doesn't already exist. You can work around it with |
This issue is being marked as stale because it has been open for 30 days with no activity. |
Removes all containers after a device reprovision. This is done because identities for containers might no longer be valid after the reprovision. Edgelet will refresh the identities on its next run. Resolves #4458
Removes all containers after a device reprovision. This is done because identities for containers might no longer be valid after the reprovision. Edgelet will refresh the identities on its next run. Resolves Azure#4458
#4833 should resolve this. Closing issue. |
Expected Behavior
Reprovisioning should happen and bring device back to valid state.
Current Behavior
Endless reattempts of reprovisioning.
Steps to Reproduce
Context (Environment)
Output of
iotedge check
I don't think this output is relaevant for this issue - I just added it for completeness. Please also note that the errors/wanings are all firewall related and do not indicate real problems. The really interessting logs are the ones of iotedged and the edgeAgent module included below.
Click here
Device Information
Runtime Versions
Logs
aziot-edged logs
edge-agent logs
Additional Information
docker ps
returnsSo it caught my attention that the command shows that the container was created 5 days ago, while it restarts every few seconds; so my assumption is that the state of the container is just wrong/not updated. However I have
dynamic_reprovisioning
set totrue
and no clock skew. Could it matter the timezones of host (CET) and container (UTC) are not identical (but personally I don't believe that makes a difference)?So this issue is related but not identical to #4241 and #3982. Please let me know if I was unclear or if I could contribute further information.
The text was updated successfully, but these errors were encountered: