unsupported, make backups, use at your own risk etc...
you could update the db if you can't put the storage domain into maintenance
after that put your hosts into maintenance and out again to remount
find the id of the sd you want to update with:
engine=# select * from
You should not be using the engine and not the root user for the ssh keys.
The actions are delegated to a host and the vdsm user. So you should set-up
ssh keys for the vdsm user on one or all of the hosts (remember to select
this host as proxy host in the gui). Probably the documentation
Thanks, will give that a go
On Thu, Dec 15, 2016 at 12:13 PM, Simone Tiraboschi <stira...@redhat.com>
> On Thu, Dec 15, 2016 at 12:04 PM, Renout Gerrits <m...@renout.nl> wrote:
>> Hi Simone,
>> Do you mean the following?
shutdown all vm's.
Or do you mean something completely different?
On Thu, Dec 15, 2016 at 11:01 AM, Simone Tiraboschi <stira...@redhat.com>
> On Thu, Dec 15, 2016 at 10:33 AM, Renout Gerrits <m...@renout.nl> wrote:
>> Hi All,
I have some troubles starting a VM with cloud-init via the ovirtsdk4.
vm = vms_service.list(search=vm_name)
vm_service = vms_service.vm_service(vm.id)
Depends on your systemd configuration. ovirt-ha-agent and broker daemon's
both log to stdout and it's own logfile. All messages to stdout will go to
journald and be forwarded to /var/log/messages (ForwardToSyslog=yes in
/etc/systemd/journald.conf I think).
So the ovirt-ha-agent doesn't log to
Thanks for the link to the bug!
On Thu, Aug 25, 2016 at 11:45 AM, knarra <kna...@redhat.com> wrote:
> On 08/25/2016 01:20 PM, Renout Gerrits wrote:
> Hi all,
> Is there a way to enable the Gluster Service for a cluster in the hosted
> engine deploy?
Is there a way to enable the Gluster Service for a cluster in the hosted
In the config append you make the gluster service available with:
OVESETUP_CONFIG/applicationMode=str:both. But how would one enable it?
I would like to enable it automatically. Now I change it
In the more recent versions you have to use 'use_cloud_init=True' in the
api, which isn't described in most documentation yet. Maybe thats the
reason it isn't working?
Here's a working snippet:
vm = api.vms.get(name=vm_name)
action = params.Action(
I've got a setup with with ovirt and an equallogic iscsi. Im using the dell
hit drivers. Install all good, after a reboot the storage won't come up.
From the vdsm logs i can see the volume groups can't be found. in the lvm
vgs command the following filter is used: [ '\''r|.*|'\'' ] .
Mail list logo