Truesight Server Automation (TSSA): Catalog Update Job error: Error while add/update patch in depot: hotfix <catalog item>, A depot object of the same type with the name <catalog item>, already exists in this group - INCLUDES VIDEO

Version 9
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BladeLogic Server Automation Suite


    APPLIES TO:

    BMC BladeLogic Server Automation Suite



    PROBLEM:

     

    While running a Truesight Server Automation (TSSA/BSA) Catalog Update Job you see an error like
     

      
    Error while add/update patch in depot: hotfix <catalog item>
      
    and/or  
    A depot object of the same type with the name < catalog item >, already exists in this group.
       



     

     


    CAUSE:

    Possible RBAC issue due to running the Patch Catalog Job as different roles.


    SOLUTION:

     

    Legacy ID:KA297543

      
      This error can happen when a Patch Catalog is created by RoleA and a Catalog Update Job is run as RoleA.  Later, RoleB is granted permissions to run the CUJ but not granted permissions to see the objects that already exist in the catalog.  When RoleB runs the CUJ, the CUJ tries to add objects that already exist into the catalog/depot.  This can happen for any catalog type. 
      
        
      
    To resolve the issue:
       
      First check if there are any duplicate versions of the noted patches in the catalog by checking as a role like BLAdmins that has read access to all objects.  If there are duplicates and you cannot delete them contact BMC Support for assistance.  
      

    If there are no duplicates there are a couple ways to resolve this:
      
     
    Only run the CUJ as RoleA and discontinue using RoleB for accessing the catalog.  
     
    If both roles need access to run the CUJ and/or both roles need access to the objects in the catalog (more likely the case) then you can    create an ACL Policy that grants RoleA and RoleB    the required access to the objects in the catalog and update ACL Policy setting in the Patch Catalog.  This ACL Policy will be applied to all Depot Objects in the catalog when the CUJ runs.  Run the CUJ as RoleA.  
     
      Note - If the warnings are ignored and analysis job is executed then the Analysis job may see some strange behaviour like the job is successful but there are no targets in the job and All the targets are in "Not Started Targets". Please follow the steps above and make sure that role running the analysis has proper privileges on the target. 
     
    See the following video for further assistance in troubleshooting this issue:  
     
     
     

     


    Article Number:

    000247619


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles