nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Capture deploy Failure

brent1

TeamSite 5.0.1 on Windows 2000

I have an external task that I am running to deploy files to production. The problem is that I cannot capture a failed deployment. The script calls back a success regardless. Has anyone had any success with this?
My complete ipl follow:
******************************
use TeamSite::Config;
($iwhome = TeamSite::Config::iwgethome()) =~ tr|\\|/|;

use TeamSite::WFtask;
use TeamSite::WFworkflow;
my($jobid, $taskid, $area) = (@ARGV[0..2]);
my($task) = TeamSite::WFtask->new($taskid);

$qaDeployment = `$iwhome/opendeploy/OpenDeployNG/bin/iwodstart auto_prod`;

if ($qaDeployment == 0)
{
$task->CallBack(1, 'The automated deployment to Production was successful');
}
else
{
$task->CallBack(0, 'The automated deployment to Production failed');
}

exit;
******************************
Thanks

Brent
Beckman Coulter Inc.

Find more posts tagged with

Comments

Migrateduser

You know, one would think when the manual says about a CLT:

The iwodstart command returns the following codes regarding the status of the deployment:

0 - Successful
1 - Starting of the deployment failed
2 - Deployment ran and returned a failed status

that you could count on the fact that when you execute this CLT, it would return a value of 0, 1, or 2. Well bad assumption. When I run iwodstart, it returns this mess:

Locating OpenDeploy service.
OpenDeploy server host: localhost, RMI registry port: 9173
Got OpenDeploy service.
>>>>>-- Start deployment ZERO_deploy_2129.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
>>>>>-- Deployment ZERO_deploy_2129 finished:
ID: m60 Start time: Thu Aug 01 14:15:55 PDT 2002
Status: Completed

which really doesn't help me much at all. And when it fails, it's not much more of a help. It is not clear what you'd have to look at to get the return code promised in the documentation. I definitely like the old OD better - you get all the deployment details, which could be easily parsed for errors and you could clearly see when things worked and when things didn't. This seems to be a giant step backward.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

In all my ranting, I forgot to really touch on your question. Based on what iwodstart actually returns (see my previous post), you will never be able to use ($return_code == 0) as your check since it doesn't return a single digit like the docs say it should. Looks like you can parse the results for the line that starts with "Status" and if it passes it will contain the word "Completed", if it fails it will contain the word "Failed".

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

eiglesia

Hope this would help

my $deploy_cmd = "$odbin/iwodstart wft_filelist -k area=$area -k filelist=$filelist";
$deploy_cmd =~ s|/|\\|g;

print LOG "deploy_cmd ($deploy_cmd)\n";
my $resultsfile= "$iwhome/tmp/results.$wfid";
my $results = `$deploy_cmd > $resultsfile`;

open (RESULTS, "<$resultsfile");
while (<RESULTS>)
{
$results .= $_;
}
close RESULTS;
$results =~ s|\n||;
print LOG "results ($results)\n";

#####
# Parse Results for status
#####
#Status: Completed is successful
my $callback;
my $comment;
if ($results =~ m|Status: Completed|)
{
$callback = 0;
$comment = "OpenDeploy SUCCESS. (see log $logfile)";
}
elsif ($results =~ m|Status: Failed|)
{
$callback = 1;
$comment = "OpenDeploy FAILED. (see log $logfile)";
}
else
{
$callback = 1;
$comment = "OpenDeploy Unknown Failure. (see log $logfile)";
}
print LOG "callback ($callback) : commment ($comment)\n";

#####
# Callback to the workflow and End
#####
$task->CallBack($callback, "$comment");
close LOG;

Regards,

Eduardo

brent1

Thank you! That technique worked.
Any idea why you have to redirect the output to a file and then read it back in to get the output from the command?

Brent
Beckman Coulter Inc.

Migrateduser

You don't need to redirect the output to a file. You can parse the output inline if you use backtics to execute the command.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

brent1

Nope. Works from the command line, does not work within the workflow.

Example:
...
my $foo = `$cmd`;
...
If I run the .ipl script from the command line on the TeamSite server I can get the output from the command. $foo = the output from the command.
When I call the same .ipl as an externaltask from a workflow $foo is empty after this line.
Strange but true.
FWIW, $? = 0 in either case.

Brent
Beckman Coulter Inc.

output.afp

Migrateduser

I'm not really sure what you're saying, but what I meant was that if you execute the iwodstart CLT using backtics within your externaltask script, and capture the output with a perl variable:

my $cmd = "$ODHOME/bin/iwodstart \"$OdName\" -k filelst=\"$filelist_name\"";

my $result = `$cmd`;

then the variable $result will contain the output string returned by the iwodstart command. You still have to do the work to parse this string to determine if the deployment passed or failed, but it still works. I've used this in an externaltask and it definitely works.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

output.afp.zip

brent1

Right, we're talking about the same thing, except when I run the code in your example $result is empty and therefore does not let me test for success.
The screwy part is that if I run the same script from the command line for debugging purposes, $result would contain the output string.

Brent
Beckman Coulter Inc.

Migrateduser

That just doesn't make any sense. Cut and paste your code here.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

brent1

I agree, it doesn't make sense.

Thus, the question.

**************************
use TeamSite::Config;
($iwhome = TeamSite::Config::iwgethome()) =~ tr|\\|/|;

use TeamSite::WFtask;
use TeamSite::WFworkflow;
my($jobid, $taskid, $area) = (@ARGV[0..2]);
my($task) = TeamSite::WFtask->new($taskid);

$qaDeployment = `$iwhome/opendeploy/OpenDeployNG/bin/iwodstart auto_prod`;

if ($qaDeployment !~ m|fail|i)
{
$task->CallBack(1, 'The automated deployment to Production was successful');
}
else
{
$task->CallBack(0, 'The automated deployment to Production failed');
}

exit;
**************************

This code always returns success, even if the OpenDeploy service is stopped on the receiving server.

Brent
Beckman Coulter Inc.

Migrateduser

When you run this via your workflow, does the deployment actually occur or not? If the deployment doesn't even execute, try this. After your "use" statements, enter the following command:

umask(022);

I know this is a longshot, but I have had certain CLTs work on the command line and not work in a workflow script. A UNIX guru got deep into our system and came up with this solution. It's worth a try. However, if the deployment is executing and you're just not getting the response in your variable, I'm stumped on that one - it works fine for me.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

brent1

The deployment does actually occur, I just don't get the return string in the variable.
The umask won't help as it is a Windows box. I do suspect that it is a permissions issue though.
Thanks for your time Dave. It is a stumper.
Are there any Interwoven engineers lurking out there with ideas?

Brent
Beckman Coulter Inc.

james1

Brent

There is a bug against OpenDeploy 5.5.1:

"Under error conditions, Windows OD CLT's set ErrorLevel to non-zero values, but they should also call "exit" with non-zero values."

I believe that you may be running into this bug, since you are always seeing a return value of 0.

The bug seems to be fixed in OD 5.5.1 SP2, for Windows 2000 only, not Windows NT. In the meantime, the bug report has this workaround:

"If an installation of iw-perl is available, users can use the unsupported ODHOME/solutions/perl/iwodstart.ipl script, which does exit non-zero under error conditions."

I'm not sure if the kinds of errors that your deployment is encountering are severe enough for OD to exit non-zero...?

Good luck!
-- James

Adam Stoller

The iwodstart.ipl script *also* suffered from a slight bug which I *think* will be fixed in the upcomming OpenDeploy 5.5.1 SP2 (not sure).

The manifestation of this particular bug is that while a failed deployment will exit with a non-zero status - the actual value of that status [at the shell return level] will *not* coincide with the values expected (exit codes 1 and 2).

The fix for this specific issue - just in case you need it (there will be a few other clean-ups in the eventual release of this fix) is around line 117 of the script.

Existing code:
----------------------
my($status) = $?;
print "STATUS: $status\n";
die "OpenDeploy Failed" if ($status != 0);
---------------------

Revised code:
---------------------
my($status) = $?;
print "STATUS: $status\n";
if ($status != 0){
warn "OpenDeploy Failed";
exit($status);
}
------------------

This Perl version of the iwodstart script is only intended to be used on Windows - because there were problems with the exit status not being properly propogated from the iwodstart.bat script when used within a Perl script.

The Unix iwodstart shell script did not suffer from this problem.

--fish
(Interwoven, Curriculum Development)

Adam Stoller

A couple of things.

[1] return status of iwodstart.bat
-----------------------------------
Tthere were problems found with trying to get the return code from the iwodstart.bat script when called from a Perl script on Windows - to this end, there is a Perl version of the command in IWODHOME/solutions/perl/ called iwodstart.ipl

This Perl script exits with a status value of zero on success and a non-zero exit status on failure.

I am pretty sure that this script went out in 5.0.1 or a SP of 5.0.1 - but if you don't have it - contact Interwoven Support to request a copy.
------------------------------------
[2] getting the return status of a CLT

$result = `$command`;

will return the *output* of the command not the status return value of the command. Instead you could either do:

$result = system("$command");

or

$output = `$command`;
$result = $?;

In either of the above cases - you can now check the value of $result to see if it is 0 (zero) or not.
---------------------------------

--fish
(Interwoven, Curriculum Development)