Tempest test test_can_create_server_with_max_number_personality_files fails with 'object has no attribute 'b64decode'' error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
High
|
Anna Babich |
Bug Description
The bug has been reproduced against the following env:
Snapshot:
ababich@
SNAPSHOT_ID=#268
Environment:
[root@nailgun ~]# fuel node
id | status | name | cluster | ip | mac | roles | pending_roles | online | group_id
---+---
1 | ready | slave-05_
6 | ready | slave-04_
4 | ready | slave-03_
3 | ready | slave-01_
2 | ready | slave-06_ironic | 1 | 10.109.20.8 | 64:e4:00:b1:f1:ee | ironic | | 1 | 1
5 | ready | slave-02_
[root@nailgun ~]#
The Tempest test tempest.
Traceback (most recent call last):
File "tempest/
self.
AttributeError: 'module' object has no attribute 'b64decode'
The root cause looks like the test case uses b64decode method from Python base64 package instead of method proposed by Oslo's base64 package imported here: https:/
After replacing https:/
self.assertEqua
linux_
and test's re-running it passed:
{0} tempest.
Changed in mos: | |
status: | New → In Progress |
importance: | Undecided → High |
Changed in mos: | |
status: | In Progress → Fix Committed |
The upstream bug: https:/ /bugs.launchpad .net/tempest/ +bug/1625079