Related to this previous post that did not entirely solve the issue:
https://repost.aws/questions/QUVlaGuW0NRX-AXrSUJlvWHQ/can-t-update-nucelus-due-to-dependency
I have some devices that have an old version of the component aws.greengrass.Cli
. That component is preventing me from updating nucleus. There is a deployment on the group for that device, which does not include the CLI component. As advised in the linked post, I tried deploying an empty deployment to the core device, which successfully removed the component from the list of components in the web interface. Unfortunately the component is still present on the device and still prevents me from deploying an update.
I can see it when I log onto the device and run /greengrass/v2/bin/greengrass-cli component list:
Component Name: aws.greengrass.Cli
Version: 2.9.4
State: RUNNING
Configuration: {"AuthorizedPosixGroups":null,"AuthorizedWindowsGroups":null}
I have this issue on many devices, so it would be great if I had a way to delete this component without having to SSH into each one of them, but at this point any way to remove the component be great
Thanks for the quick answer. It turns out the empty deployments that I made to the devices (individually) had failed, which is why the CLI component was still there. Revising the empty deployment did fix the issue