- Newest
- Most votes
- Most comments
Hi there,
We'll investigate why it failed without the extra flag and loop back here later.
Update:
snap - failed to install
: it was reported before. They are investigating on this issue and will take this over.Region must be specified
: Greengrass will set region env variable. When ran manually without Greengrass, the env variable missed which is expected.
Hi,
Region parameter can be passed through cli or as an environment variable. Systems Manager greengrass component sets the environment variable so ssm-setup-cli -install is all that is required in the lifecycle step.
The issue here seems to be snap failing to install the ssm agent. The setup cli ultimately runs
snap install /path/to/amazon-ssm-agent.snap --classic
which ends up failing on Nvidia Jetson Nano - running Ubuntu 18.04. We have tried reproducing with an Ubuntu 18.04 ec2 instance, but have not been successful.
If the above command succeeds when run manually but fails when setup cli runs it then possibly there is some configuration on the device which prevents the installation under certain conditions. Snap logs might help to root cause.
Relevant content
- asked 2 years ago
- Accepted Answerasked 2 years ago
- asked 10 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 10 months ago
Thanks @Lihao - is there a ticket somewhere where I can keep an eye on the
snap - failed to install
issue resolution?