1 Answer
- Newest
- Most votes
- Most comments
1
You can check in the /greengrass/v2/logs/greengrass.log
which is the exact component that is creating the conflict. Check also that there is only 1 deployment targeting the core device by looking under the Deployments tab in the Core devices screen. If there are more than 1 deployment, check that the component's versions in the different deployments are not conflicting.
Relevant content
- Accepted Answerasked 10 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
I think I am experiencing a similar issue. In the greengrass log I have this message:
Component com.company.component version constraints: thing/ThingID requires =1.0.65, thinggroup/GROUP_CONTAINING_ThingID requires =1.0.66
I previously deployed com.company.component to core device ThingID (v1.0.65). I then wanted to add that component to a group and deploy it there (v1.0.66), but I get this version conflict. I have tried cancelling the deployment to the core device and deleting all revisions of that deployment but I always get the above message. Do you know what might be going wrong?
Update on the above: I was able to get it working by changing the first deployment to have a single basic component. This removed all of the other components that were on the device (and their dependencies) so I was able to do the group deployment. Would still like to know why it's not possible to override one deployment with another though