By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

AWS Greengrass - Erro with public component version

0

Hello,

I currently have an Ubuntu device running AWS Greengrass Core Device with different components installed. When trying to update the version of the public component aws.greengrass.clientdevices.mqtt.Bridge and other components the deploy fails. Reviewing the log file greengrass.log I discover the next error:

Failed to negotiate version with cloud and no local version to fall back to. {componentName=aws.greengrass.Nucleus, versionRequirement={aws.greengrass.LogManager=>=2.1.0 <2.8.0, aws.greengrass.Cli=>=2.5.0 <2.8.0, aws.greengrass.StreamManager=>=2.0.0 <2.6.0, aws.greengrass.clientdevices.IPDetector=>=2.2.0 <2.9.0, aws.greengrass.clientdevices.Auth=>=2.6.0 <2.9.0}}

The surprising thing is that it requires non-existing versions, like for the component aws.greengrass.clientdevices.IPDetector (latest version is 2.1.4) or aws.greengrass.clientdevices.Auth (latest version 2.2.3)

Thank you very much in advance. All the best.

Alberto

Topics
Internet of Things (IoT)
Tags
AWS IoT GreengrassAWS IoT CoreInternet of Things (IoT)
Language
English
albdom
asked 2 years ago332 views
1 Answer
2
Accepted Answer

Hi Alberto,

what this message is saying is that your deployment cannot find a version of the Nucleus component which is compatible with the requirements of the components being deployed. In particular the issue comes from Auth requiring a version >=2.6.0 and StreamManager requiring a version <2.6.0.

To fix, review your deployment and in the configuration step ensure you select the latest version for each one of the components included.

You can also force a specific version of the Nucleus component by including it in the deployment and specifying the version in the deployment.

Cheers,

Massimimliano

AWS
EXPERT
MassimilianoAWS
answered 2 years ago
  • albdom
    2 years ago

    Thank you very much for the quick response, it was indeed solved as you mentioned!

  • JonathanKaye
    2 years ago

    I am also having this problem but Auth's latest version is 2.2.3. I cannot find an Auth version >= 2.6.0 in the available public components list, so I reverted my Nucleus to 2.7.0 and then adjusted other component versions. That seemed to work, but I really don't want to use older Nucleus versions. Where is the mythical Auth >= 2.6.0?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content