TS Area deployment not working

Environment is TS 6.7.1, OD 6.1.1 on Solaris 10

I'm trying to use a TS Area deployment to deploy the differences between the current and previous EDITIONS of a branch.

The deployment runs but it deploys all files of the current EDITION every time.

Log file shows that the deployment is comparing the correct EDITIONS, however it fails to restrict the deployment to only the changed files.

I suspect I'm overlooking something but have run out of ideas.

Any help would be appreciated.

David T.

Find more posts tagged with

Comments

ISCBorisB

Attach your Deployment configuration

cpm_dst

To simplify troubleshooting I've narrowed the deployment down to a single directory containing three files.

In the previous EDITION they are:

ex000099.xml 2012-08-01 10:57 AM
ex000100.xml 2012-08-01 11:49 AM
ex000101.xml 2012-08-01 12:22 PM

and in the current EDITION they are:

ex000099.xml 2013-02-14 12:41 PM
ex000100.xml 2012-08-01 11:49 AM
ex000101.xml 2012-08-01 12:22 PM

I expected that only ex000099.xml would be deployed by the attached deployment config file.

Thanks,

David T.

ISCBorisB

To simplify troubleshooting I've narrowed the deployment down to a single directory containing three files.

In the previous EDITION they are:

ex000099.xml 2012-08-01 10:57 AM
ex000100.xml 2012-08-01 11:49 AM
ex000101.xml 2012-08-01 12:22 PM

and in the current EDITION they are:

ex000099.xml 2013-02-14 12:41 PM
ex000100.xml 2012-08-01 11:49 AM
ex000101.xml 2012-08-01 12:22 PM

I expected that only ex000099.xml would be deployed by the attached deployment config file.

Thanks,

David T.

With the casual glance there seems to be no problem in your configuration.
If I were you i would've checked two things

1. You have verbose logging. Get to the sender OD Log and check LIB "Sending" Entries. It shows
transported Files one by one, indicating action's reason for each. What reason has been entered
for un-modified Entries?

2. Are you sure that File's Extended Attributes (not just MD) have not changed? if that's the case,
the file is considered modified, even though timestamp of the file itself is not changed and record EA
is switched off.

Chart1 (1).rptdesign

nipper

Try using ignoremode="yes"

It is in the deploy manual

ISCBorisB

Try using ignoremode="yes"

It is in the deploy manual

Ah yes, thank you! I forgot about this stuff completely.

If submit.cfg does not enforce it (IMO it should, especially on Unix),
ignore[Modes|User|Group] Comparison rules may be in order.

cpm_dst

ISCBorisB:

Partial log below, all files say [ src-is-newer]:

LIB: (2) 2013-03-26 11:25:54 [Tue Mar 26 11:25:54 2013] Comparing path[/iwmnt/****/main/lodes/Experimental/ABC/EDITION/ABC_2010_p2/appendix/ex/000] with prev path[/iwmnt/****/main/lodes/Experimental/ABC/EDITION/ABC_2010_p1/appendix/ex/000]
LIB: (3) 2013-03-26 11:25:54 Walking TeamSite directory[.]
LIB: (4) 2013-03-26 11:25:54 Teamsite 6.7.1 based deployment
LIB: (3) 2013-03-26 11:25:54 Path(./ex000099.xml) included.
LIB: (3) 2013-03-26 11:25:54 Path(./ex000100.xml) included.
LIB: (3) 2013-03-26 11:25:54 Path(./ex000101.xml) included.
LIB: (2) 2013-03-26 11:25:54 Comparing done
ENG: 2013-03-26 11:25:54 EDT GMT-04:00 Thread-366 After COMPARE, res=0
ENG: 2013-03-26 11:25:54 EDT GMT-04:00 Thread-366 PRECOMMIT
LIB: 2013-03-26 11:25:54 [Tue Mar 26 11:25:54 2013] DEPLOYING - TeamSite difference to [/iwmnt/****/main/lodes/Experimental/_DEF_Library/WORKAREA/library]
LIB: (3) 2013-03-26 11:25:54 Opening directives file[/var/tmp/iwdirSCAlRaWiz]
LIB: 2013-03-26 11:25:54 Sending [./ex000099.xml] [ src-is-newer]
LIB: 2013-03-26 11:25:54 Sending [./ex000100.xml] [ src-is-newer]
LIB: 2013-03-26 11:25:54 Sending [./ex000101.xml] [ src-is-newer]
ENG: 2013-03-26 11:25:54 EDT GMT-04:00 Thread-366 After PRECOMMIT, res=0

I've checked both sets of files with iwextattr, it doesn't show any EAs on the files. Is there any other way to check for EAs?

nipper:

I have tried the deployment with ignoremode="yes", unfortunately it didn't change the result.

Thanks to you both for taking time to respond.

David T.

ISCBorisB

nipper:

I have tried the deployment with ignoremode="yes", unfortunately it didn't change the result

It's ignoreModes, not ignoreMode. Also, try to add ignoreUser and ignoreGroup as well.
Make sure you capitalize as documented (ignoreModes, not ignoremodes, etc)

Bowker

Also verify there are no temporary files left behind in the folder on the receiver from a failed deployment.

Screenshot.png