-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat(uat): implement scenario outline GGMQ-1-T27 #379
Conversation
Unit Tests Coverage Report
Minimum allowed coverage is Generated by 🐒 cobertura-action against 130278a |
Then I retrieve the certificate of broker "default_broker" and store as "BROKER_CERTIFICATE_BEFORE_DISCONNECT" | ||
|
||
When I set device mqtt connectivity to offline | ||
And the greengrass log on the device contains the line "com.aws.greengrass.mqttclient.AwsIotMqtt5Client: Failed to connect to AWS IoT Core" at least 3 times within 2 minutes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you want this 3 times? Why isn't 1 enough?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At first time 1 is enough. Usually Nucleus makes 3 attempts in the short period of time like:
2023-07-25T20:43:30.342Z [ERROR] (Thread-10) com.aws.greengrass.mqttclient.AwsIotMqtt5Client: Failed to connect to AWS IoT Core. {clientId=gg-5e37c73c40370bb47008-ggc-thing, error=socket operation timed out.}
2023-07-25T20:43:34.858Z [ERROR] (Thread-10) com.aws.greengrass.mqttclient.AwsIotMqtt5Client: Failed to connect to AWS IoT Core. {clientId=gg-5e37c73c40370bb47008-ggc-thing, error=socket operation timed out.}
2023-07-25T20:43:37.958Z [ERROR] (Thread-10) com.aws.greengrass.mqttclient.AwsIotMqtt5Client: Failed to connect to AWS IoT Core. {clientId=gg-5e37c73c40370bb47008-ggc-thing, error=socket operation timed out.}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So if you only need 1, why does this step require 3?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assumed Nucleus made series of attempts before falling to disconnected state.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, will change to 1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
onDisconnection() log another message - "Connection interrupted".
Message "Failed to connect to AWS IoT Core" we are waiting for logged from onConnectionFailure() which called 3 times after onDisconnection() .
But "Connection interrupted" is appeared already in log file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, "Connection interrupted" means that the device was disconnected. If you see this, and there is no "Connection resumed" then it is offline.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 224fb32
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At the moment has no steps to check log file miss some string.
Issue #, if available:
Implement GGMQ scenario based on GGAD-1-T27
Description of changes:
Why is this change necessary:
Implement replacement of GGAD-1-T27 scenario outline
How was this change tested:
Scenarios have been run on Linux for 4 clients (later reduced to 1) and Windows (one client) for both MQTT v3 and v5.
Test results:
Linux:
Windows:
Any additional information or context required to review the change:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.