Worker node name has some limitation
Bug #1820810 reported by
zhipeng liu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
zhipeng liu |
Bug Description
Brief Description
-----------------
When I named worker node as worker-0, it failed when I unlock worker node.
Severity
--------
Major
Steps to Reproduce
------------------
According to deployment guide to deploy bare metal environment, set worker node name as worker-0
------------------
Actual Behavior
----------------
This name should be acceptable
Changed in starlingx: | |
assignee: | Cindy Xie (xxie1) → zhipeng liu (zhipengs) |
tags: |
added: stx.2.0 removed: stx.2019.05 |
To post a comment you must log in.
In sysinv.log, python2. 7/site- packages/ sysinv/ common/ ceph.py" , line 559, in update_crushmap ihost_orig[ 'hostname' ][8:])
We can find root cause
File "/usr/lib64/
storage_num = int(hostupdate.
ValueError: invalid literal for int() with base 10: ''
If we name node as compute-0 it can get storage_num = 0
If we name node as worker-0 it cannot get storage_num
We should change the code here to fix the bug. common/ ceph.py" , line 559
sysinv/