AMS cloud manager build failed after updating node and npm versions | Community
Skip to main content
S
SrikanthPo3
Level 5
September 29, 2023
Solved

AMS cloud manager build failed after updating node and npm versions

  • September 29, 2023
  • 3 replies
  • 4251 views

Hi,

We have updated node and npm versions in our AEM code repository from v8.9.4 & 5.6.0 to v18.18.0 & 10.1.0 along with other front-end plug ins.

After that develop Cloud Manager pipeline failed with below error(attached build log for reference) 15:43:14,013 [main] [INFO] Running 'npm install' in /build_root/build/companyname/aem-ui 15:43:14,394 [Thread-14] [ERROR] /build_root/build/companyname/aem-ui/target/node/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /build_root/build/companyname/aem-ui/target/node/node)

Does this require removal/uninstall of old node/npm and manually install new version for the build to be successful.

https://stackoverflow.com/questions/72921215/getting-glibc-2-28-not-found

 

We are on Adobe Managed Services, using Cloud Manager pipelines for deployment into Dev, Stage and Production environments.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by A_H_M_Imrul

I had to import node certificate onto keystore to resolve PKIX Certificate exception but other than that no other change for local maven build to be successful.


@srikanthpo3 

Though its little uncertain, however it seem the new node version is not supported by the underlying OS. Probably you may need to downgrade the node version to 16 or so.

Here is a reference of a similar scenario: https://help.heroku.com/R7DTSTD0/fix-node-js-error-version-glibc_2-28-not-found

Can you give it a try with a downgraded version?

3 replies

A_H_M_Imrul
Community Advisor
A_H_M_ImrulCommunity Advisor
Community Advisor
September 29, 2023

Hello @srikanthpo3,

Is that upgrade working fine locally? Can you build it successfully locally?

On cloud manager you can't and don't need to remove node explicitly, its a stateless build on CM based on whatever you define in the pom.xml.  

Please share the error snippet for better visibility.

 

   

    S
    SrikanthPo3Author
    Level 5
    September 29, 2023

    Hi @a_h_m_imrul ,

    Local maven build is successful.

    15:43:14,394 [Thread-14] [ERROR] /build_root/build/{{mycompany}}/aem-ui/target/node/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /build_root/build/{{mycompany}}/aem-ui/target/node/node)

      S
      SrikanthPo3Author
      Level 5
      September 29, 2023

      I had to import node certificate onto keystore to resolve PKIX Certificate exception but other than that no other change for local maven build to be successful.

        aanchal-sikka
        Community Advisor
        aanchal-sikkaCommunity Advisor
        Community Advisor
        September 29, 2023

        Hello @srikanthpo3 

         

        By default the front-end pipeline uses Node 14, but 12 and 16 are also available.

        You can use the CM_CUSTOM_VAR_NODE_VERSION environment variable to set the desired version.

         

        Command:

         

        aio cloudmanager:set-pipeline-variables <pipeline id> --variable NODE_VERSION 16

         

         

        https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developing/developing-with-front-end-pipelines.html?lang=en#node-versions

         

        Documentation may/may not be up-to-date. Please try with 18 version as well

        Aanchal Sikka
          S
          SrikanthPo3Author
          Level 5
          October 4, 2023

          Hi @aanchal-sikka 

          Where do we run the above command?

          In Cloud Manager -> Edit Pipeline, I am unable to find an option to provide custom node version.

            aanchal-sikka
            Community Advisor
            aanchal-sikkaCommunity Advisor
            Community Advisor
            October 4, 2023

            Hello @srikanthpo3 

             

            Please refer to https://github.com/adobe/aio-cli-plugin-cloudmanager

            It will help you set up the command line interface. You would also need to set up credentials locally.

            The document has the details

             

             

            Aanchal Sikka
              kautuk_sahni
              Community Manager
              kautuk_sahniCommunity Manager
              Community Manager
              October 4, 2023

              @srikanthpo3  Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

              Kautuk Sahni
              S
              SrikanthPo3Author
              Level 5
              October 4, 2023

              Hi @kautuk_sahni 

              Did not get a response for Adobe support case yet, as a back up we are planning to downgrade node version to 16 and check but we were waiting for response from Adobe support.

              I will update this group once the issue is resolved.

                S
                SrikanthPo3Author
                Level 5
                October 5, 2023

                We downgraded node version to 16.x to resolve this issue. Could not work on @aanchal-sikka 's suggestion because of delivery time constraints.

                Thanks everyone for the suggestions.

                  Terms & ConditionsAccessibility statement

                  Loading footer...