Re: [xcat-user] Prescripts running twice

Thu, 26 May 2016 03:09:52 -0700

Could you add a debug code like 'echo "XXXXXXXX"' in your prescripts and run the 'nodeset' again. Then try to search keyword 'XXXXXXXX' from all the files in the following paths:
 
MN:/install/autoinst
CN:/xcatpost
 
BTW, could you see the corresponding message when running the 'updatenode'?

Thanks
Best Regards
----------------------------------------------------------------------
Wang Xiaopeng (王晓朋)
IBM China System Technology Laboratory
Tel: 86-10-82453455
Email: w...@cn.ibm.com
Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193
 
 
----- Original message -----
From: "Russell Auld" <russa...@comcast.net>
To: "'xCAT Users Mailing list'" <xcat-user@lists.sourceforge.net>
Cc:
Subject: Re: [xcat-user] Prescripts running twice
Date: Mon, May 23, 2016 8:41 PM
 

I changed the prescripts table so that the prescripts are set as “prescripts.begin” but they still were run twice.

I added additional logging commands to the prescripts so that they log to /var/log/messages on the master node.

I verified that the prescript script files are not in the /xcatpost directory.

I then reimaged a machine and watched the logs closely.

 

The second running of the prescripts is occurring when the Anaconda process terminates.

When the blue screen of the text-mode installer goes away, there are various messages that get printed on the screen. Messages such as “cleaning up”, “terminating anaconda”, etc.

 

If you look in the anaconda.ks file that is left behind on the nodes, there are some final steps that involve communication back to the xCAT master. It looks like these are “updatenode” commands.

 

Is it possible that one of these commands are causing the prescripts to execute again?

Remember that I am setting the machines like this:

“nodeset <node> osimage=<osimage>”

 

There does not seem to be much detail regarding what constitutes the “beginning” and “end” of a command such as “nodeset osimage”.

 

How can I debug this further?

 

 

From: Russell Auld [mailto:russa...@comcast.net]
Sent: Thursday, May 19, 2016 11:09 PM
To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
Subject: Re: [xcat-user] Prescripts running twice

 

No, the script only exists in the prescripts directory.

On May 19, 2016 10:42 PM, Xiao Peng Wang <w...@cn.ibm.com> wrote:

We don't see the prescripts will be run inside the anaconda. But the postscript does be run in the anaconda. Did you put the same script in the postscripts attribute for the node?


Thanks
Best Regards
----------------------------------------------------------------------
Wang Xiaopeng (王晓朋)
IBM China System Technology Laboratory
Tel: 86-10-82453455
Email: w...@cn.ibm.com
Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193

 

 

----- Original message -----
From: Russell Auld <russa...@comcast.net>
To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
Cc:
Subject: Re: [xcat-user] Prescripts running twice
Date: Fri, May 20, 2016 2:03 AM
 

A closer inspection of the logs on the master reveals that the second execution of the prescript occurred at the end of the postscript phase, before the reboot.
Is this the expected behavior when the prescript is set as an "end" script?
If so, why did it run right after I executed the nodeset command?

On May 19, 2016 10:30 AM, Russell Auld <russa...@comcast.net> wrote:

I noticed that my prescripts are being executed twice when I do a “nodeset <node> osimage”

I have the scripts set as “prescripts-end” in the prescripts table.

What’s the meaning of “begin” and “end” with respect to “osimage”?

Why is my script running twice?

The first execution occurs when I run nodeset, which is what I expect.

What I didn’t expect is that it would run again somewhere later in the process of imaging the node.

I can tell by the results of the script’s execution that the second run was somewhere around the end of the Anaconda stage or the beginning of the postbootscripts phase.

 

I’m doing stateful installs of RHEL6 using xCAT 2.8.5

Version 2.8.5 (git commit 51b69940b6fc7b54fc2a1f89330e69c8f830a3fc, built Mon Sep  1 02:28:50 EDT 2014)

 

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

 

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to