After ACM deployment project packages are staying in "install" state | Community
Skip to main content
R
raghud1980
Level 2
June 19, 2023
Solved

After ACM deployment project packages are staying in "install" state

  • June 19, 2023
  • 5 replies
  • 1517 views

Hi,

 

When ACM is deploying code in environment packages are changing into "install" state. Another observation is, the core components version is changing from 2.11.0 to any other available lower version like 2.7.0/2.5.0/2.3.2 which is weird. The pom.xml is setup with 2.11.0 version for both core.wcm.components.content.zip and core.wcm.components.config.zip packages

 

Service Pack installed : aem-service-pkg-6.5.16-NPR-40173-B02.zip

 

Can someone share any idea how this problem can be addressed. 

 

Thanks,

Raghu

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 Tanika02

Hello @raghud1980 

 

  1. Verify the package versions: Double-check that the correct versions of the packages (core.wcm.components.content.zip and core.wcm.components.config.zip) are included in your codebase. Ensure that the pom.xml file accurately reflects the desired version (2.11.0 in your case).

  2. Check package installation order: Confirm that the installation order of packages is correct. Sometimes, the installation of dependent packages may affect the state of other packages. Ensure that any dependencies are installed before the packages you are experiencing issues with.

  3. Review ACM pipeline configurations: Check the configurations of your ACM pipeline. Make sure the pipeline is set up to use the correct package versions and configurations. Verify that the pipeline is not overriding or downgrading the packages during the deployment process.

  4. Investigate conflicting packages: Determine if there are any other packages or configurations in your environment that might conflict with the desired package versions. Check for any other packages or code changes that could be modifying the state or versions of the core components.

5 replies

Nishant-Singh
Adobe Employee
Nishant-SinghAdobe Employee
Adobe Employee
June 19, 2023

Hi @raghud1980 

 

There must be some unresolved dependencies of components or services for bundles. use /system/console and click on the install state bundles to check the dependences.

For core components check if the same version is used in all module while embedding the core packages.

    aanchal-sikka
    Community Advisor
    aanchal-sikkaCommunity Advisor
    Community Advisor
    June 19, 2023

    Hello @raghud1980 

     

    You have mentioned that you packages are dependent on 2.11.0 core.wcm.components. While the system has lower versions available.

    The dependency on the higher version is not met, which might be causing the packages to stay in Install state.

     

    Try installing manually, it might even tell you the issue/error, that's resulting in install status.

    Aanchal Sikka
      ManviSharma
      Adobe Employee
      ManviSharmaAdobe Employee
      Adobe Employee
      June 19, 2023

      Hi,

       

      To address the issue of environment packages changing to the "install" state and the unexpected change in core components version during deployment in AEM, you can try the following steps:

      1. Verify the version of the core component packages (core.wcm.components.content.zip and core.wcm.components.config.zip) included in your deployment package. Make sure they are the correct versions (2.11.0) that you specified in the pom.xml file.
      2. Check if there are any conflicting or outdated packages present in the AEM instance. Remove any conflicting packages and ensure that the desired versions of the core components are available.
      3. Clear the AEM instance's bundle cache by stopping the instance, deleting the "crx-quickstart/launchpad/felix/bundle" folder, and then starting the instance again.
        Tanika02
        Tanika02Accepted solution
        Level 7
        June 19, 2023

        Hello @raghud1980 

         

        1. Verify the package versions: Double-check that the correct versions of the packages (core.wcm.components.content.zip and core.wcm.components.config.zip) are included in your codebase. Ensure that the pom.xml file accurately reflects the desired version (2.11.0 in your case).

        2. Check package installation order: Confirm that the installation order of packages is correct. Sometimes, the installation of dependent packages may affect the state of other packages. Ensure that any dependencies are installed before the packages you are experiencing issues with.

        3. Review ACM pipeline configurations: Check the configurations of your ACM pipeline. Make sure the pipeline is set up to use the correct package versions and configurations. Verify that the pipeline is not overriding or downgrading the packages during the deployment process.

        4. Investigate conflicting packages: Determine if there are any other packages or configurations in your environment that might conflict with the desired package versions. Check for any other packages or code changes that could be modifying the state or versions of the core components.

          milind_bachani
          Adobe Employee
          milind_bachaniAdobe Employee
          Adobe Employee
          June 19, 2023

          Hi @raghud1980 ,

           

          I faced similar issue with SP15 for one of the clients, I was able to start by 

          • Starting the instance using java -jar command in terminal of server
          • Stopped the instance and restarted using the start script.

          I later on found that there were some differences in the start script that was in use vs the ootb latest start script.

           

          I would recommend to give a shot to start the instance using java -jar <jarname> -r <runmodes>

           

          Let me know if this helps, thanks!

            milind_bachani
            Adobe Employee
            milind_bachaniAdobe Employee
            Adobe Employee
            June 19, 2023

            Also, can you share relevant error logs for better understanding and investigation?

              Terms & ConditionsAccessibility statement

              Loading footer...