Keystone client couldn't be initialized on platform ostf tests run after distructive on HA
Bug #1398887 reported by
Kirill Omelchenko
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Medium
|
Fuel Library (Deprecated) | ||
5.0.x |
Won't Fix
|
Medium
|
Unassigned | ||
5.1.x |
Won't Fix
|
Medium
|
Fuel Library (Deprecated) | ||
6.0.x |
Won't Fix
|
Medium
|
Fuel Library (Deprecated) |
Bug Description
Scenario:
using latest fuel 5.1.1 RC2-48 iso deploy:
1. New Cluster with nova-flat network and Ceph for images and volumes
2. Add 3x Controllers, 2x computes and 2x ceph nodes
3. Deploy changes
4. Run OSTF tests (passes well)
5. Destroy primary controller node
6. Wait for about 30 minutes
7. Run OSTF tests
Expected result:
all pass well but 'Check that required services are running' which is ok in that case
Actual:
Also each Platform test is failed with message:
Keystone client is not available. Please, refer to OpenStack logs to fix this problem
Also ostf.log contains next traceback:
http://
Changed in fuel: | |
milestone: | 5.1.1 → 5.1.2 |
status: | New → Confirmed |
Changed in fuel: | |
milestone: | 5.1.2 → 6.1 |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Fuel Library Team (fuel-library) |
status: | Confirmed → New |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
status: | Confirmed → Invalid |
To post a comment you must log in.
Medium priority bugs are not backported to stable releases.