summaryrefslogtreecommitdiff
path: root/meta-openembedded/meta-python/recipes-devtools/python/python3-sqlparse
diff options
context:
space:
mode:
authorThang Tran <thuutran@amperecomputing.com>2024-12-10 06:18:28 +0300
committerHieu Huynh <hieuh@os.amperecomputing.com>2024-12-10 06:24:13 +0300
commit29380ed6d328bfd45a3c4e389cdfcb97359052aa (patch)
treebfc593d25fc6db17fd379cb08a68c26b0c47eb57 /meta-openembedded/meta-python/recipes-devtools/python/python3-sqlparse
parentc8b9c3fbdb425247ef361f8120f32447208e4dd0 (diff)
downloadopenbmc-29380ed6d328bfd45a3c4e389cdfcb97359052aa.tar.xz
meta-ampere: net-ipmid: disable rmcp-ping option
Issue: When users request OOB command "ipmitool sol activate", if host's console show any data then users can not request any OOB ipmi commands. Root cause: After the @acb8d90 commit, the rmcp-ping option effects to message handling, it makes the netipmid fail to send/receive message to/from "sol client". This commit disables rmcp-ping option to make the netipmid can work normally when users request OOB "ipmitool sol activate" command. Tested: 1. Request access Host's console via OOB command. $ ipmitool sol activate 2. Request power cycle. $ ipmitool power cycle 3. The Host's console show the logs of Host. 4. Request another OOB command. $ ipmitool chassis status 5. The chassis status is shown. Change-Id: I4f42c816471343e398779858536f861d0af98ae7 Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Diffstat (limited to 'meta-openembedded/meta-python/recipes-devtools/python/python3-sqlparse')
0 files changed, 0 insertions, 0 deletions