Bug 1244636
| Summary: | Can't automatically add RHEV-H to hosted-engine through vlan tagged network | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | cshao <cshao> | ||||||
| Component: | ovirt-hosted-engine-setup | Assignee: | Sandro Bonazzola <sbonazzo> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | meital avital <mavital> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.5.4 | CC: | alukiano, cshao, ecohen, fdeutsch, gklein, huiwa, istein, juwu, leiwang, lsurette, mburman, nsednev, yaniwang, ycui | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | integration | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-07-23 10:41:20 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1059435, 1250199 | ||||||||
| Attachments: |
|
||||||||
Created attachment 1053780 [details]
HE6.tar.gz
RHEV-H 6.7 HE all log
Created attachment 1053785 [details]
sosreport
Does this bug also appear on a plain RHEL host? (In reply to Fabian Deutsch from comment #4) > Does this bug also appear on a plain RHEL host? Hi fabiand, We haven't RHEL + vlan ENV currently in lab, can you contact RHEV QE to cove this scenario? Thanks! Nikolai, can this bug also be reproduced on plain RHEL + HE? This information will help us to identify the responsible component for this bug. I totally agree and think that Network team should have such environment and also Ying Cui's team should have such environment, especially as they're testing TUI on RHEVH. I checked deployment of hosted-engine on RHEL6.7 and I had the same error about ssh connection, but it was because I defined on vlan static ip that not mapped to hostname, but when hosted-engine try to add host to engine he use: address=socket.gethostname() and failed. To prevent failing on engine vm you can add line to /etc/hosts: vlan_ip_address your_hostname_where_you_deploy_hosted_engine So can you please verify you configuration and check that your vlan ip mapped to hostname? As Artyom wrote in previous comment, hosted-engine deploy over vlan tagged interface with rhel 6.7 is working as expected. After adding line with new ip and hostname to /etc/hosts which is part of the hosted-engine configuration steps. So i don't think it is a network bug, management network was configured with success over vlan tagged interface. (In reply to Artyom from comment #9) > I checked deployment of hosted-engine on RHEL6.7 and I had the same error > about ssh connection, but it was because I defined on vlan static ip that > not mapped to hostname, but when hosted-engine try to add host to engine he > use: > address=socket.gethostname() and failed. To prevent failing on engine vm you > can add line to /etc/hosts: > vlan_ip_address your_hostname_where_you_deploy_hosted_engine > So can you please verify you configuration and check that your vlan ip > mapped to hostname? Yes, I already mapped it, you can check my sosreport which recorded it. # cat hosts 127.0.0.1 localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 192.168.20.129 localhost.localdomain (this is rhevh) 192.168.20.159 cshao67.redhat.com (this is hosted engine) Today I will deploy another new vlan env and test this issue again. and then I will update test result in here later. We probably found the cause, it is relevant to rhev-hypervisor's hostname, if the host's hostname set FQDN, then here can automatically add RHEV-H to hosted-engine through vlan tagged network. if host's hostname set localhost.localdomain as default, then it will cause this issue just unexpected termination to back RHEV-H TUI. So set severity to medium. (In reply to shaochen from comment #13) > We probably found the cause, it is relevant to rhev-hypervisor's hostname, > if the host's hostname set FQDN, then here can automatically add RHEV-H to > hosted-engine through vlan tagged network. if host's hostname set > localhost.localdomain as default, then it will cause this issue just > unexpected termination to back RHEV-H TUI. > > So set severity to medium. Then it's not a bug. Please review the topic 5 at here https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.3/html/Installation_Guide/Configuring_the_Self-Hosted_Engine.html FQDN should look like HostedEngine-VM.example.com, should be resolvable by DNS and get IP address from DHCP by reserved MAC. I agree with Nikolai, and further more that is documented. Closing this bug according to comment 13 and comment 15. |
Description of problem: Can't automatically add RHEV-H to engine through vlan tagged network Version-Release number of selected component (if applicable): rhev-hypervisor6-6.7-20150717.0.el6ev ovirt-node-3.2.3-11.el6.noarch ovirt-node-plugin-hosted-engine-0.2.0-16.0.el6ev.noarch ovirt-hosted-engine-ha-1.2.6-2.el6ev.noarch ovirt-hosted-engine-setup-1.2.5.1-1.el6ev.noarch rhevm-appliance-20150709.0-1.x86_64.rhevm.ova How reproducible: 100% Steps to Reproduce: 1. Install rhev-hypervisor6-6.7-20150717.0 2. Setup network as vlan tagged. 3. File the OVA URL for download. 4. Choose nfs storage(please keep nfs storage is available in vlan env). 5. While setup hosted engine, choose "p2p1.20"(vlan bridge) as network. 6. Finished the engine VM create process. 7. Login engine host, finished deploy engine process(#engine-setup --offline --config-append=ovirt-engine-answers). 8. Login engine webUI, add vlan tagged(20). 9. Back to hypervisor console, choose <1> and press enter key. ... To continue make a selection from the options below: (1) Continue setup - engine installation is complete (2) Power off and restart the VM (3) Abort setup (4) Destroy VM and abort setup ... 10. Enter the name of the cluster to which you want to add the host (Default) [Default]: press enter key 11. Goes on press enter key. Actual results: 1. After step11, it will auto jump to TUI from console. 2. Can't automatically add RHEV-H to engine through vlan tagged network ==================================================================== (1) Continue setup - engine installation is complete (2) Power off and restart the VM (3) Abort setup (4) Destroy VM and abort setup (1, 2, 3, 4)[1]: 1 [ INFO ] Engine replied: DB Up!Welcome to Health Status! Enter the name of the cluster to which you want to add the host (Default) [Default]: To continue make a selection from the options below: (1) Continue setup - engine installation is complete (2) Power off and restart the VM (3) Abort setup (4) Destroy VM and abort setup (1, 2, 3, 4)[1]: 1 [ INFO ] Engine replied: DB Up!Welcome to Health Status! Enter the name of the cluster to which you want to add the host (Default) [Default]: [ ERROR ] Cannot automatically add the host to cluster Default: Cannot add Host. SSH authentication failed, verify authentication parameters are correct (Username/Password, public-key etc.) You may refer to the engine.log file for further details. [ ERROR ] Failed to execute stage 'Closing up': Cannot add the host to cluster Default [ INFO ] Stage: Clean up [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20150720013927.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination Expected results: 1. After step 11, it should pop-up dialog to continue configure register process (e.g. choose cluster). 2. Can automatically add RHEV-H to engine through vlan tagged network Additional info: 1. The same issue occurs on rhev-hypervisor7-7.1-20150717.0.el7ev build (ovirt-node-3.2.3-11.el7.noarch). 2. The same issue occurs during setup hosted engine through ova with bond as networkon.