Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-7511

Upgrade an instance with a corrupted templace config prints too much information

    Details

    • Type: Bug
    • Status: Dev backlog
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 7.1.0
    • Fix Version/s: None
    • Component/s: upgrade
    • Labels:
      None

      Description

      Since rev cccf111801ab82389211dd4214cc48c9861df337

      In our FTs, we install an old version of OpenDJ and modifies 02-config.ldif with invalid content.
      We upgrade the instance.
      Before the change for OPENDJ-6710

      ...
      Archiving concatenated schema.   0%       Archiving concatenated schema.......................................   FAIL
        Archiving concatenated schema.......................................   FAIL
       * See
      '/home/jenkins/workspace/OpenDJ-7.1.x/tests_daily/Configs/results/20200924-080110/upgrade_group/TemplateCorruption/DJ_CORRUPT7/opendj/logs/upgrade.log'
       for a detailed log of this operation
      
      -- stderr --
      
       ** An error occurred when trying to upgrade the config/upgrade folder: Error
       parsing existing schema file 02-config.ldif - Unable to parse LDIF entry
       starting at line 1 because the line "invalid_content" does not include an
       attribute name
      
      

      After:

      Archiving concatenated schema.   0%       Archiving concatenated schema.......................................   FAIL
        Archiving concatenated schema.......................................   FAIL
       * See
      '/home/jenkins/workspace/OpenDJ-7.1.x/tests_full_linux/results/20200927-062958/upgrade_group/TemplateCorruption/DJ_CORRUPT7/opendj/logs/upgrade.log'
       for a detailed log of this operation
      
      -- stderr --
      
       ** An error occurred when trying to upgrade the config/upgrade folder:
       Exception: Error parsing existing schema file 02-config.ldif - Unable to
       parse LDIF entry starting at line 1 because the line "invalid_content" does
       not include an attribute name at UpgradeUtils.java:432 UpgradeTasks.java:969
       ProgressMonitor.java:81 ProgressMonitor.java:71 UpgradeTasks.java:967
       Upgrade.java:1051 UpgradeCli.java:272 Utils.java:796 Utils.java:773
       UpgradeCli.java:131 / (1) caused by DecodeException: Unable to parse LDIF
       entry starting at line 1 because the line "invalid_content" does not include
       an attribute name at DecodeException.java:54 RejectedLdifListener.java:36
       AbstractLdifReader.java:192 LdifEntryReader.java:350 LdifEntryReader.java:120
       UpgradeUtils.java:411 UpgradeTasks.java:969 ProgressMonitor.java:81
       ProgressMonitor.java:71 UpgradeTasks.java:967 Upgrade.java:1051
       UpgradeCli.java:272 Utils.java:796 Utils.java:773 UpgradeCli.java:131 / (2)
       caused by DecodeException: Unable to parse LDIF entry starting at line 1
       because the line "invalid_content" does not include an attribute name at
       DecodeException.java:40 AbstractLdifReader.java:511 LdifEntryReader.java:304
       LdifEntryReader.java:120 UpgradeUtils.java:411 UpgradeTasks.java:969
       ProgressMonitor.java:81 ProgressMonitor.java:71 UpgradeTasks.java:967
       Upgrade.java:1051 UpgradeCli.java:272 Utils.java:796 Utils.java:773
       UpgradeCli.java:131
      

      To reproduce:

      ./run-pybot.py -s upgrade_group -t Upgrade_Template_02config_Schema_File_With_Invalid_Content opendj
      

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              cforel carole forel
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: