-
Notifications
You must be signed in to change notification settings - Fork 492
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
[Bug Report] SetMethodHandlerAsync: No authenticated context #2353
Comments
@brycewang-microsoft This seems like another problem with similar circumstances as #2337. I'd really appreciate it if you could give your insight here. What is your intuition as to what is going wrong here? |
Discussed with @and-rewsmith and @drwill-ms offline. We noticed that our library |
@brycewant-microsoft To update this bug with the discussion from our side channel, the LTS fix did not fix this issue and SDK logs were insufficient in getting this fixed. I am trying to collect wireshark logs now but it has not yet reproduced while tcpdump is running. |
Synced up with @and-rewsmith offline for this. The nuget "Microsoft.Azure.Devices.Client" with Amqp v2.5.12 can fix this, which has been included in our LTS release. Closing this issue and feel free to reopen it if needed. |
Context
Description of the issue
I am a software engineer working for the iotedge team. In our E2E tests we get the following exception a considerable amount. We didn't used to get this exception before upgrading to dotnet 6.
This issue is similar to #2337, as it happens in the same test framework when trying to set the method handler. I have also tried to reproduce this locally, but not been able to.
I took your advice from the previous issue and added a connection status changed callback. This can be seen in the test framework logs. It looks like the disconnection reason is Bad_Credential. I'm assuming this is caused by the auth related exception when trying to open async.
Based on the stack trace and the wording of the exception, it seems like the problem is that the SDK is trying to write into some amqp resource but cannot do so because the context is not authenticated. Does this look like a bug in the SDK?
Our E2E framework test code:
The text was updated successfully, but these errors were encountered: