[ovirt-users] Re: Inconsisten datacenter [urgent]
Thanks. Sorry for the late replay but I had to travel. I've tried your suggestion and now I'm not able to start the engine VM. It's trying to get access for a storage (that I can't tell which is as vdsm only shows the ID and I don't have a way to know the label without the engine). I think that I might need to hack into the database of the engine or reset it and hack in the backup so I can change some values by hand. Any other ideas? ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WE2HVYI5HF3TUFQYO7VA4GJMAIDUP46M/
[ovirt-users] Re: Inconsisten datacenter [urgent]
I'm reluctant to give any advice in a situation as fragile as that, but I believe VDSM doesn't want you to mess with virsh in oVirt: You're supposed to make things happen with hosted-engine and potentially vdsm-tool. Try to see if you can get the management VM down with hosted-engine --vm-shutdown, enable maintenance with hosted-engine --set-maintenance --mode=global (as well as --mode=local for each surviving node) and if that doesn't work then perhaps you'd want to stop the vdsm broker/agent daemons while you do gluster repairs. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/33HZ23PGEPOTHTJ7TDHFTKTHKIERH2OB/
