openstackbmc still failing with concatenation errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyghmi |
New
|
Undecided
|
Unassigned | ||
tripleo |
Fix Released
|
High
|
Unassigned |
Bug Description
I believe Derek fixed this in upstream pyghmi, but it doesn't look like it's been released yet. We may want to pre-install the git versions on the BMC images to avoid the problem. We should also request a release of pyghmi.
Note that this is probably responsible for a lot of the spurious failures in CI that I have looked at.
Pyghmi commit: https:/
Stack trace in bmc logs:
[177420.948694] openstackbmc[2379]: Traceback (most recent call last):
[177420.950266] openstackbmc[2379]: File "/usr/local/
[177420.951304] openstackbmc[2379]: mybmc.listen()
[177420.952029] openstackbmc[2379]: File "/usr/lib/
[177420.953202] openstackbmc[2379]: ipmisession.
[177420.954119] openstackbmc[2379]: File "/usr/lib/
[177420.955425] openstackbmc[2379]: relsession.
[177420.956250] openstackbmc[2379]: File "/usr/lib/
[177420.957571] openstackbmc[2379]: self._handle_
[177420.958536] openstackbmc[2379]: File "/usr/lib/
[177420.960411] openstackbmc[2379]: self._handle_
[177420.961263] openstackbmc[2379]: File "/usr/lib/
[177420.962615] openstackbmc[2379]: self._parse_
[177420.963473] openstackbmc[2379]: File "/usr/lib/
[177420.964814] openstackbmc[2379]: self._parse_
[177420.965646] openstackbmc[2379]: File "/usr/lib/
[177420.966970] openstackbmc[2379]: self.ipmicallba
[177420.967778] openstackbmc[2379]: File "/usr/lib/
[177420.969190] openstackbmc[2379]: self.bmc.
[177420.970109] openstackbmc[2379]: File "/usr/lib/
[177420.971824] openstackbmc[2379]: session.
[177420.972743] openstackbmc[2379]: File "/usr/lib/
[177420.974125] openstackbmc[2379]: data = [code] + data
[177420.974878] openstackbmc[2379]: TypeError: can only concatenate list (not "tuple") to list
I had only noticed this in a large OVB deployment, but its worth a try. I've patched the bmc-template image on rh2 to use this. @ben Do you know who to ask about a release so it just works next time we generate an image?