12 Replies Latest reply on Mar 6, 2015 1:52 PM by Chris Diehl

    Import fails: Found matching asset class by name and version but checksums did not match.

    Johannes Richter

      Hi Community,

       

      We are trying to import a batch job containing several BLPackage deploy jobs (including all dependencies) via BLCLI.

      Source and Target environment are different but on same BSA level. We already did these kind of migrations in the past without any issues.

      But in the meantime the environments were upgraded to the latest BSA release (8.5.01 Build 112).


      The error we see in the appserver.log:

       

      [03 Sep 2014 18:14:00,699] [Client-Connections-Thread-5] [ERROR] [BMC002@test.smt.infra:BLAdmins:10.70.102.36] [Client] Found matching asset class by name and version but checksums did not match. The checksum is calculated based on the entire CO zip file. Make sure the CO is distributed using the identical zip file.

      com.bladelogic.om.infra.mfw.util.BlException: Found matching asset class by name and version but checksums did not match. The checksum is calculated based on the entire CO zip file. Make sure the CO is distributed using the identical zip file.

        at com.bladelogic.om.infra.model.importexport.BlAssetClassImporter.findExistingRootClass(BlAssetClassImporter.java:579)

        at com.bladelogic.om.infra.model.importexport.BlAssetClassImporter.importRootBlAssetClass(BlAssetClassImporter.java:439)

        at com.bladelogic.om.infra.model.importexport.BlAssetClassImporter.findRootAssetClassAndImport(BlAssetClassImporter.java:409)

        at com.bladelogic.om.infra.model.importexport.BlAssetClassImporter.importObject(BlAssetClassImporter.java:106)

        at com.bladelogic.om.infra.model.importexport.BlAssetClassImporter.importObject(BlAssetClassImporter.java:55)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.saveAdditionalObjects(DefaultObjectImporter.java:166)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.importObject(DefaultObjectImporter.java:67)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.importObject(DefaultObjectImporter.java:40)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.saveAdditionalObjects(DefaultObjectImporter.java:166)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.importObject(DefaultObjectImporter.java:149)

        at com.bladelogic.om.infra.model.importexport.DepotObjectImporter.importObject(DepotObjectImporter.java:26)

        at com.bladelogic.om.infra.model.importexport.DepotObjectImporter.importObject(DepotObjectImporter.java:12)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.saveAdditionalObjects(DefaultObjectImporter.java:166)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.importObject(DefaultObjectImporter.java:67)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.importObject(DefaultObjectImporter.java:40)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.saveAdditionalObjects(DefaultObjectImporter.java:166)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.importObject(DefaultObjectImporter.java:149)

        at com.bladelogic.om.infra.model.importexport.JobObjectImporter.importObject(JobObjectImporter.java:56)

        at com.bladelogic.om.infra.model.importexport.JobObjectImporter.importObject(JobObjectImporter.java:24)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.saveAdditionalObjects(DefaultObjectImporter.java:166)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.importObject(DefaultObjectImporter.java:67)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.importObject(DefaultObjectImporter.java:40)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.saveAdditionalObjects(DefaultObjectImporter.java:166)

        at com.bladelogic.om.infra.model.base.dependency.importer.DefaultObjectImporter.importObject(DefaultObjectImporter.java:149)

        at com.bladelogic.om.infra.model.importexport.JobObjectImporter.importObject(JobObjectImporter.java:56)

        at com.bladelogic.om.infra.model.importexport.JobObjectImporter.importObject(JobObjectImporter.java:24)

        at com.bladelogic.om.infra.model.base.dependency.importer.ModelObjectImporter.saveObjectGraphToDatabase(ModelObjectImporter.java:3418)

        at com.bladelogic.om.infra.model.base.dependency.importer.ModelObjectImporter.access$000(ModelObjectImporter.java:103)

        at com.bladelogic.om.infra.model.base.dependency.importer.ModelObjectImporter$1.doDBOperation(ModelObjectImporter.java:263)

        at com.bladelogic.om.infra.app.db.TransactionalOperation.manageTransaction(TransactionalOperation.java:182)

        at com.bladelogic.om.infra.app.db.TransactionalOperation.execute(TransactionalOperation.java:136)

        at com.bladelogic.om.infra.model.base.dependency.importer.ModelObjectImporter.saveImportedObject(ModelObjectImporter.java:274)

        at com.bladelogic.om.infra.message.model.frame.ModelFrame.service(ModelFrame.java:116)

        at com.bladelogic.om.infra.mfw.net.ClientWorkerThread.processRequest(ClientWorkerThread.java:385)

        at com.bladelogic.om.infra.mfw.net.ClientWorkerThread.processClientRequest(ClientWorkerThread.java:282)

        at com.bladelogic.om.infra.mfw.net.ClientWorkerThread.handleClientRequest(ClientWorkerThread.java:182)

        at com.bladelogic.om.infra.mfw.net.ClientWorkerThread.execute(ClientWorkerThread.java:101)

        at com.bladelogic.om.infra.mfw.net.ClientWorkerThread.execute(ClientWorkerThread.java:27)

        at com.bladelogic.om.infra.app.service.thread.BlBlockingThread.run(BlBlockingThread.java:95)

       

       

      Does anybody know how to resolve this issue?


      Thanks,
      Johannes

        • 1. Re: Import fails: Found matching asset class by name and version but checksums did not match.
          Bill Robinson

          can you export w/o the COs ?

           

          it looks like there is some problem w/ the CO zips in the export ?

          • 2. Re: Import fails: Found matching asset class by name and version but checksums did not match.
            Johannes Richter

            We can give it a try. I think it is one of the parameters of the blcli export command.

            Actually, I checked the contents of the export and there are no zip files included...!?

            • 3. Re: Import fails: Found matching asset class by name and version but checksums did not match.
              Johannes Richter

              Hi Bill,


              I checked BLCLI documentation and unfortunately the exportObject command doesn't have a option to exclude COs:

               

              This version of exportObject also lets you specify:

              Whether or not you want to include Component Discovery Jobs.

              Whether or not you want to include Compliance Jobs.

              Whether or not you want to include Software Deploy Jobs.

              Whether or not you want to include depot software objects.

              Whether or not you want to include BLPackages.

              Whether you want to keep BLPackage soft links, or convert them to hard links.

              Whether or not you want to include referenced grammar files.

              Whether or not you want to exclude component templates.

              Whether or not you want to exclude NSH scripts.

              Whether or not you want to exclude depot files.

              Whether or not you want to exclude NSH Script Jobs.

               

               

              Any other idea?

              • 4. Re: Import fails: Found matching asset class by name and version but checksums did not match.
                Johannes Richter

                Support ticket logged: ISS04353665

                 

                Same error pops up, when manually exporting and importing:

                screen_shot_BSA_console.jpg

                • 5. Re: Import fails: Found matching asset class by name and version but checksums did not match.
                  Parag Desai

                  Hi Johannes,

                   

                  I have tried the export/import of a batch job between two different env build 96 (exporting) and build 217 (importing), it has worked for me. These are two different env altogether. As discussed this could be env specific.

                   

                  Bill, can you please advise on this?

                   

                  Thanks,

                  Parag

                  • 6. Re: Import fails: Found matching asset class by name and version but checksums did not match.
                    Johannes Richter

                    Our current idea that this is related to the environments (source and target).

                    As already written we export from our DEV environment and try to import to our TEST environment (which fails).

                    But if we import the package again to the source (DEV) it works without issues.

                    Both environments are on the same level (8.5.01 Build 112).


                    Just to be sure everything was said: The DEV environment was upgraded from 8.5 GA to 8.5 SP1. As we had issues with web services we waited for a hot fix, which then was installed on top of SP1 in DEV. In the other environments (also TEST) we directly installed the HF.

                     

                    DEV: 8.5 GA -> 8.5 SP1 -> 8.5 SP1 HF 112

                    TEST/QA/PROD: 8.5 GA -> 8.5 SP1 HF 112

                     

                    Not sure if that could be related!?

                    • 7. Re: Import fails: Found matching asset class by name and version but checksums did not match.
                      Bill Robinson

                      ?do you have any duplicate COs in the config object dictionary in dev ?  what COs are in the export ?

                      • 8. Re: Import fails: Found matching asset class by name and version but checksums did not match.
                        Johannes Richter

                        Bill,

                        There are no duplicate server objects (root) in DEV. We also compared the versions between DEV and TEST and they are exactly the same.

                         

                        Here is the list:

                         

                        .NET Assemblies1Server Object
                        Active Directory81020262Server Object
                        Active Directory82010000Server Object
                        Active Directory82020000Server Object
                        Active Directory82030000Server Object
                        Active Directory85000000Server Object
                        Active Directory85010067Server Object
                        AIX Package List1Server Object
                        AIX Patch List1Server Object
                        BladeLogic UCS Manager81020262Server Object
                        BladeLogic UCS Manager82010000Server Object
                        BladeLogic UCS Manager82020000Server Object
                        BladeLogic UCS Manager82030000Server Object
                        BladeLogic UCS Manager85000000Server Object
                        BladeLogic UCS Manager85010067Server Object
                        BLPackages81020262Server Object
                        BLPackages82010000Server Object
                        BLPackages82020000Server Object
                        BLPackages82030000Server Object
                        BLPackages85000000Server Object
                        BLPackages85010067Server Object
                        Citrix XenServer82010000Server Object
                        Citrix XenServer82020000Server Object
                        Citrix XenServer82030000Server Object
                        Citrix XenServer85000000Server Object
                        Citrix XenServer85010067Server Object
                        Complus1Server Object
                        Configuration1Server Object
                        Daemons81020262Server Object
                        Daemons82010000Server Object
                        Daemons82020000Server Object
                        Daemons82030000Server Object
                        Daemons85000000Server Object
                        Daemons85010067Server Object
                        Debian Packages1Server Object
                        Event Logs1Server Object
                        Extended Objects1Server Object
                        FileSystem1Server Object
                        Global Zone82010000Server Object
                        Global Zone82020000Server Object
                        Global Zone82030000Server Object
                        Global Zone85000000Server Object
                        Global Zone85010067Server Object
                        Hardware Information81020262Server Object
                        Hardware Information82010000Server Object
                        Hardware Information82020000Server Object
                        Hardware Information82030000Server Object
                        Hardware Information85000000Server Object
                        Hardware Information85010067Server Object
                        HP Bundle List1Server Object
                        HP Patch List1Server Object
                        HP Product List1Server Object
                        IBM Configuration81020262Server Object
                        IBM Configuration82010000Server Object
                        IBM Configuration82010276Server Object
                        IBM Configuration82020311Server Object
                        IBM Configuration82040430Server Object
                        IBM Configuration85000464Server Object
                        IBM Configuration85010058Server Object
                        Metabase1Server Object
                        Microsoft SCVMM81020262Server Object
                        Microsoft VMM82010000Server Object
                        Microsoft VMM82020313Server Object
                        Microsoft VMM85000000Server Object
                        Microsoft VMM85010067Server Object
                        Processes81020262Server Object
                        Processes82010000Server Object
                        Processes82020000Server Object
                        Processes82030000Server Object
                        Processes85000000Server Object
                        Processes85010067Server Object
                        Registry1Server Object
                        RHEL KVM81020262Server Object
                        RHEL KVM82010000Server Object
                        RHEL KVM82020000Server Object
                        RHEL KVM82030000Server Object
                        RHEL KVM85000000Server Object
                        RHEL KVM85010067Server Object
                        RHEV Manager82010000Server Object
                        RHEV Manager82020000Server Object
                        RHEV Manager82030000Server Object
                        RHEV Manager85000000Server Object
                        RHEV Manager85010067Server Object
                        RPM List1Server Object
                        Solaris Package List1Server Object
                        Solaris Patch Cluster List1Server Object
                        Solaris Patch List1Server Object
                        System Info1Server Object
                        Unix Groups81020262Server Object
                        Unix Groups82010000Server Object
                        Unix Groups82020000Server Object
                        Unix Groups82030000Server Object
                        Unix Groups85000000Server Object
                        Unix Groups85010067Server Object
                        Unix Users81020262Server Object
                        Unix Users82010000Server Object
                        Unix Users82020000Server Object
                        Unix Users82030000Server Object
                        Unix Users85000000Server Object
                        Unix Users85010067Server Object
                        VMWare1Server Object
                        VMware vCenter Server81020262Server Object
                        VMware vCenter Server82010000Server Object
                        VMware vCenter Server82010290Server Object
                        VMware vCenter Server82020311Server Object
                        VMware vCenter Server82040437Server Object
                        VMware vCenter Server82040456Server Object
                        VMware vCenter Server82040468Server Object
                        VMware vCenter Server85000000Server Object
                        VMware vCenter Server85010058Server Object
                        VMWareVC1Server Object
                        Windows Application List1Server Object
                        Windows Group List1Server Object
                        Windows Hotfix List1Server Object
                        Windows Service List1Server Object
                        Windows User List1Server Object

                         

                         

                        How can I check wich CO's are included in the export - as far as I know none, but not sure.


                        Johannes

                        • 9. Re: Import fails: Found matching asset class by name and version but checksums did not match.
                          Johannes Richter

                          We just tried to import the DEV export in our QA environment and it fails with same error as in the TEST environment.

                          While we are able to import it in the DEV environment without issues.

                           

                          So it could be related to the different upgrade paths?

                          DEV: 8.5 GA -> 8.5 SP1 -> 8.5 SP1 HF 112

                          TEST/QA/PROD: 8.5 GA -> 8.5 SP1 HF 112

                          • 10. Re: Import fails: Found matching asset class by name and version but checksums did not match.
                            Johannes Richter

                            We did one more test. We exported a similar package from TEST and we successfully imported it in QA.

                             

                            I currently see two possible issues here:

                            a) we have an issue with the different upgrade procedures we followed

                            b) we have some environment or package issues in DEV

                             

                            Summary of our tests:

                             

                            Export                Import               Result

                            -----------------------------------------------------------

                            DEV                    TEST               Fail

                            DEV                    QA                   Fail

                            TEST                  QA                   Success

                            DEV                    DEV                 Success

                            • 11. Re: Import fails: Found matching asset class by name and version but checksums did not match.
                              Johannes Richter

                              We made some further progress with troubleshooting the issue.

                              We minimized the issue to BLPackage, which are using Server Objects (CO's), e.g. UnixUsers, UnixGroups, etc.

                              These packages cause the batch job import to fail.

                              We compared the checksums of the used server objects in the databases (table BL_ASSET_CLASS) of all environments and we see that the DEV environment (were we do the export) has different checksums to the following environments (they all have same checksums).

                               

                              As the checksums of the assets is part of the blexport.xml the import will fail due to mismatching checksums.

                               

                              2014-09-10_10-46-23.png

                               

                              We only have differences for version 85010067, older versions have same checksum over all environments!

                              Can these differences come from the already mentioned upgrade paths?

                               

                              DEV: 8.5 GA -> 8.5 SP1 -> 8.5 SP1 HF 112

                              TEST/QA/PROD: 8.5 GA -> 8.5 SP1 HF 112

                               

                              For testing only, I modified the expected checksums in the blexport.xml to the green ones and import was successful.

                               

                              How can we resolve this issue?


                              Thanks,

                              Johannes

                              • 12. Re: Import fails: Found matching asset class by name and version but checksums did not match.

                                Did anybody ever find more on this subject?  I just built a comp template and all the goodies, and received the same error moving between test and prod..really don't want to re-create it all