Bug 1375240
| Summary: | Hosted engine deployment of 4.0 appliance on 3.6.9 host has failed. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-hosted-engine-setup | Reporter: | Nikolai Sednev <nsednev> | ||||
| Component: | General | Assignee: | Sandro Bonazzola <sbonazzo> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | meital avital <mavital> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 1.3.7.2 | CC: | bugs, didi, nsednev, ylavi | ||||
| Target Milestone: | --- | Flags: | rule-engine:
planning_ack?
rule-engine: devel_ack? rule-engine: testing_ack? |
||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-09-14 12:11:44 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: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1356127 | ||||||
| Attachments: |
|
||||||
Created attachment 1200223 [details]
sosreport from host
(In reply to Nikolai Sednev from comment #0) > Description of problem: > I've tried to deploy hosted-engine using > rhevm-appliance-20160831.0-1.el7ev.noarch on 3.6.9 host and failed. > Hosted engine deployment of 4.0 appliance on 3.6.9 host has failed. Why do you think it should have succeeded? > |- Please note: Data Warehouse is required for the > engine. If you choose to not configure it on this host, you have to > configure it on a remote host, and then configure the engine on this host so > that it can access the database of the remote Data Warehouse host. > |- Configure Data Warehouse on this host (Yes, No) > [Yes]: [ ERROR ] Failed to execute stage 'Environment customization': End of > file In 4.0, DWH is mandatory, thus included in the appliance, and hosted-engine setup knows this and passes an answer to above question. 3.6 hosted-engine does not, as the 3.6 appliance did not include dwh. AFAIU this bug can be closed. Users should use 3.6 appliance on 3.6 hosted-engine and 4.0 appliance on 4.0 hosted-engine. (In reply to Yedidyah Bar David from comment #2) > (In reply to Nikolai Sednev from comment #0) > > Description of problem: > > I've tried to deploy hosted-engine using > > rhevm-appliance-20160831.0-1.el7ev.noarch on 3.6.9 host and failed. > > Hosted engine deployment of 4.0 appliance on 3.6.9 host has failed. > > Why do you think it should have succeeded? In order to reproduce and verify https://bugzilla.redhat.com/show_bug.cgi?id=1356127 and there should not be such limitation that 4.0 engine can't be deployed over 3.6.9 host. > > > |- Please note: Data Warehouse is required for the > > engine. If you choose to not configure it on this host, you have to > > configure it on a remote host, and then configure the engine on this host so > > that it can access the database of the remote Data Warehouse host. > > |- Configure Data Warehouse on this host (Yes, No) > > [Yes]: [ ERROR ] Failed to execute stage 'Environment customization': End of > > file > > In 4.0, DWH is mandatory, thus included in the appliance, and hosted-engine > setup knows this and passes an answer to above question. 3.6 hosted-engine > does not, as the 3.6 appliance did not include dwh. > > AFAIU this bug can be closed. Users should use 3.6 appliance on 3.6 > hosted-engine and 4.0 appliance on 4.0 hosted-engine. (In reply to Nikolai Sednev from comment #3) > (In reply to Yedidyah Bar David from comment #2) > > (In reply to Nikolai Sednev from comment #0) > > > Description of problem: > > > I've tried to deploy hosted-engine using > > > rhevm-appliance-20160831.0-1.el7ev.noarch on 3.6.9 host and failed. > > > Hosted engine deployment of 4.0 appliance on 3.6.9 host has failed. > > > > Why do you think it should have succeeded? > In order to reproduce and verify > https://bugzilla.redhat.com/show_bug.cgi?id=1356127 Can you clarify the flow you need there? IIUC it does not deal with hosted-engine setup versions. You should be able to setup both at 3.6 and then upgrade the engine (if the flow requires this). > and there should not be > such limitation that 4.0 engine can't be deployed over 3.6.9 host. 1. Not sure I agree 2. Is this documented? 3. It can be, just not automatically. Do not choose to run engine-setup automatically and run it by yourself. 4. Even if we agree, it's a 3.6 bug, and I think we solve only severe-enough 3.6 bugs, now that 4.0 is out. Is this one severe enough? *** This bug has been marked as a duplicate of bug 1375573 *** |
Description of problem: I've tried to deploy hosted-engine using rhevm-appliance-20160831.0-1.el7ev.noarch on 3.6.9 host and failed. Hosted engine deployment of 4.0 appliance on 3.6.9 host has failed. # hosted-engine --deploy [ INFO ] Stage: Initializing [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup Continuing will configure this host for serving as hypervisor and create a VM where you have to install the engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]: Configuration files: [] Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160912163942-yqnecp.log Version: otopi-1.4.2 (otopi-1.4.2-1.el7ev) It has been detected that this program is executed through an SSH connection without using screen. Continuing with the installation may lead to broken installation if the network connection fails. It is highly recommended to abort the installation and run it inside a screen session using command "screen". Do you want to continue anyway? (Yes, No)[No]: yes [ INFO ] Hardware supports virtualization [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Stage: Environment customization --== STORAGE CONFIGURATION ==-- During customization use CTRL-D to abort. Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]: Please specify the full shared storage connection path to use (example: host:/path): 10.35.64.11:/vol/RHEV/Virt/nsednev_3_6_HE_1 [ INFO ] Installing on first host --== SYSTEM CONFIGURATION ==-- --== NETWORK CONFIGURATION ==-- [ INFO ] Bridge ovirtmgmt already created iptables was detected on your computer, do you wish setup to configure it? (Yes, No)[Yes]: Please indicate a pingable gateway IP address [10.35.117.254]: --== VM CONFIGURATION ==-- Booting from cdrom on RHEL7 is ISO image based only, as cdrom passthrough is disabled (BZ760885) Please specify the device to boot the VM from (choose disk for the oVirt engine appliance) (cdrom, disk, pxe) [disk]: [ INFO ] Detecting available oVirt engine appliances The following appliance have been found on your system: [1] - The RHEV-M Appliance image (OVA) - 20160731.0-1.el7ev [2] - Directly select an OVA file Please select an appliance (1, 2) [1]: [ INFO ] Verifying its sha1sum [ INFO ] Checking OVF archive content (could take a few minutes depending on archive size) [ INFO ] Checking OVF XML content (could take a few minutes depending on archive size) [WARNING] OVF does not contain a valid image description, using default. Would you like to use cloud-init to customize the appliance on the first boot (Yes, No)[Yes]? Would you like to generate on-fly a cloud-init ISO image (of no-cloud type) or do you have an existing one (Generate, Existing)[Generate]? Please provide the FQDN you would like to use for the engine appliance. Note: This will be the FQDN of the engine VM you are now going to launch, it should not point to the base host or to any other existing machine. Engine VM FQDN: (leave it empty to skip): []: nsednev-he-1.qa.lab.tlv.redhat.com Automatically execute engine-setup on the engine appliance on first boot (Yes, No)[Yes]? Automatically restart the engine VM as a monitored service after engine-setup (Yes, No)[Yes]? Please provide the domain name you would like to use for the engine appliance. Engine VM domain: [qa.lab.tlv.redhat.com] Enter root password that will be used for the engine appliance (leave it empty to skip): Confirm appliance root password: How should the engine VM network should be configured (DHCP, Static)[DHCP]? Add lines for the appliance itself and for this host to /etc/hosts on the engine VM? Note: ensuring that this host could resolve the engine VM hostname is still up to you (Yes, No)[No] yes The following CPU types are supported by this host: - model_SandyBridge: Intel SandyBridge Family - model_Westmere: Intel Westmere Family - model_Nehalem: Intel Nehalem Family - model_Penryn: Intel Penryn Family - model_Conroe: Intel Conroe Family Please specify the CPU type to be used by the VM [model_SandyBridge]: Please specify the number of virtual CPUs for the VM [Defaults to appliance OVF value: 2]: 4 You may specify a unicast MAC address for the VM or accept a randomly generated default [00:16:3e:7b:b0:9e]: 00:16:3E:7B:B8:53 Please specify the memory size of the VM in MB [Defaults to appliance OVF value: 4096]: Please specify the console type you would like to use to connect to the VM (vnc, spice) [vnc]: --== HOSTED ENGINE CONFIGURATION ==-- Enter the name which will be used to identify this host inside the Administrator Portal [hosted_engine_1]: alma03.qa.lab.tlv.redhat.com Enter 'admin@internal' user password that will be used for accessing the Administrator Portal: Confirm 'admin@internal' user password: Please provide the name of the SMTP server through which we will send notifications [localhost]: smtp.redhat.com Please provide the TCP port number of the SMTP server [25]: Please provide the email address from which notifications will be sent [root@localhost]: nsednevhe1 Please provide a comma-separated list of email addresses which will get notifications [root@localhost]: nsednev [ INFO ] Stage: Setup validation --== CONFIGURATION PREVIEW ==-- Bridge interface : enp5s0f0 Engine FQDN : nsednev-he-1.qa.lab.tlv.redhat.com Bridge name : ovirtmgmt Host address : alma03.qa.lab.tlv.redhat.com SSH daemon port : 22 Firewall manager : iptables Gateway address : 10.35.117.254 Host name for web application : alma03.qa.lab.tlv.redhat.com Storage Domain type : nfs3 Host ID : 1 Image size GB : 50 GlusterFS Share Name : hosted_engine_glusterfs GlusterFS Brick Provisioning : False Storage connection : 10.35.64.11:/vol/RHEV/Virt/nsednev_3_6_HE_1 Console type : vnc Memory size MB : 4096 MAC address : 00:16:3E:7B:B8:53 Boot type : disk Number of CPUs : 4 OVF archive (for disk boot) : /usr/share/ovirt-engine-appliance/rhevm-appliance-20160731.0-1.el7ev.ova Restart engine VM after engine-setup: True CPU Type : model_SandyBridge Please confirm installation settings (Yes, No)[Yes]: [ INFO ] Stage: Transaction setup [ INFO ] Stage: Misc configuration [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Configuring libvirt [ INFO ] Configuring VDSM [ INFO ] Starting vdsmd [ INFO ] Waiting for VDSM hardware info [ INFO ] Creating Storage Domain [ INFO ] Creating Storage Pool [ INFO ] Connecting Storage Pool [ INFO ] Verifying sanlock lockspace initialization [ INFO ] Creating Image for 'hosted-engine.lockspace' ... [ INFO ] Image for 'hosted-engine.lockspace' created successfully [ INFO ] Creating Image for 'hosted-engine.metadata' ... [ INFO ] Image for 'hosted-engine.metadata' created successfully [ INFO ] Creating VM Image [ INFO ] Extracting disk image from OVF archive (could take a few minutes depending on archive size) [ INFO ] Validating pre-allocated volume size [ INFO ] Uploading volume to data domain (could take a few minutes depending on archive size) [ INFO ] Image successfully imported from OVF [ INFO ] Destroying Storage Pool [ INFO ] Start monitoring domain [ INFO ] Configuring VM [ INFO ] Updating hosted-engine configuration [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up [ INFO ] Creating VM You can now connect to the VM with the following command: /bin/remote-viewer vnc://localhost:5900 Use temporary password "6171KEWA" to connect to vnc console. Please note that in order to use remote-viewer you need to be able to run graphical applications. This means that if you are using ssh you have to supply the -Y flag (enables trusted X11 forwarding). Otherwise you can run the command from a terminal in your preferred desktop environment. If you cannot run graphical applications you can connect to the graphic console from another host or connect to the serial console using the following command: socat UNIX-CONNECT:/var/run/ovirt-vmconsole-console/3f50326f-940d-4e6e-a351-e0677be6eea3.sock,user=ovirt-vmconsole STDIO,raw,echo=0,escape=1 Please ensure that your Guest OS is properly configured to support serial console according to your distro documentation. Follow http://www.ovirt.org/Serial_Console_Setup#I_need_to_access_the_console_the_old_way for more info. If you need to reboot the VM you will need to start it manually using the command: hosted-engine --vm-start You can then set a temporary password using the command: hosted-engine --add-console-password [ INFO ] Running engine-setup on the appliance |- [ INFO ] Stage: Initializing |- [ INFO ] Stage: Environment setup |- Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-wsp.conf', '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/root/ovirt-engine-answers', '/root/heanswers.conf'] |- Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20160912095012-9icp3w.log |- Version: otopi-1.5.1 (otopi-1.5.1-3.el7ev) |- [ INFO ] Stage: Environment packages setup |- [ INFO ] Stage: Programs detection |- [ INFO ] Stage: Environment setup |- [ INFO ] Stage: Environment customization |- |- --== PRODUCT OPTIONS ==-- |- |- Please note: Data Warehouse is required for the engine. If you choose to not configure it on this host, you have to configure it on a remote host, and then configure the engine on this host so that it can access the database of the remote Data Warehouse host. |- Configure Data Warehouse on this host (Yes, No) [Yes]: [ ERROR ] Failed to execute stage 'Environment customization': End of file |- [ INFO ] Stage: Clean up |- Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160912095012-9icp3w.log |- [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160912095013-setup.conf' |- [ INFO ] Stage: Pre-termination |- [ INFO ] Stage: Termination |- [ ERROR ] Execution of setup failed |- HE_APPLIANCE_ENGINE_SETUP_FAIL [ ERROR ] Engine setup failed on the appliance [ ERROR ] Failed to execute stage 'Closing up': Engine setup failed on the appliance Please check its log on the appliance. [ INFO ] Stage: Clean up [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20160912165015.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: this system is not reliable, please check the issue, fix and redeploy Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160912163942-yqnecp.log Version-Release number of selected component (if applicable): Host: ovirt-vmconsole-1.0.4-1.el7ev.noarch ovirt-setup-lib-1.0.1-1.el7ev.noarch qemu-kvm-rhev-2.3.0-31.el7_2.21.x86_64 ovirt-hosted-engine-setup-1.3.7.3-1.el7ev.noarch sanlock-3.2.4-3.el7_2.x86_64 libvirt-client-1.2.17-13.el7_2.5.x86_64 mom-0.5.6-1.el7ev.noarch ovirt-host-deploy-1.4.1-1.el7ev.noarch vdsm-4.17.35-1.el7ev.noarch rhevm-appliance-20160731.0-1.el7ev.noarch rhevm-sdk-python-3.6.9.1-1.el7ev.noarch ovirt-hosted-engine-ha-1.3.5.8-1.el7ev.noarch rhev-release-3.6.9-2-001.noarch ovirt-vmconsole-host-1.0.4-1.el7ev.noarch Linux version 3.10.0-327.28.3.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC) ) #1 SMP Fri Aug 12 13:21:05 EDT 2016 Linux 3.10.0-327.28.3.el7.x86_64 #1 SMP Fri Aug 12 13:21:05 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.2 (Maipo) How reproducible: 100% Steps to Reproduce: 1.Install el7.2 with latest components of 3.6.9 and rhevm-appliance-20160831.0-1.el7ev.noarch on host. 2.Deploy hosted-engine using disk option rhevm-appliance-20160831.0-1.el7ev.noarch. 3. Actual results: Deployment fails. [ ERROR ] Failed to execute stage 'Environment customizatio n': End of file Expected results: Deployment should pass. Additional info: