Bug 972910
| Summary: | Adding a host to a cluster yields an exception logged in engine.log | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Dustin Tsang <dtsang> | ||||||||||
| Component: | rhsc | Assignee: | Sahina Bose <sabose> | ||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Dustin Tsang <dtsang> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | unspecified | CC: | dtsang, knarra, mmahoney, mmccune, pprakash, rhs-bugs, ssampat | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2013-06-14 04:59:04 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: |
|
||||||||||||
Created attachment 759341 [details]
exception exerpt from engine log
Created attachment 759342 [details]
vdsm log
Created attachment 759343 [details]
super vdsm log
This is a warning message in the logs. The engine code first checks if there's a vdsm-id for host being added using an ssh session. If not present, the vdsm returns exception which is logged as warning, and engine proceeds with installing the host and creating a new id. The id check is done to make sure the host being added is not already present. |
Created attachment 759339 [details] engine log *Note this may be related to 919422 Description of problem: When adding the host and waiting for the host to come to the up state, an exception is received in the engine.log. Version-Release number of selected component (if applicable): rhsc-bb2 How reproducible: 70% it occurs on the second host being added to a node Steps to Reproduce: 1. create a 3.2 cluster in rhsc 2. add one node to the cluster 3. add a second node to the cluster Actual results: no exception is raised. Node does become up. Expected results: Node becomes up but with any exceptions raised. Additional info: