Bug 470032 - ipmitool missing "Get User Payload Access Command"
ipmitool missing "Get User Payload Access Command"
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: OpenIPMI (Show other bugs)
4.7
All Linux
medium Severity medium
: rc
: ---
Assigned To: Jan Safranek
BaseOS QE
:
Depends On: 470031
Blocks:
  Show dependency treegraph
 
Reported: 2008-11-05 07:02 EST by Karel Volný
Modified: 2010-04-06 07:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-04-06 07:38:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Karel Volný 2008-11-05 07:02:27 EST
+++ This bug was initially created as a clone of Bug #470031 +++

Description of problem:
ipmitool is missing the possibility of determining the settings that were set by the "sol payload enable/disable" command

Version-Release number of selected component (if applicable):
1.8.10

How reproducible:
always

Steps to Reproduce:
1. ipmitool sol payload enable 1 1
2. ipmitool sol payload get 1 1
  
Actual results:
[root@tornado ~]# ipmitool sol payload enable 1 1
[root@tornado ~]# ipmitool sol payload get 1 1
SOL Commands: info [<channel number>]
              set <parameter> <value> [channel]
              payload <enable|disable> [channel] [userid]
              activate [<usesolforkeepalive|nokeepalive>]
              deactivate
              looptest [<loop times>] [<loop interval(in ms)>]

Expected results:
[root@tornado ~]# ipmitool sol payload enable 1 1
Enabling SOL payload for user 1 on channel 1
[root@tornado ~]# ipmitool sol payload get 1 1
SOL payload for user 1 on channel 1 is ENABLED

Additional info:
this was an additional issue raised in bug #224142, see the end of the comment #12 to that bug, but it was not fixed as it was not a subject of that bug

see IPMI spec chapter 24.7
Comment 2 Jan Safranek 2010-04-06 07:38:35 EDT
Only important issues like performance and security are fixed in RHEL 4.9 and
later. This bug does not meet necessary criteria and is therefore closed.

Note You need to log in before you can comment on or make changes to this bug.