RPC call failure blocks host from being inventoried
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Heitor Matsui |
Bug Description
Brief Description
-----------------
A new RPC call introduced on https:/
Severity
--------
Critical, blocks the upgrade from proceeding
Steps to Reproduce
------------------
Upgrade controller-1
Try to unlock controller-1
Check sysinv.log and observe RPC call error messages
Expected Behavior
------------------
Host controller-1 unlocks without errors
Actual Behavior
----------------
Host controller-1 is blocked from unlocking with "not yet inventoried" error
Reproducibility
---------------
Reproducible
System Configuration
-------
AIO DX, Standard (DC and non-DC)
Branch/Pull Time/Commit
-------
master
Last Pass
---------
N/A
Timestamp/Logs
--------------
sysinv 2022-05-12 11:03:12.870 35610 ERROR sysinv.
Traceback (most recent call last):
File "/usr/lib64/
**args)
File "/usr/lib64/
raise AttributeError("No such RPC function '%s'" % method)
AttributeError: No such RPC function 'get_isystem'
: AttributeError: No such RPC function 'get_isystem'
Traceback (most recent call last):
File "/usr/lib64/
**args)
File "/usr/lib64/
raise AttributeError("No such RPC function '%s'" % method)
AttributeError: No such RPC function 'get_isystem'
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
2022-05-12 11:03:12.870 35610 ERROR sysinv.
sysinv 2022-05-12 11:03:12.900 35610 INFO sysinv.
Test Activity
-------------
Feature Testing
Workaround
----------
Comment lines introduced on the change referenced in the description, then restart sysinv-agent with: sudo systemctl restart sysinv-agent
Changed in starlingx: | |
status: | New → In Progress |
Changed in starlingx: | |
assignee: | nobody → Heitor Matsui (heitormatsui) |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.7.0 stx.config |
This RPC call is new, so calling it from load n+1 to conductor running in load n will fail, solution will be to treat this exception and allow it to pass during upgrades, since this is a expected error to happen, like it is treated in other parts of the agent/manager.py code.