How exactly did you upgrade?
Usually yum upgrade will not touch ovirt-engine packages as it is in yum
From which version to which version have you upgraded?
Have you run engine-upgrade utility?
If you did not, please run it.
If you did, please attach logs from
It seems like an old bug.
Since oVirt3.1 a lot of bugs were fixed in the edit nic dialog.
Maybe consider using ovirt3.2?
- Original Message -
From: Vincent Van der Kussen vinc...@vanderkussen.org
Sent: Wednesday, April 3, 2013 9:38:23 AM
I did a yum update and rebooted.
engine-upgrade was run on 24-March
When run now, it states that there are no updates available.
[root@reliant ~]# engine-upgrade
Loaded plugins: versionlock
Checking for updates... (This may take several minutes)
No updates available
On 04/04/2013 09:45 PM, Eduardo Ramos wrote:
I'm trying to connect my ovirt-engine in a samba4 server. Samba4 is
ActiveDirectory complaint. But when I use engine-manage-domains, it
returns me a strange message:
[root@ovirt-dir eduardo]# engine-manage-domains -action=add
OK... you are running a very old version of engine (3.1).
The upgrade did not upgraded into 3.2, so nothing as far as I know should have
But the .keystore permissions is owned by root now, so some other package
(maybe selinux-policy) changed permissions...
The simplest way to
Right, links in sdk entities are used only for convenient tracking of objects
sdk itself abstracts HTTP internals, and expose decorators for
where every collection decorator has list()/get()/add()/etc. methods for
objects and entity's
After following the steps in http://www.ovirt.org/Building_oVirt_engine, I
met some problems in deploying it.
Here's the status while I visit
HTTP Status 500 -
*type* Exception report
Ok, I'll do the upgrade some day but this raises some questions.
Thanks for the reply!
Now that there are el6 packages available, oVirt could be used in
small production environments by people who can't afford a RHEV subscription
or don't need the support
So I'm wondering if there will be
The primary is iSCSI.
On 04/07/2013 03:59 AM, Shu Ming wrote:
Which type of storage domain was in your engine? NFS? iSCSI? or other
The clue was obviously in the engine.log (FSCK error) but I couldn't
see what was needing an fsck or why this would
Mail list logo