| Summary: | 3rd node addition brings down the hosted engine appliance | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-hosted-engine-setup | Reporter: | Bhaskarakiran <byarlaga> | ||||
| Component: | General | Assignee: | Simone Tiraboschi <stirabos> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | meital avital <mavital> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | --- | CC: | bugs, byarlaga, mzywusko, sbonazzo, stirabos, ylavi | ||||
| Target Milestone: | ovirt-3.6.8 | Flags: | ylavi:
ovirt-3.6.z?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-06-27 12:30:05 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
How did you get to this step if BZ #1329202 was blocking you? Yaniv, All these errors / disconnects are seen during the 3rd node addition. Tried first time, the appliance went down, second time, certificate errors and etc.. May be the order i filed the bugs is different. Do you still have this issue? Simone can you try to reproduce? I have seperated the networks for ovirt and gluster and do not see but if its the same for both then there are issues. I don't have the spare systems to reproduce. May be someone can try. On my opinion this is just the combination of side effects from two different issues that we are going to solve with 3.6.6/3.6.7: The first one was the SetupNetwork issue deploying an host: https://bugzilla.redhat.com/show_bug.cgi?id=1322257 https://bugzilla.redhat.com/show_bug.cgi?id=1320128 If host-deploy failed for that issue, your host can end with the management network not properly configured. If you used the same network also for gluster you lost also the storage connection. If you use two separate networks for the management and the storage, the storage connection will probably survive. The second one was here: https://bugzilla.redhat.com/show_bug.cgi?id=1298693 You had a single point of failure deploying hosted-engine on gluster so, if you loose gluster due to the SetupNetwork issue on the host pointed by the hosted-engine configuration, the engine VM will go down. Bhaskarakiran, can you please try to reproduce with 3.6.7 RC and a single network but using custom mount options as for https://bugzilla.redhat.com/show_bug.cgi?id=1298693#c20 ? I would need some time as i don't have machines with single network. Will update as i progress. Please reopen is you can reproduce and provide the needed info |
Created attachment 1151201 [details] sosreports of hosted engine Description of problem: ----------------------- During the 3rd node addition to the hosted engine, the appliance goes down (doesn't run and ping). Need to manually start the VM with "hosted-engine --vm-start". This happens every time. Attaching the hosted engine sos reports. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: