N1SM add osprofile script bad behavior
We created an osprofile using N1SM and attempted to create
a script to handle configuaing and turning onthe eth1 port.
The "post" script was defined on the N1SM server with n1sh similar to
add osprofile galaxy4100 script /var/tmp/configure_eth1.sh type post
The curious behavior was first noticed when deploying the galaxy4100
profile to a target host. We noticved that the eth1 was not configured.
In fact we found it was not executed.
The BIG curiosity was the N1SM server no longer had a file
/var/tmp/configure_eth1.sh or that file anywhere. I then found
that if I put a copy of configure_eth1.sh back in /var/tmp and
did the loados deploy again. It worked OK and the /var/tmp
file was not deleted.
Given the fact that after the add ... .. scriptcommand is exectued in n1sh
the /var/tmp file is removed AND the deployment NEVER complains
that it is not there nor does it stop the deployment. We see this
as a serious bug that took us many days to notice what was happening
and deserves attention to be corrected.
NOTE: Putting the file in other places than /var/tmp will preserve the file
after the add osprofile xxxxx script /someotherpath/YourScript type post
