[Sahara] Create instructions on how to troubleshoot Cluster Creation failure

Bug #1564321 reported by Fabrizio Soppelsa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Status tracked in 10.0.x
10.0.x
Invalid
Medium
MOS Sahara
7.0.x
Invalid
Medium
MOS Sahara
8.0.x
Invalid
Medium
MOS Sahara
9.x
Won't Fix
Medium
MOS Sahara

Bug Description

Detailed bug description: Information in Horizon and in Sahara logs is often not much detailed to troubleshoot a Launch Cluster failure, i.e. They are way too generic. Often they report an errorID: How to troubleshoot that? It's not so immediate by looking into Nova or Neutron. I propose to write some simple instruction steps and hints in documentation on how to identify the causes of typical Sahara failures.

Description of the environment:
- Operating system: Ubuntu
- Versions of components: MOS 7.0

Dina Belova (dbelova)
Changed in mos:
status: New → Confirmed
assignee: nobody → MOS Sahara (mos-sahara)
importance: Undecided → Medium
milestone: none → 10.0
Revision history for this message
Nikita Konovalov (nkonovalov) wrote :

Fabrizio, the thing you suggest to have should be a part of some generally available document. Do we have any examples of such troubleshooting documents?

If we do, please give me any links to those and I'll find a way to add Sahara troubleshooting steps there. I've got a collection of some typical cases already and it looks like it will be growing.

You've also mentioned 7.0 and 8.0 updates? How do we put anything like this in previous releases?

Revision history for this message
Dina Belova (dbelova) wrote :

Won't be fixed in 9.0 due to medium priority

Revision history for this message
Dina Belova (dbelova) wrote :

Added move-to-10.0 tag due to the fact bug was transferred from 9.0 to 10.0

tags: added: move-to-10.0
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

Closing as Invalid after a month without feedback. Fabrizio, please feel free to re-open it, if you provide more input.

Changed in mos:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.