Are you trying to deploy a /a directory in the package? does the user you are mapped to have permissions on / ?
Yes the origin package was trying to create a /a directory, however since then we've tried serveral other names e.g. /test /play123 etc.
The user definitely has permissions, if we "untick" the simuate option in phases on the job the job runs perfectly and the directory gets created.
I have this problem too. Has anyone figured out why?
What is bizzare, the problem occurs on one package but not another.
Looking at the log info for the Simulate, it has found the directory /a already -
05/11/11 09:12:19.372 DEBUG bldeploy - [/a] Found directory: /a
and the error then states that it cannot create a file called /a which would suggest that it wants to create a file not a folder - (might not be that simple !)
I presume that your one step was "mkdir /a" or "mkdir /export/home/a" ?
A BLpackage does not need you to create the dir before you deploy payload to that dir, it just creates the path specified.
However there must have been something going on with the package itself. I created a second package with the exact same payload and contents and it deployed fine. Damn gremlins!
1 of 1 people found this helpful
In 7.6 there's a known "feature" that prevents any user from using BladeLogic to create a new directory in /.
Luckily there's a simple work around, just use an external command in your package to create it using "mkdir -p /a or mkdir -p /export/home/a".
Apparently this has been fixed in 8.