Bug 1804749 - [RHOSP16][Ironic] ironic conductor logs are flooded with "Get PICMG Properities error"
Summary: [RHOSP16][Ironic] ironic conductor logs are flooded with "Get PICMG Properiti...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 16.0 (Train)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: z2
: 16.0 (Train on RHEL 8.1)
Assignee: RHOS Maint
QA Contact: Alistair Tonner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-19 14:50 UTC by MD Sufiyan
Modified: 2020-05-14 12:08 UTC (History)
2 users (show)

Fixed In Version: openstack-ironic-13.0.4-0.20200402125201.3e5816e.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-14 12:07:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 716651 0 None MERGED Move ipmi logging to a separate option 2020-10-21 07:52:56 UTC
Red Hat Product Errata RHBA-2020:2160 0 None None None 2020-05-14 12:08:13 UTC

Description MD Sufiyan 2020-02-19 14:50:11 UTC
Description of problem:

Seeing the following error in ironic-coductor log(s) when debug is set to true in ironic.conf

~~~
lib/python3.6/site-packages/ironic/common/utils.py:77
2020-02-19 09:33:06.054 7 DEBUG ironic.common.utils [req-9367314b-4a65-4d86-bb42-cf825fe66fb9 - - - - -] Command stdout is: "Chassis Power is off
" execute /usr/lib/python3.6/site-packages/ironic/common/utils.py:78
2020-02-19 09:33:06.055 7 DEBUG ironic.common.utils [req-9367314b-4a65-4d86-bb42-cf825fe66fb9 - - - - -] Command stderr is: "Running Get PICMG Properties my_addr 0x20, transit 0, target 0x20
Error response 0xc1 from Get PICMG Properities
Running Get VSO Capabilities my_addr 0x20, transit 0, target 0x20
Invalid completion code received: Invalid command
Discovered IPMB address 0x0
~~~

~~~
 [root@undercloud-0 ~]# cat /var/lib/config-data/puppet-generated/ironic/etc/ironic/ironic.conf | grep -i "debug="
debug=True
~~~

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

- OSP16
- Ironic

()[ironic@undercloud-0 /]$ rpm -qa | grep -i ironic
python3-ironic-lib-2.21.0-0.20190923194637.2c7d1cf.el8ost.noarch
openstack-ironic-conductor-13.0.3-0.20191202201522.cfa58af.el8ost.noarch
python3-ironicclient-3.1.0-0.20190926124316.04ef2d7.el8ost.noarch
puppet-ironic-15.4.1-0.20191022165413.8fe6978.el8ost.noarch
python3-ironic-inspector-client-3.7.0-0.20190923163033.d95a4cd.el8ost.noarch
openstack-ironic-common-13.0.3-0.20191202201522.cfa58af.el8ost.noarch
openstack-ironic-staging-drivers-0.12.1-0.20191014171135.bcedf43.el8ost.noarch


How reproducible:
Every time

Steps to Reproduce:
1. Install undercloud and overcloud
2. Enable debug in ironic
3. Reported error gets captured in "/var/log/containers/ironic/ironic-conductor.log"

Expected results:
No such error mesaages

Additional info:

The issue is not causing any problem and introspection is also getting completed. However, flooding of this error should be investigated to avoid such loggings.

Comment 1 Bob Fournier 2020-02-19 15:03:17 UTC
Thanks. This is already being tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1734133 but since this bug is for OSP-16 won't close it as a dup.

Comment 4 Bob Fournier 2020-04-16 17:44:41 UTC
Using 16z2 with openstack-ironic-conductor-13.0.4-0.20200405204619.253253e.el8ost.noarch

See the new field in /etc/ironic/ironic.conf:

# Enables all ipmi commands to be executed with an additional
# debugging output. This is a separate option as ipmitool can
# log a substantial amount of misleading text when in this
# mode. (boolean value)
#debug = false

In ironic-conductor.log, no longer see "Running Get PICMG Properties" messages and no longer see the error messages.

Comment 6 errata-xmlrpc 2020-05-14 12:07:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2160


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