Problem resolved.
The clue was obviously in the engine.log (FSCK error) but I couldn't see
what was needing an fsck or why this would prevent the storage of every
vm from being mounted.
I still dont understand the whole of the ovirt storage mechanism.
More information was in the node vdsm.log
On 04/05/2013 02:31 PM, René Koch (ovido) wrote:
On Tue, 2013-04-02 at 01:27 +0300, Itamar Heim wrote:
On 03/22/2013 04:55 PM, René Koch (ovido) wrote:
Hi,
If you login with PowerUser permission you have 2 tabs (Basic and
Extended) where Basic is the UserPortal and Extended the
PowerUserPortal
I have lost the ability to manage the hosts or VM's using ovirt
engine web interface after performing yum update on the ovirt-engine
host, and on one Fedora 17 host. The data center is offline, and I
can't place the hosts into maintenance mode. I don't think that there
are any actions I can perfo
Which type of storage domain was in your engine? NFS? iSCSI? or other types?
Andy Singleton:
Problem resolved.
The clue was obviously in the engine.log (FSCK error) but I couldn't
see what was needing an fsck or why this would prevent the storage of
every vm from being mounted.
I still dont u
How exactly did you upgrade?
Usually yum upgrade will not touch ovirt-engine packages as it is in yum
version lock.
>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 /var/log/ovirt-engine
5 matches
Mail list logo
