[ovirt-users] hosted-engine-deploy error
Simone Tiraboschi
stirabos at redhat.com
Mon Jul 25 08:32:41 UTC 2016
On Mon, Jul 25, 2016 at 5:23 AM, qinglong.dong at horebdata.cn
<qinglong.dong at horebdata.cn> wrote:
> Hi, all:
> I tried to deploy an hosted engine, but I got an error:
> [root at node ~]# hosted-engine --deploy
> ......
> --== CONFIGURATION PREVIEW ==--
>
> Bridge interface : enp6s0f0
> Engine FQDN : engine.horebdata.cn
> Bridge name : ovirtmgmt
> Host address : node.horebdata.cn
> SSH daemon port : 22
> Firewall manager : iptables
> Gateway address : 192.168.1.1
> Host name for web application : node
> Storage Domain type : iscsi
> Host ID : 1
> LUN ID : 23866376332323932
> Image size GB : 25
> iSCSI Portal IP Address : 192.168.128.115
> iSCSI Target Name : engine
> iSCSI Portal port : 3260
> iSCSI Portal user :
> Console type : vnc
> Memory size MB : 4096
> MAC address : 00:16:3e:48:db:9e
> Boot type : cdrom
> Number of CPUs : 2
> ISO image (cdrom boot/cloud-init) : /tmp/1.iso
> 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 ] Configuring the management bridge
> [ INFO ] Creating Volume Group
> [ ERROR ] Error creating Volume Group: Failed to initialize physical device:
> ("[u'/dev/mapper/23866376332323932']",)
> The selected device is already used.
> To create a vg on this device, you must use Force.
> WARNING: This will destroy existing data on the device.
> (Force, Abort)[Abort]? Force
> [ INFO ] Creating Storage Domain
> [ INFO ] Creating Storage Pool
> [ INFO ] Connecting Storage Pool
> [ INFO ] Verifying sanlock lockspace initialization
> [ ERROR ] Failed to execute stage 'Misc configuration': [Errno 101] Network
> is unreachable
> [ INFO ] Stage: Clean up
> [ INFO ] Generating answer file
> '/var/lib/ovirt-hosted-engine-setup/answers/answers-20160725101205.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-20160725100535-h2y78c.log
> [root at node ~]# cat
> /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160725100535-h2y78c.log
> | grep ERROR
> 2016-07-25 10:07:01 ERROR otopi.plugins.gr_he_setup.storage.blockd
> blockd._misc:664 Error creating Volume Group: Failed to initialize physical
> device: ("[u'/dev/mapper/23866376332323932']",)
> 2016-07-25 10:11:59 ERROR otopi.context context._executeMethod:151 Failed to
> execute stage 'Misc configuration': [Errno 101] Network is unreachable
> 2016-07-25 10:12:05 ERROR otopi.plugins.gr_he_setup.core.misc
> misc._terminate:99 Hosted Engine deployment failed: this system is not
> reliable, please check the issue, fix and redeploy
> [root at node ~]# cat /var/log/vdsm/vdsm.log | grep ERROR
> jsonrpc.Executor/4::ERROR::2016-07-25
> 10:07:01,491::lvm::737::Storage.LVM::(_initpvs) pvcreate failed with rc=5
> jsonrpc.Executor/4::ERROR::2016-07-25
> 10:07:01,492::lvm::738::Storage.LVM::(_initpvs) [], [' WARNING: lvmetad is
> running but disabled. Restart lvmetad before enabling it!', '
> /dev/mapper/23866376332323932: read failed after 0 of 4096 at 0:
> Input/output error', ' /dev/mapper/23866376332323932: read failed after 0
> of 4096 at 42949607424: Input/output error', '
> /dev/mapper/23866376332323932: read failed after 0 of 4096 at 42949664768:
> Input/output error', ' WARNING: Error counts reached a limit of 3. Device
> /dev/mapper/23866376332323932 was disabled', ' Failed to wipe new metadata
> area at the start of the /dev/mapper/23866376332323932', ' Failed to add
> metadata area for new physical volume /dev/mapper/23866376332323932', '
> Failed to setup physical volume "/dev/mapper/23866376332323932"']
> jsonrpc.Executor/4::ERROR::2016-07-25
> 10:07:01,492::task::868::Storage.TaskManager.Task::(_setError)
> Task=`a1b55dc1-2c23-4e9f-b81a-43b189557028`::Unexpected error
> jsonrpc.Executor/4::ERROR::2016-07-25
> 10:07:01,496::dispatcher::77::Storage.Dispatcher::(wrapper) {'status':
> {'message': 'Failed to initialize physical device:
> ("[u\'/dev/mapper/23866376332323932\']",)', 'code': 601}}
> jsonrpc.Executor/2::ERROR::2016-07-25
> 10:10:47,116::sdc::140::Storage.StorageDomainCache::(_findDomain) looking
> for unfetched domain caf8a1f7-16db-4a02-9ab9-872987ccef6f
> jsonrpc.Executor/2::ERROR::2016-07-25
> 10:10:47,116::sdc::157::Storage.StorageDomainCache::(_findUnfetchedDomain)
> looking for domain caf8a1f7-16db-4a02-9ab9-872987ccef6f
> jsonrpc.Executor/2::ERROR::2016-07-25
> 10:10:47,156::sdc::146::Storage.StorageDomainCache::(_findDomain) domain
> caf8a1f7-16db-4a02-9ab9-872987ccef6f not found
> jsonrpc.Executor/5::ERROR::2016-07-25
> 10:10:49,671::sdc::140::Storage.StorageDomainCache::(_findDomain) looking
> for unfetched domain ee01d0a7-4e12-4c57-931e-88008980ca98
> jsonrpc.Executor/5::ERROR::2016-07-25
> 10:10:49,671::sdc::157::Storage.StorageDomainCache::(_findUnfetchedDomain)
> looking for domain ee01d0a7-4e12-4c57-931e-88008980ca98
> jsonrpc.Executor/5::ERROR::2016-07-25
> 10:10:49,702::sdc::146::Storage.StorageDomainCache::(_findDomain) domain
> ee01d0a7-4e12-4c57-931e-88008980ca98 not found
> JsonRpc (StompReactor)::ERROR::2016-07-25
> 10:12:05,484::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: unexpected eof
> [root at node2 ~]# ifconfig
> enp6s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> ether 00:1e:67:a5:1b:ee txqueuelen 1000 (Ethernet)
> RX packets 36653 bytes 29439245 (28.0 MiB)
> RX errors 0 dropped 17 overruns 0 frame 0
> TX packets 79820 bytes 103065531 (98.2 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device memory 0xd1160000-d117ffff
>
> enp6s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.1.62 netmask 255.255.255.0 broadcast 192.168.1.255
> ether 00:1e:67:a5:1b:ef txqueuelen 1000 (Ethernet)
> RX packets 7858 bytes 1113116 (1.0 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 468 bytes 21375 (20.8 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device memory 0xd1140000-d115ffff
>
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> loop txqueuelen 0 (Local Loopback)
> RX packets 344 bytes 122776 (119.8 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 344 bytes 122776 (119.8 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> ovirtmgmt: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.128.60 netmask 255.255.255.0 broadcast
> 192.168.128.255
> ether 00:1e:67:a5:1b:ee txqueuelen 0 (Ethernet)
> RX packets 16372 bytes 24322248 (23.1 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 8893 bytes 97964857 (93.4 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
> ether 52:54:00:0a:ae:5c txqueuelen 0 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> It seems that there is something wrong with the network or the
> storage. I got the same error when the iscsi storage was replaced by an nfs
> storage. I have deployed it on the same host using the same storage
> successfully a few days ago, but now I can't. Anyone can help? Thanks!
Hi,
the issue is not related to the storage but just on the capability to
connect to VDSM on localhost.
Can you please follow here?
http://lists.ovirt.org/pipermail/users/2016-July/041415.html
Yaniv, another reproducer.
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
More information about the Users
mailing list