4 Replies Latest reply on Apr 17, 2017 7:22 AM by rstoker13

    Updates to catalog item not being pulled by SNOW plugin

    rstoker13 Enthusiast
    VMware Employees

      When attempting to CRUD a property definition in an existing published catalog item, the changes are not being synced by the SNOW plugin. Even when I force the execution of the scheduled imports, the updates are not carried through(last executed at 1:05 PM 4/13/17). I am seeing no indication of a problem in the logs. It just doesn't appear to recognize a change in the catalog item.

       

      I can force an update by removing the 'Service' in vRA and recreating it with the necessary catalog items included. However, this is not an acceptable solution. I have included a few screencaps for reference.

       

      vra1.PNGvra2.PNGvra3.PNGsnow1.PNGsnow2.PNG

        • 1. Re: Updates to catalog item not being pulled by SNOW plugin
          kbhushan05 Enthusiast

          By default, scheduled Import job runs after 12 hrs. interval in production environment. If blueprint's last modified time is greater than schedule import job's last run time then only job will update catalog item. Scheduled import run interval is configurable property and can be changed as per requirement.

           

          Manual execution will not work unless property 'CatalogImportLastRunTime' value is cleared from the system. For forceful execution, please clear  value of 'CatalogImportLastRunTime' and re-run the scheduled import job.

           

          I suggest delete only modified catalog item or blueprint from Catalog, clear value of 'CatalogImportLastRunTime' property (highlighted in yellow) from Integration-vRealize Automation and re-run the scheduled import 'vRealize-Automation-ImportCatalogItems'.

           

          • 2. Re: Updates to catalog item not being pulled by SNOW plugin
            rstoker13 Enthusiast
            VMware Employees

            Thank you for the suggestion. This allowed me to properly run a forced execution of the scheduled imports. After doing so, it appears to properly pull in the changes made to the catalog item. I'm a bit frustrated that manual intervention has been required. One would assume that the scheduled runs would find changes and update the SNOW resources.

             

            I also noticed this issue with updating CMDB entries from the vRA machine details. Following your steps above allowed the CIs to obtain the correct data. Again, not thrilled that I had to perform this process to pull information that is supposed to be gathered by the scheduled imports.

            • 3. Re: Updates to catalog item not being pulled by SNOW plugin
              kbhushan05 Enthusiast

              This process auto pull all changes but only on production service now instances.  Scheduled Import job will not auto run on dev instaces. Hence we need to follow manual steps.

              • 4. Re: Updates to catalog item not being pulled by SNOW plugin
                rstoker13 Enthusiast
                VMware Employees

                Gotcha. I appreciate the prompt response!