Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1727

Upgrade shows error although nothing is wrong

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 2.3.0
    • None
    • backend
    • None

      Problem description:

      • given:
        • I use Optimize 2.2
        • and I want to upgrade to 2.3
      • when:
        • I execute the upgrade script
      • then:
        • I get an error, although nothing is wrong:
          Execute upgrade...
          ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
          
      • expected:
        • the script only logs an error if there went something wrong during the upgrade

      Hint:
      We should think about adding the logging framwork in the parent module as a dependency, so we resolve this issue in every module that will every be created. On the other hand we will remove the transport client and replace it with the http client. Then we might not have this issue anymore anyways, so it would be okay to fix it just in the upgrade module.

        This is the controller panel for Smart Panels app

            [OPT-1727] Upgrade shows error although nothing is wrong

             ✘  ~/Downloads/release/2.2.0  java -jar upgrade/upgrade-optimize-from-2.2.0-to-2.3.0-SNAPSHOT.jar
            
            
            ================================ WARNING! ================================ 
            
            Please be aware that you are about to upgrade the Optimize data 
            schema in Elasticsearch from version 2.2.0 to 2.3.0. 
            There is no warranty that this upgrade might not break the data 
            structure in Elasticsearch. Therefore, it is highly recommended to 
            create a backup of your data in Elasticsearch in case something goes wrong. 
            
            Do you want to proceed? [(y)es/(n)o] 
            
            1. (y)es = I already did a backup and want to proceed. 
            2. (n)o = Thanks for reminding me, I want to do a backup first. 
            
            Your answer (type your answer and hit enter): y
            
            Execute upgrade...
            17:37:02.308 [main] INFO  o.c.o.u.plan.UpgradeExecutionPlan - Starting step 1/16: CreateIndexAliasForExistingIndexStep
            

            Sebastian Bathke added a comment - ✘  ~/Downloads/release/2.2.0  java -jar upgrade/upgrade-optimize-from-2.2.0-to-2.3.0-SNAPSHOT.jar ================================ WARNING! ================================ Please be aware that you are about to upgrade the Optimize data schema in Elasticsearch from version 2.2.0 to 2.3.0. There is no warranty that this upgrade might not break the data structure in Elasticsearch. Therefore, it is highly recommended to create a backup of your data in Elasticsearch in case something goes wrong. Do you want to proceed? [(y)es/(n)o] 1. (y)es = I already did a backup and want to proceed. 2. (n)o = Thanks for reminding me, I want to do a backup first. Your answer (type your answer and hit enter): y Execute upgrade... 17:37:02.308 [main] INFO o.c.o.u.plan.UpgradeExecutionPlan - Starting step 1/16: CreateIndexAliasForExistingIndexStep

              Unassigned Unassigned
              johannes.heinemann Johannes
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: