IBM Support

Mustgather: How to investigate the behavior of Resource Synchronization

Troubleshooting


Problem

Resource Synchronization is a background process that propagates changes from Resource Templates to the Base Resources mapped to Environments (and their children), as well as any resources that have property: Include Agents Automatically. At times, you might need to investigate what changes are getting synchronized. This technote explains how to obtain additional information regarding the behavior of Resource Synchronization.

Symptom

You added or renamed resources in a Resource template, but you do not see the changes propagated to the Environment that was created from that Blueprint/Resource Template. Note that if you delete resources from a Resource template, the deletions are never propagated. This is working as expected.

Environment

The background Resource Synchronization process by default runs every 5 minutes, and the
default interval is controlled by this property:

com.urbancode.resource.sync.interval=5
(in minutes).
The property is stored in the file:
<server>\conf\server\installed.properties

Diagnosing The Problem

Append the following trace string in Settings > System > Logging:

log4j.logger.com.urbancode.ds.subsys.resource.domain.ResourceSyncService=TRACE
log4j.logger.com.urbancode.ds.subsys.resource.domain.TemplateSyncher=TRACE
You should then see entries like the following in deployserver.out (this example was generated by UrbanCode Deploy 6.2.5.0):
2019-01-10 10:37:28,785 TRACE ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.ResourceSyncService - Current user is: User: admin
2019-01-10 10:37:28,785 TRACE ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.ResourceSyncService - Processing dynamic group: /Top3/FromMyTem2/Grp1
2019-01-10 10:37:28,795 TRACE ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.ResourceSyncService - Syncing resource /AddingAgent/e2 in environment e2
2019-01-10 10:37:28,835 DEBUG ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.TemplateSyncher - Syncing resource /AddingAgent/e2 with templates [ResourceTemplate#e01f270a-d4f6-43ac-8d1e-a625e0b563bc, ResourceTemplate#483d06d1-1d30-4083-a2f4-289ca2c314b1]
2019-01-10 10:37:28,835 DEBUG ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.TemplateSyncher - Checking template on /ResTem/Agent Prototype
2019-01-10 10:37:28,835 DEBUG ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.TemplateSyncher - /ResTem/Agent Prototype has a template which qualifies for sync with bp1
2019-01-10 10:37:28,845 TRACE ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.TemplateSyncher - Target props: {}
....
2019-01-10 10:37:28,875 DEBUG ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.TemplateSyncher - Syncing resource /Top3/e1/Grp1/IBM277-R90FKAU9 with templates [ResourceTemplate#a5a27839-0ec1-45f0-a006-975e816ef61f, ResourceTemplate#3be8f131-69bd-427f-950b-ae40c1fb7dcd]
2019-01-10 10:37:28,875 DEBUG ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.TemplateSyncher - Checking template on /MyTem2/Grp1/Agent Prototype/grp2
2019-01-10 10:37:28,885 DEBUG ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.TemplateSyncher - /MyTem2/Grp1/Agent Prototype/grp2 has a template which qualifies for sync with bp1
2019-01-10 10:37:28,885 DEBUG ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.TemplateSyncher - Looking for grp2 under /Top3/e1/Grp1/IBM277-R90FKAU9
2019-01-10 10:37:28,885 DEBUG ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.TemplateSyncher - Syncing resource /Top3/e1/Grp1/IBM277-R90FKAU9/grp2 with templates [ResourceTemplate#a5a27839-0ec1-45f0-a006-975e816ef61f, ResourceTemplate#3be8f131-69bd-427f-950b-ae40c1fb7dcd]
2019-01-10 10:37:28,885 DEBUG ResourceSyncService-background-sync com.urbancode.ds.subsys.resource.domain.ResourceSyncService - Full resource sync took 150ms

Resolving The Problem

Wait for a multiple of the com.urbancode.resource.sync.interval and then collect the file:
<server>\var\log\deployserver.out
and send it to UrbanCode Support for investigation, together with a screenshot of the concerned Resource Template and of the relevant branch of the Resource tree or Environment where you expect the changes to be propagated.

Related Information

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Component":"Server","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

UCD

Document Information

Modified date:
10 January 2019

UID

ibm10794297