pasu strips OneCLI's banner and status lines so only the requested settings are
shown, but OneCLI has grown several status lines over the years that were not
filtered and leaked into the output. Add the missing patterns.
Recovered from the unmerged lenovobuild branch (229533cb, a6932bb4), which added
"Connected to BMC at IP address" (master only matched "by"), "Succeed in running
the command:" and "start to convert cmd.". Extended after testing a current
OneCLI 5.3.0 on a Lenovo ThinkSystem SR635, which also emits "Start to connect
...", "Connected to the node(N) by KCS" and a trailing "Succeed." -- now
filtered too.
Validated by running a real OneCLI 5.3.0 "config show" through the filter:
every banner/footer line is removed and all 756 setting lines pass unchanged.
Co-authored-by: Jarrod Johnson <10814490+jjohnson42@users.noreply.github.com>
tcons opens an rcons console per node in a tiled tmux session. On tmux 3.x
(shipped by all currently supported platforms) it no longer works:
* The session was named "tcons.$$". Modern tmux treats "." as the
session:window.pane target separator, so "tmux attach -t tcons.$$" is
parsed as session "tcons", pane "$$" and fails with "can't find
session"/"can't find pane" -- tcons cannot attach to the session it
just created. Rename it to "tcons_$$".
* The per-node "tmux select-pane", "tmux split" and "tmux select-layout"
commands had no target. When tcons is run from inside an existing tmux
session (the common case) they act on the caller's current session
instead of the detached tcons session, splitting the operator's own
window. Target every command explicitly at the tcons session.
* Move the pane-border-status option inside the loop so the console title
is set on each pane as it is created.
Validated on tmux next-3.4: the reworked script builds a 3-pane tiled
session with no errors, whereas the previous version's dotted session name
is unaddressable ("can't find pane").
Recovered from the unmerged lenovobuild branch (originals 5107b6ba1,
cefefa7d1, 6c72a2707, e040d24bb).
Co-authored-by: Jarrod Johnson <10814490+jjohnson42@users.noreply.github.com>
When nodehm.conserver is a hostname, rcons compared that name directly against
the management node's local IP addresses, so the "conserver is this host"
check never matched and rcons connected via `-s` (a remote confluent session)
even when the conserver was the local host. Resolve the name to an address
with getent first so the comparison works.
Recovered from the unmerged lenovobuild branch (original faa767e5).
Co-authored-by: Jarrod Johnson <10814490+jjohnson42@users.noreply.github.com>
There's a typo on genimage thats easy to fix, also the explanation for
Fedora is extremely outdated, on modern Fedora releases statelite is
generated automatically:
[root@headnode ~]# lsdef -t osimage
fedora35-x86_64-install-compute (osimage)
fedora35-x86_64-install-service (osimage)
fedora35-x86_64-netboot-compute (osimage)
fedora35-x86_64-statelite-compute (osimage)
Also theres a typo on OpenStack setup that grep caught, so we added
it too the commit, for cosmetic reasons.
* * osimage table schema change: add a "environvar" col in osimage table to hold environment variables used in osimage customized files
* osimage object schema change: add a environvar attribute, which refers to osimage.environvar
* the environment variables specified in "environvar" attribute will be exported during invocation of postinstall scripts in genimage
* support variables in synclists
* support environment variables in genimage,mkinstall,getpostscript
* support environment variables for xdcp -i -F in packimage
* add support for syncfiles with scp
* refine logic of EXECTUTE support message non rsync filesync
* refine syncfiles
* add startsyncfile script for cumulus
* refine format, fix updatenode without options causes command to crash #5142
Previously, it is impossible to know if the goconerver is started
by xcat. This patch add a marker in /etc/goconserver/server.conf
to help check the status. In addition, use server-cred.pem instead
of server-key.pem as it is not exist on SN.
This patch also control the service status of goconserver and conserver
when restarting the xcatd service on service node.
```
[root@sn02 ~]# chdef sn02 setupconserver=1
1 object definitions have been created or modified.
[root@sn02 ~]# service xcatd restart
Restarting xcatd (via systemctl): [ OK ]
[root@sn02 ~]# ps -ef | grep conserver
root 27679 1 0 02:26 ? 00:00:00 /usr/sbin/conserver -o -O1 -d
root 27680 27679 0 02:26 ? 00:00:00 /usr/sbin/conserver -o -O1 -d
root 27756 26188 0 02:26 pts/1 00:00:00 grep --color=auto conserver
[root@sn02 ~]# chdef sn02 setupconserver=2
1 object definitions have been created or modified.
[root@sn02 ~]# service xcatd restart
Restarting xcatd (via systemctl): [ OK ]
[root@sn02 ~]#
[root@sn02 ~]#
[root@sn02 ~]#
[root@sn02 ~]# ps -ef | grep conserver
root 27885 1 0 02:26 ? 00:00:00 /usr/bin/goconserver
root 27986 26188 0 02:33 pts/1 00:00:00 grep --color=auto conserver
```
goconserver could send back message based on the client type
this commit set CONGO_CLIENT_TYPE to xcat to make the message
from goconserver more friendly.
Enhance the original implement of rcons to support goconserver.
`rcons` will help the user choose from one of the console backend
service based on the console server status of management node.
Implement #4216
The IVP expects xcatd to be fully operational by the
time is begins a run. It is possible for xcatd to
be delayed. The delay should not ause a corruption
of the zvmnotify property in the site table.
In addition, tests for tabdump failures should be
corrected and the log file should be set up sooner
so that debug information is available for similar
problems.
Change-Id: I2b0e3e875cc28f740a35b348faa0cc74f5acb7bf
Daniel Hilst
Vinícius Ferrão
besawn
Mark Gurevich
Vinícius Ferrão
peterwywong
Wai Yee Wong
cxhong
Bin Xu
xuweibj
GONG Jie
yangsong
Yuan Bai
Bin Xu
chenglch
Steven P. Gessner