2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-05-22 11:42:05 +00:00

18 Commits

Author SHA1 Message Date
XuWei
af33fbe131 disable rpower reset and boot command for OpenBMC 2017-09-21 03:27:52 -04:00
yangsong
22b51e3efa fix issue Weird problem with rinstall #3877 (#3883) 2017-09-08 14:14:20 +08:00
immarvin
b167c2932b fix issue rinstall/winstall -c doesn't open console #3535 2017-08-01 05:51:30 -04:00
zet809
4f0bd2b5ba fix issue 3297: rinstall could not set runcmd and runimg's currchain (#3491)
* fix issue 3297: rinstall could not set runcmd and runimg's currchain
2017-07-18 18:17:14 +08:00
Mark Gurevich
30b4929625 Fixes to rinstall/winstall man pages 2017-06-15 16:03:04 -04:00
chenglch
d9d0cfd42c Avoid of circular reference in a loop of rinstall (#3121)
This is a temporary fix for getadapter which will hang forever if
error happens in `rinstall stage`. The root cause is the circular
reference in `runxcmd`. As global variable `$::xcmd_outref` and
`%::xcmd_outref_hash` are used to save the output message, if the
plugin command are called with runxcmd and the plugin called also
calls another plugin with `runxcmd`, the circular reference will happen.
In this situation, if the output reponse is used in a iterator,
like:
```
   foreach my $line (@$res) {
      xCAT::MsgUtils->message("I", $rsp, $callback);
```
`$res` points to the global variable, and `MsgUtils->message` in the
runxcmd calls also add the value in the global variable, as the
iter object is changed, the loop will not be terminated.

This patch can not solve the circular reference problem, it is just
a workaround to avoid infinite loop.

Some known issues: the error message will print twice as the
`MsgUtils->message` called in runxcmd. But we can not simply remove
it as the plugin may not be called with `runxcmd`.

Error message example:

```
Error: frame10node10: mgt configuration can not be found.
frame10node10: Unable to identify plugin for this command, check relevant tables: noderes.netboot
frame10node10: Unable to identify plugin for this command, check relevant tables: noderes.netboot
Failed to run 'nodeset' against the following nodes: frame10node10
Error: failed to run command: rinstall frame10node10 runcmd=getadapter
```
partial-fix: #3046
2017-06-07 22:21:26 -05:00
yangsong
5c4dd31844 fix issue [fvt]2.13.4 nodeset osimage have no right output if command wrong #2971 (#3147)
* fix issue#2971:  one CLI arguments validation issue is not correct for nodeset/rinstall/winstall
2017-05-31 17:36:09 +08:00
Victor Hu
e2f2d67ba8 Check the failed nodes array before printing out the (#3110)
error messages
2017-05-22 21:41:14 -05:00
yangsong
7d2ac05f4d add rinstall support for openbmc (#3009)
* add rinstall support for openbmc based server, it is still for technical preview.

* use <D> instead of <I> in xCAT::MsgUtils->message to display the rsetboot+rpower response correct
2017-05-11 15:33:34 +08:00
immarvin
0efb6aa83f fix issue rinstall is not able to set or detect the arch , does not happen with nodeset #2745 2017-03-29 13:11:07 +08:00
ypbj
b5974bcaf1 update rinstall output 2017-01-10 03:04:27 -05:00
Mark Gurevich
0a3fbd8d51 perltidy all perl files 2016-07-20 11:40:27 -04:00
penguhyang
45e364d123 fix rinstall bug for #1461 2016-07-04 07:05:07 -04:00
penguhyang
394eca0f50 fix #1157, enhance rinstall command 2016-06-27 22:42:50 -04:00
Jarrod Johnson
2fab20c5f6 Have rinstall default to uefi boot
When doing rinstall, default to UEFI now
2015-06-24 15:09:30 -04:00
ligc
c0f65b7ae7 remove install/netboot/statelite related flags from rmimage, liteimg and rinstall 2015-05-14 04:57:44 -04:00
WangXiaoPeng
fbb5fca652 defect 4553: make rinstall only output error message when certain node failed instead of stopping running 2015-05-12 22:47:35 -04:00
lissav
d4c7b7051b add rinstall plugin 2014-06-24 07:49:45 -04:00