Closed neo954 closed 5 years ago
And I consider this bug as a BLOCK issue.
@bybai It seems reasonable, the tool should not break the ssh session.
This is a accepted bug, but not a BLOCK issue. We advise to use alias nic like "-i eth0:0" instead of "-i eth0".
If it is mentioned as you,
Just print error to ask ask user to input eth0:0
and quit without continuing, we cannot go ahead if the wrong input will cause big issue.
Hi @gurevichmark , could you look at this issue?
Refer to xcat2/xcat2-task-management#163
Is this issue fixed? If not, pls move to 2.14.3, if yes, pls close this defect.
Since we now ask admin to setup VIP manually. I do not think this issue is valid anymore.
Hi, @neo954 , as @gurevichmark have mentioned above, what is your idea?
No updates since July. Closing this issue.
This bug is against
xcatha.py
commit 3c0251fe0763f597f098bd16a4d4542c3fe8b9c8.Host c910f03c01p07 has the following network configuration.
While run
xcatha.py
with the following command line arguments. It try to replace the IP address of the backbone network interface to 10.3.1.99. And this network reconfiguration break the ssh session used to runxcatha.py
.The expected behavior is keep the IP address of the backbone network interface. And apply the"virtual IP" as an alias on the same network adapter.