- Newest
- Most votes
- Most comments
Hello,
I could see that, 'mqttpubsub' and 'cloudcomponent' test groups are being failed when running running test suite GGV2Q_2.4.1 on Greengrass 2.7.0 using IDT 4.5.1. On checking the logs, you noticed that the TES component responded with expired AWS credentials.
To begin with can you please confirm if the clock on the device is correct. Also, to further investigate the issue, I would need to take a look at the IDT[1] and Greengrass[2] logs generated pertaining to this specific issue. You can create a technical case using AWS Support console and share us all the above mentioned logs.
References:
[1]. https://docs.aws.amazon.com/greengrass/v2/developerguide/idt-troubleshooting.html#where-to-look
[2]. https://docs.aws.amazon.com/greengrass/v2/developerguide/monitor-logs.html#access-local-logs
Maybe the credentials are expiring before the tests are able to complete? You can try the following things:
- Request a longer expiration period for the temporary credentials. The default is 15 minutes. The max can be up to 12 hours usually. See https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_getsessiontoken for more info.
- Run only one of the failing test cases, as it should run more quickly than running multiple test cases back to back (if that's what you were doing before), to see if the test case is only failing because of the timeout. You can do this by providing a group-id and test-id (test case id) arguments to the run-suite command. See https://docs.aws.amazon.com/greengrass/v2/developerguide/run-tests.html for more info.
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 18 days ago
Is the failure in the cloudcomponent test group caused by similar errors?
yes, the [cloudcomponent/greengrass.log] have the same error.