This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

Back to bug 1873614

Who When What Removed Added
camorris 2020-08-28 18:37:30 UTC Version 16.0 (Train) 16.1 (Train)
Dmitry Tantsur 2020-08-30 10:55:44 UTC Target Release --- 8.0
Version 16.1 (Train) 8.2
Pool ID sst_cs_system_management_rhel_8
Component openstack-ironic ipmitool
Assignee rhos-maint vdolezal
QA Contact atonner kernel-qe-hw
Target Milestone --- rc
Product Red Hat OpenStack Red Hat Enterprise Linux 8
Víctor R. Ruiz 2020-09-03 10:04:54 UTC CC rvr
QA Contact kernel-qe-hw rasibley
camorris 2020-09-07 17:50:54 UTC Blocks 1876620
David Vallee Delisle 2020-09-11 13:30:18 UTC CC dvd
Mark Chappell 2020-09-18 10:44:15 UTC CC mchappel
Dmitry Tantsur 2020-09-18 10:50:46 UTC CC vdolezal
Flags needinfo?(vdolezal)
Severity unspecified high
Red Hat One Jira (issues.redhat.com) 2020-10-27 23:09:41 UTC Link ID Red Hat Issue Tracker - Private RHELPLAN-52450
Chris 2020-10-29 13:09:43 UTC CC christopher.martin2
Josef Ridky 2020-11-12 12:50:12 UTC CC jridky
Flags needinfo?(vdolezal) needinfo?(dtantsur)
Dmitry Tantsur 2020-11-12 16:21:13 UTC Flags needinfo?(dtantsur)
August Simonelli 2020-11-13 02:31:26 UTC CC asimonel
PnT Account Manager 2020-11-20 16:06:49 UTC Assignee vdolezal ovasik
PnT Account Manager 2020-11-20 16:07:38 UTC CC vdolezal
Pavel Cahyna 2020-12-10 22:35:31 UTC CC pcahyna
Assignee ovasik pcahyna
Pavel Cahyna 2021-02-24 10:24:38 UTC Status NEW ASSIGNED
RHEL Program Management 2021-02-24 10:24:53 UTC Keywords Triaged
Alex Stupnikov 2021-04-06 08:31:23 UTC CC astupnik
Link ID Red Hat Knowledge Base (Solution) 5931381
Víctor R. Ruiz 2021-04-19 13:12:29 UTC QA Contact rasibley jbastian
Jeff Bastian 2021-04-19 15:22:18 UTC Flags needinfo?(camorris)
Pavel Cahyna 2021-04-28 07:46:20 UTC Flags needinfo?(asimonel)
August Simonelli 2021-04-29 05:46:52 UTC Flags needinfo?(asimonel)
Pavel Cahyna 2021-05-07 14:25:55 UTC Doc Type If docs needed, set a value Bug Fix
camorris 2021-05-20 20:08:45 UTC Flags needinfo?(camorris)
Pavel Cahyna 2021-07-07 16:39:50 UTC Flags needinfo?(dtantsur) needinfo?(mchappel)
Dmitry Tantsur 2021-07-08 11:56:19 UTC Flags needinfo?(dtantsur)
Mark Chappell 2021-07-08 12:08:48 UTC Flags needinfo?(mchappel)
Pavel Cahyna 2021-07-27 09:48:46 UTC Flags needinfo?(camorris) needinfo?(mchappel) needinfo?(dtantsur)
Dmitry Tantsur 2021-07-27 15:36:12 UTC Flags needinfo?(dtantsur)
Pavel Cahyna 2021-08-04 12:50:10 UTC Flags needinfo?(dtantsur)
Dmitry Tantsur 2021-08-04 13:51:19 UTC Flags needinfo?(dtantsur)
Pavel Cahyna 2021-08-08 23:24:07 UTC Blocks 1876620
camorris 2021-08-25 18:25:55 UTC Flags needinfo?(camorris)
Filip Krska 2021-09-23 13:37:36 UTC Priority unspecified low
CC fkrska
Severity high low
Red Hat Bugzilla 2022-03-12 08:29:01 UTC CC dvd
Pavel Cahyna 2022-05-24 17:07:11 UTC Doc Type Bug Fix Release Note
Gabi Fialová 2022-06-15 08:56:05 UTC Docs Contact sjanderk
CC gfialova
Šárka Jana 2022-09-08 14:59:11 UTC Doc Type Release Note Known Issue
Šárka Jana 2022-10-24 13:45:54 UTC Doc Text .`ipmitool` is incompatible with certain server platforms

The `ipmitool` utility serves for monitoring, configuring, and managing devices that support the Intelligent Platform Management Interface (IPMI). The current version of `ipmitool` uses Cipher Suite 17 by default instead of the previous Cipher Suite 3. Consequently, `ipmitool` fails to communicate with certain bare metal nodes that announced support for Cipher Suite 17 during negotiation, but do not actually support this cipher suite. As a result, `ipmitool` aborts with the “no matching cipher suite” error message.

To work around this problem, update your baseboard management controller (BMC) firmware to use the Cipher Suite 17.

Optionally, if the BMC firmware update is not available, you can work around this problem by forcing `ipmitool` to use a certain cipher suite. When invoking a managing task with `ipmitool`, add the `-C` option to the `ipmitool` command together with the _number_ of the cipher suite you want to use. See the following example:
-----
# ipmitool -I lanplus -H _myserver.example.com_ -P _mypass_ -C 3 chassis power status
-----
Šárka Jana 2022-11-02 09:08:30 UTC Doc Text .`ipmitool` is incompatible with certain server platforms

The `ipmitool` utility serves for monitoring, configuring, and managing devices that support the Intelligent Platform Management Interface (IPMI). The current version of `ipmitool` uses Cipher Suite 17 by default instead of the previous Cipher Suite 3. Consequently, `ipmitool` fails to communicate with certain bare metal nodes that announced support for Cipher Suite 17 during negotiation, but do not actually support this cipher suite. As a result, `ipmitool` aborts with the “no matching cipher suite” error message.

To work around this problem, update your baseboard management controller (BMC) firmware to use the Cipher Suite 17.

Optionally, if the BMC firmware update is not available, you can work around this problem by forcing `ipmitool` to use a certain cipher suite. When invoking a managing task with `ipmitool`, add the `-C` option to the `ipmitool` command together with the _number_ of the cipher suite you want to use. See the following example:
-----
# ipmitool -I lanplus -H _myserver.example.com_ -P _mypass_ -C 3 chassis power status
-----
.`ipmitool` is incompatible with certain server platforms

The `ipmitool` utility serves for monitoring, configuring, and managing devices that support the Intelligent Platform Management Interface (IPMI). The current version of `ipmitool` uses Cipher Suite 17 by default instead of the previous Cipher Suite 3. Consequently, `ipmitool` fails to communicate with certain bare metal nodes that announced support for Cipher Suite 17 during negotiation, but do not actually support this cipher suite. As a result, `ipmitool` aborts with the “no matching cipher suite” error message.

To solve this problem, update your baseboard management controller (BMC) firmware to use the Cipher Suite 17.

Optionally, if the BMC firmware update is not available, you can work around this problem by forcing `ipmitool` to use a certain cipher suite. When invoking a managing task with `ipmitool`, add the `-C` option to the `ipmitool` command together with the _number_ of the cipher suite you want to use. See the following example:
-----
# ipmitool -I lanplus -H _myserver.example.com_ -P _mypass_ -C 3 chassis power status
-----
Lenka Špačková 2022-11-08 14:48:10 UTC Doc Text .`ipmitool` is incompatible with certain server platforms

The `ipmitool` utility serves for monitoring, configuring, and managing devices that support the Intelligent Platform Management Interface (IPMI). The current version of `ipmitool` uses Cipher Suite 17 by default instead of the previous Cipher Suite 3. Consequently, `ipmitool` fails to communicate with certain bare metal nodes that announced support for Cipher Suite 17 during negotiation, but do not actually support this cipher suite. As a result, `ipmitool` aborts with the “no matching cipher suite” error message.

To solve this problem, update your baseboard management controller (BMC) firmware to use the Cipher Suite 17.

Optionally, if the BMC firmware update is not available, you can work around this problem by forcing `ipmitool` to use a certain cipher suite. When invoking a managing task with `ipmitool`, add the `-C` option to the `ipmitool` command together with the _number_ of the cipher suite you want to use. See the following example:
-----
# ipmitool -I lanplus -H _myserver.example.com_ -P _mypass_ -C 3 chassis power status
-----
.`ipmitool` is incompatible with certain server platforms

The `ipmitool` utility serves for monitoring, configuring, and managing devices that support the Intelligent Platform Management Interface (IPMI). The current version of `ipmitool` uses Cipher Suite 17 by default instead of the previous Cipher Suite 3. Consequently, `ipmitool` fails to communicate with certain bare metal nodes that announced support for Cipher Suite 17 during negotiation, but do not actually support this cipher suite. As a result, `ipmitool` aborts with the `no matching cipher suite` error message.

To solve this problem, update your baseboard management controller (BMC) firmware to use the Cipher Suite 17.

Optionally, if the BMC firmware update is not available, you can work around this problem by forcing `ipmitool` to use a certain cipher suite. When invoking a managing task with `ipmitool`, add the `-C` option to the `ipmitool` command together with the _number_ of the cipher suite you want to use. See the following example:
-----
# ipmitool -I lanplus -H _myserver.example.com_ -P _mypass_ -C 3 chassis power status
-----
Mark Chappell 2022-12-01 09:33:01 UTC Flags needinfo?(mchappel)
Lucie Vařáková 2023-01-16 13:50:06 UTC CC lmanasko, sjanderk
Flags needinfo?(sjanderk)
Gabi Fialová 2023-01-24 11:37:44 UTC CC gfialova
Šárka Jana 2023-02-02 13:53:17 UTC Flags needinfo?(sjanderk) needinfo?(pcahyna)
Pavel Cahyna 2023-02-07 11:56:04 UTC Flags needinfo?(pcahyna)
Lenka Špačková 2023-03-13 14:08:01 UTC Doc Text .`ipmitool` is incompatible with certain server platforms

The `ipmitool` utility serves for monitoring, configuring, and managing devices that support the Intelligent Platform Management Interface (IPMI). The current version of `ipmitool` uses Cipher Suite 17 by default instead of the previous Cipher Suite 3. Consequently, `ipmitool` fails to communicate with certain bare metal nodes that announced support for Cipher Suite 17 during negotiation, but do not actually support this cipher suite. As a result, `ipmitool` aborts with the `no matching cipher suite` error message.

To solve this problem, update your baseboard management controller (BMC) firmware to use the Cipher Suite 17.

Optionally, if the BMC firmware update is not available, you can work around this problem by forcing `ipmitool` to use a certain cipher suite. When invoking a managing task with `ipmitool`, add the `-C` option to the `ipmitool` command together with the _number_ of the cipher suite you want to use. See the following example:
-----
# ipmitool -I lanplus -H _myserver.example.com_ -P _mypass_ -C 3 chassis power status
-----
.`ipmitool` is incompatible with certain server platforms

The `ipmitool` utility serves for monitoring, configuring, and managing devices that support the Intelligent Platform Management Interface (IPMI). The current version of `ipmitool` uses Cipher Suite 17 by default instead of the previous Cipher Suite 3. Consequently, `ipmitool` fails to communicate with certain bare metal nodes that announced support for Cipher Suite 17 during negotiation, but do not actually support this cipher suite. As a result, `ipmitool` aborts with the `no matching cipher suite` error message.

To solve this problem, update your baseboard management controller (BMC) firmware to use the Cipher Suite 17.

Optionally, if the BMC firmware update is not available, you can work around this problem by forcing `ipmitool` to use a certain cipher suite. When invoking a managing task with `ipmitool`, add the `-C` option to the `ipmitool` command together with the _number_ of the cipher suite you want to use. See the following example:
-----
# ipmitool -I lanplus -H myserver.example.com -P mypass -C 3 chassis power status
-----
Lenka Špačková 2023-03-28 08:39:39 UTC Doc Text .`ipmitool` is incompatible with certain server platforms

The `ipmitool` utility serves for monitoring, configuring, and managing devices that support the Intelligent Platform Management Interface (IPMI). The current version of `ipmitool` uses Cipher Suite 17 by default instead of the previous Cipher Suite 3. Consequently, `ipmitool` fails to communicate with certain bare metal nodes that announced support for Cipher Suite 17 during negotiation, but do not actually support this cipher suite. As a result, `ipmitool` aborts with the `no matching cipher suite` error message.

To solve this problem, update your baseboard management controller (BMC) firmware to use the Cipher Suite 17.

Optionally, if the BMC firmware update is not available, you can work around this problem by forcing `ipmitool` to use a certain cipher suite. When invoking a managing task with `ipmitool`, add the `-C` option to the `ipmitool` command together with the _number_ of the cipher suite you want to use. See the following example:
-----
# ipmitool -I lanplus -H myserver.example.com -P mypass -C 3 chassis power status
-----
.`ipmitool` is incompatible with certain server platforms

The `ipmitool` utility serves for monitoring, configuring, and managing devices that support the Intelligent Platform Management Interface (IPMI). The current version of `ipmitool` uses Cipher Suite 17 by default instead of the previous Cipher Suite 3. Consequently, `ipmitool` fails to communicate with certain bare metal nodes that announced support for Cipher Suite 17 during negotiation, but do not actually support this cipher suite. As a result, `ipmitool` aborts with the `no matching cipher suite` error message.

To solve this problem, update your baseboard management controller (BMC) firmware to use the Cipher Suite 17.

Optionally, if the BMC firmware update is not available, you can work around this problem by forcing `ipmitool` to use a certain cipher suite. When invoking a managing task with `ipmitool`, add the `-C` option to the `ipmitool` command together with the _number_ of the cipher suite you want to use. See the following example:
-----
# ipmitool -I lanplus -H myserver.example.com -P mypass -C 3 chassis power status
-----
Jenny Severance 2023-09-21 21:28:55 UTC Keywords MigratedToJIRA
Red Hat One Jira (issues.redhat.com) 2023-09-21 21:31:25 UTC Link ID Red Hat Issue Tracker RHEL-6846
RHEL Program Management 2023-09-21 22:08:16 UTC Status ASSIGNED CLOSED
Resolution --- MIGRATED
Last Closed 2023-09-21 22:08:16 UTC

Back to bug 1873614