On Sun, Feb 19, 2017 at 12:42 PM, Денис Мишанин wrote:
> After restarting the ISCSI storage I can not run ovirt-engine in prodation
> use I am looking for help
You have this in vdsm.log:
Is that on the hosted engine? Or separate bare machine?
Am 19.02.2017 11:42 vorm. schrieb "Денис Мишанин" :
After restarting the ISCSI storage I can not run ovirt-engine in prodation
use I am looking for help
On Thu, Feb 16, 2017 at 4:41 PM, Sandro Bonazzola wrote:
> The oVirt Project is pleased to announce the availability of the Second
> Test Compose of oVirt 4.1.1 for testing, as of February 16th, 2017
> This is pre-release software. Please take a look at our community
I must say, I removed the network from the host but the VM's still
have it on their nics and that is the issue and stop me from changing
the networkname. In my opinion nothing affects changing the name when
it's only on the VM and the VM is down.
I hope we can work something out on
Yes I saw it's not ideal to do this using the DB.
It would be nice if it's possible to change it if the using VM's are down.
2017-02-19 14:10 GMT+01:00 Alona Kaplan :
> Hi Matt,
> It won't work.
> The name is the key for the sync operation. So it cannot
It won't work.
The name is the key for the sync operation. So it cannot be out of sync.
If you change the name via the db (which is highly not recommended!), the
network will be considered as a new one.
You will end up (after refreshing the capabilities) with unmanaged network
OK, thanks for this, but what if I change them in the Database and
resync ? As ovirtmgmt is seperate it should be able to control the
I'm curious about that as I think that should work.
2017-02-19 10:30 GMT+01:00 Michael Burman :
> Hi again
This can't be changed.
When the network attached to host, it is used by vdsm and has a
vdsm-'network-name' which in use.
When it used by a VM, virsh using this name, so you can't change it, unless
removing and detaching the network from VM and host.
On Fri, Feb 17, 2017
Mail list logo