[Users] Progress on image operations (dd & USR1 signal)
by Ernest Beinrohr
Hi, I am using ovirt 3.2 and noticed that during image operations (move,
copy)
the user has no progress report. This is painful, especially if the
images are large
or the storage is slow.
Vdsm uses 'dd' to transfer images and dd provides a simple progress
report, when
it receives the USR1 signal. Could this be uses to provide the user with
some kind
of progress?
Right now i would do it with myself with strace and kill, but ovirt/vdsm
detects an
stderr output and reports a failure.
$ strace -ff -etrace=write -p `pidof dd` 2>&1 | grep -v 'write(1'
# then, in a second terminal I send the signal
$ killall -USR1 dd
Process 8706 attached - interrupt to quit
--- SIGUSR1 (User defined signal 1) @ 0 (0) ---
write(2, "14022+0 records in\n14021+0 recor"..., 39) = 39
write(2, "14702084096 bytes (15 GB) copied", 32) = 32
write(2, ", 2189.75 s, 6.7 MB/s\n", 22) = 22
--
Ernest Beinrohr, AXON PRO
Ing <http://www.beinrohr.sk/ing.php>, RHCE
<http://www.beinrohr.sk/rhce.php>, RHCVA
<http://www.beinrohr.sk/rhce.php>, LPIC
<http://www.beinrohr.sk/lpic.php>, +421-2--6241-0360
<callto://+421-2--6241-0360>, +421-903--482-603 <callto://+421-903--482-603>
icq:28153343, skype:oernii-work <callto://oernii-work>,
jabber:oernii@jabber.org
------------------------------------------------------------------------
“The bureaucracy is expanding to meet the needs of the expanding
bureaucracy.” ― Oscar Wilde
11 years, 1 month
[Users] oVirt 3.2 and 3.2.1: unable to attach cd
by Gianluca Cecchi
Hello,
lastly with 3.2 and 3.2.1 on F18 hosts I'm not able to attach cd
At the window, after selecting iso and click OK I get:
Error while executing action Change CD: Drive image file could not be found
In webadmin gui events list I get:
Failed to change disk in VM winxp (Host: local_host, User: admin@internal).
It happens with all iso files I already used before.
ISO_DOMAIN is up and they are listed in IMAGES pane
engine-iso-uploader.log
2013-03-15 23:48:24::INFO::engine-iso-uploader::1031::root::
virtio-win-floppies.iso uploaded successfully
In engine.log
2013-03-15 23:48:56,625 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(ajp--127.0.0.1-8702-2) [432e3405] Failed in ChangeDiskVDS method
2013-03-15 23:48:56,626 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(ajp--127.0.0.1-8702-2) [432e3405] Error code imageErr and error
message VDSGenericException: VDSErrorException: Failed to
ChangeDiskVDS, error = Drive image file Bad volume specification
/rhev/data-center/65c9777e-23f1-4f04-8cea-e7c8871dc88b/52739fc1-2d01-48a0-8f3b-415301ba035c/images/11111111-1111-1111-1111-111111111111/virtio-win-floppies.iso
could not be found
2013-03-15 23:48:56,627 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(ajp--127.0.0.1-8702-2) [432e3405] Command
org.ovirt.engine.core.vdsbroker.vdsbroker.ChangeDiskVDSCommand return
value
org.ovirt.engine.core.vdsbroker.vdsbroker.OneVmReturnForXmlRpc@51bde37c
2013-03-15 23:48:56,627 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(ajp--127.0.0.1-8702-2) [432e3405] HostName = local_host
2013-03-15 23:48:56,632 ERROR
[org.ovirt.engine.core.vdsbroker.VDSCommandBase]
(ajp--127.0.0.1-8702-2) [432e3405] Command ChangeDiskVDS execution
failed. Exception: VDSErrorException: VDSGenericException:
VDSErrorException: Failed to ChangeDiskVDS, error = Drive image file
Bad volume specification
/rhev/data-center/65c9777e-23f1-4f04-8cea-e7c8871dc88b/52739fc1-2d01-48a0-8f3b-415301ba035c/images/11111111-1111-1111-1111-111111111111/virtio-win-floppies.iso
could not be found
2013-03-15 23:48:56,632 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ChangeDiskVDSCommand]
(ajp--127.0.0.1-8702-2) [432e3405] FINISH, ChangeDiskVDSCommand, log
id: 3b2e220e
2013-03-15 23:48:56,633 ERROR
[org.ovirt.engine.core.bll.ChangeDiskCommand] (ajp--127.0.0.1-8702-2)
[432e3405] Command org.ovirt.engine.core.bll.ChangeDiskCommand throw
Vdc Bll exception. With error message VdcBLLException:
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
VDSGenericException: VDSErrorException: Failed to ChangeDiskVDS, error
= Drive image file Bad volume specification
/rhev/data-center/65c9777e-23f1-4f04-8cea-e7c8871dc88b/52739fc1-2d01-48a0-8f3b-415301ba035c/images/11111111-1111-1111-1111-111111111111/virtio-win-floppies.iso
could not be found
2013-03-15 23:48:56,639 ERROR
[org.ovirt.engine.core.bll.ChangeDiskCommand] (ajp--127.0.0.1-8702-2)
[432e3405] Transaction rolled-back for command:
org.ovirt.engine.core.bll.ChangeDiskCommand.
In fact there is no iso image where it searches for...
# ll /rhev/data-center/65c9777e-23f1-4f04-8cea-e7c8871dc88b/52739fc1-2d01-48a0-8f3b-415301ba035c/images/11111111-1111-1111-1111-111111111111/virtio-win-floppies.iso
ls: cannot access
/rhev/data-center/65c9777e-23f1-4f04-8cea-e7c8871dc88b/52739fc1-2d01-48a0-8f3b-415301ba035c/images/11111111-1111-1111-1111-111111111111/virtio-win-floppies.iso:
No such file or directory
df -h gives:
tekkaman.localdomain.local:/ISO 53G 31G 20G 62%
/rhev/data-center/mnt/tekkaman.localdomain.local:_ISO
# ll /rhev/data-center/
total 16
drwxr-xr-x. 2 vdsm kvm 4096 Jan 26 18:51 63384f91-1af6-43e4-b10b-9989a0ed3231
drwxr-xr-x. 2 vdsm kvm 4096 Mar 15 23:26 65c9777e-23f1-4f04-8cea-e7c8871dc88b
drwxr-xr-x. 2 vdsm kvm 4096 Feb 10 23:23 hsm-tasks
drwxr-xr-x. 3 vdsm kvm 4096 Feb 19 23:12 mnt
but
# ll /rhev/data-center/65c9777e-23f1-4f04-8cea-e7c8871dc88b/
total 8
lrwxrwxrwx. 1 vdsm kvm 64 Mar 15 23:26
0a8035e6-e41d-40ff-a154-e0a374f264b2 ->
/rhev/data-center/mnt/_DATA/0a8035e6-e41d-40ff-a154-e0a374f264b2
lrwxrwxrwx. 1 vdsm kvm 64 Mar 15 23:26 mastersd ->
/rhev/data-center/mnt/_DATA/0a8035e6-e41d-40ff-a154-e0a374f264b2
and
# ll /rhev/data-center/63384f91-1af6-43e4-b10b-9989a0ed3231/
total 0
and
# ll /rhev/data-center/mnt/tekkaman.localdomain.local:_ISO
total 4
drwxr-xr-x. 4 vdsm kvm 4096 Feb 10 23:27 52739fc1-2d01-48a0-8f3b-415301ba035c
# ll /rhev/data-center/mnt/tekkaman.localdomain.local:_ISO/52739fc1-2d01-48a0-8f3b-415301ba035c/images/11111111-1111-1111-1111-111111111111
total 394192
-rw-r-----. 1 vdsm kvm 14024704 Feb 16 00:27 spice-guest-tools-0.3.iso
-rw-r-----. 1 vdsm kvm 6404096 Mar 9 09:53 spice-guest-tools-0.52.iso
-rw-r-----. 1 vdsm kvm 59838464 Mar 15 23:48 virtio-win-floppies.iso
-rw-r-----. 1 vdsm kvm 323375104 Feb 15 19:35 winxp_sp3.iso
I don't know why it tries to go under data domain to search for iso images....
What can I do?
Thanks,
Gianluca
11 years, 1 month
[Users] openvswitch intergration status
by Jiri Belka
Hi,
is there a plan to integrate openvswitch, if so what's status?
Basic bridging sucks, and now everything is virtual, no? :)
Maybe some benefits:
* decreases cost for special (legacy) enterprise switches
* virtualization buzzword included
* one can simulate switch in ovirt
(that was my start to investigate, i wanted to have a trunk port
pointing to virtualized FW and couple of vlans with guests, not
possible right now in ovirt, each vlan = one iface)
* there's backward compatibility
- see http://packages.debian.org/sid/openvswitch-brcompat
Let's be hype :D
jbelka
11 years, 1 month
Re: [Users] [EL6 RPMS] new nightly ovirt rpms
by Dave Neary
Hi Itamar,
On 03/15/2013 11:50 AM, Itamar Heim wrote:
> fyi - ovirt 3.2.1 will release .el6 rpms as well.
> (more work needed for ubuntu, but cleanups in the works to accomodate as
> well)
I know that several members of the list are willing to be guinea pigs
for very early testing of Ubuntu/Debian support - is there a way we can
involve people specifically for this?
Thanks!
Dave.
--
Dave Neary - Community Action and Impact
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
11 years, 1 month
[Users] BUG: soft lockup
by suporte＠logicworks.pt
------=_Part_1216_16598823.1363371726540
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
I have a host that have this error BUG: soft lockup - CPU#4 stuck for 22s! [sh: 1534], and the host died
this host was installed from fedora18 minimum installation, kernel version 3.8.2-206.fc18.x86_64. I have another host with the same configuration, and have no errors, until now.
Any idea?
------=_Part_1216_16598823.1363371726540
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: verdana,helvetica,sans-serif; font-size: 10pt; color: #330066'>I have a host that have this error BUG: soft lockup - CPU#4 stuck for 22s! [sh: 1534], and the host died<br><br>this host was installed from fedora18 minimum installation, kernel version 3.8.2-206.fc18.x86_64. I have another host with the same configuration, and have no errors, until now.<br><br>Any idea?<br></div></body></html>
------=_Part_1216_16598823.1363371726540--
11 years, 1 month
[Users] ovirt node 2.6.1 installation succeeding, but not booting on Gateway SX2370
by Ian Forde
Hi all -
I've got a couple of Gateway SX2370 desktops that I'm using as hypervisors.
Each can take up to 16GB RAM, and are small, both currently running CentOS
6.3 with the Dreyou repo for VDSM and work great. My next plan was to use
ovirt-node booted from an SD card on them, so I:
. Downloaded ovirt node 2.6.1
. Burned it to a USB stick from my CentOS 6 desktop using
livecd-iso-to-disk.
. Booted the stick successfully on the Gateway box (although it saw it as
EFI - we'll get to that in a second) and was able to install ovirt-node to
the SD card.
. Shut the box down
. Tried to boot the SD card
. The system reports no hard disk upon boot.
The BIOS sees it as an EFI device, so I believe that it can't find the EFI
partition, and dies. The funny thing is that that same SD card will boot
on boxes that don't have EFI or UEFI. And unfortunately, there's no way in
the BIOS to disable EFI detection on hard disks. And it won't let me mark
the SD card as "non-EFI" so that I can have a sane "legacy" boot. And even
so, I don't know how to defeat its detection, which is probably picking up
on the presence of GPT on the SD card to make its determination.
Anyhoo - here's how I solved it. From seeing various RH entries in
bugzilla over the last year and a half regarding EFI, I decided to cheat,
as it doesn't like the bootable partition #2:
. Create a FAT32 filesystem on partition 1 of the SD card
. Create the directory /EFI in partition 1, and copy the contents of
<ovirt-node-iso>:/boot/EFI/ to it.
. Edit partition1:/EFI/BOOT/BOOTX64.conf and partition1:/EFI/BOOT/grub.cfg
to better reflect what's really on the disk. (I was skimming the thread
and post referenced at
http://lists.ovirt.org/pipermail/users/2012-February/006279.html for info.)
That got me a 2nd bootable entry in my BIOS, which I was able to set to
default and boot from successfully (despite a subsequent warning about
secure boot not being available).
So here's my question: Is there a way that I can submit info back about
the ovirt-node install that can help debug the stock install of ovirt-node
getting media to boot on a box that won't let me disable EFI?
-Ian
11 years, 1 month
[Users] Weird errors when trying to connect to an iSCSI target.
by noc
I have been able to connect to this iSCSI target before but now I'm
getting some weird errors, see attached vdsm.log but in short its about
the following:
Thread-161303::DEBUG::2013-03-07
09:54:14,401::task::568::TaskManager.Task::(_updateState)
Task=`182a27fe-dfb0-4e68-965e-c77b61050da9`::moving from state init ->
state preparing
Thread-161303::INFO::2013-03-07
09:54:14,402::logUtils::41::dispatcher::(wrapper) Run and protect:
discoverSendTargets(con={'connection': '192.168.4.234', 'password':
'******', 'port': '3260', 'user': ''}, options=None)
Thread-161303::DEBUG::2013-03-07
09:54:14,402::misc::84::Storage.Misc.excCmd::(<lambda>) '/usr/bin/sudo
-n /sbin/iscsiadm -m discoverydb -t sendtargets -I default -p
192.168.4.234:3260 --op=new' (cwd None)
Thread-161303::DEBUG::2013-03-07
09:54:14,428::misc::84::Storage.Misc.excCmd::(<lambda>) SUCCESS: <err> =
''; <rc> = 0
Thread-161303::DEBUG::2013-03-07
09:54:14,428::misc::84::Storage.Misc.excCmd::(<lambda>) '/usr/bin/sudo
-n /sbin/iscsiadm -m discoverydb -t sendtargets -I default -p
192.168.4.234:3260 -n node.startup -v manual --op=update' (cwd None)
Thread-161303::DEBUG::2013-03-07
09:54:14,452::misc::84::Storage.Misc.excCmd::(<lambda>) FAILED: <err> =
'iscsiadm: Cannot modify node.startup. Invalid param name.\n'; <rc> = 7
Thread-161303::DEBUG::2013-03-07
09:54:14,453::misc::84::Storage.Misc.excCmd::(<lambda>) '/usr/bin/sudo
-n /sbin/iscsiadm -m iface' (cwd None)
Thread-161303::DEBUG::2013-03-07
09:54:14,476::misc::84::Storage.Misc.excCmd::(<lambda>) SUCCESS: <err> =
''; <rc> = 0
Thread-161303::DEBUG::2013-03-07
09:54:14,477::misc::84::Storage.Misc.excCmd::(<lambda>) '/usr/bin/sudo
-n /sbin/iscsiadm -m discoverydb -t sendtargets -I default -p
192.168.4.234:3260 --discover' (cwd None)
Thread-161303::DEBUG::2013-03-07
09:54:14,512::misc::84::Storage.Misc.excCmd::(<lambda>) FAILED: <err> =
'iscsiadm: No portals found\n'; <rc> = 21
Thread-161303::DEBUG::2013-03-07
09:54:14,516::misc::84::Storage.Misc.excCmd::(<lambda>) '/usr/bin/sudo
-n /sbin/iscsiadm -m iface' (cwd None)
Thread-161303::DEBUG::2013-03-07
09:54:14,541::misc::84::Storage.Misc.excCmd::(<lambda>) SUCCESS: <err> =
''; <rc> = 0
Thread-161303::DEBUG::2013-03-07
09:54:14,541::misc::84::Storage.Misc.excCmd::(<lambda>) '/usr/bin/sudo
-n /sbin/iscsiadm -m discoverydb -t sendtargets -I default -p
192.168.4.234:3260 --op=delete' (cwd None)
Thread-161303::DEBUG::2013-03-07
09:54:14,565::misc::84::Storage.Misc.excCmd::(<lambda>) SUCCESS: <err> =
''; <rc> = 0
Thread-161303::ERROR::2013-03-07
09:54:14,566::hsm::2799::Storage.HSM::(discoverSendTargets) Discovery failed
Traceback (most recent call last):
File "/usr/share/vdsm/storage/hsm.py", line 2797, in discoverSendTargets
targets = iscsi.discoverSendTargets(iface, portal, cred)
File "/usr/share/vdsm/storage/iscsi.py", line 202, in discoverSendTargets
targets = iscsiadm.discoverydb_discover(discoverType, iface.name,
portalStr)
File "/usr/share/vdsm/storage/iscsiadm.py", line 213, in
discoverydb_discover
raise IscsiDiscoverdbError(rc, out, err)
IscsiDiscoverdbError: (21, [], ['iscsiadm: No portals found'])
Thread-161303::ERROR::2013-03-07
09:54:14,567::task::833::TaskManager.Task::(_setError)
Task=`182a27fe-dfb0-4e68-965e-c77b61050da9`::Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 840, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/logUtils.py", line 42, in wrapper
res = f(*args, **kwargs)
File "/usr/share/vdsm/storage/hsm.py", line 2800, in discoverSendTargets
raise se.iSCSIDiscoveryError(portal, e)
Running the commands in a shell indeed gives the errors shown.
I have a wild guess but what interface is -I default referring to?
I had more than one interface activated for this host but moved it to a
cluster which didn't have the network definitions and removed the now
invalid networks from the host. Just checked with tcpdump and the
traffic is going through ovirtmgmt interface and the storage is responding.
/var/lib/iscsi isn't filled with info, only
sendtargets/target_ip_address/st_config
Joop
--
irc: jvandewege
11 years, 1 month
[Users] Cannot add host - non-responsive.
by snmishra＠linux.vnet.ibm.com
I am trying to add a fedora18 host to an engine that was built from
source. SElinux and firewalld are disabled/stopped on both the fedora
boxes. I can ping between the two machines using IP and FQDN. But when
I go to add the host it gets connection refused error and goes
non-responsive. Here are the engine logs.
Any Clues?
Sharad Mishra
2013-03-15 01:21:07,208 INFO
[org.ovirt.engine.core.bll.AddVdsCommand] (http--0.0.0.0-8700-1)
[2ebde801] Running command: AddVdsCommand internal: false. Entities
affected : ID: 99408929-82cf-4dc7-a532-9d998063fa95 Type: VdsGroups
2013-03-15 01:21:07,279 INFO
[org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (http--0.0.0.0-8700-1)
Running command: AddVdsSpmIdCommand internal: true. Entities affected
: ID: f66bcf41-56bc-4ac9-b702-c5674060a1a3 Type: VDS
2013-03-15 01:21:07,293 INFO
[org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (http--0.0.0.0-8700-1)
Lock freed to object EngineLock [exclusiveLocks= key:
5849b030-626e-47cb-ad90-3ce782d831b3 value: REGISTER_VDS
, sharedLocks= ]
2013-03-15 01:21:07,297 ERROR
[org.ovirt.engine.core.vdsbroker.ResourceManager]
(http--0.0.0.0-8700-1) Cannot get vdsManager for
vdsid=f66bcf41-56bc-4ac9-b702-c5674060a1a3
2013-03-15 01:21:07,313 INFO
[org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand]
(http--0.0.0.0-8700-1) START, RemoveVdsVDSCommand(HostName = ovirt2,
HostId = f66bcf41-56bc-4ac9-b702-c5674060a1a3), log id: 4a95fb09
2013-03-15 01:21:07,314 ERROR
[org.ovirt.engine.core.vdsbroker.ResourceManager]
(http--0.0.0.0-8700-1) Cannot get vdsManager for
vdsid=f66bcf41-56bc-4ac9-b702-c5674060a1a3
2013-03-15 01:21:07,315 INFO
[org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand]
(http--0.0.0.0-8700-1) FINISH, RemoveVdsVDSCommand, log id: 4a95fb09
2013-03-15 01:21:07,317 ERROR
[org.ovirt.engine.core.vdsbroker.ResourceManager]
(http--0.0.0.0-8700-1) Cannot get vdsManager for
vdsid=f66bcf41-56bc-4ac9-b702-c5674060a1a3
2013-03-15 01:21:07,333 INFO
[org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand]
(http--0.0.0.0-8700-1) START, AddVdsVDSCommand(HostName = ovirt2,
HostId = f66bcf41-56bc-4ac9-b702-c5674060a1a3), log id: 2621f1c9
2013-03-15 01:21:07,334 INFO
[org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand]
(http--0.0.0.0-8700-1) AddVds - entered , starting logic to add VDS
f66bcf41-56bc-4ac9-b702-c5674060a1a3
2013-03-15 01:21:07,350 INFO
[org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand]
(http--0.0.0.0-8700-1) AddVds - VDS
f66bcf41-56bc-4ac9-b702-c5674060a1a3 was added, will try to add it to
the resource manager
2013-03-15 01:21:07,354 INFO
[org.ovirt.engine.core.vdsbroker.VdsManager] (http--0.0.0.0-8700-1)
Entered VdsManager constructor
2013-03-15 01:21:07,360 INFO
[org.ovirt.engine.core.vdsbroker.VdsManager] (http--0.0.0.0-8700-1)
Initialize vdsBroker (9.27.28.20,54,321)
2013-03-15 01:21:07,398 INFO
[org.ovirt.engine.core.vdsbroker.ResourceManager]
(http--0.0.0.0-8700-1) VDS f66bcf41-56bc-4ac9-b702-c5674060a1a3 was
added to the Resource Manager
2013-03-15 01:21:07,399 INFO
[org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand]
(http--0.0.0.0-8700-1) FINISH, AddVdsVDSCommand, log id: 2621f1c9
2013-03-15 01:21:10,499 WARN
[org.ovirt.engine.core.vdsbroker.VdsManager]
(DefaultQuartzScheduler_Worker-8) Failed to refresh VDS , vds =
f66bcf41-56bc-4ac9-b702-c5674060a1a3 : ovirt2, VDS Network Error,
continuing.
java.net.ConnectException: Connection refused
2013-03-15 01:21:13,529 WARN
[org.ovirt.engine.core.vdsbroker.VdsManager]
(DefaultQuartzScheduler_Worker-10) Failed to refresh VDS , vds =
f66bcf41-56bc-4ac9-b702-c5674060a1a3 : ovirt2, VDS Network Error,
continuing.
java.net.ConnectException: Connection refused
2013-03-15 01:21:16,556 ERROR
[org.ovirt.engine.core.vdsbroker.VdsManager]
(DefaultQuartzScheduler_Worker-4) Server failed to respond, vds_id =
f66bcf41-56bc-4ac9-b702-c5674060a1a3, vds_name = ovirt2, error =
java.net.ConnectException: Connection refused
2013-03-15 01:21:16,577 INFO
[org.ovirt.engine.core.bll.VdsEventListener] (pool-10-thread-8)
ResourceManager::vdsNotResponding entered for Host
f66bcf41-56bc-4ac9-b702-c5674060a1a3, 9.27.28.20
2013-03-15 01:21:16,644 WARN
[org.ovirt.engine.core.bll.VdsNotRespondingTreatmentCommand]
(pool-10-thread-8) [734218b6] CanDoAction of action
VdsNotRespondingTreatment failed. Reasons:VDS_FENCE_DISABLED
11 years, 1 month
[Users] ovirt 3.2 all-in-one setup always fails
by Alex Leonhardt
Hi,
The setup keeps failing at "waitforhostup" with :
Installing:
AIO: Validating CPU Compatibility... [ DONE ]
AIO: Adding firewall rules... [ DONE ]
Configuring oVirt Engine... [ DONE ]
Configuring JVM... [ DONE ]
Creating CA... [ DONE ]
Updating ovirt-engine service... [ DONE ]
Setting Database Configuration... [ DONE ]
Setting Database Security... [ DONE ]
Creating Database... [ DONE ]
Updating the Default Data Center Storage Type... [ DONE ]
Editing oVirt Engine Configuration... [ DONE ]
Editing Postgresql Configuration... [ DONE ]
Configuring the Default ISO Domain... [ DONE ]
Configuring Firewall... [ DONE ]
Starting ovirt-engine Service... [ DONE ]
Configuring HTTPD... [ DONE ]
AIO: Creating storage directory... [ DONE ]
AIO: Adding Local Datacenter and cluster... [ DONE ]
AIO: Adding Local host (This may take several minutes)... [ ERROR ]
Error: Host was found in a 'Failed' state. Please check engine and
bootstrap installation logs.
Please check log file
/var/log/ovirt-engine/engine-setup_2013_03_08_14_17_42.log for more
information
#####
2013-03-08 14:22:43::DEBUG::setup_sequences::59::root:: running
waitForHostUp
2013-03-08 14:22:43::DEBUG::all_in_one_100::303::root:: Waiting for host to
become operational
2013-03-08 14:22:43::DEBUG::all_in_one_100::306::root:: current host status
is: installing
2013-03-08 14:22:43::DEBUG::all_in_one_100::317::root:: Traceback (most
recent call last):
File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line
314, in isHostUp
raise Exception(INFO_CREATE_HOST_WAITING_UP)
Exception: Waiting for the host to start
2013-03-08 14:22:48::DEBUG::all_in_one_100::303::root:: Waiting for host to
become operational
2013-03-08 14:22:49::DEBUG::all_in_one_100::306::root:: current host status
is: install_failed
2013-03-08 14:22:49::DEBUG::all_in_one_100::317::root:: Traceback (most
recent call last):
File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line
312, in isHostUp
raise utils.RetryFailException(ERROR_CREATE_HOST_FAILED)
RetryFailException: Error: Host was found in a 'Failed' state. Please check
engine and bootstrap installation logs.
2013-03-08 14:22:49::DEBUG::setup_sequences::62::root:: Traceback (most
recent call last):
File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 60, in run
function()
File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line
300, in waitForHostUp
utils.retry(isHostUp, tries=120, timeout=600, sleep=5)
File "/usr/share/ovirt-engine/scripts/common_utils.py", line 1010, in
retry
raise e
RetryFailException: Error: Host was found in a 'Failed' state. Please check
engine and bootstrap installation logs.
2013-03-08 14:22:49::DEBUG::engine-setup::1934::root:: *** The following
params were used as user input:
I have the full log if required ?? Any help would be appreciated.
The options used were :
oVirt Engine will be installed using the following configuration:
=================================================================
override-httpd-config: yes
http-port: 80
https-port: 443
host-fqdn: stphv01
auth-pass: ********
org-name: LOCAL
application-mode: both
default-dc-type: NFS
db-remote-install: local
db-local-pass: ********
nfs-mp: /exports/iso
override-firewall: None
config-allinone: yes
storage-path: /vmfs/ovirt
superuser-pass: ********
Alex
--
| RHCE | Senior Systems Engineer | www.vcore.co | www.vsearchcloud.com |
11 years, 1 month
