Bug 1296215
Summary: | error messages have lack of information | ||||||
---|---|---|---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Storage Console | Reporter: | Martin Kudlej <mkudlej> | ||||
Component: | core | Assignee: | Nishanth Thomas <nthomas> | ||||
core sub component: | events | QA Contact: | sds-qe-bugs | ||||
Status: | CLOSED WONTFIX | Docs Contact: | |||||
Severity: | unspecified | ||||||
Priority: | unspecified | CC: | mbukatov, nthomas, sankarshan | ||||
Version: | 2 | Keywords: | TestBlocker | ||||
Target Milestone: | --- | ||||||
Target Release: | 2 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-03-10 09:36:12 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Martin Kudlej
2016-01-06 15:46:44 UTC
Created attachment 1116562 [details] skyring console log Additional information ====================== I hit this issue again. On the Tasks page I see that the following task failed: > Create Cluster: cluster01 > 09d6820f-c4f9-4910-a49e-5bfbec6afce2 See excerpt from skyring console log which start with the 1st mention of this task and ends with the last. File /var/log/skyring/bigfin.log doesn't contain more details either: ~~~ 2016-01-20T10:26:11.515+01:00 ERROR utils.go:133 FailTask] Cluster creation failed: CreateCluster(): function failed at python side ~~~ File /var/log/salt/master is empty on usm server machine. The problem is that there are no useful information provided by usm server, the only option is to manually check nodes which is hardly optimal. Sounds duplicate to 1300656. How does it differ? (In reply to Nishanth Thomas from comment #2) > Sounds duplicate to 1300656. How does it differ? Those are completely separate, but related issues. See the description of BZ 1300656: > This BZ is concerned with *the fact that the create cluster operation fails* in > this way every now and then. There is another BZ 1296215 which deals with the > fact that there is no good evidence what actually happens in similar cases. In other words: * BZ 1296215 (this BZ) is about missing information in the logs when any failure on a python side happens * BZ 1300656 is about one particular failure of "Create Cluster" task Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. |