Bug 1225462
Summary: | [HC] Issue creating Replica 3 set on HC deploy | ||
---|---|---|---|
Product: | [oVirt] ovirt-hosted-engine-setup | Reporter: | Sandro Bonazzola <sbonazzo> |
Component: | General | Assignee: | bugs <bugs> |
Status: | CLOSED WONTFIX | QA Contact: | meital avital <mavital> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | --- | CC: | bazulay, bugs, dfediuck, gklein, lsurette, mgoldboi, rbalakri, sabose, sbonazzo, srevivo, ykaul, ylavi |
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: | 2016-04-18 12:35:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1217448 |
Description
Sandro Bonazzola
2015-05-27 12:35:24 UTC
Sahina, can you help with this issue? Is it possible during HE setup to ssh to the 2nd node, and peer probe the first host with "192.168.1.107" ? Gluster needs to know that 192.168.1.107 is another known address for the host, and this is one way to do it. (In reply to Sahina Bose from comment #2) > Is it possible during HE setup to ssh to the 2nd node, and peer probe the > first host with "192.168.1.107" ? > Gluster needs to know that 192.168.1.107 is another known address for the > host, and this is one way to do it. Do you mean executing vdsm cli.glusterHostAdd(host) on the second and third host? Issue there will be that nobody will have configured vdsm yet. Or do you mean by calling gluster cli directly there? Isn't there a way to tell glusterd running on localhost which interface must be used and let it propagate info to other members of the cluster? Solving on Hosted Engine side. I'll open a RFE for gluster. (In reply to Sandro Bonazzola from comment #3) > (In reply to Sahina Bose from comment #2) > > Is it possible during HE setup to ssh to the 2nd node, and peer probe the > > first host with "192.168.1.107" ? > > Gluster needs to know that 192.168.1.107 is another known address for the > > host, and this is one way to do it. > > Do you mean executing vdsm cli.glusterHostAdd(host) on the second and third > host? > Issue there will be that nobody will have configured vdsm yet. > Or do you mean by calling gluster cli directly there? If vdsm is not installed on the other hosts, then this is an issue. The other way to do this would be to correct the brick interfaces after vdsm is installed. So you would set up the gluster volume with the 10.0.. ip addresses, and once all hosts are installed with vdsm, the alternate ip address can be peer probed too. We then need to run replace-brick with the alternate ip address. Not an ideal way, though. > > Isn't there a way to tell glusterd running on localhost which interface must > be used and let it propagate info to other members of the cluster? No Is this still required? I think we plan to provision the HC nodes via Ansible and gdeploy. (In reply to Sahina Bose from comment #6) > Is this still required? I think we plan to provision the HC nodes via > Ansible and gdeploy. Closing as per above comment |