[ovirt-users] problems getting vGPU working

2019-03-04 Thread cmc
Hi,

I'm having trouble getting my Nvidia vGPU to work on a VM.

Setup: RHEV 4.2 on RHEL 7.5, Tesla M60 (switched to graphics mode).
I'm using the NVIDIA-GRID-RHEL-7.5-410.92-410.91-412.16.zip package
from Nvidia.

On the hypervisor, I've installed the
NVIDIA-vGPU-rhel-7.5-410.91.x86_64 rpm. vfio kernel modules are
loaded, nvidia-smi shows the card, and I can see all the vGPUs via
vdsm-client

I've created a CentOS 7.4 VM and added a 'B' type vGPU instance in
'custom properties'. I've configured gridd.conf to point to the
license server and it reports picking up a license in
/var/log/messages. I installed the driver via the .run file
(NVIDIA-Linux-x86_64-410.92-grid.run). The nvidia kernel module is
loaded, but so also is the 'qxl' paravirtual driver.

lspci reports:

00:02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual
graphic card (rev 04)
00:07.0 VGA compatible controller: NVIDIA Corporation GM204GL [Tesla
M60] (rev a1)

The Xorg.0.log reports:

[ 1622.212] (--) PCI:*(0:0:2:0) 1b36:0100:1af4:1100 rev 4, Mem @
0xf000/134217728, 0xfb00/8388608, 0xfb87/8192, I/O @
0xc100/32, BIOS @ 0x/65536
[ 1622.212] (--) PCI: (0:0:7:0) 10de:13f2:10de:1177 rev 161, Mem @
0xfa00/16777216, 0xd000/268435456, 0xf800/33554432, I/O @
0xc000/128, BIOS @ 0x/131072
[ 1622.212] (II) LoadModule: "glx"
[ 1622.212] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 1622.213] (II) Module glx: vendor="X.Org Foundation"
[ 1622.213] compiled for 1.19.3, module version = 1.0.0
[ 1622.213] ABI class: X.Org Server Extension, version 10.0
[ 1622.213] (II) LoadModule: "nvidia"
[ 1622.214] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[ 1622.214] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 1622.214] compiled for 4.0.2, module version = 1.0.0
[ 1622.214] Module class: X.Org Video Driver
[ 1622.214] (II) NVIDIA dlloader X Driver 410.92 Thu Dec 20 04:48:17 CST 2018
[ 1622.214] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 1622.214] (++) using VT number 1
[ 1622.214] (EE) No devices detected.
[ 1622.214] (EE)
Fatal server error:
[ 1622.214] (EE) no screens found(EE)
[ 1622.214] (EE)

Could the qxl module be somehow blocking the nvidia driver? I tried
blacklisting the driver in grub, though that didn't work anyway.

Thanks in advance for any help.

Cam
___
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/HLONOVCAQOK73HYVSEYUG3U4NSGIZ7ZV/


Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-30 Thread cmc
Hi Denis,

>
> That sound really strange. I would suspect some storage problems or
> something. As i told you earlier, output of --vm-status may shed light on
> that issue.

Unfortunately, I can't replicate it at the moment due to the need to
keep the VMs up.

>
>>
>
> Did you tried to migrate form bare metal engine to the hosted engine?
>>

Yes, I used this procedure:

http://www.ovirt.org/documentation/self-hosted/chap-Migrating_from_Bare_Metal_to_an_EL-Based_Self-Hosted_Environment/

Essentially, I used a brand new host not joined to the cluster to
deploy the Hosted Engine VM.

> Engine is responsible for starting those VMs. As you had no engine, there
> was no one to start them. Hosted Engine tools are only responsible for the
> engine VM, not other VMs.

I could not find out why the engine would not start from the logs I looked at.
I didn't have the time to spend on it as I had to get the VMs up and running

> I know, there exists 'bare metal - to - hosted engine' migration procedure,
> but i doubt i knew it good enough. If i remember correctly, you need to take
> a backup of your bare metal engine database, run migration preparation
> script, that will handle spm_id duplications, deploy your first HE host,
> restore database from the backup, deploy more HE hosts. I'm not sure if
> those steps are correct and would better ask Martin about migration process.

I did all these steps as per the URL above, and it did not report any
errors during the process.
The Hosted Engine VM started fine, but it did not appear in the list
of VMs. I think the problem here
was that the list of display types was incorrectly written in the
hosted engine properties file. I was still
left with the issue that the Hosted Engine could not be migrated to
any other host. It was suggested
to re-install the other hosts with the 'deploy hosted engine' option
(which was missing in the official
documentation). This didn't fix the issue so it was suggested that the
host_id was incorrect (as it did not
reflect the SPM ID of the host. I fixed this, then restarted the
cluster...with the result that the engine
would not start, and no VMs started. I could not see any storage
errors in any of the logs I looked at,
but it had not been a problem previously when rebooting hosts (though
I'd never restarted the whole cluster
before). When I used the old bare metal engine, I could get into the
GUI to start the VMs, not sure why
they didn't come up automatically.

I'd like to get it working and will work with the person who takes it
over to do this. I'd like to see it succeed
so eventually we could use oVirt as a proof of concept to replace
VMWare with RHEV. Everyone's help has been great,
but unfortunately it hasn't been entirely smooth sailing (for this
migration) so far.

Thanks again,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Help! No VMs start after reboot of cluster

2017-06-30 Thread cmc
The broker was reported as down - I recall there was something about
'Failed to getVmStats' in the systemctl output. I wasn't sure how to
check the storage from the oVirt point of view (the GUI was
unavailable). When I put the bare metal engine back, it did take a
short while for the storage to become available (it is FC storage).
The agent did not report any errors in systemctl.

On Fri, Jun 30, 2017 at 4:39 PM, David Gossage
<dgoss...@carouselchecks.com> wrote:
>
>
> On Fri, Jun 30, 2017 at 10:34 AM, cmc <iuco...@gmail.com> wrote:
>>
>> Hi Denis,
>>
>> Yes, I did check that and it said it was out of global maintenance
>> ('False' I think it said).
>>
>
> Did you check that the storage the hostedengine VM attaches to mounted and
> is in a healthy state, and that the broker and agent services are running?
> Both have logs that may give some indication if it detects an issue as well.
>
>
>> Thanks,
>>
>> Cam
>>
>> On Fri, Jun 30, 2017 at 4:31 PM, Denis Chaplygin <dchap...@redhat.com>
>> wrote:
>> > Hello!
>> >
>> > On Fri, Jun 30, 2017 at 4:35 PM, cmc <iuco...@gmail.com> wrote:
>> >>
>> >> I restarted my 3 host cluster after setting it into global maintenance
>> >> mode and then shutting down all of the nodes and then bringing them up
>> >> again. I moved it out of global maintenance mode and no VM is running,
>> >> including the hosted engine.
>> >>
>> >> Any help greatly appreciated!
>> >
>> >
>> > Are you sure you are really out of global maintenance? Could you please
>> > post
>> > hosted-engine --vm-status output?
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-30 Thread cmc
I ran 'hosted-engine --vm-start' after trying to ping the engine and
running 'hosted-engine --vm-status' (which said it wasn't running) and
it reported that it was 'destroying storage' and starting the engine,
though it did not start it. I could not see any evidence from
'hosted-engine --vm-status' or logs that it started. By this point I
was in a panic to get VMs running. So I had to fire up the old bare
metal engine. This has been a very disappointing experience. I still
have no idea why the IDs in 'host_id' differed from the spm ID, and
why, when I put the cluster into global maintenance and shutdown all
the hosts, the Hosted Engine did not come up, nor any of the VMs. I
don't feel confident in this any more. If I try the deploying the
Hosted Engine again I am not sure if it will result in the same
non-functional cluster. It gave no error on deployment, but clearly
something was wrong.

I have two questions:

1. Why did the VMs (apart from the Hosted Engine VM) not start on
power up of the hosts? Is it because the hosts were powered down, that
they stay in a down state on power up of the host?

2. Now that I have connected the bare metal engine back to the
cluster, is there a way back, or do I have to start from scratch
again? I imagine there is no way of getting the Hosted Engine running
again. If not, what do I need to 'clean' all the hosts of the remnants
of the failed deployment? I can of course reinitialise the LUN that
the Hosted Engine was on - anything else?

Thanks

On Fri, Jun 30, 2017 at 4:30 PM, Denis Chaplygin <dchap...@redhat.com> wrote:
> Hello!
>
> On Fri, Jun 30, 2017 at 4:19 PM, cmc <iuco...@gmail.com> wrote:
>>
>> Help! I put the cluster into global maintenance, then powered off and
>> then on all of the nodes I have powered off and powered on all the
>> nodes. I have taken it out of global maintenance. No VM has started,
>> including the hosted engine. This is very bad. I am going to look
>> through logs to see why nothing has started. Help greatly appreciated.
>
>
> Global maintenance mode turns off high availability for the hosted engine
> vm. You should either cancel global maintenance or start vm manually with
> hosted-engine --vm-start
>
> Global maintenance was added to allow manual maintenance of the engine VM,
> so in that mode state of the engine VM and engine itself is not managed and
> you a free to stop engine or vm or both, do whatever you like and hosted
> engine tools will not interfere. Obviously when engine VM just dies while
> cluster is in global maintenance (or all nodes reboot, as in your case)
> there is no one to restart it :)
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Help! No VMs start after reboot of cluster

2017-06-30 Thread cmc
Hi Denis,

Yes, I did check that and it said it was out of global maintenance
('False' I think it said).

Thanks,

Cam

On Fri, Jun 30, 2017 at 4:31 PM, Denis Chaplygin <dchap...@redhat.com> wrote:
> Hello!
>
> On Fri, Jun 30, 2017 at 4:35 PM, cmc <iuco...@gmail.com> wrote:
>>
>> I restarted my 3 host cluster after setting it into global maintenance
>> mode and then shutting down all of the nodes and then bringing them up
>> again. I moved it out of global maintenance mode and no VM is running,
>> including the hosted engine.
>>
>> Any help greatly appreciated!
>
>
> Are you sure you are really out of global maintenance? Could you please post
> hosted-engine --vm-status output?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-30 Thread cmc
I've had no other choice but to power up the old bare metal engine to
be able to start the VMs. This is probably really bad but I had to get
the VMs running.
I am guessing now that if the host is shutdown rather than simply
rebooted, that the VMs will not restart on powerup of the host. This
would not have been such a problem if the Hosted Engine started.

So I'm not sure where to go from here...

I guess it is start from scratch again?

On Fri, Jun 30, 2017 at 3:19 PM, cmc <iuco...@gmail.com> wrote:
> Help! I put the cluster into global maintenance, then powered off and
> then on all of the nodes I have powered off and powered on all the
> nodes. I have taken it out of global maintenance. No VM has started,
> including the hosted engine. This is very bad. I am going to look
> through logs to see why nothing has started. Help greatly appreciated.
>
> Thanks,
>
> Cam
>
> On Fri, Jun 30, 2017 at 1:00 PM, cmc <iuco...@gmail.com> wrote:
>> So I can run from any node: hosted-engine --set-maintenance
>> --mode=global. By 'agents', you mean the ovirt-ha-agent, right? This
>> shouldn't affect the running of any VMs, correct? Sorry for the
>> questions, just want to do it correctly and not make assumptions :)
>>
>> Cheers,
>>
>> C
>>
>> On Fri, Jun 30, 2017 at 12:12 PM, Martin Sivak <msi...@redhat.com> wrote:
>>> Hi,
>>>
>>>> Just to clarify: you mean the host_id in
>>>> /etc/ovirt-hosted-engine/hosted-engine.conf should match the spm_id,
>>>> correct?
>>>
>>> Exactly.
>>>
>>> Put the cluster to global maintenance first. Or kill all agents (has
>>> the same effect).
>>>
>>> Martin
>>>
>>> On Fri, Jun 30, 2017 at 12:47 PM, cmc <iuco...@gmail.com> wrote:
>>>> Just to clarify: you mean the host_id in
>>>> /etc/ovirt-hosted-engine/hosted-engine.conf should match the spm_id,
>>>> correct?
>>>>
>>>> On Fri, Jun 30, 2017 at 9:47 AM, Martin Sivak <msi...@redhat.com> wrote:
>>>>> Hi,
>>>>>
>>>>> cleaning metadata won't help in this case. Try transferring the
>>>>> spm_ids you got from the engine to the proper hosted engine hosts so
>>>>> the hosted engine ids match the spm_ids. Then restart all hosted
>>>>> engine services. I would actually recommend restarting all hosts after
>>>>> this change, but I have no idea how many VMs you have running.
>>>>>
>>>>> Martin
>>>>>
>>>>> On Thu, Jun 29, 2017 at 8:27 PM, cmc <iuco...@gmail.com> wrote:
>>>>>> Tried running a 'hosted-engine --clean-metadata" as per
>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1350539, since
>>>>>> ovirt-ha-agent was not running anyway, but it fails with the following
>>>>>> error:
>>>>>>
>>>>>> ERROR:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Failed
>>>>>> to start monitoring domain
>>>>>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>>>>>> during domain acquisition
>>>>>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Traceback (most recent
>>>>>> call last):
>>>>>>   File 
>>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>>>>>> line 191, in _run_agent
>>>>>> return action(he)
>>>>>>   File 
>>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>>>>>> line 67, in action_clean
>>>>>> return he.clean(options.force_cleanup)
>>>>>>   File 
>>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>>>>>> line 345, in clean
>>>>>> self._initialize_domain_monitor()
>>>>>>   File 
>>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>>>>>> line 823, in _initialize_domain_monitor
>>>>>> raise Exception(msg)
>>>>>> Exception: Failed to start monitoring domain
>>>>>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>>>>>> during domain acquisition
>>>>>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Trying to restart agent
>>>>>> WARNING:ovirt_hosted_engine_ha.agent.agent.Agent

[ovirt-users] Help! No VMs start after reboot of cluster

2017-06-30 Thread cmc
Hi,

I restarted my 3 host cluster after setting it into global maintenance
mode and then shutting down all of the nodes and then bringing them up
again. I moved it out of global maintenance mode and no VM is running,
including the hosted engine.

Any help greatly appreciated!

Thanks,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-30 Thread cmc
Help! I put the cluster into global maintenance, then powered off and
then on all of the nodes I have powered off and powered on all the
nodes. I have taken it out of global maintenance. No VM has started,
including the hosted engine. This is very bad. I am going to look
through logs to see why nothing has started. Help greatly appreciated.

Thanks,

Cam

On Fri, Jun 30, 2017 at 1:00 PM, cmc <iuco...@gmail.com> wrote:
> So I can run from any node: hosted-engine --set-maintenance
> --mode=global. By 'agents', you mean the ovirt-ha-agent, right? This
> shouldn't affect the running of any VMs, correct? Sorry for the
> questions, just want to do it correctly and not make assumptions :)
>
> Cheers,
>
> C
>
> On Fri, Jun 30, 2017 at 12:12 PM, Martin Sivak <msi...@redhat.com> wrote:
>> Hi,
>>
>>> Just to clarify: you mean the host_id in
>>> /etc/ovirt-hosted-engine/hosted-engine.conf should match the spm_id,
>>> correct?
>>
>> Exactly.
>>
>> Put the cluster to global maintenance first. Or kill all agents (has
>> the same effect).
>>
>> Martin
>>
>> On Fri, Jun 30, 2017 at 12:47 PM, cmc <iuco...@gmail.com> wrote:
>>> Just to clarify: you mean the host_id in
>>> /etc/ovirt-hosted-engine/hosted-engine.conf should match the spm_id,
>>> correct?
>>>
>>> On Fri, Jun 30, 2017 at 9:47 AM, Martin Sivak <msi...@redhat.com> wrote:
>>>> Hi,
>>>>
>>>> cleaning metadata won't help in this case. Try transferring the
>>>> spm_ids you got from the engine to the proper hosted engine hosts so
>>>> the hosted engine ids match the spm_ids. Then restart all hosted
>>>> engine services. I would actually recommend restarting all hosts after
>>>> this change, but I have no idea how many VMs you have running.
>>>>
>>>> Martin
>>>>
>>>> On Thu, Jun 29, 2017 at 8:27 PM, cmc <iuco...@gmail.com> wrote:
>>>>> Tried running a 'hosted-engine --clean-metadata" as per
>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1350539, since
>>>>> ovirt-ha-agent was not running anyway, but it fails with the following
>>>>> error:
>>>>>
>>>>> ERROR:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Failed
>>>>> to start monitoring domain
>>>>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>>>>> during domain acquisition
>>>>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Traceback (most recent
>>>>> call last):
>>>>>   File 
>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>>>>> line 191, in _run_agent
>>>>> return action(he)
>>>>>   File 
>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>>>>> line 67, in action_clean
>>>>> return he.clean(options.force_cleanup)
>>>>>   File 
>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>>>>> line 345, in clean
>>>>> self._initialize_domain_monitor()
>>>>>   File 
>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>>>>> line 823, in _initialize_domain_monitor
>>>>> raise Exception(msg)
>>>>> Exception: Failed to start monitoring domain
>>>>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>>>>> during domain acquisition
>>>>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Trying to restart agent
>>>>> WARNING:ovirt_hosted_engine_ha.agent.agent.Agent:Restarting agent, 
>>>>> attempt '0'
>>>>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Too many errors
>>>>> occurred, giving up. Please review the log and consider filing a bug.
>>>>> INFO:ovirt_hosted_engine_ha.agent.agent.Agent:Agent shutting down
>>>>>
>>>>> On Thu, Jun 29, 2017 at 6:10 PM, cmc <iuco...@gmail.com> wrote:
>>>>>> Actually, it looks like sanlock problems:
>>>>>>
>>>>>>"SanlockInitializationError: Failed to initialize sanlock, the
>>>>>> number of errors has exceeded the limit"
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Jun 29, 2017 at 5:10 PM, cmc <iuco...@gmail.com> wro

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-30 Thread cmc
So I can run from any node: hosted-engine --set-maintenance
--mode=global. By 'agents', you mean the ovirt-ha-agent, right? This
shouldn't affect the running of any VMs, correct? Sorry for the
questions, just want to do it correctly and not make assumptions :)

Cheers,

C

On Fri, Jun 30, 2017 at 12:12 PM, Martin Sivak <msi...@redhat.com> wrote:
> Hi,
>
>> Just to clarify: you mean the host_id in
>> /etc/ovirt-hosted-engine/hosted-engine.conf should match the spm_id,
>> correct?
>
> Exactly.
>
> Put the cluster to global maintenance first. Or kill all agents (has
> the same effect).
>
> Martin
>
> On Fri, Jun 30, 2017 at 12:47 PM, cmc <iuco...@gmail.com> wrote:
>> Just to clarify: you mean the host_id in
>> /etc/ovirt-hosted-engine/hosted-engine.conf should match the spm_id,
>> correct?
>>
>> On Fri, Jun 30, 2017 at 9:47 AM, Martin Sivak <msi...@redhat.com> wrote:
>>> Hi,
>>>
>>> cleaning metadata won't help in this case. Try transferring the
>>> spm_ids you got from the engine to the proper hosted engine hosts so
>>> the hosted engine ids match the spm_ids. Then restart all hosted
>>> engine services. I would actually recommend restarting all hosts after
>>> this change, but I have no idea how many VMs you have running.
>>>
>>> Martin
>>>
>>> On Thu, Jun 29, 2017 at 8:27 PM, cmc <iuco...@gmail.com> wrote:
>>>> Tried running a 'hosted-engine --clean-metadata" as per
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1350539, since
>>>> ovirt-ha-agent was not running anyway, but it fails with the following
>>>> error:
>>>>
>>>> ERROR:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Failed
>>>> to start monitoring domain
>>>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>>>> during domain acquisition
>>>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Traceback (most recent
>>>> call last):
>>>>   File 
>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>>>> line 191, in _run_agent
>>>> return action(he)
>>>>   File 
>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>>>> line 67, in action_clean
>>>> return he.clean(options.force_cleanup)
>>>>   File 
>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>>>> line 345, in clean
>>>> self._initialize_domain_monitor()
>>>>   File 
>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>>>> line 823, in _initialize_domain_monitor
>>>> raise Exception(msg)
>>>> Exception: Failed to start monitoring domain
>>>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>>>> during domain acquisition
>>>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Trying to restart agent
>>>> WARNING:ovirt_hosted_engine_ha.agent.agent.Agent:Restarting agent, attempt 
>>>> '0'
>>>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Too many errors
>>>> occurred, giving up. Please review the log and consider filing a bug.
>>>> INFO:ovirt_hosted_engine_ha.agent.agent.Agent:Agent shutting down
>>>>
>>>> On Thu, Jun 29, 2017 at 6:10 PM, cmc <iuco...@gmail.com> wrote:
>>>>> Actually, it looks like sanlock problems:
>>>>>
>>>>>"SanlockInitializationError: Failed to initialize sanlock, the
>>>>> number of errors has exceeded the limit"
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Jun 29, 2017 at 5:10 PM, cmc <iuco...@gmail.com> wrote:
>>>>>> Sorry, I am mistaken, two hosts failed for the agent with the following 
>>>>>> error:
>>>>>>
>>>>>> ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
>>>>>> ERROR Failed to start monitoring domain
>>>>>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>>>>>> during domain acquisition
>>>>>> ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
>>>>>> ERROR Shutting down the agent because of 3 failures in a row!
>>>>>>
>>>>>> What could cause these timeouts? Some other service not running?
>>>>>

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-30 Thread cmc
Just to clarify: you mean the host_id in
/etc/ovirt-hosted-engine/hosted-engine.conf should match the spm_id,
correct?

On Fri, Jun 30, 2017 at 9:47 AM, Martin Sivak <msi...@redhat.com> wrote:
> Hi,
>
> cleaning metadata won't help in this case. Try transferring the
> spm_ids you got from the engine to the proper hosted engine hosts so
> the hosted engine ids match the spm_ids. Then restart all hosted
> engine services. I would actually recommend restarting all hosts after
> this change, but I have no idea how many VMs you have running.
>
> Martin
>
> On Thu, Jun 29, 2017 at 8:27 PM, cmc <iuco...@gmail.com> wrote:
>> Tried running a 'hosted-engine --clean-metadata" as per
>> https://bugzilla.redhat.com/show_bug.cgi?id=1350539, since
>> ovirt-ha-agent was not running anyway, but it fails with the following
>> error:
>>
>> ERROR:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Failed
>> to start monitoring domain
>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>> during domain acquisition
>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Traceback (most recent
>> call last):
>>   File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>> line 191, in _run_agent
>> return action(he)
>>   File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>> line 67, in action_clean
>> return he.clean(options.force_cleanup)
>>   File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>> line 345, in clean
>> self._initialize_domain_monitor()
>>   File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>> line 823, in _initialize_domain_monitor
>> raise Exception(msg)
>> Exception: Failed to start monitoring domain
>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>> during domain acquisition
>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Trying to restart agent
>> WARNING:ovirt_hosted_engine_ha.agent.agent.Agent:Restarting agent, attempt 
>> '0'
>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Too many errors
>> occurred, giving up. Please review the log and consider filing a bug.
>> INFO:ovirt_hosted_engine_ha.agent.agent.Agent:Agent shutting down
>>
>> On Thu, Jun 29, 2017 at 6:10 PM, cmc <iuco...@gmail.com> wrote:
>>> Actually, it looks like sanlock problems:
>>>
>>>"SanlockInitializationError: Failed to initialize sanlock, the
>>> number of errors has exceeded the limit"
>>>
>>>
>>>
>>> On Thu, Jun 29, 2017 at 5:10 PM, cmc <iuco...@gmail.com> wrote:
>>>> Sorry, I am mistaken, two hosts failed for the agent with the following 
>>>> error:
>>>>
>>>> ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
>>>> ERROR Failed to start monitoring domain
>>>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>>>> during domain acquisition
>>>> ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
>>>> ERROR Shutting down the agent because of 3 failures in a row!
>>>>
>>>> What could cause these timeouts? Some other service not running?
>>>>
>>>> On Thu, Jun 29, 2017 at 5:03 PM, cmc <iuco...@gmail.com> wrote:
>>>>> Both services are up on all three hosts. The broke logs just report:
>>>>>
>>>>> Thread-6549::INFO::2017-06-29
>>>>> 17:01:51,481::listener::134::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(setup)
>>>>> Connection established
>>>>> Thread-6549::INFO::2017-06-29
>>>>> 17:01:51,483::listener::186::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle)
>>>>> Connection closed
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Cam
>>>>>
>>>>> On Thu, Jun 29, 2017 at 4:00 PM, Martin Sivak <msi...@redhat.com> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> please make sure that both ovirt-ha-agent and ovirt-ha-broker services
>>>>>> are restarted and up. The error says the agent can't talk to the
>>>>>> broker. Is there anything in the broker.log?
>>>>>>
>>>>>> Best regards
>>>>>>
>>>>>> Martin Sivak
>>>>>>
>>>>>

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-30 Thread cmc
Ok, Thanks Martin. It should be feasible to get all VMs onto one host,
so I can do that (unless you recommend just shutting the entire
cluster down at once?). For the engine, I'll shut it down since it
won't migrate to another host, before shutting that host down.

Will let you know how it goes.

Thanks,

Cam

On Fri, Jun 30, 2017 at 9:47 AM, Martin Sivak <msi...@redhat.com> wrote:
> Hi,
>
> cleaning metadata won't help in this case. Try transferring the
> spm_ids you got from the engine to the proper hosted engine hosts so
> the hosted engine ids match the spm_ids. Then restart all hosted
> engine services. I would actually recommend restarting all hosts after
> this change, but I have no idea how many VMs you have running.
>
> Martin
>
> On Thu, Jun 29, 2017 at 8:27 PM, cmc <iuco...@gmail.com> wrote:
>> Tried running a 'hosted-engine --clean-metadata" as per
>> https://bugzilla.redhat.com/show_bug.cgi?id=1350539, since
>> ovirt-ha-agent was not running anyway, but it fails with the following
>> error:
>>
>> ERROR:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Failed
>> to start monitoring domain
>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>> during domain acquisition
>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Traceback (most recent
>> call last):
>>   File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>> line 191, in _run_agent
>> return action(he)
>>   File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>> line 67, in action_clean
>> return he.clean(options.force_cleanup)
>>   File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>> line 345, in clean
>> self._initialize_domain_monitor()
>>   File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>> line 823, in _initialize_domain_monitor
>> raise Exception(msg)
>> Exception: Failed to start monitoring domain
>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>> during domain acquisition
>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Trying to restart agent
>> WARNING:ovirt_hosted_engine_ha.agent.agent.Agent:Restarting agent, attempt 
>> '0'
>> ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Too many errors
>> occurred, giving up. Please review the log and consider filing a bug.
>> INFO:ovirt_hosted_engine_ha.agent.agent.Agent:Agent shutting down
>>
>> On Thu, Jun 29, 2017 at 6:10 PM, cmc <iuco...@gmail.com> wrote:
>>> Actually, it looks like sanlock problems:
>>>
>>>"SanlockInitializationError: Failed to initialize sanlock, the
>>> number of errors has exceeded the limit"
>>>
>>>
>>>
>>> On Thu, Jun 29, 2017 at 5:10 PM, cmc <iuco...@gmail.com> wrote:
>>>> Sorry, I am mistaken, two hosts failed for the agent with the following 
>>>> error:
>>>>
>>>> ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
>>>> ERROR Failed to start monitoring domain
>>>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>>>> during domain acquisition
>>>> ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
>>>> ERROR Shutting down the agent because of 3 failures in a row!
>>>>
>>>> What could cause these timeouts? Some other service not running?
>>>>
>>>> On Thu, Jun 29, 2017 at 5:03 PM, cmc <iuco...@gmail.com> wrote:
>>>>> Both services are up on all three hosts. The broke logs just report:
>>>>>
>>>>> Thread-6549::INFO::2017-06-29
>>>>> 17:01:51,481::listener::134::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(setup)
>>>>> Connection established
>>>>> Thread-6549::INFO::2017-06-29
>>>>> 17:01:51,483::listener::186::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle)
>>>>> Connection closed
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Cam
>>>>>
>>>>> On Thu, Jun 29, 2017 at 4:00 PM, Martin Sivak <msi...@redhat.com> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> please make sure that both ovirt-ha-agent and ovirt-ha-broker services
>>>>>> are restarted and up. The error says the agent can't talk to the
>>>>>> broker. Is there anything in

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-29 Thread cmc
Tried running a 'hosted-engine --clean-metadata" as per
https://bugzilla.redhat.com/show_bug.cgi?id=1350539, since
ovirt-ha-agent was not running anyway, but it fails with the following
error:

ERROR:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Failed
to start monitoring domain
(sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
during domain acquisition
ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Traceback (most recent
call last):
  File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
line 191, in _run_agent
return action(he)
  File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
line 67, in action_clean
return he.clean(options.force_cleanup)
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
line 345, in clean
self._initialize_domain_monitor()
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
line 823, in _initialize_domain_monitor
raise Exception(msg)
Exception: Failed to start monitoring domain
(sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
during domain acquisition
ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Trying to restart agent
WARNING:ovirt_hosted_engine_ha.agent.agent.Agent:Restarting agent, attempt '0'
ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Too many errors
occurred, giving up. Please review the log and consider filing a bug.
INFO:ovirt_hosted_engine_ha.agent.agent.Agent:Agent shutting down

On Thu, Jun 29, 2017 at 6:10 PM, cmc <iuco...@gmail.com> wrote:
> Actually, it looks like sanlock problems:
>
>"SanlockInitializationError: Failed to initialize sanlock, the
> number of errors has exceeded the limit"
>
>
>
> On Thu, Jun 29, 2017 at 5:10 PM, cmc <iuco...@gmail.com> wrote:
>> Sorry, I am mistaken, two hosts failed for the agent with the following 
>> error:
>>
>> ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
>> ERROR Failed to start monitoring domain
>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>> during domain acquisition
>> ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
>> ERROR Shutting down the agent because of 3 failures in a row!
>>
>> What could cause these timeouts? Some other service not running?
>>
>> On Thu, Jun 29, 2017 at 5:03 PM, cmc <iuco...@gmail.com> wrote:
>>> Both services are up on all three hosts. The broke logs just report:
>>>
>>> Thread-6549::INFO::2017-06-29
>>> 17:01:51,481::listener::134::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(setup)
>>> Connection established
>>> Thread-6549::INFO::2017-06-29
>>> 17:01:51,483::listener::186::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle)
>>> Connection closed
>>>
>>> Thanks,
>>>
>>> Cam
>>>
>>> On Thu, Jun 29, 2017 at 4:00 PM, Martin Sivak <msi...@redhat.com> wrote:
>>>> Hi,
>>>>
>>>> please make sure that both ovirt-ha-agent and ovirt-ha-broker services
>>>> are restarted and up. The error says the agent can't talk to the
>>>> broker. Is there anything in the broker.log?
>>>>
>>>> Best regards
>>>>
>>>> Martin Sivak
>>>>
>>>> On Thu, Jun 29, 2017 at 4:42 PM, cmc <iuco...@gmail.com> wrote:
>>>>> I've restarted those two services across all hosts, have taken the
>>>>> Hosted Engine host out of maintenance, and when I try to migrate the
>>>>> Hosted Engine over to another host, it reports that all three hosts
>>>>> 'did not satisfy internal filter HA because it is not a Hosted Engine
>>>>> host'.
>>>>>
>>>>> On the host that the Hosted Engine is currently on it reports in the 
>>>>> agent.log:
>>>>>
>>>>> ovirt-ha-agent ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR
>>>>> Connection closed: Connection closed
>>>>> Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
>>>>> ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR Exception
>>>>> getting service path: Connection closed
>>>>> Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
>>>>> ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent
>>>>> call last):
>>>>> File
>>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/age

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-29 Thread cmc
Hi Denis,

I ran the query as you suggested, just by starting at spm_id=1 and on
up to 3 (the number of hosts I have), and it identified a different
host for each spm_id, indicating that they are indeed unique, so this
looks good.

Regards,

Cam

On Thu, Jun 29, 2017 at 2:07 PM, Denis Chaplygin  wrote:
> Hello!
>
> On Thu, Jun 29, 2017 at 1:22 PM, Martin Sivak  wrote:
>>
>> Change the ids so they are distinct. I need to check if there is a way
>> to read the SPM ids from the engine as using the same numbers would be
>> the best.
>
>
> Host (SPM) ids are not shown in the UI, but you can search on it by typing
> 'spm_id=' into a search box and it will return you host with the
> specified id or nothing if that id is not in use
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-29 Thread cmc
Actually, it looks like sanlock problems:

   "SanlockInitializationError: Failed to initialize sanlock, the
number of errors has exceeded the limit"



On Thu, Jun 29, 2017 at 5:10 PM, cmc <iuco...@gmail.com> wrote:
> Sorry, I am mistaken, two hosts failed for the agent with the following error:
>
> ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
> ERROR Failed to start monitoring domain
> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
> during domain acquisition
> ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
> ERROR Shutting down the agent because of 3 failures in a row!
>
> What could cause these timeouts? Some other service not running?
>
> On Thu, Jun 29, 2017 at 5:03 PM, cmc <iuco...@gmail.com> wrote:
>> Both services are up on all three hosts. The broke logs just report:
>>
>> Thread-6549::INFO::2017-06-29
>> 17:01:51,481::listener::134::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(setup)
>> Connection established
>> Thread-6549::INFO::2017-06-29
>> 17:01:51,483::listener::186::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle)
>> Connection closed
>>
>> Thanks,
>>
>> Cam
>>
>> On Thu, Jun 29, 2017 at 4:00 PM, Martin Sivak <msi...@redhat.com> wrote:
>>> Hi,
>>>
>>> please make sure that both ovirt-ha-agent and ovirt-ha-broker services
>>> are restarted and up. The error says the agent can't talk to the
>>> broker. Is there anything in the broker.log?
>>>
>>> Best regards
>>>
>>> Martin Sivak
>>>
>>> On Thu, Jun 29, 2017 at 4:42 PM, cmc <iuco...@gmail.com> wrote:
>>>> I've restarted those two services across all hosts, have taken the
>>>> Hosted Engine host out of maintenance, and when I try to migrate the
>>>> Hosted Engine over to another host, it reports that all three hosts
>>>> 'did not satisfy internal filter HA because it is not a Hosted Engine
>>>> host'.
>>>>
>>>> On the host that the Hosted Engine is currently on it reports in the 
>>>> agent.log:
>>>>
>>>> ovirt-ha-agent ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR
>>>> Connection closed: Connection closed
>>>> Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
>>>> ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR Exception
>>>> getting service path: Connection closed
>>>> Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
>>>> ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent
>>>> call last):
>>>> File
>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>>>> line 191, in _run_agent
>>>>   return action(he)
>>>> File
>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>>>> line 64, in action_proper
>>>>   return
>>>> he.start_monitoring()
>>>> File
>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>>>> line 411, in start_monitoring
>>>>   
>>>> self._initialize_sanlock()
>>>> File
>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>>>> line 691, in _initialize_sanlock
>>>>
>>>> constants.SERVICE_TYPE + constants.LOCKSPACE_EXTENSION)
>>>> File
>>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>>>> line 162, in get_service_path
>>>>   .format(str(e)))
>>>>   RequestError: Failed
>>>> to get service path: Connection closed
>>>> Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
>>>> ovirt_hosted_engine_ha.agent.agent.Agent ERROR Trying to restart agent
>>>>
>>>> On Thu, Jun 29, 2017 at 1:25 PM, Martin Sivak <msi...@redhat.com> wrote:
>>>>> Hi,
&

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-29 Thread cmc
Sorry, I am mistaken, two hosts failed for the agent with the following error:

ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
ERROR Failed to start monitoring domain
(sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
during domain acquisition
ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
ERROR Shutting down the agent because of 3 failures in a row!

What could cause these timeouts? Some other service not running?

On Thu, Jun 29, 2017 at 5:03 PM, cmc <iuco...@gmail.com> wrote:
> Both services are up on all three hosts. The broke logs just report:
>
> Thread-6549::INFO::2017-06-29
> 17:01:51,481::listener::134::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(setup)
> Connection established
> Thread-6549::INFO::2017-06-29
> 17:01:51,483::listener::186::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle)
> Connection closed
>
> Thanks,
>
> Cam
>
> On Thu, Jun 29, 2017 at 4:00 PM, Martin Sivak <msi...@redhat.com> wrote:
>> Hi,
>>
>> please make sure that both ovirt-ha-agent and ovirt-ha-broker services
>> are restarted and up. The error says the agent can't talk to the
>> broker. Is there anything in the broker.log?
>>
>> Best regards
>>
>> Martin Sivak
>>
>> On Thu, Jun 29, 2017 at 4:42 PM, cmc <iuco...@gmail.com> wrote:
>>> I've restarted those two services across all hosts, have taken the
>>> Hosted Engine host out of maintenance, and when I try to migrate the
>>> Hosted Engine over to another host, it reports that all three hosts
>>> 'did not satisfy internal filter HA because it is not a Hosted Engine
>>> host'.
>>>
>>> On the host that the Hosted Engine is currently on it reports in the 
>>> agent.log:
>>>
>>> ovirt-ha-agent ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR
>>> Connection closed: Connection closed
>>> Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
>>> ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR Exception
>>> getting service path: Connection closed
>>> Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
>>> ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent
>>> call last):
>>> File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>>> line 191, in _run_agent
>>>   return action(he)
>>> File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>>> line 64, in action_proper
>>>   return
>>> he.start_monitoring()
>>> File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>>> line 411, in start_monitoring
>>>   
>>> self._initialize_sanlock()
>>> File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>>> line 691, in _initialize_sanlock
>>>
>>> constants.SERVICE_TYPE + constants.LOCKSPACE_EXTENSION)
>>> File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>>> line 162, in get_service_path
>>>   .format(str(e)))
>>>   RequestError: Failed
>>> to get service path: Connection closed
>>> Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
>>> ovirt_hosted_engine_ha.agent.agent.Agent ERROR Trying to restart agent
>>>
>>> On Thu, Jun 29, 2017 at 1:25 PM, Martin Sivak <msi...@redhat.com> wrote:
>>>> Hi,
>>>>
>>>> yep, you have to restart the ovirt-ha-agent and ovirt-ha-broker services.
>>>>
>>>> The scheduling message just means that the host has score 0 or is not
>>>> reporting score at all.
>>>>
>>>> Martin
>>>>
>>>> On Thu, Jun 29, 2017 at 1:33 PM, cmc <iuco...@gmail.com> wrote:
>>>>> Thanks Martin, do I have to restart anything? When I try to use the
>>>>> 'migrate' operation, it complains that the other two

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-29 Thread cmc
Both services are up on all three hosts. The broke logs just report:

Thread-6549::INFO::2017-06-29
17:01:51,481::listener::134::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(setup)
Connection established
Thread-6549::INFO::2017-06-29
17:01:51,483::listener::186::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle)
Connection closed

Thanks,

Cam

On Thu, Jun 29, 2017 at 4:00 PM, Martin Sivak <msi...@redhat.com> wrote:
> Hi,
>
> please make sure that both ovirt-ha-agent and ovirt-ha-broker services
> are restarted and up. The error says the agent can't talk to the
> broker. Is there anything in the broker.log?
>
> Best regards
>
> Martin Sivak
>
> On Thu, Jun 29, 2017 at 4:42 PM, cmc <iuco...@gmail.com> wrote:
>> I've restarted those two services across all hosts, have taken the
>> Hosted Engine host out of maintenance, and when I try to migrate the
>> Hosted Engine over to another host, it reports that all three hosts
>> 'did not satisfy internal filter HA because it is not a Hosted Engine
>> host'.
>>
>> On the host that the Hosted Engine is currently on it reports in the 
>> agent.log:
>>
>> ovirt-ha-agent ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR
>> Connection closed: Connection closed
>> Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
>> ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR Exception
>> getting service path: Connection closed
>> Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
>> ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent
>> call last):
>> File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>> line 191, in _run_agent
>>   return action(he)
>> File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
>> line 64, in action_proper
>>   return
>> he.start_monitoring()
>> File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>> line 411, in start_monitoring
>>   
>> self._initialize_sanlock()
>> File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>> line 691, in _initialize_sanlock
>>
>> constants.SERVICE_TYPE + constants.LOCKSPACE_EXTENSION)
>> File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>> line 162, in get_service_path
>>   .format(str(e)))
>>   RequestError: Failed
>> to get service path: Connection closed
>> Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
>> ovirt_hosted_engine_ha.agent.agent.Agent ERROR Trying to restart agent
>>
>> On Thu, Jun 29, 2017 at 1:25 PM, Martin Sivak <msi...@redhat.com> wrote:
>>> Hi,
>>>
>>> yep, you have to restart the ovirt-ha-agent and ovirt-ha-broker services.
>>>
>>> The scheduling message just means that the host has score 0 or is not
>>> reporting score at all.
>>>
>>> Martin
>>>
>>> On Thu, Jun 29, 2017 at 1:33 PM, cmc <iuco...@gmail.com> wrote:
>>>> Thanks Martin, do I have to restart anything? When I try to use the
>>>> 'migrate' operation, it complains that the other two hosts 'did not
>>>> satisfy internal filter HA because it is not a Hosted Engine host..'
>>>> (even though I reinstalled both these hosts with the 'deploy hosted
>>>> engine' option, which suggests that something needs restarting. Should
>>>> I worry about the sanlock errors, or will that be resolved by the
>>>> change in host_id?
>>>>
>>>> Kind regards,
>>>>
>>>> Cam
>>>>
>>>> On Thu, Jun 29, 2017 at 12:22 PM, Martin Sivak <msi...@redhat.com> wrote:
>>>>> Change the ids so they are distinct. I need to check if there is a way
>>>>> to read the SPM ids from the engine as using the same numbers would be
>>>>> the best.
>>>>>
>>>>> Martin
>>>>>
>>>>>
>>>&

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-29 Thread cmc
I've restarted those two services across all hosts, have taken the
Hosted Engine host out of maintenance, and when I try to migrate the
Hosted Engine over to another host, it reports that all three hosts
'did not satisfy internal filter HA because it is not a Hosted Engine
host'.

On the host that the Hosted Engine is currently on it reports in the agent.log:

ovirt-ha-agent ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR
Connection closed: Connection closed
Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR Exception
getting service path: Connection closed
Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent
call last):
File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
line 191, in _run_agent
  return action(he)
File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
line 64, in action_proper
  return
he.start_monitoring()
File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
line 411, in start_monitoring
  self._initialize_sanlock()
File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
line 691, in _initialize_sanlock

constants.SERVICE_TYPE + constants.LOCKSPACE_EXTENSION)
File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
line 162, in get_service_path
  .format(str(e)))
  RequestError: Failed
to get service path: Connection closed
Jun 29 15:22:25 kvm-ldn-03 ovirt-ha-agent[12653]: ovirt-ha-agent
ovirt_hosted_engine_ha.agent.agent.Agent ERROR Trying to restart agent

On Thu, Jun 29, 2017 at 1:25 PM, Martin Sivak <msi...@redhat.com> wrote:
> Hi,
>
> yep, you have to restart the ovirt-ha-agent and ovirt-ha-broker services.
>
> The scheduling message just means that the host has score 0 or is not
> reporting score at all.
>
> Martin
>
> On Thu, Jun 29, 2017 at 1:33 PM, cmc <iuco...@gmail.com> wrote:
>> Thanks Martin, do I have to restart anything? When I try to use the
>> 'migrate' operation, it complains that the other two hosts 'did not
>> satisfy internal filter HA because it is not a Hosted Engine host..'
>> (even though I reinstalled both these hosts with the 'deploy hosted
>> engine' option, which suggests that something needs restarting. Should
>> I worry about the sanlock errors, or will that be resolved by the
>> change in host_id?
>>
>> Kind regards,
>>
>> Cam
>>
>> On Thu, Jun 29, 2017 at 12:22 PM, Martin Sivak <msi...@redhat.com> wrote:
>>> Change the ids so they are distinct. I need to check if there is a way
>>> to read the SPM ids from the engine as using the same numbers would be
>>> the best.
>>>
>>> Martin
>>>
>>>
>>>
>>> On Thu, Jun 29, 2017 at 12:46 PM, cmc <iuco...@gmail.com> wrote:
>>>> Is there any way of recovering from this situation? I'd prefer to fix
>>>> the issue rather than re-deploy, but if there is no recovery path, I
>>>> could perhaps try re-deploying the hosted engine. In which case, would
>>>> the best option be to take a backup of the Hosted Engine, and then
>>>> shut it down, re-initialise the SAN partition (or use another
>>>> partition) and retry the deployment? Would it be better to use the
>>>> older backup from the bare metal engine that I originally used, or use
>>>> a backup from the Hosted Engine? I'm not sure if any VMs have been
>>>> added since switching to Hosted Engine.
>>>>
>>>> Unfortunately I have very little time left to get this working before
>>>> I have to hand it over for eval (by end of Friday).
>>>>
>>>> Here are some log snippets from the cluster that are current
>>>>
>>>> In /var/log/vdsm/vdsm.log on the host that has the Hosted Engine:
>>>>
>>>> 2017-06-29 10:50:15,071+0100 INFO  (monitor/207221b) [storage.SANLock]
>>>> Acquiring host id for domain 207221b2-959b-426b-b945-18e1adfed62f (id:
>>>> 3) (clusterlock:282)
>>>> 2017-06-29

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-29 Thread cmc
Thanks Martin, do I have to restart anything? When I try to use the
'migrate' operation, it complains that the other two hosts 'did not
satisfy internal filter HA because it is not a Hosted Engine host..'
(even though I reinstalled both these hosts with the 'deploy hosted
engine' option, which suggests that something needs restarting. Should
I worry about the sanlock errors, or will that be resolved by the
change in host_id?

Kind regards,

Cam

On Thu, Jun 29, 2017 at 12:22 PM, Martin Sivak <msi...@redhat.com> wrote:
> Change the ids so they are distinct. I need to check if there is a way
> to read the SPM ids from the engine as using the same numbers would be
> the best.
>
> Martin
>
>
>
> On Thu, Jun 29, 2017 at 12:46 PM, cmc <iuco...@gmail.com> wrote:
>> Is there any way of recovering from this situation? I'd prefer to fix
>> the issue rather than re-deploy, but if there is no recovery path, I
>> could perhaps try re-deploying the hosted engine. In which case, would
>> the best option be to take a backup of the Hosted Engine, and then
>> shut it down, re-initialise the SAN partition (or use another
>> partition) and retry the deployment? Would it be better to use the
>> older backup from the bare metal engine that I originally used, or use
>> a backup from the Hosted Engine? I'm not sure if any VMs have been
>> added since switching to Hosted Engine.
>>
>> Unfortunately I have very little time left to get this working before
>> I have to hand it over for eval (by end of Friday).
>>
>> Here are some log snippets from the cluster that are current
>>
>> In /var/log/vdsm/vdsm.log on the host that has the Hosted Engine:
>>
>> 2017-06-29 10:50:15,071+0100 INFO  (monitor/207221b) [storage.SANLock]
>> Acquiring host id for domain 207221b2-959b-426b-b945-18e1adfed62f (id:
>> 3) (clusterlock:282)
>> 2017-06-29 10:50:15,072+0100 ERROR (monitor/207221b) [storage.Monitor]
>> Error acquiring host id 3 for domain
>> 207221b2-959b-426b-b945-18e1adfed62f (monitor:558)
>> Traceback (most recent call last):
>>   File "/usr/share/vdsm/storage/monitor.py", line 555, in _acquireHostId
>> self.domain.acquireHostId(self.hostId, async=True)
>>   File "/usr/share/vdsm/storage/sd.py", line 790, in acquireHostId
>> self._manifest.acquireHostId(hostId, async)
>>   File "/usr/share/vdsm/storage/sd.py", line 449, in acquireHostId
>> self._domainLock.acquireHostId(hostId, async)
>>   File "/usr/lib/python2.7/site-packages/vdsm/storage/clusterlock.py",
>> line 297, in acquireHostId
>> raise se.AcquireHostIdFailure(self._sdUUID, e)
>> AcquireHostIdFailure: Cannot acquire host id:
>> ('207221b2-959b-426b-b945-18e1adfed62f', SanlockException(22, 'Sanlock
>> lockspace add failure', 'Invalid argument'))
>>
>> From /var/log/ovirt-hosted-engine-ha/agent.log on the same host:
>>
>> MainThread::ERROR::2017-06-19
>> 13:30:50,592::hosted_engine::822::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_domain_monitor)
>> Failed to start monitoring domain
>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>> during domain acquisition
>> MainThread::WARNING::2017-06-19
>> 13:30:50,593::hosted_engine::469::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring)
>> Error while monitoring engine: Failed to start monitoring domain
>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>> during domain acquisition
>> MainThread::WARNING::2017-06-19
>> 13:30:50,593::hosted_engine::472::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring)
>> Unexpected error
>> Traceback (most recent call last):
>>   File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>> line 443, in start_monitoring
>> self._initialize_domain_monitor()
>>   File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
>> line 823, in _initialize_domain_monitor
>> raise Exception(msg)
>> Exception: Failed to start monitoring domain
>> (sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
>> during domain acquisition
>> MainThread::ERROR::2017-06-19
>> 13:30:50,593::hosted_engine::485::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring)
>> Shutting down the agent because of 3 failures in a row!
>>
>> From sanlock.log:
>>
>> 2017-06-29 11:17:06+0100 1194149 [2530]: add_lockspace
>> 207221b2-959b-426b-b945-18e1adfed62f:3:/dev/207221b2-959b-426

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-29 Thread cmc
scan)
Found OVF_STORE: imgUUID:222610db-7880-4f4f-8559-a3635fd73555,
volUUID:c6e0d29b-eabf-4a09-a330-df54cfdd73f1
MainThread::INFO::2017-06-29
10:56:33,926::ovf_store::112::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(getEngineVMOVF)
Extracting Engine VM OVF from the OVF_STORE
MainThread::INFO::2017-06-29
10:56:33,938::ovf_store::119::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(getEngineVMOVF)
OVF_STORE volume path:
/rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/images/222610db-7880-4f4f-8559-a3635fd73555/c6e0d29b-eabf-4a09-a330-df54cfdd73f1
MainThread::INFO::2017-06-29
10:56:33,967::config::431::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(_get_vm_conf_content_from_ovf_store)
Found an OVF for HE VM, trying to convert
MainThread::INFO::2017-06-29
10:56:33,971::config::436::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(_get_vm_conf_content_from_ovf_store)
Got vm.conf from OVF_STORE
MainThread::INFO::2017-06-29
10:56:36,736::states::678::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score)
Score is 0 due to unexpected vm shutdown at Thu Jun 29 10:53:59 2017
MainThread::INFO::2017-06-29
10:56:36,736::hosted_engine::453::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring)
Current state EngineUnexpectedlyDown (score: 0)
MainThread::INFO::2017-06-29
10:56:46,772::config::485::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(refresh_vm_conf)
Reloading vm.conf from the shared storage domain

/var/log/messages:

Jun 29 10:53:46 kvm-ldn-02 kernel: dd: sending ioctl 80306d02 to a partition!


host 1:

/var/log/messages also in sanlock.log

Jun 29 11:01:02 kvm-ldn-01 sanlock[2400]: 2017-06-29 11:01:02+0100
678325 [9132]: s4531 delta_acquire host_id 1 busy1 1 2 1193177
3d4ec963-8486-43a2-a7d9-afa82508f89f.kvm-ldn-03
Jun 29 11:01:03 kvm-ldn-01 sanlock[2400]: 2017-06-29 11:01:03+0100
678326 [24159]: s4531 add_lockspace fail result -262

/var/log/ovirt-hosted-engine-ha/agent.log:

MainThread::ERROR::2017-06-27
15:21:01,143::hosted_engine::822::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_domain_monitor)
Failed to start monitoring domain
(sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
during domain acquisition
MainThread::WARNING::2017-06-27
15:21:01,144::hosted_engine::469::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring)
Error while monitoring engine: Failed to start monitoring domain
(sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
during domain acquisition
MainThread::WARNING::2017-06-27
15:21:01,144::hosted_engine::472::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring)
Unexpected error
Traceback (most recent call last):
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
line 443, in start_monitoring
self._initialize_domain_monitor()
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
line 823, in _initialize_domain_monitor
raise Exception(msg)
Exception: Failed to start monitoring domain
(sd_uuid=207221b2-959b-426b-b945-18e1adfed62f, host_id=1): timeout
during domain acquisition
MainThread::ERROR::2017-06-27
15:21:01,144::hosted_engine::485::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring)
Shutting down the agent because of 3 failures in a row!
MainThread::INFO::2017-06-27
15:21:06,717::hosted_engine::848::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status)
VDSM domain monitor status: PENDING
MainThread::INFO::2017-06-27
15:21:09,335::hosted_engine::776::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_stop_domain_monitor)
Failed to stop monitoring domain
(sd_uuid=207221b2-959b-426b-b945-18e1adfed62f): Storage domain is
member of pool: u'domain=207221b2-959b-426b-b945-18e1adfed62f'
MainThread::INFO::2017-06-27
15:21:09,339::agent::144::ovirt_hosted_engine_ha.agent.agent.Agent::(run)
Agent shutting down


Thanks for any help,


Cam


On Wed, Jun 28, 2017 at 11:25 AM, cmc <iuco...@gmail.com> wrote:
> Hi Martin,
>
> yes, on two of the machines they have the same host_id. The other has
> a different host_id.
>
> To update since yesterday: I reinstalled and deployed Hosted Engine on
> the other host (so all three hosts in the cluster now have it
> installed). The second one I deployed said it was able to host the
> engine (unlike the first I reinstalled), so I tried putting the host
> with the Hosted Engine on it into maintenance to see if it would
> migrate over. It managed to move all hosts but the Hosted Engine. And
> now the host that said it was able to host the engine says
> 'unavailable due to HA score'. The host that it was trying to move
> from is now in 'preparing for maintenance' for the last 12 hours.
>
> The summary is:
>
> kvm-ldn-01 - one of

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-28 Thread cmc
Hi Martin,

yes, on two of the machines they have the same host_id. The other has
a different host_id.

To update since yesterday: I reinstalled and deployed Hosted Engine on
the other host (so all three hosts in the cluster now have it
installed). The second one I deployed said it was able to host the
engine (unlike the first I reinstalled), so I tried putting the host
with the Hosted Engine on it into maintenance to see if it would
migrate over. It managed to move all hosts but the Hosted Engine. And
now the host that said it was able to host the engine says
'unavailable due to HA score'. The host that it was trying to move
from is now in 'preparing for maintenance' for the last 12 hours.

The summary is:

kvm-ldn-01 - one of the original, pre-Hosted Engine hosts, reinstalled
with 'Deploy Hosted Engine'. No icon saying it can host the Hosted
Hngine, host_id of '2' in /etc/ovirt-hosted-engine/hosted-engine.conf.
'add_lockspace' fails in sanlock.log

kvm-ldn-02 - the other host that was pre-existing before Hosted Engine
was created. Reinstalled with 'Deploy Hosted Engine'. Had an icon
saying that it was able to host the Hosted Engine, but after migration
was attempted when putting kvm-ldn-03 into maintenance, it reports:
'unavailable due to HA score'. It has a host_id of '1' in
/etc/ovirt-hosted-engine/hosted-engine.conf. No errors in sanlock.log

kvm-ldn-03 - this was the host I deployed Hosted Engine on, which was
not part of the original cluster. I restored the bare-metal engine
backup in the Hosted Engine on this host when deploying it, without
error. It currently has the Hosted Engine on it (as the only VM after
I put that host into maintenance to test the HA of Hosted Engine).
Sanlock log shows conflicts

I will look through all the logs for any other errors. Please let me
know if you need any logs or other clarification/information.

Thanks,

Campbell

On Wed, Jun 28, 2017 at 9:25 AM, Martin Sivak <msi...@redhat.com> wrote:
> Hi,
>
> can you please check the contents of
> /etc/ovirt-hosted-engine/hosted-engine.conf or
> /etc/ovirt-hosted-engine-ha/agent.conf (I am not sure which one it is
> right now) and search for host-id?
>
> Make sure the IDs are different. If they are not, then there is a bug 
> somewhere.
>
> Martin
>
> On Tue, Jun 27, 2017 at 6:26 PM, cmc <iuco...@gmail.com> wrote:
>> I see this on the host it is trying to migrate in /var/log/sanlock:
>>
>> 2017-06-27 17:10:40+0100 527703 [2407]: s3528 lockspace
>> 207221b2-959b-426b-b945-18e1adfed62f:1:/dev/207221b2-959b-426b-b945-18e1adfed62f/ids:0
>> 2017-06-27 17:13:00+0100 527843 [27446]: s3528 delta_acquire host_id 1
>> busy1 1 2 1042692 3d4ec963-8486-43a2-a7d9-afa82508f89f.kvm-ldn-03
>> 2017-06-27 17:13:01+0100 527844 [2407]: s3528 add_lockspace fail result -262
>>
>> The sanlock service is running. Why would this occur?
>>
>> Thanks,
>>
>> C
>>
>> On Tue, Jun 27, 2017 at 5:21 PM, cmc <iuco...@gmail.com> wrote:
>>> Hi Martin,
>>>
>>> Thanks for the reply. I have done this, and the deployment completed
>>> without error. However, it still will not allow the Hosted Engine
>>> migrate to another host. The
>>> /etc/ovirt-hosted-engine/hosted-engine.conf got created ok on the host
>>> I re-installed, but the ovirt-ha-broker.service, though it starts,
>>> reports:
>>>
>>> 8<---
>>>
>>> Jun 27 14:58:26 kvm-ldn-01 systemd[1]: Starting oVirt Hosted Engine
>>> High Availability Communications Broker...
>>> Jun 27 14:58:27 kvm-ldn-01 ovirt-ha-broker[6101]: ovirt-ha-broker
>>> ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker ERROR
>>> Failed to read metadata from
>>> /rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/ha_agent/hosted-engine.metadata
>>>   Traceback (most
>>> recent call last):
>>> File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
>>> line 129, in get_raw_stats_for_service_type
>>>   f =
>>> os.open(path, direct_flag | os.O_RDONLY | os.O_SYNC)
>>>   OSError: [Errno 2]
>>> No such file or directory:
>>> '/rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/ha_agent/hosted-engine.metadata'
>>>
>>> 8<---
>>>
>>> I checked the path, and it exists. I can run 'less -f' on it fine. The
>>> perms are slightly different on the host that is running

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-27 Thread cmc
On the host that has the Hosted Engine VM, the sanlock.log reports:

2017-06-27 17:30:20+0100 1043742 [7307]: add_lockspace
207221b2-959b-426b-b945-18e1adfed62f:3:/dev/207221b2-959b-426b-b945-18e1adfed62f/ids:0
conflicts with name of list1 s5
207221b2-959b-426b-b945-18e1adfed62f:1:/dev/207221b2-959b-426b-b945-18e1adfed62f/ids:0

Again, I'm not sure what has happened here.

On Tue, Jun 27, 2017 at 5:26 PM, cmc <iuco...@gmail.com> wrote:
> I see this on the host it is trying to migrate in /var/log/sanlock:
>
> 2017-06-27 17:10:40+0100 527703 [2407]: s3528 lockspace
> 207221b2-959b-426b-b945-18e1adfed62f:1:/dev/207221b2-959b-426b-b945-18e1adfed62f/ids:0
> 2017-06-27 17:13:00+0100 527843 [27446]: s3528 delta_acquire host_id 1
> busy1 1 2 1042692 3d4ec963-8486-43a2-a7d9-afa82508f89f.kvm-ldn-03
> 2017-06-27 17:13:01+0100 527844 [2407]: s3528 add_lockspace fail result -262
>
> The sanlock service is running. Why would this occur?
>
> Thanks,
>
> C
>
> On Tue, Jun 27, 2017 at 5:21 PM, cmc <iuco...@gmail.com> wrote:
>> Hi Martin,
>>
>> Thanks for the reply. I have done this, and the deployment completed
>> without error. However, it still will not allow the Hosted Engine
>> migrate to another host. The
>> /etc/ovirt-hosted-engine/hosted-engine.conf got created ok on the host
>> I re-installed, but the ovirt-ha-broker.service, though it starts,
>> reports:
>>
>> 8<---
>>
>> Jun 27 14:58:26 kvm-ldn-01 systemd[1]: Starting oVirt Hosted Engine
>> High Availability Communications Broker...
>> Jun 27 14:58:27 kvm-ldn-01 ovirt-ha-broker[6101]: ovirt-ha-broker
>> ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker ERROR
>> Failed to read metadata from
>> /rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/ha_agent/hosted-engine.metadata
>>   Traceback (most
>> recent call last):
>> File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
>> line 129, in get_raw_stats_for_service_type
>>   f =
>> os.open(path, direct_flag | os.O_RDONLY | os.O_SYNC)
>>   OSError: [Errno 2]
>> No such file or directory:
>> '/rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/ha_agent/hosted-engine.metadata'
>>
>> 8<---
>>
>> I checked the path, and it exists. I can run 'less -f' on it fine. The
>> perms are slightly different on the host that is running the VM vs the
>> one that is reporting errors (600 vs 660), ownership is vdsm:qemu. Is
>> this a san locking issue?
>>
>> Thanks for any help,
>>
>> Cam
>>
>> On Tue, Jun 27, 2017 at 1:41 PM, Martin Sivak <msi...@redhat.com> wrote:
>>>> Should it be? It was not in the instructions for the migration from
>>>> bare-metal to Hosted VM
>>>
>>> The hosted engine will only migrate to hosts that have the services
>>> running. Please put one other host to maintenance and select Hosted
>>> engine action: DEPLOY in the reinstall dialog.
>>>
>>> Best regards
>>>
>>> Martin Sivak
>>>
>>> On Tue, Jun 27, 2017 at 1:23 PM, cmc <iuco...@gmail.com> wrote:
>>>> I changed the 'os.other.devices.display.protocols.value.3.6 =
>>>> spice/qxl,vnc/cirrus,vnc/qxl' line to have the same display protocols
>>>> as 4 and the hosted engine now appears in the list of VMs. I am
>>>> guessing the compatibility version was causing it to use the 3.6
>>>> version. However, I am still unable to migrate the engine VM to
>>>> another host. When I try putting the host it is currently on into
>>>> maintenance, it reports:
>>>>
>>>> Error while executing action: Cannot switch the Host(s) to Maintenance 
>>>> mode.
>>>> There are no available hosts capable of running the engine VM.
>>>>
>>>> Running 'hosted-engine --vm-status' still shows 'Engine status:
>>>> unknown stale-data'.
>>>>
>>>> The ovirt-ha-broker service is only running on one host. It was set to
>>>> 'disabled' in systemd. It won't start as there is no
>>>> /etc/ovirt-hosted-engine/hosted-engine.conf on the other two hosts.
>>>> Should it be? It was not in the instructions for the migration from
>>>> bare-metal to Hosted VM
>>>>
>>>> Thanks,

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-27 Thread cmc
I see this on the host it is trying to migrate in /var/log/sanlock:

2017-06-27 17:10:40+0100 527703 [2407]: s3528 lockspace
207221b2-959b-426b-b945-18e1adfed62f:1:/dev/207221b2-959b-426b-b945-18e1adfed62f/ids:0
2017-06-27 17:13:00+0100 527843 [27446]: s3528 delta_acquire host_id 1
busy1 1 2 1042692 3d4ec963-8486-43a2-a7d9-afa82508f89f.kvm-ldn-03
2017-06-27 17:13:01+0100 527844 [2407]: s3528 add_lockspace fail result -262

The sanlock service is running. Why would this occur?

Thanks,

C

On Tue, Jun 27, 2017 at 5:21 PM, cmc <iuco...@gmail.com> wrote:
> Hi Martin,
>
> Thanks for the reply. I have done this, and the deployment completed
> without error. However, it still will not allow the Hosted Engine
> migrate to another host. The
> /etc/ovirt-hosted-engine/hosted-engine.conf got created ok on the host
> I re-installed, but the ovirt-ha-broker.service, though it starts,
> reports:
>
> 8<---
>
> Jun 27 14:58:26 kvm-ldn-01 systemd[1]: Starting oVirt Hosted Engine
> High Availability Communications Broker...
> Jun 27 14:58:27 kvm-ldn-01 ovirt-ha-broker[6101]: ovirt-ha-broker
> ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker ERROR
> Failed to read metadata from
> /rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/ha_agent/hosted-engine.metadata
>   Traceback (most
> recent call last):
> File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
> line 129, in get_raw_stats_for_service_type
>   f =
> os.open(path, direct_flag | os.O_RDONLY | os.O_SYNC)
>   OSError: [Errno 2]
> No such file or directory:
> '/rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/ha_agent/hosted-engine.metadata'
>
> 8<---
>
> I checked the path, and it exists. I can run 'less -f' on it fine. The
> perms are slightly different on the host that is running the VM vs the
> one that is reporting errors (600 vs 660), ownership is vdsm:qemu. Is
> this a san locking issue?
>
> Thanks for any help,
>
> Cam
>
> On Tue, Jun 27, 2017 at 1:41 PM, Martin Sivak <msi...@redhat.com> wrote:
>>> Should it be? It was not in the instructions for the migration from
>>> bare-metal to Hosted VM
>>
>> The hosted engine will only migrate to hosts that have the services
>> running. Please put one other host to maintenance and select Hosted
>> engine action: DEPLOY in the reinstall dialog.
>>
>> Best regards
>>
>> Martin Sivak
>>
>> On Tue, Jun 27, 2017 at 1:23 PM, cmc <iuco...@gmail.com> wrote:
>>> I changed the 'os.other.devices.display.protocols.value.3.6 =
>>> spice/qxl,vnc/cirrus,vnc/qxl' line to have the same display protocols
>>> as 4 and the hosted engine now appears in the list of VMs. I am
>>> guessing the compatibility version was causing it to use the 3.6
>>> version. However, I am still unable to migrate the engine VM to
>>> another host. When I try putting the host it is currently on into
>>> maintenance, it reports:
>>>
>>> Error while executing action: Cannot switch the Host(s) to Maintenance mode.
>>> There are no available hosts capable of running the engine VM.
>>>
>>> Running 'hosted-engine --vm-status' still shows 'Engine status:
>>> unknown stale-data'.
>>>
>>> The ovirt-ha-broker service is only running on one host. It was set to
>>> 'disabled' in systemd. It won't start as there is no
>>> /etc/ovirt-hosted-engine/hosted-engine.conf on the other two hosts.
>>> Should it be? It was not in the instructions for the migration from
>>> bare-metal to Hosted VM
>>>
>>> Thanks,
>>>
>>> Cam
>>>
>>> On Thu, Jun 22, 2017 at 1:07 PM, cmc <iuco...@gmail.com> wrote:
>>>> Hi Tomas,
>>>>
>>>> So in my /usr/share/ovirt-engine/conf/osinfo-defaults.properties on my
>>>> engine VM, I have:
>>>>
>>>> os.other.devices.display.protocols.value = 
>>>> spice/qxl,vnc/vga,vnc/qxl,vnc/cirrus
>>>> os.other.devices.display.protocols.value.3.6 = spice/qxl,vnc/cirrus,vnc/qxl
>>>>
>>>> That seems to match - I assume since this is 4.1, the 3.6 should not apply
>>>>
>>>> Is there somewhere else I should be looking?
>>>>
>>>> Thanks,
>>>>
>>>> Cam
&g

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-27 Thread cmc
Hi Martin,

Thanks for the reply. I have done this, and the deployment completed
without error. However, it still will not allow the Hosted Engine
migrate to another host. The
/etc/ovirt-hosted-engine/hosted-engine.conf got created ok on the host
I re-installed, but the ovirt-ha-broker.service, though it starts,
reports:

8<---

Jun 27 14:58:26 kvm-ldn-01 systemd[1]: Starting oVirt Hosted Engine
High Availability Communications Broker...
Jun 27 14:58:27 kvm-ldn-01 ovirt-ha-broker[6101]: ovirt-ha-broker
ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker ERROR
Failed to read metadata from
/rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/ha_agent/hosted-engine.metadata
  Traceback (most
recent call last):
File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
line 129, in get_raw_stats_for_service_type
  f =
os.open(path, direct_flag | os.O_RDONLY | os.O_SYNC)
  OSError: [Errno 2]
No such file or directory:
'/rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/ha_agent/hosted-engine.metadata'

8<---

I checked the path, and it exists. I can run 'less -f' on it fine. The
perms are slightly different on the host that is running the VM vs the
one that is reporting errors (600 vs 660), ownership is vdsm:qemu. Is
this a san locking issue?

Thanks for any help,

Cam

On Tue, Jun 27, 2017 at 1:41 PM, Martin Sivak <msi...@redhat.com> wrote:
>> Should it be? It was not in the instructions for the migration from
>> bare-metal to Hosted VM
>
> The hosted engine will only migrate to hosts that have the services
> running. Please put one other host to maintenance and select Hosted
> engine action: DEPLOY in the reinstall dialog.
>
> Best regards
>
> Martin Sivak
>
> On Tue, Jun 27, 2017 at 1:23 PM, cmc <iuco...@gmail.com> wrote:
>> I changed the 'os.other.devices.display.protocols.value.3.6 =
>> spice/qxl,vnc/cirrus,vnc/qxl' line to have the same display protocols
>> as 4 and the hosted engine now appears in the list of VMs. I am
>> guessing the compatibility version was causing it to use the 3.6
>> version. However, I am still unable to migrate the engine VM to
>> another host. When I try putting the host it is currently on into
>> maintenance, it reports:
>>
>> Error while executing action: Cannot switch the Host(s) to Maintenance mode.
>> There are no available hosts capable of running the engine VM.
>>
>> Running 'hosted-engine --vm-status' still shows 'Engine status:
>> unknown stale-data'.
>>
>> The ovirt-ha-broker service is only running on one host. It was set to
>> 'disabled' in systemd. It won't start as there is no
>> /etc/ovirt-hosted-engine/hosted-engine.conf on the other two hosts.
>> Should it be? It was not in the instructions for the migration from
>> bare-metal to Hosted VM
>>
>> Thanks,
>>
>> Cam
>>
>> On Thu, Jun 22, 2017 at 1:07 PM, cmc <iuco...@gmail.com> wrote:
>>> Hi Tomas,
>>>
>>> So in my /usr/share/ovirt-engine/conf/osinfo-defaults.properties on my
>>> engine VM, I have:
>>>
>>> os.other.devices.display.protocols.value = 
>>> spice/qxl,vnc/vga,vnc/qxl,vnc/cirrus
>>> os.other.devices.display.protocols.value.3.6 = spice/qxl,vnc/cirrus,vnc/qxl
>>>
>>> That seems to match - I assume since this is 4.1, the 3.6 should not apply
>>>
>>> Is there somewhere else I should be looking?
>>>
>>> Thanks,
>>>
>>> Cam
>>>
>>> On Thu, Jun 22, 2017 at 11:40 AM, Tomas Jelinek <tjeli...@redhat.com> wrote:
>>>>
>>>>
>>>> On Thu, Jun 22, 2017 at 12:38 PM, Michal Skrivanek
>>>> <michal.skriva...@redhat.com> wrote:
>>>>>
>>>>>
>>>>> > On 22 Jun 2017, at 12:31, Martin Sivak <msi...@redhat.com> wrote:
>>>>> >
>>>>> > Tomas, what fields are needed in a VM to pass the check that causes
>>>>> > the following error?
>>>>> >
>>>>> >>>>> WARN  [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
>>>>> >>>>> (org.ovirt.thread.pool-6-thread-23) [] Validation of action
>>>>> >>>>> 'ImportVm'
>>>>> >>>>> failed for user SYSTEM. Reasons: VAR__ACTION__IMPORT
>>>>> >>>>>
&

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-27 Thread cmc
I changed the 'os.other.devices.display.protocols.value.3.6 =
spice/qxl,vnc/cirrus,vnc/qxl' line to have the same display protocols
as 4 and the hosted engine now appears in the list of VMs. I am
guessing the compatibility version was causing it to use the 3.6
version. However, I am still unable to migrate the engine VM to
another host. When I try putting the host it is currently on into
maintenance, it reports:

Error while executing action: Cannot switch the Host(s) to Maintenance mode.
There are no available hosts capable of running the engine VM.

Running 'hosted-engine --vm-status' still shows 'Engine status:
unknown stale-data'.

The ovirt-ha-broker service is only running on one host. It was set to
'disabled' in systemd. It won't start as there is no
/etc/ovirt-hosted-engine/hosted-engine.conf on the other two hosts.
Should it be? It was not in the instructions for the migration from
bare-metal to Hosted VM

Thanks,

Cam

On Thu, Jun 22, 2017 at 1:07 PM, cmc <iuco...@gmail.com> wrote:
> Hi Tomas,
>
> So in my /usr/share/ovirt-engine/conf/osinfo-defaults.properties on my
> engine VM, I have:
>
> os.other.devices.display.protocols.value = 
> spice/qxl,vnc/vga,vnc/qxl,vnc/cirrus
> os.other.devices.display.protocols.value.3.6 = spice/qxl,vnc/cirrus,vnc/qxl
>
> That seems to match - I assume since this is 4.1, the 3.6 should not apply
>
> Is there somewhere else I should be looking?
>
> Thanks,
>
> Cam
>
> On Thu, Jun 22, 2017 at 11:40 AM, Tomas Jelinek <tjeli...@redhat.com> wrote:
>>
>>
>> On Thu, Jun 22, 2017 at 12:38 PM, Michal Skrivanek
>> <michal.skriva...@redhat.com> wrote:
>>>
>>>
>>> > On 22 Jun 2017, at 12:31, Martin Sivak <msi...@redhat.com> wrote:
>>> >
>>> > Tomas, what fields are needed in a VM to pass the check that causes
>>> > the following error?
>>> >
>>> >>>>> WARN  [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
>>> >>>>> (org.ovirt.thread.pool-6-thread-23) [] Validation of action
>>> >>>>> 'ImportVm'
>>> >>>>> failed for user SYSTEM. Reasons: VAR__ACTION__IMPORT
>>> >>>>>
>>> >>>>> ,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_VM_DISPLAY_TYPE_IS_NOT_SUPPORTED_BY_OS
>>>
>>> to match the OS and VM Display type;-)
>>> Configuration is in osinfo….e.g. if that is import from older releases on
>>> Linux this is typically caused by the cahgen of cirrus to vga for non-SPICE
>>> VMs
>>
>>
>> yep, the default supported combinations for 4.0+ is this:
>> os.other.devices.display.protocols.value =
>> spice/qxl,vnc/vga,vnc/qxl,vnc/cirrus
>>
>>>
>>>
>>> >
>>> > Thanks.
>>> >
>>> > On Thu, Jun 22, 2017 at 12:19 PM, cmc <iuco...@gmail.com> wrote:
>>> >> Hi Martin,
>>> >>
>>> >>>
>>> >>> just as a random comment, do you still have the database backup from
>>> >>> the bare metal -> VM attempt? It might be possible to just try again
>>> >>> using it. Or in the worst case.. update the offending value there
>>> >>> before restoring it to the new engine instance.
>>> >>
>>> >> I still have the backup. I'd rather do the latter, as re-running the
>>> >> HE deployment is quite lengthy and involved (I have to re-initialise
>>> >> the FC storage each time). Do you know what the offending value(s)
>>> >> would be? Would it be in the Postgres DB or in a config file
>>> >> somewhere?
>>> >>
>>> >> Cheers,
>>> >>
>>> >> Cam
>>> >>
>>> >>> Regards
>>> >>>
>>> >>> Martin Sivak
>>> >>>
>>> >>> On Thu, Jun 22, 2017 at 11:39 AM, cmc <iuco...@gmail.com> wrote:
>>> >>>> Hi Yanir,
>>> >>>>
>>> >>>> Thanks for the reply.
>>> >>>>
>>> >>>>> First of all, maybe a chain reaction of :
>>> >>>>> WARN  [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
>>> >>>>> (org.ovirt.thread.pool-6-thread-23) [] Validation of action
>>> >>>>> 'ImportVm'
>>> >>>>> failed for user SYSTEM. Reasons: VAR__ACTION__IMPORT
>>> >>>>>
>>> >>>>> ,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_VM_DISPLAY_TYPE_IS_NOT_SUPPORTED_BY_OS
>>> >&

Re: [ovirt-users] problems migrating to hosted engine from bare metal

2017-06-22 Thread cmc
Hi Juan,

Thanks for the reply. I didn't have any reliable NFS storage, or any
Gluster or iscsi storage available to me, but I found some unused
space on the fibre channel storage that is used as the storage domain
for the cluster, which was very fortunate. So I created a LUN on that.
I also found out that storage for the hosted engine is not allowed to
be shared with anything else (not sure why) so I made a small 140GB
partition on that. I also found out that there are plans to be able to
migrate the Hosted Engine onto different storage later on (it is in
development?).

I was able to deploy without error, but now the hosted engine cannot
be migrated to other hosts due to an error, so I've sent an email
about that.

Kind regards,

Campbell

On Thu, Jun 22, 2017 at 4:24 PM, Juan Pablo <pablo.localh...@gmail.com> wrote:
> hosted engine lives on the hosted engine share you defined at the
> begining . it does not migrate later to another storage, if you want
> that you need to re-deploy.
> hows your hardware and logical setup? will it change ?
>
>
>
> 2017-06-13 10:59 GMT-03:00 cmc <iuco...@gmail.com>:
>> Hi,
>>
>> I created a new host to deploy a hosted engine, and then used a backup
>> from the bare metal engine and restored this, as per the procedure in:
>>
>> http://www.ovirt.org/documentation/self-hosted/chap-Migrating_from_Bare_Metal_to_an_EL-Based_Self-Hosted_Environment/
>>
>> Everything worked fine up until step 15 ('Continue setup') as the
>> script said the engine was not responding. I tried the reboot option
>> (option 3), but still it would not connect. So I could not do the
>> final step involving the internal CA, adding the host to an existing
>> cluster (of which there were two other hosts). I was able to connect
>> via vnc and ssh fine to the engine, and from here I could see that the
>> ovirt-engine service was up. I had to install the aaa-ldap extension
>> package to enable ldap auth separately however, but once done I was
>> able to log in, and it showed the old cluster as it was on the bare
>> metal engine. I added the host that I created the hosted engine on,
>> and it installed various packages and then I configured the network
>> and it looked fine, apart from the fact that I could not see a VM
>> named 'HostedEngine' in the list of VMs. I think however that this was
>> not a properly working setup, as the NFS storage I used to setup the
>> hosted engine became unavailable and I think this killed the hosted
>> engine, which caused it to reboot the host it was on. The hosted
>> engine has not come back since then, so I'm guessing it either isn't
>> properly set up for HA or it needs the NFS storage or something else
>> was not properly done by me in the setup. I've restarted the bare
>> metal engine for now as I needed it running for now.
>>
>>  My questions are:
>>
>> 1. My understanding is that the NFS storage is initially used to
>> create the hosted engine disk image, and is temporary, and that the
>> hosted engine later gets migrated to the storage used by the rest of
>> the cluster (which in my case is directly attached to the hosts via
>> fibre channel). I suspect that this did not happen. The bare metal
>> engine had some local ISO storage (on a hard disk local to it), which
>> will not be replicated to the hosted engine VM - will this cause a
>> problem for the deployment? I can create some new ISO storage later if
>> not.
>>
>> 2. What is the recommended way to recover from this situation? Should
>> I just run 'hosted-engine --deploy' again and try and find out what is
>> going wrong at step 15?
>>
>> I can probably get the disk image that was on NFS and mount it to find
>> out what went wrong on the initial deployment, or I can run the
>> deployment again and then get the log when it fails at step 15.
>>
>> Ovirt version was 4.1.2.2
>>
>> Thanks for any help,
>>
>> Cam
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-22 Thread cmc
Hi Tomas,

So in my /usr/share/ovirt-engine/conf/osinfo-defaults.properties on my
engine VM, I have:

os.other.devices.display.protocols.value = spice/qxl,vnc/vga,vnc/qxl,vnc/cirrus
os.other.devices.display.protocols.value.3.6 = spice/qxl,vnc/cirrus,vnc/qxl

That seems to match - I assume since this is 4.1, the 3.6 should not apply

Is there somewhere else I should be looking?

Thanks,

Cam

On Thu, Jun 22, 2017 at 11:40 AM, Tomas Jelinek <tjeli...@redhat.com> wrote:
>
>
> On Thu, Jun 22, 2017 at 12:38 PM, Michal Skrivanek
> <michal.skriva...@redhat.com> wrote:
>>
>>
>> > On 22 Jun 2017, at 12:31, Martin Sivak <msi...@redhat.com> wrote:
>> >
>> > Tomas, what fields are needed in a VM to pass the check that causes
>> > the following error?
>> >
>> >>>>> WARN  [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
>> >>>>> (org.ovirt.thread.pool-6-thread-23) [] Validation of action
>> >>>>> 'ImportVm'
>> >>>>> failed for user SYSTEM. Reasons: VAR__ACTION__IMPORT
>> >>>>>
>> >>>>> ,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_VM_DISPLAY_TYPE_IS_NOT_SUPPORTED_BY_OS
>>
>> to match the OS and VM Display type;-)
>> Configuration is in osinfo….e.g. if that is import from older releases on
>> Linux this is typically caused by the cahgen of cirrus to vga for non-SPICE
>> VMs
>
>
> yep, the default supported combinations for 4.0+ is this:
> os.other.devices.display.protocols.value =
> spice/qxl,vnc/vga,vnc/qxl,vnc/cirrus
>
>>
>>
>> >
>> > Thanks.
>> >
>> > On Thu, Jun 22, 2017 at 12:19 PM, cmc <iuco...@gmail.com> wrote:
>> >> Hi Martin,
>> >>
>> >>>
>> >>> just as a random comment, do you still have the database backup from
>> >>> the bare metal -> VM attempt? It might be possible to just try again
>> >>> using it. Or in the worst case.. update the offending value there
>> >>> before restoring it to the new engine instance.
>> >>
>> >> I still have the backup. I'd rather do the latter, as re-running the
>> >> HE deployment is quite lengthy and involved (I have to re-initialise
>> >> the FC storage each time). Do you know what the offending value(s)
>> >> would be? Would it be in the Postgres DB or in a config file
>> >> somewhere?
>> >>
>> >> Cheers,
>> >>
>> >> Cam
>> >>
>> >>> Regards
>> >>>
>> >>> Martin Sivak
>> >>>
>> >>> On Thu, Jun 22, 2017 at 11:39 AM, cmc <iuco...@gmail.com> wrote:
>> >>>> Hi Yanir,
>> >>>>
>> >>>> Thanks for the reply.
>> >>>>
>> >>>>> First of all, maybe a chain reaction of :
>> >>>>> WARN  [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
>> >>>>> (org.ovirt.thread.pool-6-thread-23) [] Validation of action
>> >>>>> 'ImportVm'
>> >>>>> failed for user SYSTEM. Reasons: VAR__ACTION__IMPORT
>> >>>>>
>> >>>>> ,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_VM_DISPLAY_TYPE_IS_NOT_SUPPORTED_BY_OS
>> >>>>> is causing the hosted engine vm not to be set up correctly  and
>> >>>>> further
>> >>>>> actions were made when the hosted engine vm wasnt in a stable state.
>> >>>>>
>> >>>>> As for now, are you trying to revert back to a previous/initial
>> >>>>> state ?
>> >>>>
>> >>>> I'm not trying to revert it to a previous state for now. This was a
>> >>>> migration from a bare metal engine, and it didn't report any error
>> >>>> during the migration. I'd had some problems on my first attempts at
>> >>>> this migration, whereby it never completed (due to a proxy issue) but
>> >>>> I managed to resolve this. Do you know of a way to get the Hosted
>> >>>> Engine VM into a stable state, without rebuilding the entire cluster
>> >>>> from scratch (since I have a lot of VMs on it)?
>> >>>>
>> >>>> Thanks for any help.
>> >>>>
>> >>>> Regards,
>> >>>>
>> >>>> Cam
>> >>>>
>> >>>>> Regards,
>> >>>>> Yanir
>> >>>&

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-22 Thread cmc
Hi Martin,

>
> just as a random comment, do you still have the database backup from
> the bare metal -> VM attempt? It might be possible to just try again
> using it. Or in the worst case.. update the offending value there
> before restoring it to the new engine instance.

I still have the backup. I'd rather do the latter, as re-running the
HE deployment is quite lengthy and involved (I have to re-initialise
the FC storage each time). Do you know what the offending value(s)
would be? Would it be in the Postgres DB or in a config file
somewhere?

Cheers,

Cam

> Regards
>
> Martin Sivak
>
> On Thu, Jun 22, 2017 at 11:39 AM, cmc <iuco...@gmail.com> wrote:
>> Hi Yanir,
>>
>> Thanks for the reply.
>>
>>> First of all, maybe a chain reaction of :
>>> WARN  [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
>>> (org.ovirt.thread.pool-6-thread-23) [] Validation of action 'ImportVm'
>>> failed for user SYSTEM. Reasons: VAR__ACTION__IMPORT
>>> ,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_VM_DISPLAY_TYPE_IS_NOT_SUPPORTED_BY_OS
>>> is causing the hosted engine vm not to be set up correctly  and further
>>> actions were made when the hosted engine vm wasnt in a stable state.
>>>
>>> As for now, are you trying to revert back to a previous/initial state ?
>>
>> I'm not trying to revert it to a previous state for now. This was a
>> migration from a bare metal engine, and it didn't report any error
>> during the migration. I'd had some problems on my first attempts at
>> this migration, whereby it never completed (due to a proxy issue) but
>> I managed to resolve this. Do you know of a way to get the Hosted
>> Engine VM into a stable state, without rebuilding the entire cluster
>> from scratch (since I have a lot of VMs on it)?
>>
>> Thanks for any help.
>>
>> Regards,
>>
>> Cam
>>
>>> Regards,
>>> Yanir
>>>
>>> On Wed, Jun 21, 2017 at 4:32 PM, cmc <iuco...@gmail.com> wrote:
>>>>
>>>> Hi Jenny/Martin,
>>>>
>>>> Any idea what I can do here? The hosted engine VM has no log on any
>>>> host in /var/log/libvirt/qemu, and I fear that if I need to put the
>>>> host into maintenance, e.g., to upgrade it that I created it on (which
>>>> I think is hosting it), or if it fails for any reason, it won't get
>>>> migrated to another host, and I will not be able to manage the
>>>> cluster. It seems to be a very dangerous position to be in.
>>>>
>>>> Thanks,
>>>>
>>>> Cam
>>>>
>>>> On Wed, Jun 21, 2017 at 11:48 AM, cmc <iuco...@gmail.com> wrote:
>>>> > Thanks Martin. The hosts are all part of the same cluster.
>>>> >
>>>> > I get these errors in the engine.log on the engine:
>>>> >
>>>> > 2017-06-19 03:28:05,030Z WARN
>>>> > [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
>>>> > (org.ovirt.thread.pool-6-thread-23) [] Validation of action 'ImportVm'
>>>> > failed for user SYST
>>>> > EM. Reasons:
>>>> > VAR__ACTION__IMPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_VM_DISPLAY_TYPE_IS_NOT_SUPPORTED_BY_OS
>>>> > 2017-06-19 03:28:05,030Z INFO
>>>> > [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
>>>> > (org.ovirt.thread.pool-6-thread-23) [] Lock freed to object
>>>> > 'EngineLock:{exclusiveLocks='[a
>>>> > 79e6b0e-fff4-4cba-a02c-4c00be151300=<VM,
>>>> > ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>,
>>>> > HostedEngine=<VM_NAME, ACTION_TYPE_FAILED_NAME_ALREADY_USED>]',
>>>> > sharedLocks=
>>>> > '[a79e6b0e-fff4-4cba-a02c-4c00be151300=<REMOTE_VM,
>>>> > ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>]'}'
>>>> > 2017-06-19 03:28:05,030Z ERROR
>>>> > [org.ovirt.engine.core.bll.HostedEngineImporter]
>>>> > (org.ovirt.thread.pool-6-thread-23) [] Failed importing the Hosted
>>>> > Engine VM
>>>> >
>>>> > The sanlock.log reports conflicts on that same host, and a different
>>>> > error on the other hosts, not sure if they are related.
>>>> >
>>>> > And this in the /var/log/ovirt-hosted-engine-ha/agent log on the host
>>>> > which I deployed the hosted engine VM on:
>>>> >
>>>> > MainThread::ERROR::2017-06-19
>>>> >
>>>> > 13:0

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-22 Thread cmc
Hi Yanir,

Thanks for the reply.

> First of all, maybe a chain reaction of :
> WARN  [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
> (org.ovirt.thread.pool-6-thread-23) [] Validation of action 'ImportVm'
> failed for user SYSTEM. Reasons: VAR__ACTION__IMPORT
> ,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_VM_DISPLAY_TYPE_IS_NOT_SUPPORTED_BY_OS
> is causing the hosted engine vm not to be set up correctly  and further
> actions were made when the hosted engine vm wasnt in a stable state.
>
> As for now, are you trying to revert back to a previous/initial state ?

I'm not trying to revert it to a previous state for now. This was a
migration from a bare metal engine, and it didn't report any error
during the migration. I'd had some problems on my first attempts at
this migration, whereby it never completed (due to a proxy issue) but
I managed to resolve this. Do you know of a way to get the Hosted
Engine VM into a stable state, without rebuilding the entire cluster
from scratch (since I have a lot of VMs on it)?

Thanks for any help.

Regards,

Cam

> Regards,
> Yanir
>
> On Wed, Jun 21, 2017 at 4:32 PM, cmc <iuco...@gmail.com> wrote:
>>
>> Hi Jenny/Martin,
>>
>> Any idea what I can do here? The hosted engine VM has no log on any
>> host in /var/log/libvirt/qemu, and I fear that if I need to put the
>> host into maintenance, e.g., to upgrade it that I created it on (which
>> I think is hosting it), or if it fails for any reason, it won't get
>> migrated to another host, and I will not be able to manage the
>> cluster. It seems to be a very dangerous position to be in.
>>
>> Thanks,
>>
>> Cam
>>
>> On Wed, Jun 21, 2017 at 11:48 AM, cmc <iuco...@gmail.com> wrote:
>> > Thanks Martin. The hosts are all part of the same cluster.
>> >
>> > I get these errors in the engine.log on the engine:
>> >
>> > 2017-06-19 03:28:05,030Z WARN
>> > [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
>> > (org.ovirt.thread.pool-6-thread-23) [] Validation of action 'ImportVm'
>> > failed for user SYST
>> > EM. Reasons:
>> > VAR__ACTION__IMPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_VM_DISPLAY_TYPE_IS_NOT_SUPPORTED_BY_OS
>> > 2017-06-19 03:28:05,030Z INFO
>> > [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
>> > (org.ovirt.thread.pool-6-thread-23) [] Lock freed to object
>> > 'EngineLock:{exclusiveLocks='[a
>> > 79e6b0e-fff4-4cba-a02c-4c00be151300=<VM,
>> > ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>,
>> > HostedEngine=<VM_NAME, ACTION_TYPE_FAILED_NAME_ALREADY_USED>]',
>> > sharedLocks=
>> > '[a79e6b0e-fff4-4cba-a02c-4c00be151300=<REMOTE_VM,
>> > ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>]'}'
>> > 2017-06-19 03:28:05,030Z ERROR
>> > [org.ovirt.engine.core.bll.HostedEngineImporter]
>> > (org.ovirt.thread.pool-6-thread-23) [] Failed importing the Hosted
>> > Engine VM
>> >
>> > The sanlock.log reports conflicts on that same host, and a different
>> > error on the other hosts, not sure if they are related.
>> >
>> > And this in the /var/log/ovirt-hosted-engine-ha/agent log on the host
>> > which I deployed the hosted engine VM on:
>> >
>> > MainThread::ERROR::2017-06-19
>> >
>> > 13:09:49,743::ovf_store::124::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(getEngineVMOVF)
>> > Unable to extract HEVM OVF
>> > MainThread::ERROR::2017-06-19
>> >
>> > 13:09:49,743::config::445::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(_get_vm_conf_content_from_ovf_store)
>> > Failed extracting VM OVF from the OVF_STORE volume, falling back to
>> > initial vm.conf
>> >
>> > I've seen some of these issues reported in bugzilla, but they were for
>> > older versions of oVirt (and appear to be resolved).
>> >
>> > I will install that package on the other two hosts, for which I will
>> > put them in maintenance as vdsm is installed as an upgrade. I guess
>> > restarting vdsm is a good idea after that?
>> >
>> > Thanks,
>> >
>> > Campbell
>> >
>> > On Wed, Jun 21, 2017 at 10:51 AM, Martin Sivak <msi...@redhat.com>
>> > wrote:
>> >> Hi,
>> >>
>> >> you do not have to install it on all hosts. But you should have more
>> >> than one and ideally all hosted engine enabled nodes should belong to
>> >> the same engine cluster.
>> >>
>> >> Best regards
>>

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-21 Thread cmc
Hi Jenny/Martin,

Any idea what I can do here? The hosted engine VM has no log on any
host in /var/log/libvirt/qemu, and I fear that if I need to put the
host into maintenance, e.g., to upgrade it that I created it on (which
I think is hosting it), or if it fails for any reason, it won't get
migrated to another host, and I will not be able to manage the
cluster. It seems to be a very dangerous position to be in.

Thanks,

Cam

On Wed, Jun 21, 2017 at 11:48 AM, cmc <iuco...@gmail.com> wrote:
> Thanks Martin. The hosts are all part of the same cluster.
>
> I get these errors in the engine.log on the engine:
>
> 2017-06-19 03:28:05,030Z WARN
> [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
> (org.ovirt.thread.pool-6-thread-23) [] Validation of action 'ImportVm'
> failed for user SYST
> EM. Reasons: 
> VAR__ACTION__IMPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_VM_DISPLAY_TYPE_IS_NOT_SUPPORTED_BY_OS
> 2017-06-19 03:28:05,030Z INFO
> [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
> (org.ovirt.thread.pool-6-thread-23) [] Lock freed to object
> 'EngineLock:{exclusiveLocks='[a
> 79e6b0e-fff4-4cba-a02c-4c00be151300=<VM,
> ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>,
> HostedEngine=<VM_NAME, ACTION_TYPE_FAILED_NAME_ALREADY_USED>]',
> sharedLocks=
> '[a79e6b0e-fff4-4cba-a02c-4c00be151300=<REMOTE_VM,
> ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>]'}'
> 2017-06-19 03:28:05,030Z ERROR
> [org.ovirt.engine.core.bll.HostedEngineImporter]
> (org.ovirt.thread.pool-6-thread-23) [] Failed importing the Hosted
> Engine VM
>
> The sanlock.log reports conflicts on that same host, and a different
> error on the other hosts, not sure if they are related.
>
> And this in the /var/log/ovirt-hosted-engine-ha/agent log on the host
> which I deployed the hosted engine VM on:
>
> MainThread::ERROR::2017-06-19
> 13:09:49,743::ovf_store::124::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(getEngineVMOVF)
> Unable to extract HEVM OVF
> MainThread::ERROR::2017-06-19
> 13:09:49,743::config::445::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(_get_vm_conf_content_from_ovf_store)
> Failed extracting VM OVF from the OVF_STORE volume, falling back to
> initial vm.conf
>
> I've seen some of these issues reported in bugzilla, but they were for
> older versions of oVirt (and appear to be resolved).
>
> I will install that package on the other two hosts, for which I will
> put them in maintenance as vdsm is installed as an upgrade. I guess
> restarting vdsm is a good idea after that?
>
> Thanks,
>
> Campbell
>
> On Wed, Jun 21, 2017 at 10:51 AM, Martin Sivak <msi...@redhat.com> wrote:
>> Hi,
>>
>> you do not have to install it on all hosts. But you should have more
>> than one and ideally all hosted engine enabled nodes should belong to
>> the same engine cluster.
>>
>> Best regards
>>
>> Martin Sivak
>>
>> On Wed, Jun 21, 2017 at 11:29 AM, cmc <iuco...@gmail.com> wrote:
>>> Hi Jenny,
>>>
>>> Does ovirt-hosted-engine-ha need to be installed across all hosts?
>>> Could that be the reason it is failing to see it properly?
>>>
>>> Thanks,
>>>
>>> Cam
>>>
>>> On Mon, Jun 19, 2017 at 1:27 PM, cmc <iuco...@gmail.com> wrote:
>>>> Hi Jenny,
>>>>
>>>> Logs are attached. I can see errors in there, but am unsure how they arose.
>>>>
>>>> Thanks,
>>>>
>>>> Campbell
>>>>
>>>> On Mon, Jun 19, 2017 at 12:29 PM, Evgenia Tokar <eto...@redhat.com> wrote:
>>>>> From the output it looks like the agent is down, try starting it by 
>>>>> running:
>>>>> systemctl start ovirt-ha-agent.
>>>>>
>>>>> The engine is supposed to see the hosted engine storage domain and import 
>>>>> it
>>>>> to the system, then it should import the hosted engine vm.
>>>>>
>>>>> Can you attach the agent log from the host
>>>>> (/var/log/ovirt-hosted-engine-ha/agent.log)
>>>>> and the engine log from the engine vm (/var/log/ovirt-engine/engine.log)?
>>>>>
>>>>> Thanks,
>>>>> Jenny
>>>>>
>>>>>
>>>>> On Mon, Jun 19, 2017 at 12:41 PM, cmc <iuco...@gmail.com> wrote:
>>>>>>
>>>>>>  Hi Jenny,
>>>>>>
>>>>>> > What version are you running?
>>>>>>
>>>>>> 4.1.2.2-1.el7.centos
>>>>>>
>&g

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-21 Thread cmc
Thanks Martin. The hosts are all part of the same cluster.

I get these errors in the engine.log on the engine:

2017-06-19 03:28:05,030Z WARN
[org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
(org.ovirt.thread.pool-6-thread-23) [] Validation of action 'ImportVm'
failed for user SYST
EM. Reasons: 
VAR__ACTION__IMPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_VM_DISPLAY_TYPE_IS_NOT_SUPPORTED_BY_OS
2017-06-19 03:28:05,030Z INFO
[org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
(org.ovirt.thread.pool-6-thread-23) [] Lock freed to object
'EngineLock:{exclusiveLocks='[a
79e6b0e-fff4-4cba-a02c-4c00be151300=<VM,
ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>,
HostedEngine=<VM_NAME, ACTION_TYPE_FAILED_NAME_ALREADY_USED>]',
sharedLocks=
'[a79e6b0e-fff4-4cba-a02c-4c00be151300=<REMOTE_VM,
ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>]'}'
2017-06-19 03:28:05,030Z ERROR
[org.ovirt.engine.core.bll.HostedEngineImporter]
(org.ovirt.thread.pool-6-thread-23) [] Failed importing the Hosted
Engine VM

The sanlock.log reports conflicts on that same host, and a different
error on the other hosts, not sure if they are related.

And this in the /var/log/ovirt-hosted-engine-ha/agent log on the host
which I deployed the hosted engine VM on:

MainThread::ERROR::2017-06-19
13:09:49,743::ovf_store::124::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(getEngineVMOVF)
Unable to extract HEVM OVF
MainThread::ERROR::2017-06-19
13:09:49,743::config::445::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(_get_vm_conf_content_from_ovf_store)
Failed extracting VM OVF from the OVF_STORE volume, falling back to
initial vm.conf

I've seen some of these issues reported in bugzilla, but they were for
older versions of oVirt (and appear to be resolved).

I will install that package on the other two hosts, for which I will
put them in maintenance as vdsm is installed as an upgrade. I guess
restarting vdsm is a good idea after that?

Thanks,

Campbell

On Wed, Jun 21, 2017 at 10:51 AM, Martin Sivak <msi...@redhat.com> wrote:
> Hi,
>
> you do not have to install it on all hosts. But you should have more
> than one and ideally all hosted engine enabled nodes should belong to
> the same engine cluster.
>
> Best regards
>
> Martin Sivak
>
> On Wed, Jun 21, 2017 at 11:29 AM, cmc <iuco...@gmail.com> wrote:
>> Hi Jenny,
>>
>> Does ovirt-hosted-engine-ha need to be installed across all hosts?
>> Could that be the reason it is failing to see it properly?
>>
>> Thanks,
>>
>> Cam
>>
>> On Mon, Jun 19, 2017 at 1:27 PM, cmc <iuco...@gmail.com> wrote:
>>> Hi Jenny,
>>>
>>> Logs are attached. I can see errors in there, but am unsure how they arose.
>>>
>>> Thanks,
>>>
>>> Campbell
>>>
>>> On Mon, Jun 19, 2017 at 12:29 PM, Evgenia Tokar <eto...@redhat.com> wrote:
>>>> From the output it looks like the agent is down, try starting it by 
>>>> running:
>>>> systemctl start ovirt-ha-agent.
>>>>
>>>> The engine is supposed to see the hosted engine storage domain and import 
>>>> it
>>>> to the system, then it should import the hosted engine vm.
>>>>
>>>> Can you attach the agent log from the host
>>>> (/var/log/ovirt-hosted-engine-ha/agent.log)
>>>> and the engine log from the engine vm (/var/log/ovirt-engine/engine.log)?
>>>>
>>>> Thanks,
>>>> Jenny
>>>>
>>>>
>>>> On Mon, Jun 19, 2017 at 12:41 PM, cmc <iuco...@gmail.com> wrote:
>>>>>
>>>>>  Hi Jenny,
>>>>>
>>>>> > What version are you running?
>>>>>
>>>>> 4.1.2.2-1.el7.centos
>>>>>
>>>>> > For the hosted engine vm to be imported and displayed in the engine, you
>>>>> > must first create a master storage domain.
>>>>>
>>>>> To provide a bit more detail: this was a migration of a bare-metal
>>>>> engine in an existing cluster to a hosted engine VM for that cluster.
>>>>> As part of this migration, I built an entirely new host and ran
>>>>> 'hosted-engine --deploy' (followed these instructions:
>>>>>
>>>>> http://www.ovirt.org/documentation/self-hosted/chap-Migrating_from_Bare_Metal_to_an_EL-Based_Self-Hosted_Environment/).
>>>>> I restored the backup from the engine and it completed without any
>>>>> errors. I didn't see any instructions regarding a master storage
>>>>> domain in the page above. The cluster has two existing 

Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-21 Thread cmc
Hi Jenny,

Does ovirt-hosted-engine-ha need to be installed across all hosts?
Could that be the reason it is failing to see it properly?

Thanks,

Cam

On Mon, Jun 19, 2017 at 1:27 PM, cmc <iuco...@gmail.com> wrote:
> Hi Jenny,
>
> Logs are attached. I can see errors in there, but am unsure how they arose.
>
> Thanks,
>
> Campbell
>
> On Mon, Jun 19, 2017 at 12:29 PM, Evgenia Tokar <eto...@redhat.com> wrote:
>> From the output it looks like the agent is down, try starting it by running:
>> systemctl start ovirt-ha-agent.
>>
>> The engine is supposed to see the hosted engine storage domain and import it
>> to the system, then it should import the hosted engine vm.
>>
>> Can you attach the agent log from the host
>> (/var/log/ovirt-hosted-engine-ha/agent.log)
>> and the engine log from the engine vm (/var/log/ovirt-engine/engine.log)?
>>
>> Thanks,
>> Jenny
>>
>>
>> On Mon, Jun 19, 2017 at 12:41 PM, cmc <iuco...@gmail.com> wrote:
>>>
>>>  Hi Jenny,
>>>
>>> > What version are you running?
>>>
>>> 4.1.2.2-1.el7.centos
>>>
>>> > For the hosted engine vm to be imported and displayed in the engine, you
>>> > must first create a master storage domain.
>>>
>>> To provide a bit more detail: this was a migration of a bare-metal
>>> engine in an existing cluster to a hosted engine VM for that cluster.
>>> As part of this migration, I built an entirely new host and ran
>>> 'hosted-engine --deploy' (followed these instructions:
>>>
>>> http://www.ovirt.org/documentation/self-hosted/chap-Migrating_from_Bare_Metal_to_an_EL-Based_Self-Hosted_Environment/).
>>> I restored the backup from the engine and it completed without any
>>> errors. I didn't see any instructions regarding a master storage
>>> domain in the page above. The cluster has two existing master storage
>>> domains, one is fibre channel, which is up, and one ISO domain, which
>>> is currently offline.
>>>
>>> > What do you mean the hosted engine commands are failing? What happens
>>> > when
>>> > you run hosted-engine --vm-status now?
>>>
>>> Interestingly, whereas when I ran it before, it exited with no output
>>> and a return code of '1', it now reports:
>>>
>>> --== Host 1 status ==--
>>>
>>> conf_on_shared_storage : True
>>> Status up-to-date  : False
>>> Hostname   : kvm-ldn-03.ldn.fscfc.co.uk
>>> Host ID: 1
>>> Engine status  : unknown stale-data
>>> Score  : 0
>>> stopped: True
>>> Local maintenance  : False
>>> crc32  : 0217f07b
>>> local_conf_timestamp   : 2911
>>> Host timestamp : 2897
>>> Extra metadata (valid at timestamp):
>>> metadata_parse_version=1
>>> metadata_feature_version=1
>>> timestamp=2897 (Thu Jun 15 16:22:54 2017)
>>> host-id=1
>>> score=0
>>> vm_conf_refresh_time=2911 (Thu Jun 15 16:23:08 2017)
>>> conf_on_shared_storage=True
>>> maintenance=False
>>> state=AgentStopped
>>> stopped=True
>>>
>>> Yet I can login to the web GUI fine. I guess it is not HA due to being
>>> in an unknown state currently? Does the hosted-engine-ha rpm need to
>>> be installed across all nodes in the cluster, btw?
>>>
>>> Thanks for the help,
>>>
>>> Cam
>>>
>>> >
>>> > Jenny Tokar
>>> >
>>> >
>>> > On Thu, Jun 15, 2017 at 6:32 PM, cmc <iuco...@gmail.com> wrote:
>>> >>
>>> >> Hi,
>>> >>
>>> >> I've migrated from a bare-metal engine to a hosted engine. There were
>>> >> no errors during the install, however, the hosted engine did not get
>>> >> started. I tried running:
>>> >>
>>> >> hosted-engine --status
>>> >>
>>> >> on the host I deployed it on, and it returns nothing (exit code is 1
>>> >> however). I could not ping it either. So I tried starting it via
>>> >> 'hosted-engine --vm-start' and it returned:
>>> >>
>>> >> Virtual machine does not exist
>>> >>
>>> >> But it then became available. I logged into it successfully. It is not
>>> >> in the list of VMs however.
>>> >>
>>> >> Any ideas why the hosted-engine commands fail, and why it is not in
>>> >> the list of virtual machines?
>>> >>
>>> >> Thanks for any help,
>>> >>
>>> >> Cam
>>> >> ___
>>> >> Users mailing list
>>> >> Users@ovirt.org
>>> >> http://lists.ovirt.org/mailman/listinfo/users
>>> >
>>> >
>>
>>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] HostedEngine VM not visible, but running

2017-06-19 Thread cmc
 Hi Jenny,

> What version are you running?

4.1.2.2-1.el7.centos

> For the hosted engine vm to be imported and displayed in the engine, you
> must first create a master storage domain.

To provide a bit more detail: this was a migration of a bare-metal
engine in an existing cluster to a hosted engine VM for that cluster.
As part of this migration, I built an entirely new host and ran
'hosted-engine --deploy' (followed these instructions:
http://www.ovirt.org/documentation/self-hosted/chap-Migrating_from_Bare_Metal_to_an_EL-Based_Self-Hosted_Environment/).
I restored the backup from the engine and it completed without any
errors. I didn't see any instructions regarding a master storage
domain in the page above. The cluster has two existing master storage
domains, one is fibre channel, which is up, and one ISO domain, which
is currently offline.

> What do you mean the hosted engine commands are failing? What happens when
> you run hosted-engine --vm-status now?

Interestingly, whereas when I ran it before, it exited with no output
and a return code of '1', it now reports:

--== Host 1 status ==--

conf_on_shared_storage : True
Status up-to-date  : False
Hostname   : kvm-ldn-03.ldn.fscfc.co.uk
Host ID: 1
Engine status  : unknown stale-data
Score  : 0
stopped: True
Local maintenance  : False
crc32  : 0217f07b
local_conf_timestamp   : 2911
Host timestamp : 2897
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=2897 (Thu Jun 15 16:22:54 2017)
host-id=1
score=0
vm_conf_refresh_time=2911 (Thu Jun 15 16:23:08 2017)
conf_on_shared_storage=True
maintenance=False
state=AgentStopped
stopped=True

Yet I can login to the web GUI fine. I guess it is not HA due to being
in an unknown state currently? Does the hosted-engine-ha rpm need to
be installed across all nodes in the cluster, btw?

Thanks for the help,

Cam

>
> Jenny Tokar
>
>
> On Thu, Jun 15, 2017 at 6:32 PM, cmc <iuco...@gmail.com> wrote:
>>
>> Hi,
>>
>> I've migrated from a bare-metal engine to a hosted engine. There were
>> no errors during the install, however, the hosted engine did not get
>> started. I tried running:
>>
>> hosted-engine --status
>>
>> on the host I deployed it on, and it returns nothing (exit code is 1
>> however). I could not ping it either. So I tried starting it via
>> 'hosted-engine --vm-start' and it returned:
>>
>> Virtual machine does not exist
>>
>> But it then became available. I logged into it successfully. It is not
>> in the list of VMs however.
>>
>> Any ideas why the hosted-engine commands fail, and why it is not in
>> the list of virtual machines?
>>
>> Thanks for any help,
>>
>> Cam
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] HostedEngine VM not visible, but running

2017-06-15 Thread cmc
Hi,

I've migrated from a bare-metal engine to a hosted engine. There were
no errors during the install, however, the hosted engine did not get
started. I tried running:

hosted-engine --status

on the host I deployed it on, and it returns nothing (exit code is 1
however). I could not ping it either. So I tried starting it via
'hosted-engine --vm-start' and it returned:

Virtual machine does not exist

But it then became available. I logged into it successfully. It is not
in the list of VMs however.

Any ideas why the hosted-engine commands fail, and why it is not in
the list of virtual machines?

Thanks for any help,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] quick question on hosted engine storage

2017-06-15 Thread cmc
Thanks again Michael

On Thu, Jun 15, 2017 at 10:08 AM, Martin Sivak <msi...@redhat.com> wrote:
> Hi,
>
> the current code does not officially allow using the hosted engine
> storage domain for other VMs. We are currently working on removing
> that limitation.
>
> Best regards
>
> Martin Sivak
>
> On Thu, Jun 15, 2017 at 10:59 AM, cmc <iuco...@gmail.com> wrote:
>> If you choose fibre channel for the hosted engine storage, can this
>> storage be shared later by other VMs? I assume you don't need a
>> dedicated LUN, just one that isn't in use before hand.
>>
>> Thanks,
>>
>> C
>>
>> On Wed, Jun 14, 2017 at 6:28 PM, cmc <iuco...@gmail.com> wrote:
>>> Thanks Martin.
>>>
>>> On Wed, Jun 14, 2017 at 4:15 PM, Martin Sivak <msi...@redhat.com> wrote:
>>>> Hi,
>>>>
>>>> the storage is not migrated automatically. Hosted engine VM will keep
>>>> using the storage domain you configured during the setup phase.
>>>>
>>>> Best regards
>>>>
>>>> --
>>>> Martin Sivak
>>>> SLA / oVirt
>>>>
>>>>
>>>> On Wed, Jun 14, 2017 at 5:02 PM, cmc <iuco...@gmail.com> wrote:
>>>>> Hi,
>>>>>
>>>>> When building a hosted engine VM, and choosing 'nfs' for storage, it
>>>>> does the install to this nfs share. Once the host is setup with, e.g.,
>>>>> fibre channel as storage for VMs, does the hosted engine get migrated
>>>>> automatically to this storage? When does this actually happen?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Cam
>>>>> ___
>>>>> Users mailing list
>>>>> Users@ovirt.org
>>>>> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] quick question on hosted engine storage

2017-06-15 Thread cmc
Sorry, Thanks again Martin!

On Thu, Jun 15, 2017 at 11:51 AM, cmc <iuco...@gmail.com> wrote:
> Thanks again Michael
>
> On Thu, Jun 15, 2017 at 10:08 AM, Martin Sivak <msi...@redhat.com> wrote:
>> Hi,
>>
>> the current code does not officially allow using the hosted engine
>> storage domain for other VMs. We are currently working on removing
>> that limitation.
>>
>> Best regards
>>
>> Martin Sivak
>>
>> On Thu, Jun 15, 2017 at 10:59 AM, cmc <iuco...@gmail.com> wrote:
>>> If you choose fibre channel for the hosted engine storage, can this
>>> storage be shared later by other VMs? I assume you don't need a
>>> dedicated LUN, just one that isn't in use before hand.
>>>
>>> Thanks,
>>>
>>> C
>>>
>>> On Wed, Jun 14, 2017 at 6:28 PM, cmc <iuco...@gmail.com> wrote:
>>>> Thanks Martin.
>>>>
>>>> On Wed, Jun 14, 2017 at 4:15 PM, Martin Sivak <msi...@redhat.com> wrote:
>>>>> Hi,
>>>>>
>>>>> the storage is not migrated automatically. Hosted engine VM will keep
>>>>> using the storage domain you configured during the setup phase.
>>>>>
>>>>> Best regards
>>>>>
>>>>> --
>>>>> Martin Sivak
>>>>> SLA / oVirt
>>>>>
>>>>>
>>>>> On Wed, Jun 14, 2017 at 5:02 PM, cmc <iuco...@gmail.com> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> When building a hosted engine VM, and choosing 'nfs' for storage, it
>>>>>> does the install to this nfs share. Once the host is setup with, e.g.,
>>>>>> fibre channel as storage for VMs, does the hosted engine get migrated
>>>>>> automatically to this storage? When does this actually happen?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Cam
>>>>>> ___
>>>>>> Users mailing list
>>>>>> Users@ovirt.org
>>>>>> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] quick question on hosted engine storage

2017-06-15 Thread cmc
If you choose fibre channel for the hosted engine storage, can this
storage be shared later by other VMs? I assume you don't need a
dedicated LUN, just one that isn't in use before hand.

Thanks,

C

On Wed, Jun 14, 2017 at 6:28 PM, cmc <iuco...@gmail.com> wrote:
> Thanks Martin.
>
> On Wed, Jun 14, 2017 at 4:15 PM, Martin Sivak <msi...@redhat.com> wrote:
>> Hi,
>>
>> the storage is not migrated automatically. Hosted engine VM will keep
>> using the storage domain you configured during the setup phase.
>>
>> Best regards
>>
>> --
>> Martin Sivak
>> SLA / oVirt
>>
>>
>> On Wed, Jun 14, 2017 at 5:02 PM, cmc <iuco...@gmail.com> wrote:
>>> Hi,
>>>
>>> When building a hosted engine VM, and choosing 'nfs' for storage, it
>>> does the install to this nfs share. Once the host is setup with, e.g.,
>>> fibre channel as storage for VMs, does the hosted engine get migrated
>>> automatically to this storage? When does this actually happen?
>>>
>>> Thanks,
>>>
>>> Cam
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] quick question on hosted engine storage

2017-06-14 Thread cmc
Thanks Martin.

On Wed, Jun 14, 2017 at 4:15 PM, Martin Sivak <msi...@redhat.com> wrote:
> Hi,
>
> the storage is not migrated automatically. Hosted engine VM will keep
> using the storage domain you configured during the setup phase.
>
> Best regards
>
> --
> Martin Sivak
> SLA / oVirt
>
>
> On Wed, Jun 14, 2017 at 5:02 PM, cmc <iuco...@gmail.com> wrote:
>> Hi,
>>
>> When building a hosted engine VM, and choosing 'nfs' for storage, it
>> does the install to this nfs share. Once the host is setup with, e.g.,
>> fibre channel as storage for VMs, does the hosted engine get migrated
>> automatically to this storage? When does this actually happen?
>>
>> Thanks,
>>
>> Cam
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] quick question on hosted engine storage

2017-06-14 Thread cmc
Hi,

When building a hosted engine VM, and choosing 'nfs' for storage, it
does the install to this nfs share. Once the host is setup with, e.g.,
fibre channel as storage for VMs, does the hosted engine get migrated
automatically to this storage? When does this actually happen?

Thanks,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] problems migrating to hosted engine from bare metal

2017-06-13 Thread cmc
Hi,

I created a new host to deploy a hosted engine, and then used a backup
from the bare metal engine and restored this, as per the procedure in:

http://www.ovirt.org/documentation/self-hosted/chap-Migrating_from_Bare_Metal_to_an_EL-Based_Self-Hosted_Environment/

Everything worked fine up until step 15 ('Continue setup') as the
script said the engine was not responding. I tried the reboot option
(option 3), but still it would not connect. So I could not do the
final step involving the internal CA, adding the host to an existing
cluster (of which there were two other hosts). I was able to connect
via vnc and ssh fine to the engine, and from here I could see that the
ovirt-engine service was up. I had to install the aaa-ldap extension
package to enable ldap auth separately however, but once done I was
able to log in, and it showed the old cluster as it was on the bare
metal engine. I added the host that I created the hosted engine on,
and it installed various packages and then I configured the network
and it looked fine, apart from the fact that I could not see a VM
named 'HostedEngine' in the list of VMs. I think however that this was
not a properly working setup, as the NFS storage I used to setup the
hosted engine became unavailable and I think this killed the hosted
engine, which caused it to reboot the host it was on. The hosted
engine has not come back since then, so I'm guessing it either isn't
properly set up for HA or it needs the NFS storage or something else
was not properly done by me in the setup. I've restarted the bare
metal engine for now as I needed it running for now.

 My questions are:

1. My understanding is that the NFS storage is initially used to
create the hosted engine disk image, and is temporary, and that the
hosted engine later gets migrated to the storage used by the rest of
the cluster (which in my case is directly attached to the hosts via
fibre channel). I suspect that this did not happen. The bare metal
engine had some local ISO storage (on a hard disk local to it), which
will not be replicated to the hosted engine VM - will this cause a
problem for the deployment? I can create some new ISO storage later if
not.

2. What is the recommended way to recover from this situation? Should
I just run 'hosted-engine --deploy' again and try and find out what is
going wrong at step 15?

I can probably get the disk image that was on NFS and mount it to find
out what went wrong on the initial deployment, or I can run the
deployment again and then get the log when it fails at step 15.

Ovirt version was 4.1.2.2

Thanks for any help,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] virt-viewer disabling rhel6

2017-06-06 Thread cmc
Thanks for the update Lev.

On Sun, Jun 4, 2017 at 11:48 AM, Lev Veyde <lve...@redhat.com> wrote:

> Hi Cam,
>
> The reason why it works in RHEL 6.7 clients is due to the fact that
> version of virt-viewer that is supplied with it, doesn't support the
> mechanism to check for the minimum required version.
>
> Wasn't aware we can modify the versions we require through
> RemoteViewerSupportedVersions config. Michal - thanks for the hint.
>
> Thanks in advance,
>
> On Fri, Jun 2, 2017 at 4:00 PM, cmc <iuco...@gmail.com> wrote:
>
>> Thanks Michal, that is a huge help. We're busy building an image for EL7
>> but it isn't yet fully finished, so we're still on 6.x for now. We're
>> updating to 6.8 and then 6.9 in the meantime. Interesting that it still
>> works for 6.7 though - I can't explain that. I have updated
>> RemoteViewerSupportedVersions and restarted the engine and it works like a
>> charm.
>>
>> Cheers,
>>
>> Cam
>>
>> On Thu, Jun 1, 2017 at 7:22 PM, Michal Skrivanek <
>> michal.skriva...@redhat.com> wrote:
>>
>>>
>>> On 1 Jun 2017, at 15:10, Lev Veyde <lve...@redhat.com> wrote:
>>>
>>> Hi Cam,
>>>
>>> Unfotunately RHEL 6 clients are no longer supported in the oVirt 4.1 due
>>> to the new functions that were added which require a more recent version of
>>> the virt-viewer, thus the issue.
>>>
>>> You should use a more recent version e.g. to use RHEL 7 as the client to
>>> resolve the issue.
>>>
>>>
>>> That said, using engine-config you can change the version check and
>>> allow to launch it . You’ll miss some features but it may not really be
>>> that important if all you need is to see the screen and cannot update
>>> clients to EL7
>>> See https://bugzilla.redhat.com/show_bug.cgi?id=1285883
>>>
>>> Thanks,
>>> michal
>>>
>>>
>>> Thanks in advance,
>>>
>>> On Wed, May 31, 2017 at 4:50 PM, cmc <iuco...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> virt-viewer no longer appears to work when trying to launch a console
>>>> with EL 6.8 and oVirt 4.1. The error is:
>>>>
>>>> "At least Remote Viewer version 99.0-1 is required to setup this
>>>> connection"
>>>>
>>>> When I ran remote-viewer in debug mode, it seems that it is
>>>> deliberately disabling rhel6 by setting the version to a non-existent
>>>> version:
>>>>
>>>> (remote-viewer:23829): remote-viewer-DEBUG: Minimum version '2.0-160'
>>>> for OS id 'rhev-win64'
>>>> (remote-viewer:23829): remote-viewer-DEBUG: Minimum version '2.0-160'
>>>> for OS id 'rhev-win32'
>>>> (remote-viewer:23829): remote-viewer-DEBUG: Minimum version '2.0-6'
>>>> for OS id 'rhel7'
>>>> (remote-viewer:23829): remote-viewer-DEBUG: Minimum version '99.0-1'
>>>> for OS id 'rhel6'
>>>>
>>>> rhel 6.7 (and presumably brfore) works fine. I contacted the
>>>> maintainers of virt-viewer and they said that this is an ovirt issue.
>>>> Is this somehow disabled in 4.1? Can someone tell me why this is the
>>>> case?
>>>>
>>>> Thanks in advance for any insights,
>>>>
>>>> Cam
>>>> ___
>>>> Users mailing list
>>>> Users@ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Lev Veyde
>>>
>>> Software Engineer, RHCE | RHCVA | MCITP
>>> Red Hat Israel
>>>
>>> <https://www.redhat.com/>
>>>
>>> l...@redhat.com | lve...@redhat.com
>>> <https://red.ht/sig>
>>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
>
> Lev Veyde
>
> Software Engineer, RHCE | RHCVA | MCITP
>
> Red Hat Israel
>
> <https://www.redhat.com>
>
> l...@redhat.com | lve...@redhat.com
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] virt-viewer disabling rhel6

2017-06-02 Thread cmc
Thanks Michal, that is a huge help. We're busy building an image for EL7
but it isn't yet fully finished, so we're still on 6.x for now. We're
updating to 6.8 and then 6.9 in the meantime. Interesting that it still
works for 6.7 though - I can't explain that. I have updated
RemoteViewerSupportedVersions and restarted the engine and it works like a
charm.

Cheers,

Cam

On Thu, Jun 1, 2017 at 7:22 PM, Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

>
> On 1 Jun 2017, at 15:10, Lev Veyde <lve...@redhat.com> wrote:
>
> Hi Cam,
>
> Unfotunately RHEL 6 clients are no longer supported in the oVirt 4.1 due
> to the new functions that were added which require a more recent version of
> the virt-viewer, thus the issue.
>
> You should use a more recent version e.g. to use RHEL 7 as the client to
> resolve the issue.
>
>
> That said, using engine-config you can change the version check and allow
> to launch it . You’ll miss some features but it may not really be that
> important if all you need is to see the screen and cannot update clients to
> EL7
> See https://bugzilla.redhat.com/show_bug.cgi?id=1285883
>
> Thanks,
> michal
>
>
> Thanks in advance,
>
> On Wed, May 31, 2017 at 4:50 PM, cmc <iuco...@gmail.com> wrote:
>
>> Hi,
>>
>> virt-viewer no longer appears to work when trying to launch a console
>> with EL 6.8 and oVirt 4.1. The error is:
>>
>> "At least Remote Viewer version 99.0-1 is required to setup this
>> connection"
>>
>> When I ran remote-viewer in debug mode, it seems that it is
>> deliberately disabling rhel6 by setting the version to a non-existent
>> version:
>>
>> (remote-viewer:23829): remote-viewer-DEBUG: Minimum version '2.0-160'
>> for OS id 'rhev-win64'
>> (remote-viewer:23829): remote-viewer-DEBUG: Minimum version '2.0-160'
>> for OS id 'rhev-win32'
>> (remote-viewer:23829): remote-viewer-DEBUG: Minimum version '2.0-6'
>> for OS id 'rhel7'
>> (remote-viewer:23829): remote-viewer-DEBUG: Minimum version '99.0-1'
>> for OS id 'rhel6'
>>
>> rhel 6.7 (and presumably brfore) works fine. I contacted the
>> maintainers of virt-viewer and they said that this is an ovirt issue.
>> Is this somehow disabled in 4.1? Can someone tell me why this is the
>> case?
>>
>> Thanks in advance for any insights,
>>
>> Cam
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
>
> --
>
> Lev Veyde
>
> Software Engineer, RHCE | RHCVA | MCITP
> Red Hat Israel
>
> <https://www.redhat.com/>
>
> l...@redhat.com | lve...@redhat.com
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] virt-viewer disabling rhel6

2017-05-31 Thread cmc
Hi,

virt-viewer no longer appears to work when trying to launch a console
with EL 6.8 and oVirt 4.1. The error is:

"At least Remote Viewer version 99.0-1 is required to setup this connection"

When I ran remote-viewer in debug mode, it seems that it is
deliberately disabling rhel6 by setting the version to a non-existent
version:

(remote-viewer:23829): remote-viewer-DEBUG: Minimum version '2.0-160'
for OS id 'rhev-win64'
(remote-viewer:23829): remote-viewer-DEBUG: Minimum version '2.0-160'
for OS id 'rhev-win32'
(remote-viewer:23829): remote-viewer-DEBUG: Minimum version '2.0-6'
for OS id 'rhel7'
(remote-viewer:23829): remote-viewer-DEBUG: Minimum version '99.0-1'
for OS id 'rhel6'

rhel 6.7 (and presumably brfore) works fine. I contacted the
maintainers of virt-viewer and they said that this is an ovirt issue.
Is this somehow disabled in 4.1? Can someone tell me why this is the
case?

Thanks in advance for any insights,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] migration of a VM: fails

2017-05-23 Thread cmc
Hi Michal,

>
> is it from older host to newr host or vice versa?

They are now on the same version, and I still have some troubles
migrating hosts, but not consistently

> can you downgrade the new one to the same version and try again?

I've upgraded both now. I'll await Francesco's reply after the latest
tests, but as it happens after updating both hosts, I'm guessing it is
not specific to the older version

Thanks,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] migration of a VM: fails

2017-05-23 Thread cmc
Hi Francesco,

>
> do you always have the same error?

Yes

> Are you by any chance using the post copy migration mode?

Not sure what that is. The migration is initiated by either putting
the host in maintenance, or selecting 'upgrade' from the menu.

> Could you please share the libvirt debug logs, at least on the source side?
>
> https://wiki.libvirt.org/page/DebugLogs
>
> You may want to do a test run with the debug logs turned on and disable them
> just after, those are VERY verbose.
>

Before I put it into debug mode, I'd tried to migrate the troublesome
VM by itself, and it worked. So I then thought I try putting the host
that has that VM into maintenance, and it successfully copied that VM
over, but failed on another VM this time (a Linux VM). I took the host
out of maintenance, and switched on debug mode (restarting libvirtd
made the host rather unhappy, but it sorted itself out), and then
tried putting the host back into maintenance. It complained about
another VM failing to be migrated, though I couldn't see that VM on
the host. It did succeed in moving the VM that was causing it
problems, and is now in maintenance mode. So it seems a bit hit and
miss. Do you still want the logs?

Thanks,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Upgrade from rhel 6.7 to 6.8 breaks virt-viewer console

2017-05-18 Thread cmc
Hi,

 Having trouble launching consoles for VMs on rhel 6.8 (virt-viewer
2.0-14). I get:

"At least Remote Viewer version 99.0-1 is required to setup this connection"

It works fine in rhel 6.7 (using firefox or chrome). I downgraded the
version of virt-viewer to the 6.7 version (2.0-7) in 6.8 but then I
get a proxy error (no proxy is set in the browser).

Can someone tell me whether it is possible to get virt-viewer to
launch a console for a VM with oVirt 4.1 and rhel 6.8? This redhat
article (https://access.redhat.com/articles/2800531) says you need to
upgrade to rhel 7.0, but that is not an option. I've also read that it
was possible with a workaround with 4.0 but not 4.1.

Thanks for any help.

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] migration of a VM: fails

2017-05-18 Thread cmc
I have to shut the VM down to stop it trying to repeatedly trying to
migrate the problematic host (always the same one). If I take it out
of maintenance, it will move the VMs back to balance (as per policy),
so this is rather inconvenient. It took leaving it overnight and
letting oVirt try repeatedly every few minutes to get it to migrate
the VM (I can't wait that long, so I've had to shut that VM down for
now)

On Wed, May 17, 2017 at 4:13 PM, cmc <iuco...@gmail.com> wrote:
> Just a note on this: a similar thing is now happening with the same VM
> when I upgrade the other node, i.e., it can't move this one VM over
> (so far) from one host to another. I will leave it trying overnight to
> see if it succeeds.
>
> Thanks,
>
> Cam
>
> On Wed, May 17, 2017 at 11:40 AM, cmc <iuco...@gmail.com> wrote:
>> Hi Francesco,
>>
>> I left it running after I posted to the list, and it eventually (after
>> many failed attempts) moved the VM without any intervention by me, and
>> then updated the host, so that explains the differences in the
>> versions of qemu between the hosts (they probably would have been the
>> same when I tried the move first). The xml is attached.
>>
>> qemu and libvirt versions on the source host:
>>
>> ipxe-roms-qemu-20160127-5.git6366fa7a.el7.noarch
>> libvirt-daemon-driver-qemu-2.0.0-10.el7_3.5.x86_64
>> qemu-img-ev-2.6.0-28.el7_3.9.1.x86_64
>> qemu-kvm-common-ev-2.6.0-28.el7_3.9.1.x86_64
>> qemu-kvm-ev-2.6.0-28.el7_3.9.1.x86_64
>> qemu-kvm-tools-ev-2.6.0-28.el7_3.3.1.x86_64
>>
>> libvirt-2.0.0-10.el7_3.5.x86_64
>> libvirt-client-2.0.0-10.el7_3.5.x86_64
>> libvirt-daemon-2.0.0-10.el7_3.5.x86_64
>> libvirt-daemon-config-network-2.0.0-10.el7_3.5.x86_64
>> libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.5.x86_64
>> libvirt-daemon-driver-interface-2.0.0-10.el7_3.5.x86_64
>> libvirt-daemon-driver-lxc-2.0.0-10.el7_3.5.x86_64
>> libvirt-daemon-driver-network-2.0.0-10.el7_3.5.x86_64
>> libvirt-daemon-driver-nodedev-2.0.0-10.el7_3.5.x86_64
>> libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.5.x86_64
>> libvirt-daemon-driver-qemu-2.0.0-10.el7_3.5.x86_64
>> libvirt-daemon-driver-secret-2.0.0-10.el7_3.5.x86_64
>> libvirt-daemon-driver-storage-2.0.0-10.el7_3.5.x86_64
>> libvirt-daemon-kvm-2.0.0-10.el7_3.5.x86_64
>> libvirt-lock-sanlock-2.0.0-10.el7_3.5.x86_64
>> libvirt-python-2.0.0-2.el7.x86_64
>>
>> qemu and libvirt versions on the dest host:
>>
>> ipxe-roms-qemu-20160127-5.git6366fa7a.el7.noarch
>> libvirt-daemon-driver-qemu-2.0.0-10.el7_3.4.x86_64
>> qemu-img-ev-2.6.0-28.el7_3.3.1.x86_64
>> qemu-kvm-common-ev-2.6.0-28.el7_3.3.1.x86_64
>> qemu-kvm-ev-2.6.0-28.el7_3.3.1.x86_64
>> qemu-kvm-tools-ev-2.6.0-28.el7_3.3.1.x86_64
>>
>> libvirt-client-2.0.0-10.el7_3.4.x86_64
>> libvirt-daemon-2.0.0-10.el7_3.4.x86_64
>> libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.4.x86_64
>> libvirt-daemon-driver-interface-2.0.0-10.el7_3.4.x86_64
>> libvirt-daemon-driver-network-2.0.0-10.el7_3.4.x86_64
>> libvirt-daemon-driver-nodedev-2.0.0-10.el7_3.4.x86_64
>> libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.4.x86_64
>> libvirt-daemon-driver-qemu-2.0.0-10.el7_3.4.x86_64
>> libvirt-daemon-driver-secret-2.0.0-10.el7_3.4.x86_64
>> libvirt-daemon-driver-storage-2.0.0-10.el7_3.4.x86_64
>> libvirt-daemon-kvm-2.0.0-10.el7_3.4.x86_64
>> libvirt-lock-sanlock-2.0.0-10.el7_3.4.x86_64
>> libvirt-python-2.0.0-2.el7.x86_64
>>
>>
>> Thanks,
>>
>> Cam
>>
>> On Wed, May 17, 2017 at 9:12 AM, Francesco Romani <from...@redhat.com> wrote:
>>>
>>> On 05/16/2017 01:06 PM, cmc wrote:
>>>> Hi,
>>>>
>>>> Just trying to place in maintenance mode for a version upgrade, and
>>>> one VM fails to migrate. The other 20-odd move over successfully. In
>>>> /var/log/libvirt/qemu/, the VM's log on the source reports:
>>>>
>>>> 2017-05-16 09:48:06.339+: initiating migration
>>>> 2017-05-16T09:52:25.498932Z qemu-kvm: socket_writev_buffer: Got err=32
>>>> for (131328/18446744073709551615)
>>>> 2017-05-16 09:52:47.311+: initiating migration
>>>> 2017-05-16T09:57:06.755402Z qemu-kvm: socket_writev_buffer: Got err=32
>>>> for (69776/18446744073709551615)
>>>> 2017-05-16 09:57:55.109+: initiating migration
>>>> 2017-05-16T10:02:14.143221Z qemu-kvm: socket_writev_buffer: Got err=32
>>>> for (69776/18446744073709551615)
>>>> 2017-05-16 10:02:59.497+: initiating migration
>>>> 2017-05-16T10:07:18.542872Z qemu-kvm: socket_wri

Re: [ovirt-users] migration of a VM: fails

2017-05-17 Thread cmc
Just a note on this: a similar thing is now happening with the same VM
when I upgrade the other node, i.e., it can't move this one VM over
(so far) from one host to another. I will leave it trying overnight to
see if it succeeds.

Thanks,

Cam

On Wed, May 17, 2017 at 11:40 AM, cmc <iuco...@gmail.com> wrote:
> Hi Francesco,
>
> I left it running after I posted to the list, and it eventually (after
> many failed attempts) moved the VM without any intervention by me, and
> then updated the host, so that explains the differences in the
> versions of qemu between the hosts (they probably would have been the
> same when I tried the move first). The xml is attached.
>
> qemu and libvirt versions on the source host:
>
> ipxe-roms-qemu-20160127-5.git6366fa7a.el7.noarch
> libvirt-daemon-driver-qemu-2.0.0-10.el7_3.5.x86_64
> qemu-img-ev-2.6.0-28.el7_3.9.1.x86_64
> qemu-kvm-common-ev-2.6.0-28.el7_3.9.1.x86_64
> qemu-kvm-ev-2.6.0-28.el7_3.9.1.x86_64
> qemu-kvm-tools-ev-2.6.0-28.el7_3.3.1.x86_64
>
> libvirt-2.0.0-10.el7_3.5.x86_64
> libvirt-client-2.0.0-10.el7_3.5.x86_64
> libvirt-daemon-2.0.0-10.el7_3.5.x86_64
> libvirt-daemon-config-network-2.0.0-10.el7_3.5.x86_64
> libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.5.x86_64
> libvirt-daemon-driver-interface-2.0.0-10.el7_3.5.x86_64
> libvirt-daemon-driver-lxc-2.0.0-10.el7_3.5.x86_64
> libvirt-daemon-driver-network-2.0.0-10.el7_3.5.x86_64
> libvirt-daemon-driver-nodedev-2.0.0-10.el7_3.5.x86_64
> libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.5.x86_64
> libvirt-daemon-driver-qemu-2.0.0-10.el7_3.5.x86_64
> libvirt-daemon-driver-secret-2.0.0-10.el7_3.5.x86_64
> libvirt-daemon-driver-storage-2.0.0-10.el7_3.5.x86_64
> libvirt-daemon-kvm-2.0.0-10.el7_3.5.x86_64
> libvirt-lock-sanlock-2.0.0-10.el7_3.5.x86_64
> libvirt-python-2.0.0-2.el7.x86_64
>
> qemu and libvirt versions on the dest host:
>
> ipxe-roms-qemu-20160127-5.git6366fa7a.el7.noarch
> libvirt-daemon-driver-qemu-2.0.0-10.el7_3.4.x86_64
> qemu-img-ev-2.6.0-28.el7_3.3.1.x86_64
> qemu-kvm-common-ev-2.6.0-28.el7_3.3.1.x86_64
> qemu-kvm-ev-2.6.0-28.el7_3.3.1.x86_64
> qemu-kvm-tools-ev-2.6.0-28.el7_3.3.1.x86_64
>
> libvirt-client-2.0.0-10.el7_3.4.x86_64
> libvirt-daemon-2.0.0-10.el7_3.4.x86_64
> libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.4.x86_64
> libvirt-daemon-driver-interface-2.0.0-10.el7_3.4.x86_64
> libvirt-daemon-driver-network-2.0.0-10.el7_3.4.x86_64
> libvirt-daemon-driver-nodedev-2.0.0-10.el7_3.4.x86_64
> libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.4.x86_64
> libvirt-daemon-driver-qemu-2.0.0-10.el7_3.4.x86_64
> libvirt-daemon-driver-secret-2.0.0-10.el7_3.4.x86_64
> libvirt-daemon-driver-storage-2.0.0-10.el7_3.4.x86_64
> libvirt-daemon-kvm-2.0.0-10.el7_3.4.x86_64
> libvirt-lock-sanlock-2.0.0-10.el7_3.4.x86_64
> libvirt-python-2.0.0-2.el7.x86_64
>
>
> Thanks,
>
> Cam
>
> On Wed, May 17, 2017 at 9:12 AM, Francesco Romani <from...@redhat.com> wrote:
>>
>> On 05/16/2017 01:06 PM, cmc wrote:
>>> Hi,
>>>
>>> Just trying to place in maintenance mode for a version upgrade, and
>>> one VM fails to migrate. The other 20-odd move over successfully. In
>>> /var/log/libvirt/qemu/, the VM's log on the source reports:
>>>
>>> 2017-05-16 09:48:06.339+: initiating migration
>>> 2017-05-16T09:52:25.498932Z qemu-kvm: socket_writev_buffer: Got err=32
>>> for (131328/18446744073709551615)
>>> 2017-05-16 09:52:47.311+: initiating migration
>>> 2017-05-16T09:57:06.755402Z qemu-kvm: socket_writev_buffer: Got err=32
>>> for (69776/18446744073709551615)
>>> 2017-05-16 09:57:55.109+: initiating migration
>>> 2017-05-16T10:02:14.143221Z qemu-kvm: socket_writev_buffer: Got err=32
>>> for (69776/18446744073709551615)
>>> 2017-05-16 10:02:59.497+: initiating migration
>>> 2017-05-16T10:07:18.542872Z qemu-kvm: socket_writev_buffer: Got err=32
>>> for (69776/18446744073709551615)
>>> 2017-05-16 10:08:03.896+: initiating migration
>>> 2017-05-16T10:12:23.206731Z qemu-kvm: socket_writev_buffer: Got err=32
>>> for (69776/18446744073709551615)
>>> 2017-05-16 10:13:08.941+: initiating migration
>>> 2017-05-16T10:17:27.861843Z qemu-kvm: socket_writev_buffer: Got err=32
>>> for (69776/18446744073709551615)
>>> 2017-05-16 10:18:13.690+: initiating migration
>>> 2017-05-16T10:22:32.929689Z qemu-kvm: socket_writev_buffer: Got err=32
>>> for (69803/18446744073709551615)
>>> 2017-05-16 10:23:19.846+: initiating migration
>>> 2017-05-16T10:27:39.175724Z qemu-kvm: socket_writev_buffer: Got err=32
>>> for (69776/18446744073709551615)
>>> 2017-05-

[ovirt-users] migration of a VM: fails

2017-05-16 Thread cmc
Hi,

Just trying to place in maintenance mode for a version upgrade, and
one VM fails to migrate. The other 20-odd move over successfully. In
/var/log/libvirt/qemu/, the VM's log on the source reports:

2017-05-16 09:48:06.339+: initiating migration
2017-05-16T09:52:25.498932Z qemu-kvm: socket_writev_buffer: Got err=32
for (131328/18446744073709551615)
2017-05-16 09:52:47.311+: initiating migration
2017-05-16T09:57:06.755402Z qemu-kvm: socket_writev_buffer: Got err=32
for (69776/18446744073709551615)
2017-05-16 09:57:55.109+: initiating migration
2017-05-16T10:02:14.143221Z qemu-kvm: socket_writev_buffer: Got err=32
for (69776/18446744073709551615)
2017-05-16 10:02:59.497+: initiating migration
2017-05-16T10:07:18.542872Z qemu-kvm: socket_writev_buffer: Got err=32
for (69776/18446744073709551615)
2017-05-16 10:08:03.896+: initiating migration
2017-05-16T10:12:23.206731Z qemu-kvm: socket_writev_buffer: Got err=32
for (69776/18446744073709551615)
2017-05-16 10:13:08.941+: initiating migration
2017-05-16T10:17:27.861843Z qemu-kvm: socket_writev_buffer: Got err=32
for (69776/18446744073709551615)
2017-05-16 10:18:13.690+: initiating migration
2017-05-16T10:22:32.929689Z qemu-kvm: socket_writev_buffer: Got err=32
for (69803/18446744073709551615)
2017-05-16 10:23:19.846+: initiating migration
2017-05-16T10:27:39.175724Z qemu-kvm: socket_writev_buffer: Got err=32
for (69776/18446744073709551615)
2017-05-16 10:28:25.141+: initiating migration
2017-05-16T10:28:35.620070Z qemu-kvm: socket_writev_buffer: Got err=32
for (65753/18446744073709551615)
2017-05-16 10:29:10.678+: initiating migration
2017-05-16T10:33:29.718527Z qemu-kvm: socket_writev_buffer: Got err=32
for (53477/18446744073709551615)
2017-05-16 10:38:35.517+: initiating migration


On the destination host, it reports:

2017-05-16T10:33:29.598425Z qemu-kvm: Unknown combination of migration flags: 0
2017-05-16T10:33:29.599524Z qemu-kvm: error while loading state
section id 2(ram)
2017-05-16T10:33:29.601978Z qemu-kvm: load of migration failed: Invalid argument
2017-05-16 10:33:29.808+: shutting down

In the engine log:

2017-05-16 11:57:28,675+01 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
(DefaultQuartzScheduler5) [f8aa18b3-97b9-48e2-a681-cf3aaed330a5] VM
'4921c5f5-7748-47eb-a90c-8e9ecbd91bcf'(pete_win7) was unexpectedly
detected as 'MigratingTo' on VDS
'424e6317-ad68-459b-bf88-7292e26710ae'(kvm-ldn-02) (expected on
'e050c27f-8709-404c-b03e-59c0167a824b')


It stays in 'preparing for maintenance mode' on the GUI for the host,
and reports errors on the status pane below, but then it reports that
the host has successfully been put into maintenance mode, even though
the VM is still showing as in migration. After more time has elapsed,
it reports a failure again, and then eventually the host will again
report it is in maintenance mode, and so on.

When I hit 'cancel migration' it reports that the migration has been
successfully cancelled in the status pane at the bottom, but then
shows it still in migration in the upper window. When I select the VM
itself, it reports it is "Migrating From: 99%". If I cancel the
migration here, it actually does cancel the migration properly.

The VM itself is up and running ok.

Version of oVirt is 4.1.0.4-1.el7

Thanks in advance for any help. Please let me know if you need any full logs.

Regards,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vdsm issues between engine and host

2017-02-21 Thread cmc
Hi Piotr,

Thanks for the reply. It all looks healthy now. Regarding DNS, we had
some issues with it at the time. However, I think the main issue was
NetworkManager shutting the interface down seemingly at random. I had
thought it had been disabled when I set the machine up about 5 months
ago (and it has worked fine up until then). That, together with VDSM
being enabled on the engine I can't explain. The only change I had
made was an attempt to set up a hosted engine, which I did incorrectly
by not setting the host into maintenance and doing it there (I instead
tried to set it up as a VM on the running cluster). I can't see why
this may have made the changes above, but I would not know why.
Anyway, I've read the documentation more closely rather than hurrying
through it.

Feb 20 19:47:53 ovirt-engine NetworkManager[1061]: 
[1487620073.1858] device (enp5s0f0): state change: disconnected ->
prepare (reason 'none') [30 40 0]
Feb 20 19:47:53 ovirt-engine NetworkManager[1061]: 
[1487620073.1860] manager: NetworkManager state is now CONNECTING
Feb 20 19:47:53 ovirt-engine NetworkManager[1061]: 
[1487620073.1867] device (enp5s0f0): state change: prepare -> config
(reason 'none') [40 50 0]
Feb 20 19:47:53 ovirt-engine NetworkManager[1061]: 
[1487620073.2071] device (enp5s0f0): state change: config -> ip-config
(reason 'none') [50 70 0]
Feb 20 19:47:53 ovirt-engine NetworkManager[1061]: 
[1487620073.2120] device (enp5s0f0): state change: ip-config ->
ip-check (reason 'none') [70 80 0]
Feb 20 19:47:53 ovirt-engine NetworkManager[1061]: 
[1487620073.2160] device (enp5s0f0): state change: ip-check ->
secondaries (reason 'none') [80 90 0]
Feb 20 19:47:53 ovirt-engine NetworkManager[1061]: 
[1487620073.2164] device (enp5s0f0): state change: secondaries ->
activated (reason 'none') [90 100 0]
Feb 20 19:47:53 ovirt-engine NetworkManager[1061]: 
[1487620073.2166] manager: NetworkManager state is now CONNECTED_LOCAL
Feb 20 19:47:53 ovirt-engine NetworkManager[1061]: 
[1487620073.2889] manager: NetworkManager state is now
CONNECTED_GLOBAL

Thanks again and sorry to have wasted your time with this,

Cam

On Tue, Feb 21, 2017 at 8:59 AM, Piotr Kliczewski
<piotr.kliczew...@gmail.com> wrote:
> On Mon, Feb 20, 2017 at 9:47 PM, cmc <iuco...@gmail.com> wrote:
>> Hi,
>>
>> Due to networking and DNS issues. our engine was offlined (it is
>> physical machine currently, will be converting it to a VM in the
>> future when time allows). When service was restored, I noticed that
>> all the VMs were listed as being in an unknown state on one host. The
>> VMs were fine, but the engine could not ascertain their status as the
>> host itself was in an unknown state. vdsm was reporting errors and was
>> not running on the engine (or at least was in status 'failed' in
>> systemd). I tried starting vdsmd on the engine but it would not start.
>> I decided to try to restart vdsmd on the host and that did allow the
>> state of the VMs to be discovered, and the engine listed the host as
>> up again. However, there are still errors with vdsmd on both the host
>> and the engine, and the engine cannot start vdsmd. I guess it is able
>> to monitor the hosts in a limited way as it says they are both up.
>> There are communication errors between one of the hosts and the
>> engine: the host is refusing connections by the look of it
>>
>> from the engine log:
>>
>> 2017-02-20 18:41:51,226Z ERROR
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
>> (DefaultQuartzScheduler2) [f8aa18b3-97b9-48e2-a681-cf3aaed330a5]
>> Command 'GetCapabilitiesVDSCommand(HostName = k
>> vm-ldn-01, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
>> hostId='e050c27f-8709-404c-b03e-59c0167a824b',
>> vds='Host[kvm-ldn-01,e050c27f-8709-404c-b03e-59c0167a824b]'})'
>> execution failed: java.net.ConnectExce
>> ption: Connection refused
>> 2017-02-20 18:41:51,226Z ERROR
>> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
>> (DefaultQuartzScheduler2) [f8aa18b3-97b9-48e2-a681-cf3aaed330a5]
>> Failure to refresh host 'kvm-ldn-01' runtime info: java.n
>> et.ConnectException: Connection refused
>> 2017-02-20 18:41:52,772Z ERROR
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
>> (DefaultQuartzScheduler6) [f8aa18b3-97b9-48e2-a681-cf3aaed330a5]
>> Command 'GetAllVmStatsVDSCommand(HostName = kvm-ldn-01,
>> VdsIdVDSCommandParametersBase:{runAsync='true',
>> hostId='e050c27f-8709-404c-b03e-59c0167a824b'})' execution failed:
>> VDSGenericException: VDSNetworkException: Connection reset by peer
>> 2017-02-20 18:41:54,256Z ERROR
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
>> (DefaultQuartzSchedul

Re: [ovirt-users] vdsm issues between engine and host

2017-02-20 Thread cmc
>
> VDSM should not be running on the engine.

Not sure why it was enabled in systemd...I have disabled it now. AFAIK
it wasn't before.

> I decided to try to restart vdsmd on the host and that did allow the
> state of the VMs to be discovered, and the engine listed the host as
> up again. However, there are still errors with vdsmd on both the host
> and the engine, and the engine cannot start vdsmd. I guess it is able
> to monitor the hosts in a limited way as it says they are both up.
> There are communication errors between one of the hosts and the
> engine: the host is refusing connections by the look of it
>
>
> Is iptables / firewalld set up correctly?
> Y.

Ports 54321 and 22 are open from engine to host. Is there an easy way to check
the config is valid? It certainly used to work ok.

Thanks,

C
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] questions about migrating to self-hosted engine from bare-metal

2017-02-14 Thread cmc
Ok, thanks for clarifying that Simone. I will read the guide more thoroughly.

Cheers,

Cam

On Tue, Feb 14, 2017 at 1:47 PM, Simone Tiraboschi <stira...@redhat.com> wrote:
>
>
> On Tue, Feb 14, 2017 at 2:36 PM, cmc <iuco...@gmail.com> wrote:
>>
>> Hi Simone,
>>
>> >>
>> >
>> > It fails due to this one:
>> > 2017-02-13 13:07:45,812 ERROR (vm/642a0b9a) [virt.vm]
>> > (vmId='642a0b9a-49fc-4ccc-8976-f6685953d0e8') The vm start process
>> > failed
>> > (vm:616)
>> > Traceback (most recent call last):
>> >   File "/usr/share/vdsm/virt/vm.py", line 552, in _startUnderlyingVm
>> > self._run()
>> >   File "/usr/share/vdsm/virt/vm.py", line 1994, in _run
>> > self._connection.createXML(domxml, flags),
>> >   File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py",
>> > line
>> > 123, in wrapper
>> > ret = f(*args, **kwargs)
>> >   File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 941, in
>> > wrapper
>> > return func(inst, *args, **kwargs)
>> >   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3782, in
>> > createXML
>> > if ret is None:raise libvirtError('virDomainCreateXML() failed',
>> > conn=self)
>> > libvirtError: invalid argument: could not find capabilities for
>> > arch=x86_64
>> > domaintype=kvm
>> > 2017-02-13 13:07:45,852 INFO  (vm/642a0b9a) [virt.vm]
>> > (vmId='642a0b9a-49fc-4ccc-8976-f6685953d0e8') Changed state to Down:
>> > invalid
>> > argument: could not find capabilities for arch=x86_64 domaintype=kvm
>> > (code=1) (vm:1199)
>> >
>> > Is your CPU properly configured for virtualization? Are you running on a
>> > nested env?
>> >
>>
>> Yes, I assume it should be configured for virtualisation, since this
>> VM I'm creating to replace the bare-metal engine is running on one of
>> the two hosts that make up the cluster, and host 30 other running VMs
>> currently. Should it not run on the same cluster perhaps?
>>
>> My steps are:
>>
>> 1. Create a VM on the cluster. Install the ovirt release rpm, install
>> the packages ovirt-hosted-engine-setup and ovirt-engine-appliance
>> 2. run hosted-engine --deploy
>>
>> ...and that is as far as I have gotten so far.
>
>
> OK, a bit of confusion here:
> ovirt-hosted-engine-setup is going to create a VM for you based on
> ovirt-engine-appliance (with the engine).
> If you manually create a VM (L1) on your physical host (L0) to run
> hosted-engine-setup there, hosted-engine-setup will create a VM (L2) for the
> engine running inside the L1 VM and this requires nested virtualization
> support which I think it's not enabled by default on oVirt hosts.
> But the point is that you simply have to run ovirt-hosted-engine-setup on
> your physical host and not on a VM otherwise all the HA mechanism of
> hosted-engine will make no sense if nothing is bringing up your virtual
> hosts for you.
>
> hosted-engine-setup requires an host with no others running VMs so, if it's
> already managed my an engine, move it to maintenance and remove it from your
> cluster.
>
>
>>
>>
>> Thanks,
>>
>> Cam
>>
>> >
>> >>
>> >> Thanks,
>> >>
>> >> Cam
>> >>
>> >>
>> >> On Mon, Feb 13, 2017 at 6:22 PM, Yaniv Kaul <yk...@redhat.com> wrote:
>> >> >
>> >> > On Mon, Feb 13, 2017 at 6:26 PM, cmc <iuco...@gmail.com> wrote:
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170213141937-0wgc31.log
>> >> >
>> >> >
>> >> > Anything in the above log?
>> >> > Y.
>> >> >
>> >>
>> >> ___
>> >> Users mailing list
>> >> Users@ovirt.org
>> >> http://lists.ovirt.org/mailman/listinfo/users
>> >>
>> >
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] questions about migrating to self-hosted engine from bare-metal

2017-02-14 Thread cmc
Hi Simone,

>>
>
> It fails due to this one:
> 2017-02-13 13:07:45,812 ERROR (vm/642a0b9a) [virt.vm]
> (vmId='642a0b9a-49fc-4ccc-8976-f6685953d0e8') The vm start process failed
> (vm:616)
> Traceback (most recent call last):
>   File "/usr/share/vdsm/virt/vm.py", line 552, in _startUnderlyingVm
> self._run()
>   File "/usr/share/vdsm/virt/vm.py", line 1994, in _run
> self._connection.createXML(domxml, flags),
>   File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line
> 123, in wrapper
> ret = f(*args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 941, in
> wrapper
> return func(inst, *args, **kwargs)
>   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3782, in
> createXML
> if ret is None:raise libvirtError('virDomainCreateXML() failed',
> conn=self)
> libvirtError: invalid argument: could not find capabilities for arch=x86_64
> domaintype=kvm
> 2017-02-13 13:07:45,852 INFO  (vm/642a0b9a) [virt.vm]
> (vmId='642a0b9a-49fc-4ccc-8976-f6685953d0e8') Changed state to Down: invalid
> argument: could not find capabilities for arch=x86_64 domaintype=kvm
> (code=1) (vm:1199)
>
> Is your CPU properly configured for virtualization? Are you running on a
> nested env?
>

Yes, I assume it should be configured for virtualisation, since this
VM I'm creating to replace the bare-metal engine is running on one of
the two hosts that make up the cluster, and host 30 other running VMs
currently. Should it not run on the same cluster perhaps?

My steps are:

1. Create a VM on the cluster. Install the ovirt release rpm, install
the packages ovirt-hosted-engine-setup and ovirt-engine-appliance
2. run hosted-engine --deploy

...and that is as far as I have gotten so far.

Thanks,

Cam

>
>>
>> Thanks,
>>
>> Cam
>>
>>
>> On Mon, Feb 13, 2017 at 6:22 PM, Yaniv Kaul <yk...@redhat.com> wrote:
>> >
>> > On Mon, Feb 13, 2017 at 6:26 PM, cmc <iuco...@gmail.com> wrote:
>> >>
>> >>
>> >>
>> >> /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170213141937-0wgc31.log
>> >
>> >
>> > Anything in the above log?
>> > Y.
>> >
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] questions about migrating to self-hosted engine from bare-metal

2017-02-13 Thread cmc
Hi Yaniv,

Log attached. There's a bit in there where I'd tried setting the host
record to point to the new host as an experiment, but I changed it
back, and it still fails with the same error every time.

Thanks,

Cam


On Mon, Feb 13, 2017 at 6:22 PM, Yaniv Kaul <yk...@redhat.com> wrote:
>
> On Mon, Feb 13, 2017 at 6:26 PM, cmc <iuco...@gmail.com> wrote:
>>
>>
>> /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170213141937-0wgc31.log
>
>
> Anything in the above log?
> Y.
>


ovirt-hosted-engine-setup-20170213141937-0wgc31.log.gz
Description: GNU Zip compressed data
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] [Call for feedback] did you install/update to 4.1.0?

2017-02-06 Thread cmc
Hi Sandro,

I upgraded my 2 host setup + engine (engine is currently on separate
hardware, but I plan to make it self-hosted), and it went like
clockwork. My engine + hosts were running 4.0.5 and 7.2, so after
installing 4.1 release, I did an OS update to 7.3 first, starting with
the engine, then ran engine-setup. I opted to do a 'yum upgrade' on
the the first host, which actually updated all the ovirt packages as
well and rebooted (I'm not sure this is an approved method, but it
worked fine). After the first host was back, I upgraded the second
host from the GUI, but then I ran a yum upgrade to update all the OS
stuff, such as the kernel, libc etc, and rebooted.

Many thanks for making the upgrade process so smooth!

Cheers,

Cam

On Thu, Feb 2, 2017 at 12:19 PM, Sandro Bonazzola  wrote:
> Hi,
> did you install/update to 4.1.0? Let us know your experience!
> We end up knowing only when things doesn't work well, let us know it works
> fine for you :-)
>
> If you're not planning an update to 4.1.0 in the near future, let us know
> why.
> Maybe we can help.
>
> Thanks!
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] high availability

2017-02-03 Thread cmc
Hi,

I have some questions about oVirt's high availability features for
VMs. My understanding is that it relies on the engine host to monitor
and manage the hypervisor hosts, so that in the case of a
unrecoverable failure of one those hosts, it will fence the host and
migrate any VM that is designated as highly available to another host
in the cluster. However, if the engine is itself hosted as a VM on a
host that fails, this process cannot take place, as the engine will be
down and cannot initiate monitoring, fencing and migration - is that
correct?

There is the option of hosting the engine externally on dedicated
hardware, or on another cluster, but then it is still a single point
of failure. I recall reading about plans for an HA engine in the
future though.

Can someone tell me what the roadmap is? Is there a plan to put
something like an HA agent on all the hypervisors in the cluster so
there is no single point of failure?

Thanks for any information,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] [ovirt-devel] New oVirt 4.0.x documentation now live!

2017-01-16 Thread cmc
When I try to go to
http://www.ovirt.org/documentation/upgrade-guide/upgrade-guide/, and
click on any of the links on that page, e.g.,:

http://www.ovirt.org/documentation/upgrade-guide/upgrade-guide/chap-Updating_the_oVirt_Environment
http://www.ovirt.org/documentation/upgrade-guide/upgrade-guide/chap-Updates_between_Minor_Releases

I get:

Not found :(

Sorry, but the page you were trying to view does not exist.

It looks like this was the result of either:

a mistyped address
an out-of-date link

In fact, I get that on just about every link I've tried from
https://www.ovirt.org/documentation/

Am I missing something here perhaps?

-C

On Mon, Jan 16, 2017 at 5:39 PM, Brian Proffitt  wrote:
> You wanted it, we delivered!
>
> The oVirt Project is pleased to announce the availability of all-new
> principal documentation[1] for the oVirt 4.0 branch!
>
> For more information, check out the blog released today[2]!
>
> Peace,
> Brian
>
>
> [1] https://www.ovirt.org/documentation/
> [2] https://www.ovirt.org/blog/2017/01/happy-new-documentation/
>
> --
> Brian Proffitt
> Principal Community Analyst
> Open Source and Standards
> @TheTechScribe
> 574.383.9BKP
>
> ___
> Devel mailing list
> de...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] question regarding fencing proxies

2017-01-14 Thread cmc
Thanks Martin. That is what I assumed was the case, but got worried
when the host could not communicate with the idrac via the 'Test'
option in the GUI. I planned to test it when I get a chance by
migrating all VMs bar one to the other host, setting the remaining one
as HA, and then bringing that host down to see if it gets migrated
successfully. I do plan to add a 3rd host.

I was looking at adding an APC agent as well. Can you tell me whether
4.x supports 2 PDUs per host? We have diverse power on each server. I
saw a post in 2012 that only one was supported and didn't see an
option for adding two slots in the GUI.

Thanks,

Cam

On Sat, Jan 14, 2017 at 12:07 PM, Martin Perina <mper...@redhat.com> wrote:
> Hi,
>
> engine executes power management (fencing) operation using different host in
> the same cluster/DC as target host reside. It's an oVirt requirement that
> each host in the same cluster and data center is able to connect to power
> management deviced of all other hosts in the same cluster/DC.
>
>
> Here's simplified flow for defaults (fence proxy may be selected in the same
> cluster or DC)
>
> 1. Find all existing hosts in the same cluster which don't have connection
> issues (status Up, Maintenance, NonOperational for a reason different than
> network issues)
> 2. Select first host in Up (if no host is Up, then pick any other host, if
> no host found continue with DC in step 5) and try to execute fence operation
> 3. If fence operation is successful, exit
> 4. If not, retry 2 times and if still not successful go back to step 2 but
> exclude already problematic fence proxy
> 5. Find all existing hosts in the same data center which don't have
> connection issues (status Up, Maintenance, NonOperational for a reason
> different than network issues)
> 6. Select first host in Up (if no host is Up, then pick any other host, if
> no host found then fail and exit) and try to execute fence operation
> 7. If fence operation is successful, exit
> 8. If not, retry 2 times and if still not successful go back to step 6 but
> exclude already problematic fence proxy
> 9. If still no success, fail
>
> As you see your setup with only 2 hosts is kinda fragile (and not only for
> fencing operations), you need to assure that 1 hosts is always in perfect
> condition. If possible I'd recommend you to add at least one other host if
> possible to make your setup more resistant to failures.
>
> Martin Perina
>
>
> On Fri, Jan 13, 2017 at 6:10 PM, cmc <iuco...@gmail.com> wrote:
>>
>> Hi,
>>
>> Can someone tell me how the engine decides which power management
>> proxy/proxies to use (using default cluster/dc config)? I am using
>> drac 7 for a fence agent in my two host cluster, and have noticed that
>> one of the hosts cannot contact the drac. My guess is that the engine
>> is using one host to as a power management proxy and hosts cannot
>> reach their own drac as they are on the same interface + vlan.
>>
>> Example scenario:
>>
>> Engine uses host 2 as power management proxy. It can contact host 1’s
>> drac, but cannot contact its own drac. In the case of host 2 being
>> unreachable/kdumping etc, would the engine switch to use host 1 as the
>> proxy to contact host 2’s drac?
>>
>> Thanks,
>>
>> Cam
>>
>> PS: I'd like to use the APC as an additional fencing agent, each host
>> has two PSUs connected to two different APCs. Is there a guide on how
>> to specify two ports on two different PDUs to control power on a host?
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] question regarding fencing proxies

2017-01-13 Thread cmc
Hi,

Can someone tell me how the engine decides which power management
proxy/proxies to use (using default cluster/dc config)? I am using
drac 7 for a fence agent in my two host cluster, and have noticed that
one of the hosts cannot contact the drac. My guess is that the engine
is using one host to as a power management proxy and hosts cannot
reach their own drac as they are on the same interface + vlan.

Example scenario:

Engine uses host 2 as power management proxy. It can contact host 1’s
drac, but cannot contact its own drac. In the case of host 2 being
unreachable/kdumping etc, would the engine switch to use host 1 as the
proxy to contact host 2’s drac?

Thanks,

Cam

PS: I'd like to use the APC as an additional fencing agent, each host
has two PSUs connected to two different APCs. Is there a guide on how
to specify two ports on two different PDUs to control power on a host?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to delete VM disk

2017-01-13 Thread cmc
Thanks Alexander, when I upgrade I'll let you know if doesn't resolve
the issue (also am happy to let you know if it does). I haven't got a
time for when I'll upgrade at this point however.

Cheers,

Cam

On Fri, Jan 13, 2017 at 1:36 PM, Alexander Wels <aw...@redhat.com> wrote:
> On Thursday, January 12, 2017 2:09:00 PM EST cmc wrote:
>> Hi Alexander,
>>
>> That is correct. When I click remove disk, it gives me a remove disk
>> dialogue, and when I click 'OK' (whether I tick 'remove permanently'
>> or not) it will throw an exception.
>>
>> Thanks,
>>
>> Cam
>>
>
> Hi,
>
> In that case this is highly likely an instance of https://bugzilla.redhat.com/
> show_bug.cgi?id=1391466 where some of the memory cleanup code we added was a
> little to aggressive in cleaning up some of the event handlers that were
> causing memory leaks. 4.0.6 should have that issue fixed.
>
> Basically when the remove disk dialog pops up, the handlers/memory structures
> were cleaned up when they shouldn't have been causing the exception you are
> seeing.
>
> Alexander
>
>> On Thu, Jan 12, 2017 at 1:53 PM, Alexander Wels <aw...@redhat.com> wrote:
>> > On Friday, December 30, 2016 11:45:20 AM EST cmc wrote:
>> >> Hi Alexander,
>> >>
>> >> Thanks. I've attached the log. Relevant error is the last entry.
>> >>
>> >> Kind regards,
>> >>
>> >> Cam
>> >
>> > Just to be clear on the flow when this occurs, you do the following on a
>> > VM
>> > that is shut down:
>> >
>> > 1. Select the VM in the VM grid.
>> > 2. Click edit and the edit VM dialog pops up.
>> > 3. In the General tab you scroll down a little until you see the instance
>> >
>> > Images widget that has the disk listed. You have 3 options:
>> >   - Edit (edit disk)
>> >   - + (add new row, that will give you the option to attach/create a disk)
>> >   - - (remove disk)
>> >
>> > You click - (remove disk)?
>> > 4. You get the exception?
>> >
>> > Alexander
>> >
>> >> On Wed, Dec 14, 2016 at 3:12 PM, Alexander Wels <aw...@redhat.com> wrote:
>> >> > On Wednesday, December 14, 2016 11:51:49 AM EST cmc wrote:
>> >> >> Having some difficulty in getting the permutation string currently, as
>> >> >> I can't get a cache.html file to appear in the Network section of the
>> >> >> debugger, and both browsers I'm using (Chrome and FIrefox) do not
>> >> >> print the permutation ID at the bottom of the console output. I'll see
>> >> >> if I can get some more detail on how this works from some searching
>> >> >
>> >> > I improved that, I just haven't updated the wiki, as soon as you
>> >> > install
>> >> > the symbol maps, and you can recreate the issue, then the UI.log should
>> >> > have the unobfuscated stack trace, so you don't have to do all that
>> >> > stuff
>> >> > manually anymore.
>> >> >
>> >> >> On Wed, Dec 14, 2016 at 8:21 AM, Fred Rolland <froll...@redhat.com>
>> >
>> > wrote:
>> >> >> > The UI log is obfuscated.
>> >> >> > Can you please follow instruction on [1] and reproduce so that we
>> >> >> > get a
>> >> >> > human readable log.
>> >> >> >
>> >> >> > Thanks
>> >> >> >
>> >> >> > [1]
>> >> >> > http://www.ovirt.org/develop/developer-guide/engine/engine-debug-obf
>> >> >> > usc
>> >> >> > ate
>> >> >> > d-ui/>
>> >> >> >
>> >> >> > On Tue, Dec 13, 2016 at 7:42 PM, cmc <iuco...@gmail.com> wrote:
>> >> >> >> Sorry, forgot the version: 4.0.5.5-1.el7.centos
>> >> >> >>
>> >> >> >> On Tue, Dec 13, 2016 at 5:37 PM, cmc <iuco...@gmail.com> wrote:
>> >> >> >> > On the VM in the list of VMs, by right-clicking on it. It then
>> >> >> >> > gives
>> >> >> >> > you a pop up window to edit the VM, starting in the 'General'
>> >> >> >> > section
>> >> >> >> > (much as when you create a new one)
>> >> >> >> >
>> >> >> >> > Thanks,
>> >> >> >> >
>

[ovirt-users] repository issues causing updates to fail

2017-01-12 Thread cmc
Hi,

engine version: 4.0.5.5-1.el7.centos

I have an oVirt cluster with 2 hosts and my engine node is reporting
failed updates on the hosts. I checked the logs in
/var/log/ovirt-engine/host-deploy/ and found that it reports
dependency failures.

-8<-

2017-01-12 10:53:16 ERROR
otopi.plugins.ovirt_host_mgmt.packages.update update.error:102 Yum:
[u'10:qemu-kvm-ev-2.6.0-27.1.el7.x86_64 requires usbredir >= 0.7.1',
u'10:qemu-kvm-ev-2.6.0-27.1.el7.x86_64 requires seavgabios-bin >=
1.9.1-4', u'10:qemu-kvm-ev-2.6.0-27.1.el7.x86_64 requires
ipxe-roms-qemu >= 20160127-4']
2017-01-12 10:53:16 INFO otopi.plugins.ovirt_host_mgmt.packages.update
update.info:98 Yum: Performing yum transaction rollback
2017-01-12 10:53:16 DEBUG otopi.context context._executeMethod:142
method exception
Traceback (most recent call last):
  File "/tmp/ovirt-tA0ldayV0j/pythonlib/otopi/context.py", line 132,
in _executeMethod
method['method']()
  File "/tmp/ovirt-tA0ldayV0j/otopi-plugins/ovirt-host-mgmt/packages/update.py",
line 115, in _packagesCheck
if myum.buildTransaction():
  File "/tmp/ovirt-tA0ldayV0j/pythonlib/otopi/miniyum.py", line 919,
in buildTransaction
raise yum.Errors.YumBaseError(msg)
YumBaseError: [u'10:qemu-kvm-ev-2.6.0-27.1.el7.x86_64 requires
usbredir >= 0.7.1', u'10:qemu-kvm-ev-2.6.0-27.1.el7.x86_64 requires
seavgabios-bin >= 1.9.1-4', u'10:qemu-kvm-ev-2.6.0-27.1.el7.x86_64
requires ipxe-roms-qemu >= 20160127-4']
2017-01-12 10:53:16 ERROR otopi.context context._executeMethod:151
Failed to execute stage 'Package installation':
[u'10:qemu-kvm-ev-2.6.0-27.1.el7.x86_64 requires usbredir >= 0.7.1',
u'10:qemu-kvm-ev-2.6.0-27.1.el7.x86_64 requires seavgabios-bin >=
1.9.1-4', u'10:qemu-kvm-ev-2.6.0-27.1.el7.x86_64 requires
ipxe-roms-qemu >= 20160127-4']
2017-01-12 10:53:16 DEBUG otopi.transaction transaction.abort:119
aborting 'Yum Transaction'
2017-01-12 10:53:16 INFO otopi.plugins.otopi.packagers.yumpackager
yumpackager.info:80 Yum Performing yum transaction rollback
2017-01-12 10:53:16 DEBUG
otopi.plugins.ovirt_host_mgmt.packages.update update.verbose:94 Yum:
Repository virtio-win-stable is listed more than once in the
configuration
2017-01-12 10:53:16 DEBUG otopi.context context.dumpEnvironment:760
ENVIRONMENT DUMP - BEGIN
2017-01-12 10:53:16 DEBUG otopi.context context.dumpEnvironment:770
ENV BASE/error=bool:'True'

-

I've had a search in various repos for the usbredir-0.7.1,
ipxe-roms-qemu  20160127-4 and seavgabios-bin 1.9.1-4, and these exist
in 7.3 but not 7.2 (I am running 7.2). Should I just ignore these
messages then?

Thanks,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to delete VM disk

2017-01-12 Thread cmc
Hi Alexander,

That is correct. When I click remove disk, it gives me a remove disk
dialogue, and when I click 'OK' (whether I tick 'remove permanently'
or not) it will throw an exception.

Thanks,

Cam

On Thu, Jan 12, 2017 at 1:53 PM, Alexander Wels <aw...@redhat.com> wrote:
> On Friday, December 30, 2016 11:45:20 AM EST cmc wrote:
>> Hi Alexander,
>>
>> Thanks. I've attached the log. Relevant error is the last entry.
>>
>> Kind regards,
>>
>> Cam
>>
>
> Just to be clear on the flow when this occurs, you do the following on a VM
> that is shut down:
>
> 1. Select the VM in the VM grid.
> 2. Click edit and the edit VM dialog pops up.
> 3. In the General tab you scroll down a little until you see the instance
> Images widget that has the disk listed. You have 3 options:
>   - Edit (edit disk)
>   - + (add new row, that will give you the option to attach/create a disk)
>   - - (remove disk)
> You click - (remove disk)?
> 4. You get the exception?
>
> Alexander
>
>> On Wed, Dec 14, 2016 at 3:12 PM, Alexander Wels <aw...@redhat.com> wrote:
>> > On Wednesday, December 14, 2016 11:51:49 AM EST cmc wrote:
>> >> Having some difficulty in getting the permutation string currently, as
>> >> I can't get a cache.html file to appear in the Network section of the
>> >> debugger, and both browsers I'm using (Chrome and FIrefox) do not
>> >> print the permutation ID at the bottom of the console output. I'll see
>> >> if I can get some more detail on how this works from some searching
>> >
>> > I improved that, I just haven't updated the wiki, as soon as you install
>> > the symbol maps, and you can recreate the issue, then the UI.log should
>> > have the unobfuscated stack trace, so you don't have to do all that stuff
>> > manually anymore.
>> >
>> >> On Wed, Dec 14, 2016 at 8:21 AM, Fred Rolland <froll...@redhat.com>
> wrote:
>> >> > The UI log is obfuscated.
>> >> > Can you please follow instruction on [1] and reproduce so that we get a
>> >> > human readable log.
>> >> >
>> >> > Thanks
>> >> >
>> >> > [1]
>> >> > http://www.ovirt.org/develop/developer-guide/engine/engine-debug-obfusc
>> >> > ate
>> >> > d-ui/>
>> >> >
>> >> > On Tue, Dec 13, 2016 at 7:42 PM, cmc <iuco...@gmail.com> wrote:
>> >> >> Sorry, forgot the version: 4.0.5.5-1.el7.centos
>> >> >>
>> >> >> On Tue, Dec 13, 2016 at 5:37 PM, cmc <iuco...@gmail.com> wrote:
>> >> >> > On the VM in the list of VMs, by right-clicking on it. It then gives
>> >> >> > you a pop up window to edit the VM, starting in the 'General'
>> >> >> > section
>> >> >> > (much as when you create a new one)
>> >> >> >
>> >> >> > Thanks,
>> >> >> >
>> >> >> > Cam
>> >> >> >
>> >> >> > On Tue, Dec 13, 2016 at 5:04 PM, Fred Rolland <froll...@redhat.com>
>> >> >> >
>> >> >> > wrote:
>> >> >> >> Hi,
>> >> >> >>
>> >> >> >> Which version are you using ?
>> >> >> >> When you mention "Edit", on which entity is it performed.?
>> >> >> >>
>> >> >> >> The disks are currently not part of the edit VM window.
>> >> >> >>
>> >> >> >> Thanks,
>> >> >> >> Freddy
>> >> >> >>
>> >> >> >> On Tue, Dec 13, 2016 at 6:06 PM, cmc <iuco...@gmail.com> wrote:
>> >> >> >>> This VM wasn't running.
>> >> >> >>>
>> >> >> >>> On Tue, Dec 13, 2016 at 4:02 PM, Elad Ben Aharon
>> >> >> >>> <ebena...@redhat.com>
>> >> >> >>>
>> >> >> >>> wrote:
>> >> >> >>> > In general, in order to delete a disk while it is attached to a
>> >> >> >>> > running
>> >> >> >>> > VM,
>> >> >> >>> > the disk has to be deactivated (hotunplugged) first so it won't
>> >> >> >>> > be
>> >> >> >>> > accessible for read and write from the VM.
>> >

Re: [ovirt-users] Unable to delete VM disk

2017-01-12 Thread cmc
Hi Fred/Alexander,

Just wondering if you've had a chance to look at this.

Thanks,

Cam

On Fri, Dec 30, 2016 at 11:45 AM, cmc <iuco...@gmail.com> wrote:
> Hi Alexander,
>
> Thanks. I've attached the log. Relevant error is the last entry.
>
> Kind regards,
>
> Cam
>
> On Wed, Dec 14, 2016 at 3:12 PM, Alexander Wels <aw...@redhat.com> wrote:
>> On Wednesday, December 14, 2016 11:51:49 AM EST cmc wrote:
>>> Having some difficulty in getting the permutation string currently, as
>>> I can't get a cache.html file to appear in the Network section of the
>>> debugger, and both browsers I'm using (Chrome and FIrefox) do not
>>> print the permutation ID at the bottom of the console output. I'll see
>>> if I can get some more detail on how this works from some searching
>>>
>>
>> I improved that, I just haven't updated the wiki, as soon as you install the
>> symbol maps, and you can recreate the issue, then the UI.log should have the
>> unobfuscated stack trace, so you don't have to do all that stuff manually
>> anymore.
>>
>>> On Wed, Dec 14, 2016 at 8:21 AM, Fred Rolland <froll...@redhat.com> wrote:
>>> > The UI log is obfuscated.
>>> > Can you please follow instruction on [1] and reproduce so that we get a
>>> > human readable log.
>>> >
>>> > Thanks
>>> >
>>> > [1]
>>> > http://www.ovirt.org/develop/developer-guide/engine/engine-debug-obfuscate
>>> > d-ui/>
>>> > On Tue, Dec 13, 2016 at 7:42 PM, cmc <iuco...@gmail.com> wrote:
>>> >> Sorry, forgot the version: 4.0.5.5-1.el7.centos
>>> >>
>>> >> On Tue, Dec 13, 2016 at 5:37 PM, cmc <iuco...@gmail.com> wrote:
>>> >> > On the VM in the list of VMs, by right-clicking on it. It then gives
>>> >> > you a pop up window to edit the VM, starting in the 'General' section
>>> >> > (much as when you create a new one)
>>> >> >
>>> >> > Thanks,
>>> >> >
>>> >> > Cam
>>> >> >
>>> >> > On Tue, Dec 13, 2016 at 5:04 PM, Fred Rolland <froll...@redhat.com>
>>> >> >
>>> >> > wrote:
>>> >> >> Hi,
>>> >> >>
>>> >> >> Which version are you using ?
>>> >> >> When you mention "Edit", on which entity is it performed.?
>>> >> >>
>>> >> >> The disks are currently not part of the edit VM window.
>>> >> >>
>>> >> >> Thanks,
>>> >> >> Freddy
>>> >> >>
>>> >> >> On Tue, Dec 13, 2016 at 6:06 PM, cmc <iuco...@gmail.com> wrote:
>>> >> >>> This VM wasn't running.
>>> >> >>>
>>> >> >>> On Tue, Dec 13, 2016 at 4:02 PM, Elad Ben Aharon
>>> >> >>> <ebena...@redhat.com>
>>> >> >>>
>>> >> >>> wrote:
>>> >> >>> > In general, in order to delete a disk while it is attached to a
>>> >> >>> > running
>>> >> >>> > VM,
>>> >> >>> > the disk has to be deactivated (hotunplugged) first so it won't be
>>> >> >>> > accessible for read and write from the VM.
>>> >> >>> > In the 'edit' VM prompt there is no option to deactivate the disk,
>>> >> >>> > it
>>> >> >>> > should
>>> >> >>> > be done from the disks subtab under the virtual machine.
>>> >> >>> >
>>> >> >>> > On Tue, Dec 13, 2016 at 5:33 PM, cmc <iuco...@gmail.com> wrote:
>>> >> >>> >> Actually, I just tried to create a new disk via the 'Edit' menu
>>> >> >>> >> once
>>> >> >>> >> I'd deleted it from the 'Disks' tab, and it threw an exception.
>>> >> >>> >>
>>> >> >>> >> Attached is the console log.
>>> >> >>> >>
>>> >> >>> >> On Tue, Dec 13, 2016 at 3:24 PM, cmc <iuco...@gmail.com> wrote:
>>> >> >>> >> > Hi Elad,
>>> >> >>> >> >
>>> >> >>> >> > I was trying to delete the disk via the 'edit' menu, but noticed
>>> >> >

Re: [ovirt-users] Unable to delete VM disk

2016-12-30 Thread cmc
Hi Alexander,

Thanks. I've attached the log. Relevant error is the last entry.

Kind regards,

Cam

On Wed, Dec 14, 2016 at 3:12 PM, Alexander Wels <aw...@redhat.com> wrote:
> On Wednesday, December 14, 2016 11:51:49 AM EST cmc wrote:
>> Having some difficulty in getting the permutation string currently, as
>> I can't get a cache.html file to appear in the Network section of the
>> debugger, and both browsers I'm using (Chrome and FIrefox) do not
>> print the permutation ID at the bottom of the console output. I'll see
>> if I can get some more detail on how this works from some searching
>>
>
> I improved that, I just haven't updated the wiki, as soon as you install the
> symbol maps, and you can recreate the issue, then the UI.log should have the
> unobfuscated stack trace, so you don't have to do all that stuff manually
> anymore.
>
>> On Wed, Dec 14, 2016 at 8:21 AM, Fred Rolland <froll...@redhat.com> wrote:
>> > The UI log is obfuscated.
>> > Can you please follow instruction on [1] and reproduce so that we get a
>> > human readable log.
>> >
>> > Thanks
>> >
>> > [1]
>> > http://www.ovirt.org/develop/developer-guide/engine/engine-debug-obfuscate
>> > d-ui/>
>> > On Tue, Dec 13, 2016 at 7:42 PM, cmc <iuco...@gmail.com> wrote:
>> >> Sorry, forgot the version: 4.0.5.5-1.el7.centos
>> >>
>> >> On Tue, Dec 13, 2016 at 5:37 PM, cmc <iuco...@gmail.com> wrote:
>> >> > On the VM in the list of VMs, by right-clicking on it. It then gives
>> >> > you a pop up window to edit the VM, starting in the 'General' section
>> >> > (much as when you create a new one)
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Cam
>> >> >
>> >> > On Tue, Dec 13, 2016 at 5:04 PM, Fred Rolland <froll...@redhat.com>
>> >> >
>> >> > wrote:
>> >> >> Hi,
>> >> >>
>> >> >> Which version are you using ?
>> >> >> When you mention "Edit", on which entity is it performed.?
>> >> >>
>> >> >> The disks are currently not part of the edit VM window.
>> >> >>
>> >> >> Thanks,
>> >> >> Freddy
>> >> >>
>> >> >> On Tue, Dec 13, 2016 at 6:06 PM, cmc <iuco...@gmail.com> wrote:
>> >> >>> This VM wasn't running.
>> >> >>>
>> >> >>> On Tue, Dec 13, 2016 at 4:02 PM, Elad Ben Aharon
>> >> >>> <ebena...@redhat.com>
>> >> >>>
>> >> >>> wrote:
>> >> >>> > In general, in order to delete a disk while it is attached to a
>> >> >>> > running
>> >> >>> > VM,
>> >> >>> > the disk has to be deactivated (hotunplugged) first so it won't be
>> >> >>> > accessible for read and write from the VM.
>> >> >>> > In the 'edit' VM prompt there is no option to deactivate the disk,
>> >> >>> > it
>> >> >>> > should
>> >> >>> > be done from the disks subtab under the virtual machine.
>> >> >>> >
>> >> >>> > On Tue, Dec 13, 2016 at 5:33 PM, cmc <iuco...@gmail.com> wrote:
>> >> >>> >> Actually, I just tried to create a new disk via the 'Edit' menu
>> >> >>> >> once
>> >> >>> >> I'd deleted it from the 'Disks' tab, and it threw an exception.
>> >> >>> >>
>> >> >>> >> Attached is the console log.
>> >> >>> >>
>> >> >>> >> On Tue, Dec 13, 2016 at 3:24 PM, cmc <iuco...@gmail.com> wrote:
>> >> >>> >> > Hi Elad,
>> >> >>> >> >
>> >> >>> >> > I was trying to delete the disk via the 'edit' menu, but noticed
>> >> >>> >> > just
>> >> >>> >> > now that there was a 'disks' tab when the machine was
>> >> >>> >> > highlighted.
>> >> >>> >> > This has a 'activate/deactivate' function, and once deactivated,
>> >> >>> >> > was
>> >> >>> >> > able to remove it without error.
>> >> >>> >> >
>> >> >>> >&g

Re: [ovirt-users] Unable to delete VM disk

2016-12-13 Thread cmc
Sorry, forgot the version: 4.0.5.5-1.el7.centos

On Tue, Dec 13, 2016 at 5:37 PM, cmc <iuco...@gmail.com> wrote:
> On the VM in the list of VMs, by right-clicking on it. It then gives
> you a pop up window to edit the VM, starting in the 'General' section
> (much as when you create a new one)
>
> Thanks,
>
> Cam
>
> On Tue, Dec 13, 2016 at 5:04 PM, Fred Rolland <froll...@redhat.com> wrote:
>> Hi,
>>
>> Which version are you using ?
>> When you mention "Edit", on which entity is it performed.?
>>
>> The disks are currently not part of the edit VM window.
>>
>> Thanks,
>> Freddy
>>
>>
>> On Tue, Dec 13, 2016 at 6:06 PM, cmc <iuco...@gmail.com> wrote:
>>>
>>> This VM wasn't running.
>>>
>>> On Tue, Dec 13, 2016 at 4:02 PM, Elad Ben Aharon <ebena...@redhat.com>
>>> wrote:
>>> > In general, in order to delete a disk while it is attached to a running
>>> > VM,
>>> > the disk has to be deactivated (hotunplugged) first so it won't be
>>> > accessible for read and write from the VM.
>>> > In the 'edit' VM prompt there is no option to deactivate the disk, it
>>> > should
>>> > be done from the disks subtab under the virtual machine.
>>> >
>>> > On Tue, Dec 13, 2016 at 5:33 PM, cmc <iuco...@gmail.com> wrote:
>>> >>
>>> >> Actually, I just tried to create a new disk via the 'Edit' menu once
>>> >> I'd deleted it from the 'Disks' tab, and it threw an exception.
>>> >>
>>> >> Attached is the console log.
>>> >>
>>> >> On Tue, Dec 13, 2016 at 3:24 PM, cmc <iuco...@gmail.com> wrote:
>>> >> > Hi Elad,
>>> >> >
>>> >> > I was trying to delete the disk via the 'edit' menu, but noticed just
>>> >> > now that there was a 'disks' tab when the machine was highlighted.
>>> >> > This has a 'activate/deactivate' function, and once deactivated, was
>>> >> > able to remove it without error.
>>> >> >
>>> >> > It does offer the option of deleting the disk when right clicking on
>>> >> > the VM and choosing 'edit', however, there is no 'deactivate' option.
>>> >> > Not sure if this is by design (so that users should look elsewhere).
>>> >> > I
>>> >> > can still try to run the delete from the 'Edit' page, and capture
>>> >> > browser console output. Otherwise, apologies for troubling you with
>>> >> > this.
>>> >> >
>>> >> > Kind regards,
>>> >> >
>>> >> > Cam
>>> >> >
>>> >> > On Tue, Dec 13, 2016 at 12:27 PM, Elad Ben Aharon
>>> >> > <ebena...@redhat.com>
>>> >> > wrote:
>>> >> >> There is no indication for image deletion in engine.log
>>> >> >> The browser console log is located in your browser under
>>> >> >> 'settings'->'developer'.
>>> >> >> Please try to delete a disk as you tried before, get the console log
>>> >> >> and
>>> >> >> provide it.
>>> >> >>
>>> >> >> Thanks
>>> >> >>
>>> >> >> On Mon, Dec 12, 2016 at 7:40 PM, cmc <iuco...@gmail.com> wrote:
>>> >> >>>
>>> >> >>> Hi Eled,
>>> >> >>>
>>> >> >>> I've attached the ui log and the engine log but I'm not sure what
>>> >> >>> the
>>> >> >>> browser console log is - there is a 'console.log' in
>>> >> >>> /var/log/ovirt-engine,
>>> >> >>> but it is zero size (do I have to turn up debugging perhaps?).
>>> >> >>>
>>> >> >>> Kind regards,
>>> >> >>>
>>> >> >>> Cam
>>> >> >>>
>>> >> >>> On Sun, Dec 11, 2016 at 2:26 PM, Elad Ben Aharon
>>> >> >>> <ebena...@redhat.com>
>>> >> >>> wrote:
>>> >> >>> > Hi,
>>> >> >>> >
>>> >> >>> > Please attach browser console log and engine.log
>>> >> >>> >
>>> >> >>> > Thanks
>>> >> >>> >
>>&

Re: [ovirt-users] Unable to delete VM disk

2016-12-13 Thread cmc
On the VM in the list of VMs, by right-clicking on it. It then gives
you a pop up window to edit the VM, starting in the 'General' section
(much as when you create a new one)

Thanks,

Cam

On Tue, Dec 13, 2016 at 5:04 PM, Fred Rolland <froll...@redhat.com> wrote:
> Hi,
>
> Which version are you using ?
> When you mention "Edit", on which entity is it performed.?
>
> The disks are currently not part of the edit VM window.
>
> Thanks,
> Freddy
>
>
> On Tue, Dec 13, 2016 at 6:06 PM, cmc <iuco...@gmail.com> wrote:
>>
>> This VM wasn't running.
>>
>> On Tue, Dec 13, 2016 at 4:02 PM, Elad Ben Aharon <ebena...@redhat.com>
>> wrote:
>> > In general, in order to delete a disk while it is attached to a running
>> > VM,
>> > the disk has to be deactivated (hotunplugged) first so it won't be
>> > accessible for read and write from the VM.
>> > In the 'edit' VM prompt there is no option to deactivate the disk, it
>> > should
>> > be done from the disks subtab under the virtual machine.
>> >
>> > On Tue, Dec 13, 2016 at 5:33 PM, cmc <iuco...@gmail.com> wrote:
>> >>
>> >> Actually, I just tried to create a new disk via the 'Edit' menu once
>> >> I'd deleted it from the 'Disks' tab, and it threw an exception.
>> >>
>> >> Attached is the console log.
>> >>
>> >> On Tue, Dec 13, 2016 at 3:24 PM, cmc <iuco...@gmail.com> wrote:
>> >> > Hi Elad,
>> >> >
>> >> > I was trying to delete the disk via the 'edit' menu, but noticed just
>> >> > now that there was a 'disks' tab when the machine was highlighted.
>> >> > This has a 'activate/deactivate' function, and once deactivated, was
>> >> > able to remove it without error.
>> >> >
>> >> > It does offer the option of deleting the disk when right clicking on
>> >> > the VM and choosing 'edit', however, there is no 'deactivate' option.
>> >> > Not sure if this is by design (so that users should look elsewhere).
>> >> > I
>> >> > can still try to run the delete from the 'Edit' page, and capture
>> >> > browser console output. Otherwise, apologies for troubling you with
>> >> > this.
>> >> >
>> >> > Kind regards,
>> >> >
>> >> > Cam
>> >> >
>> >> > On Tue, Dec 13, 2016 at 12:27 PM, Elad Ben Aharon
>> >> > <ebena...@redhat.com>
>> >> > wrote:
>> >> >> There is no indication for image deletion in engine.log
>> >> >> The browser console log is located in your browser under
>> >> >> 'settings'->'developer'.
>> >> >> Please try to delete a disk as you tried before, get the console log
>> >> >> and
>> >> >> provide it.
>> >> >>
>> >> >> Thanks
>> >> >>
>> >> >> On Mon, Dec 12, 2016 at 7:40 PM, cmc <iuco...@gmail.com> wrote:
>> >> >>>
>> >> >>> Hi Eled,
>> >> >>>
>> >> >>> I've attached the ui log and the engine log but I'm not sure what
>> >> >>> the
>> >> >>> browser console log is - there is a 'console.log' in
>> >> >>> /var/log/ovirt-engine,
>> >> >>> but it is zero size (do I have to turn up debugging perhaps?).
>> >> >>>
>> >> >>> Kind regards,
>> >> >>>
>> >> >>> Cam
>> >> >>>
>> >> >>> On Sun, Dec 11, 2016 at 2:26 PM, Elad Ben Aharon
>> >> >>> <ebena...@redhat.com>
>> >> >>> wrote:
>> >> >>> > Hi,
>> >> >>> >
>> >> >>> > Please attach browser console log and engine.log
>> >> >>> >
>> >> >>> > Thanks
>> >> >>> >
>> >> >>> > On Fri, Dec 9, 2016 at 8:04 PM, cmc <iuco...@gmail.com> wrote:
>> >> >>> >>
>> >> >>> >> Just another note on this: I now get a UI exception every time I
>> >> >>> >> try
>> >> >>> >> to provision a disk, although it does succeed so. I'm guessing
>> >> >>> >> something else is going on, but there is no error in the engine
>> >> >>> >> log.
>> >> >>> >>
>> >> >>> >> On Fri, Dec 9, 2016 at 2:54 PM, cmc <iuco...@gmail.com> wrote:
>> >> >>> >> > Hi,
>> >> >>> >> >
>> >> >>> >> > I'm trying to delete a disk from a host I have shut down, as I
>> >> >>> >> > need
>> >> >>> >> > to
>> >> >>> >> > provision a larger one. When I try to delete it, it gives me
>> >> >>> >> > an
>> >> >>> >> > exception on the UI. I've tried removing the bootable flag,
>> >> >>> >> > and
>> >> >>> >> > creating another disk, but it still won't allow the deletion
>> >> >>> >> > of
>> >> >>> >> > the
>> >> >>> >> > disk. I can't see a relevant error in the engine log, though
>> >> >>> >> > there
>> >> >>> >> > are
>> >> >>> >> > errors in the UI log, but I expect that is just as result of
>> >> >>> >> > the
>> >> >>> >> > underlying issue with deleting the disk.
>> >> >>> >> >
>> >> >>> >> > Thanks,
>> >> >>> >> >
>> >> >>> >> > Cam
>> >> >>> >> ___
>> >> >>> >> Users mailing list
>> >> >>> >> Users@ovirt.org
>> >> >>> >> http://lists.phx.ovirt.org/mailman/listinfo/users
>> >> >>> >
>> >> >>> >
>> >> >>
>> >> >>
>> >
>> >
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.phx.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to delete VM disk

2016-12-13 Thread cmc
Actually, I just tried to create a new disk via the 'Edit' menu once
I'd deleted it from the 'Disks' tab, and it threw an exception.

Attached is the console log.

On Tue, Dec 13, 2016 at 3:24 PM, cmc <iuco...@gmail.com> wrote:
> Hi Elad,
>
> I was trying to delete the disk via the 'edit' menu, but noticed just
> now that there was a 'disks' tab when the machine was highlighted.
> This has a 'activate/deactivate' function, and once deactivated, was
> able to remove it without error.
>
> It does offer the option of deleting the disk when right clicking on
> the VM and choosing 'edit', however, there is no 'deactivate' option.
> Not sure if this is by design (so that users should look elsewhere). I
> can still try to run the delete from the 'Edit' page, and capture
> browser console output. Otherwise, apologies for troubling you with
> this.
>
> Kind regards,
>
> Cam
>
> On Tue, Dec 13, 2016 at 12:27 PM, Elad Ben Aharon <ebena...@redhat.com> wrote:
>> There is no indication for image deletion in engine.log
>> The browser console log is located in your browser under
>> 'settings'->'developer'.
>> Please try to delete a disk as you tried before, get the console log and
>> provide it.
>>
>> Thanks
>>
>> On Mon, Dec 12, 2016 at 7:40 PM, cmc <iuco...@gmail.com> wrote:
>>>
>>> Hi Eled,
>>>
>>> I've attached the ui log and the engine log but I'm not sure what the
>>> browser console log is - there is a 'console.log' in
>>> /var/log/ovirt-engine,
>>> but it is zero size (do I have to turn up debugging perhaps?).
>>>
>>> Kind regards,
>>>
>>> Cam
>>>
>>> On Sun, Dec 11, 2016 at 2:26 PM, Elad Ben Aharon <ebena...@redhat.com>
>>> wrote:
>>> > Hi,
>>> >
>>> > Please attach browser console log and engine.log
>>> >
>>> > Thanks
>>> >
>>> > On Fri, Dec 9, 2016 at 8:04 PM, cmc <iuco...@gmail.com> wrote:
>>> >>
>>> >> Just another note on this: I now get a UI exception every time I try
>>> >> to provision a disk, although it does succeed so. I'm guessing
>>> >> something else is going on, but there is no error in the engine log.
>>> >>
>>> >> On Fri, Dec 9, 2016 at 2:54 PM, cmc <iuco...@gmail.com> wrote:
>>> >> > Hi,
>>> >> >
>>> >> > I'm trying to delete a disk from a host I have shut down, as I need
>>> >> > to
>>> >> > provision a larger one. When I try to delete it, it gives me an
>>> >> > exception on the UI. I've tried removing the bootable flag, and
>>> >> > creating another disk, but it still won't allow the deletion of the
>>> >> > disk. I can't see a relevant error in the engine log, though there
>>> >> > are
>>> >> > errors in the UI log, but I expect that is just as result of the
>>> >> > underlying issue with deleting the disk.
>>> >> >
>>> >> > Thanks,
>>> >> >
>>> >> > Cam
>>> >> ___
>>> >> Users mailing list
>>> >> Users@ovirt.org
>>> >> http://lists.phx.ovirt.org/mailman/listinfo/users
>>> >
>>> >
>>
>>
Tue Dec 13 15:28:45 GMT+000 2016 org.ovirt.engine.ui.uicompat.EnumTranslator
WARNING: trying to localize null, probable error. Exception is not thrown, returning 'N/A'
webadmin-0.js:15497 Tue Dec 13 15:28:45 GMT+000 2016 org.ovirt.engine.ui.uicompat.EnumTranslator
WARNING: trying to localize null, probable error. Exception is not thrown, returning 'N/A'
webadmin-0.js:15497 Tue Dec 13 15:28:45 GMT+000 2016 org.ovirt.engine.ui.uicompat.EnumTranslator
WARNING: trying to localize null, probable error. Exception is not thrown, returning 'N/A'
webadmin-0.js:15497 Tue Dec 13 15:28:45 GMT+000 2016 org.ovirt.engine.ui.uicompat.EnumTranslator
WARNING: trying to localize null, probable error. Exception is not thrown, returning 'N/A'
webadmin-0.js:15497 Tue Dec 13 15:28:45 GMT+000 2016 org.ovirt.engine.ui.uicompat.EnumTranslator
WARNING: trying to localize null, probable error. Exception is not thrown, returning 'N/A'
webadmin-0.js:15497 Tue Dec 13 15:28:45 GMT+000 2016 org.ovirt.engine.ui.uicompat.EnumTranslator
WARNING: trying to localize null, probable error. Exception is not thrown, returning 'N/A'
webadmin-0.js:15497 Tue Dec 13 15:28:59 GMT+000 2016 org.ovirt.engine.ui.common.widget.table.ColumnResizeCellTable
WARNING: 

Re: [ovirt-users] Unable to delete VM disk

2016-12-13 Thread cmc
Hi Elad,

I was trying to delete the disk via the 'edit' menu, but noticed just
now that there was a 'disks' tab when the machine was highlighted.
This has a 'activate/deactivate' function, and once deactivated, was
able to remove it without error.

It does offer the option of deleting the disk when right clicking on
the VM and choosing 'edit', however, there is no 'deactivate' option.
Not sure if this is by design (so that users should look elsewhere). I
can still try to run the delete from the 'Edit' page, and capture
browser console output. Otherwise, apologies for troubling you with
this.

Kind regards,

Cam

On Tue, Dec 13, 2016 at 12:27 PM, Elad Ben Aharon <ebena...@redhat.com> wrote:
> There is no indication for image deletion in engine.log
> The browser console log is located in your browser under
> 'settings'->'developer'.
> Please try to delete a disk as you tried before, get the console log and
> provide it.
>
> Thanks
>
> On Mon, Dec 12, 2016 at 7:40 PM, cmc <iuco...@gmail.com> wrote:
>>
>> Hi Eled,
>>
>> I've attached the ui log and the engine log but I'm not sure what the
>> browser console log is - there is a 'console.log' in
>> /var/log/ovirt-engine,
>> but it is zero size (do I have to turn up debugging perhaps?).
>>
>> Kind regards,
>>
>> Cam
>>
>> On Sun, Dec 11, 2016 at 2:26 PM, Elad Ben Aharon <ebena...@redhat.com>
>> wrote:
>> > Hi,
>> >
>> > Please attach browser console log and engine.log
>> >
>> > Thanks
>> >
>> > On Fri, Dec 9, 2016 at 8:04 PM, cmc <iuco...@gmail.com> wrote:
>> >>
>> >> Just another note on this: I now get a UI exception every time I try
>> >> to provision a disk, although it does succeed so. I'm guessing
>> >> something else is going on, but there is no error in the engine log.
>> >>
>> >> On Fri, Dec 9, 2016 at 2:54 PM, cmc <iuco...@gmail.com> wrote:
>> >> > Hi,
>> >> >
>> >> > I'm trying to delete a disk from a host I have shut down, as I need
>> >> > to
>> >> > provision a larger one. When I try to delete it, it gives me an
>> >> > exception on the UI. I've tried removing the bootable flag, and
>> >> > creating another disk, but it still won't allow the deletion of the
>> >> > disk. I can't see a relevant error in the engine log, though there
>> >> > are
>> >> > errors in the UI log, but I expect that is just as result of the
>> >> > underlying issue with deleting the disk.
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Cam
>> >> ___
>> >> Users mailing list
>> >> Users@ovirt.org
>> >> http://lists.phx.ovirt.org/mailman/listinfo/users
>> >
>> >
>
>
___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to delete VM disk

2016-12-09 Thread cmc
Just another note on this: I now get a UI exception every time I try
to provision a disk, although it does succeed so. I'm guessing
something else is going on, but there is no error in the engine log.

On Fri, Dec 9, 2016 at 2:54 PM, cmc <iuco...@gmail.com> wrote:
> Hi,
>
> I'm trying to delete a disk from a host I have shut down, as I need to
> provision a larger one. When I try to delete it, it gives me an
> exception on the UI. I've tried removing the bootable flag, and
> creating another disk, but it still won't allow the deletion of the
> disk. I can't see a relevant error in the engine log, though there are
> errors in the UI log, but I expect that is just as result of the
> underlying issue with deleting the disk.
>
> Thanks,
>
> Cam
___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users


[ovirt-users] Unable to delete VM disk

2016-12-09 Thread cmc
Hi,

I'm trying to delete a disk from a host I have shut down, as I need to
provision a larger one. When I try to delete it, it gives me an
exception on the UI. I've tried removing the bootable flag, and
creating another disk, but it still won't allow the deletion of the
disk. I can't see a relevant error in the engine log, though there are
errors in the UI log, but I expect that is just as result of the
underlying issue with deleting the disk.

Thanks,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] expired cert for aaa

2016-11-24 Thread cmc
I ran engine-setup again, but the issue was still present. However, I found
that by using a different browser (Firefox instead of Chrome), I did not
get the error. I cleared the cookies in Chrome and the issue no longer
occured. So it may well be a browser issue.

Thanks,

C

On Thu, Nov 24, 2016 at 11:22 AM, cmc <iuco...@gmail.com> wrote:

> Interestingly, I just got this same error again after I upgraded (I
> upgraded from 4.0.4 to 4.0.5 to fix the 'internal server error' bug that
> was fixed in 4.0.5)
>
> server_error: The connection reader was unable to successfully complete
> TLS negotiation: javax.net.ssl.SSLHandshakeException: 
> java.security.cert.CertificateExpiredException:
> NotAfter: Fri Nov 04 00:19:18 GMT 2016 caused by 
> java.security.cert.CertificateExpiredException:
> NotAfter: Fri Nov 04 00:19:18 GMT 2016
>
> Shall I send the logs?
>
> On Thu, Nov 24, 2016 at 10:55 AM, Yedidyah Bar David <d...@redhat.com>
> wrote:
>
>> On Thu, Nov 24, 2016 at 12:47 PM, cmc <iuco...@gmail.com> wrote:
>> > Hi Yedidyah,
>> >
>> > Attached are the setup logs, sorry for the delay. I checked all the
>> backup
>> > certs, and the expiry dates were either in 2021 or 2026.
>>
>> Sorry, no idea.
>>
>> This means that all certs generated by engine-setup were ok.
>>
>> Not sure what caused this message. If it happens again, please
>> check the certificate's details, who issued/signed it etc.
>>
>> Best,
>>
>> >
>> > Regards,
>> >
>> > Cam
>> >
>> > On Tue, Nov 8, 2016 at 7:25 AM, Yedidyah Bar David <d...@redhat.com>
>> wrote:
>> >>
>> >> On Mon, Nov 7, 2016 at 9:15 PM, cmc <iuco...@gmail.com> wrote:
>> >> > To reply to my own email:
>> >> >
>> >> > This is now fixed.
>> >> >
>> >> > I originally ran these steps for the upgrade:
>> >> >
>> >> > # yum install
>> >> > http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm
>> >> > # yum update "ovirt-engine-setup*"
>> >> > # engine-setup
>> >> >
>> >> > There were no errors reported during the process. I could login as
>> the
>> >> > internal user without any errors. It was just using an external
>> >> > provider,
>> >> > which made me think it was an aaa issue, so I looked
>> >> > at the certificate exported from AD which had an expiry of 2063.
>> >> >
>> >> > I tried running engine-setup again, and this fixed the issue. I have
>> no
>> >> > idea
>> >> > what happened along the way, I will check the logs. I notice it
>> reports:
>> >> >
>> >> > [ INFO  ] Upgrading CA
>> >>
>> >> engine-setup always emits this message. You might find more details in
>> the
>> >> setup logs regarding what it actually did.
>> >>
>> >> >
>> >> > so it looks like it creates a cert. Why it would have created one
>> with
>> >> > such
>> >> > a short expiry date is a mystery to me.
>> >> >
>> >> > Hope this helps anyone who might come across this issue
>> >>
>> >> Thanks for the report!
>> >>
>> >> Can you please share both setup logs? Thanks.
>> >>
>> >> Also, most files should be backed up by engine-setup prior to being
>> >> changed/removed. So you can check the backups. E.g.:
>> >>
>> >> # openssl x509 -in /etc/pki/ovirt-engine/ca.pem.20160120160548 -noout
>> >> -enddate
>> >> notAfter=May 22 07:32:23 2025 GMT
>> >> # openssl x509 -in /etc/pki/ovirt-engine/ca.pem -noout -enddate
>> >> notAfter=Mar  6 09:46:44 2026 GMT
>> >>
>> >> Or,
>> >>
>> >> find /etc/pki/ovirt-engine -name "*.cer*" -o -name "*.pem*" | while
>> >> read file; do echo $file $(openssl x509 -in $file -noout -enddate);
>> >> done
>> >>
>> >> Best,
>> >> --
>> >> Didi
>> >
>> >
>>
>>
>>
>> --
>> Didi
>>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] expired cert for aaa

2016-11-24 Thread cmc
Interestingly, I just got this same error again after I upgraded (I
upgraded from 4.0.4 to 4.0.5 to fix the 'internal server error' bug that
was fixed in 4.0.5)

server_error: The connection reader was unable to successfully complete TLS
negotiation: javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateExpiredException: NotAfter: Fri Nov 04
00:19:18 GMT 2016 caused by java.security.cert.CertificateExpiredException:
NotAfter: Fri Nov 04 00:19:18 GMT 2016

Shall I send the logs?

On Thu, Nov 24, 2016 at 10:55 AM, Yedidyah Bar David <d...@redhat.com>
wrote:

> On Thu, Nov 24, 2016 at 12:47 PM, cmc <iuco...@gmail.com> wrote:
> > Hi Yedidyah,
> >
> > Attached are the setup logs, sorry for the delay. I checked all the
> backup
> > certs, and the expiry dates were either in 2021 or 2026.
>
> Sorry, no idea.
>
> This means that all certs generated by engine-setup were ok.
>
> Not sure what caused this message. If it happens again, please
> check the certificate's details, who issued/signed it etc.
>
> Best,
>
> >
> > Regards,
> >
> > Cam
> >
> > On Tue, Nov 8, 2016 at 7:25 AM, Yedidyah Bar David <d...@redhat.com>
> wrote:
> >>
> >> On Mon, Nov 7, 2016 at 9:15 PM, cmc <iuco...@gmail.com> wrote:
> >> > To reply to my own email:
> >> >
> >> > This is now fixed.
> >> >
> >> > I originally ran these steps for the upgrade:
> >> >
> >> > # yum install
> >> > http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm
> >> > # yum update "ovirt-engine-setup*"
> >> > # engine-setup
> >> >
> >> > There were no errors reported during the process. I could login as the
> >> > internal user without any errors. It was just using an external
> >> > provider,
> >> > which made me think it was an aaa issue, so I looked
> >> > at the certificate exported from AD which had an expiry of 2063.
> >> >
> >> > I tried running engine-setup again, and this fixed the issue. I have
> no
> >> > idea
> >> > what happened along the way, I will check the logs. I notice it
> reports:
> >> >
> >> > [ INFO  ] Upgrading CA
> >>
> >> engine-setup always emits this message. You might find more details in
> the
> >> setup logs regarding what it actually did.
> >>
> >> >
> >> > so it looks like it creates a cert. Why it would have created one with
> >> > such
> >> > a short expiry date is a mystery to me.
> >> >
> >> > Hope this helps anyone who might come across this issue
> >>
> >> Thanks for the report!
> >>
> >> Can you please share both setup logs? Thanks.
> >>
> >> Also, most files should be backed up by engine-setup prior to being
> >> changed/removed. So you can check the backups. E.g.:
> >>
> >> # openssl x509 -in /etc/pki/ovirt-engine/ca.pem.20160120160548 -noout
> >> -enddate
> >> notAfter=May 22 07:32:23 2025 GMT
> >> # openssl x509 -in /etc/pki/ovirt-engine/ca.pem -noout -enddate
> >> notAfter=Mar  6 09:46:44 2026 GMT
> >>
> >> Or,
> >>
> >> find /etc/pki/ovirt-engine -name "*.cer*" -o -name "*.pem*" | while
> >> read file; do echo $file $(openssl x509 -in $file -noout -enddate);
> >> done
> >>
> >> Best,
> >> --
> >> Didi
> >
> >
>
>
>
> --
> Didi
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] CpuProfileCreator

2016-11-07 Thread cmc
Hi Martin,

This appears to have resolved the issue, though I had a panic when the
upgrade broke the certificate. I re-ran engine setup and it fixed the cert
issue.

Cheers,

cam


On Mon, Nov 7, 2016 at 1:27 PM, cmc <iuco...@gmail.com> wrote:

> Hi Martin,
>
> The version is: oVirt Engine Version: 4.0.2.7-1.el7.centos
>
> I had a look through the changelog up until 4.0.4 as I was contemplating
> upgrading but may have missed it.
>
> Thanks,
>
> Cam
>
> On Fri, Nov 4, 2016 at 12:42 PM, Martin Sivak <msi...@redhat.com> wrote:
>
>> Hi,
>>
>> what version of the product are you running? We recently fixed a related
>> issue:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1369046
>>
>> Did you upgrade form 3.6 to 4.0 recently?
>>
>> Regards
>>
>> Martin Sivak
>>
>> On Thu, Nov 3, 2016 at 1:48 PM, cmc <iuco...@gmail.com> wrote:
>> > Hi,
>> >
>> > I'm having problems creating VMs with the following error message:
>> >
>> >  "User doesn't have permissions to assign the cpu profile"
>> >
>> > From the log:
>> >
>> > 2016-11-03 12:26:36,918 WARN  [org.ovirt.engine.core.bll.AddVmCommand]
>> > (default task-346) [] Validation of action 'AddVm' failed for user
>> > c...@fscfc.co.uk@fscfc.co.uk-authz. Reasons:
>> > VAR__ACTION__ADD,VAR__TYPE__VM,ACTION_TYPE_NO_PERMISSION_TO_
>> ASSIGN_CPU_PROFILE,$cpuProfileId
>> > 7e921369-83c1-46b2-86bd-1056d996873e,$cpuProfileName Wells-4th
>> >
>> > The user I am logged in as is part of a group which has the following
>> > permissions:
>> >
>> > SuperUser
>> > ClusterAdmin
>> > DatacenterAdmin
>> > CpuProfileCreator
>> >
>> > I added the last one even though I thought ClusterAdmin and
>> DatacenterAdmin
>> > would cover it.
>> >
>> > When I go to Clusters->CpuProfile for this cluster, it does show all of
>> > these permissions.
>> >
>> > What am I doing wrong here?
>> >
>> > Thanks for any help,
>> >
>> > Cam
>> >
>> >
>> >
>> >
>> >
>> > ___
>> > Users mailing list
>> > Users@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/users
>> >
>>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] expired cert for aaa

2016-11-07 Thread cmc
To reply to my own email:

This is now fixed.

I originally ran these steps for the upgrade:

# yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm
# yum update "ovirt-engine-setup*"
# engine-setup

There were no errors reported during the process. I could login as the
internal user without any errors. It was just using an external provider,
which made me think it was an aaa issue, so I looked
at the certificate exported from AD which had an expiry of 2063.

I tried running engine-setup again, and this fixed the issue. I have no
idea what happened along the way, I will check the logs. I notice it
reports:

[ INFO  ] Upgrading CA

so it looks like it creates a cert. Why it would have created one with such
a short expiry date is a mystery to me.

Hope this helps anyone who might come across this issue

Cheers,

Cam

On Mon, Nov 7, 2016 at 7:03 PM, cmc <iuco...@gmail.com> wrote:

> Hi,
>
> I upgraded my engine host from 4.0.2.7 to 4.0.4 and when I attempt to
> login via a aaa provider I get:
>
>  java.security.cert.CertificateExpiredException: NotAfter: Fri Nov 04
> 00:19:18 GMT 2016,
>
> What certificate is this referring to? The certificate from the aaa
> provider expires in 2063.
>
> It was fine until the upgrade.
>
> Thanks for any help,
>
> Cam
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] expired cert for aaa

2016-11-07 Thread cmc
Hi,

I upgraded my engine host from 4.0.2.7 to 4.0.4 and when I attempt to login
via a aaa provider I get:

 java.security.cert.CertificateExpiredException: NotAfter: Fri Nov 04
00:19:18 GMT 2016,

What certificate is this referring to? The certificate from the aaa
provider expires in 2063.

It was fine until the upgrade.

Thanks for any help,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] CpuProfileCreator

2016-11-07 Thread cmc
Hi Martin,

The version is: oVirt Engine Version: 4.0.2.7-1.el7.centos

I had a look through the changelog up until 4.0.4 as I was contemplating
upgrading but may have missed it.

Thanks,

Cam

On Fri, Nov 4, 2016 at 12:42 PM, Martin Sivak <msi...@redhat.com> wrote:

> Hi,
>
> what version of the product are you running? We recently fixed a related
> issue:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1369046
>
> Did you upgrade form 3.6 to 4.0 recently?
>
> Regards
>
> Martin Sivak
>
> On Thu, Nov 3, 2016 at 1:48 PM, cmc <iuco...@gmail.com> wrote:
> > Hi,
> >
> > I'm having problems creating VMs with the following error message:
> >
> >  "User doesn't have permissions to assign the cpu profile"
> >
> > From the log:
> >
> > 2016-11-03 12:26:36,918 WARN  [org.ovirt.engine.core.bll.AddVmCommand]
> > (default task-346) [] Validation of action 'AddVm' failed for user
> > c...@fscfc.co.uk@fscfc.co.uk-authz. Reasons:
> > VAR__ACTION__ADD,VAR__TYPE__VM,ACTION_TYPE_NO_PERMISSION_
> TO_ASSIGN_CPU_PROFILE,$cpuProfileId
> > 7e921369-83c1-46b2-86bd-1056d996873e,$cpuProfileName Wells-4th
> >
> > The user I am logged in as is part of a group which has the following
> > permissions:
> >
> > SuperUser
> > ClusterAdmin
> > DatacenterAdmin
> > CpuProfileCreator
> >
> > I added the last one even though I thought ClusterAdmin and
> DatacenterAdmin
> > would cover it.
> >
> > When I go to Clusters->CpuProfile for this cluster, it does show all of
> > these permissions.
> >
> > What am I doing wrong here?
> >
> > Thanks for any help,
> >
> > Cam
> >
> >
> >
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] CpuProfileCreator

2016-11-03 Thread cmc
Hi,

I'm having problems creating VMs with the following error message:

 "User doesn't have permissions to assign the cpu profile"

>From the log:

2016-11-03 12:26:36,918 WARN  [org.ovirt.engine.core.bll.AddVmCommand]
(default task-346) [] Validation of action 'AddVm' failed for user
c...@fscfc.co.uk@fscfc.co.uk-authz. Reasons:
VAR__ACTION__ADD,VAR__TYPE__VM,ACTION_TYPE_NO_PERMISSION_TO_ASSIGN_CPU_PROFILE,$cpuProfileId
7e921369-83c1-46b2-86bd-1056d996873e,$cpuProfileName Wells-4th

The user I am logged in as is part of a group which has the following
permissions:

SuperUser
ClusterAdmin
DatacenterAdmin
CpuProfileCreator

I added the last one even though I thought ClusterAdmin and DatacenterAdmin
would cover it.

When I go to Clusters->CpuProfile for this cluster, it does show all of
these permissions.

What am I doing wrong here?

Thanks for any help,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt AD integration problems

2016-10-17 Thread cmc
Hi Ondra,

I assigned permissions to an LDAP group and it just needed me to remove
that group and re-add it for it to authorize again.

Yes, the UPN is user@domain in our case. Not a big deal, but is there a
plan to change the display name? I get confused looks
and questions when people log in.

All working now, many thanks once again for all your help!

Cheers,

Cam

On Mon, Oct 17, 2016 at 10:06 AM, Ondra Machacek <omach...@redhat.com>
wrote:

> Hi Cam,
>
> this is OK, because we use user principal name(UPN)[1] for the
> 'username' field of the oVirt. So the result username will consist of
> UPN@authz-extension, so if your user's UPN is 'user@domain' and you
> will name your authz extension as 'domain', then the result username
> will be 'user@domain@domain'.
>
> The problem, that you can't get authorized is that you didn't assigned
> any permissions to your user.
>
> [1] https://msdn.microsoft.com/en-us/library/ms680857(v=vs.85).aspx
>
> On 10/14/2016 04:30 PM, cmc wrote:
>
>> Hi Ondra,
>>
>> It manages to authenticate, but appends the domain again once I'm logged
>> in, for instance, if I log in as user 'cam', it will log me in,
>> and display the login name in the top right corner as
>> 'c...@domain.com@domain.com <http://domain.com>' (this shows up in the
>> log as well: it shows me
>> logging in as c...@domain.com <mailto:c...@domain.com>, but then returns
>> an error as user  c...@domain.com@domain.com <http://domain.com> is not
>> authorized). My thought was
>> that something done earlier when I was playing around with sssd,
>> kerberos and AD is doing this, though I have removed these packages
>> and run authconfig to remove sssd. Any ideas?
>>
>> Cheers,
>>
>> Cam
>>
>> On Thu, Oct 13, 2016 at 2:04 PM, cmc <iuco...@gmail.com
>> <mailto:iuco...@gmail.com>> wrote:
>>
>> Hi Ondra,
>>
>> That is good to know that we don't need Kerberos - it complicates
>> things a lot.
>>
>> I think the errors might be the options I'd selected during the
>> setup. I was thrown a bit that
>> it passed all the internal tests provided by the setup script, but
>> failed on the web GUI. When
>> I've seen 'unspecified GSS failure' and 'peer not authenticated'
>> it's usually been due to
>> Kerberos (though admittedly these are just generic errors). So I
>> tried the Redhat guide for SSO at:
>>
>> https://access.redhat.com/documentation/en-US/Red_Hat_Enterp
>> rise_Virtualization/3.6/html/Administration_Guide/Configuri
>> ng_LDAP_and_Kerberos_for_Single_Sign-on.html
>> <https://access.redhat.com/documentation/en-US/Red_Hat_Enter
>> prise_Virtualization/3.6/html/Administration_Guide/Configuri
>> ng_LDAP_and_Kerberos_for_Single_Sign-on.html>
>>
>> which uses Kerberos (in ovirt-sso.conf) I had to remove the symlink
>> to the Apache
>> config it says to create, as it results in internal server errors in
>> Apache. It uses an SPN for
>> Apache in the keytab.
>>
>> Now that you've confirmed that it can actually work without any need
>> for the Kerberos stuff,
>> I will start afresh from a clean setup and apply what I've learnt
>> during this process.
>>
>> I'll try it out and let you know either way.
>>
>> Many thanks for all the help!
>>
>> Kind regards,
>>
>> Cam
>>
>>
>>
>> Yes, you really do not need anything kerberos related to
>> securely bind
>> to AD via LDAP simple bind over TLS/SSL. This is really strange
>> to me
>> what errors you are getting, but you probably configured apache
>> (or
>> something else?) to require keytab, but you don't have to, and
>> you can
>> remove that configuration.
>>
>>
>> Thanks,
>>
>> Cam
>>
>>
>>
>>
>> Thanks,
>>
>> Cam
>>
>> ___
>>
>> Users mailing list
>> Users@ovirt.org <mailto:Users@ovirt.org>
>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>
>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>
>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>
>>
>> http://lists.ovirt.org/mailman/listinfo/users
>> <http://lists.ovirt.org/mailman/listinfo/users>
>> <http://lists.ovirt.org/mailman/listinfo/users
>> <http://lists.ovirt.org/mailman/listinfo/users>>
>>
>> <http://lists.ovirt.org/mailman/listinfo/users
>> <http://lists.ovirt.org/mailman/listinfo/users>
>> <http://lists.ovirt.org/mailman/listinfo/users
>> <http://lists.ovirt.org/mailman/listinfo/users>>>
>>
>>
>>
>>
>>
>>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt AD integration problems

2016-10-14 Thread cmc
Hi Ondra,

It manages to authenticate, but appends the domain again once I'm logged
in, for instance, if I log in as user 'cam', it will log me in,
and display the login name in the top right corner as 'c...@domain.com@
domain.com' (this shows up in the log as well: it shows me
logging in as c...@domain.com, but then returns an error as user
c...@domain.com@domain.com is not authorized). My thought was
that something done earlier when I was playing around with sssd, kerberos
and AD is doing this, though I have removed these packages
and run authconfig to remove sssd. Any ideas?

Cheers,

Cam

On Thu, Oct 13, 2016 at 2:04 PM, cmc <iuco...@gmail.com> wrote:

> Hi Ondra,
>
> That is good to know that we don't need Kerberos - it complicates things a
> lot.
>
> I think the errors might be the options I'd selected during the setup. I
> was thrown a bit that
> it passed all the internal tests provided by the setup script, but failed
> on the web GUI. When
> I've seen 'unspecified GSS failure' and 'peer not authenticated' it's
> usually been due to
> Kerberos (though admittedly these are just generic errors). So I tried the
> Redhat guide for SSO at:
>
> https://access.redhat.com/documentation/en-US/Red_Hat_
> Enterprise_Virtualization/3.6/html/Administration_Guide/
> Configuring_LDAP_and_Kerberos_for_Single_Sign-on.html
>
> which uses Kerberos (in ovirt-sso.conf) I had to remove the symlink to the
> Apache
> config it says to create, as it results in internal server errors in
> Apache. It uses an SPN for
> Apache in the keytab.
>
> Now that you've confirmed that it can actually work without any need for
> the Kerberos stuff,
> I will start afresh from a clean setup and apply what I've learnt during
> this process.
>
> I'll try it out and let you know either way.
>
> Many thanks for all the help!
>
> Kind regards,
>
> Cam
>
>
>
>> Yes, you really do not need anything kerberos related to securely bind
>> to AD via LDAP simple bind over TLS/SSL. This is really strange to me
>> what errors you are getting, but you probably configured apache (or
>> something else?) to require keytab, but you don't have to, and you can
>> remove that configuration.
>>
>>
>>> Thanks,
>>>
>>> Cam
>>>
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Cam
>>>
>>> ___
>>>
>>> Users mailing list
>>> Users@ovirt.org <mailto:Users@ovirt.org>
>>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>
>>> http://lists.ovirt.org/mailman/listinfo/users
>>> <http://lists.ovirt.org/mailman/listinfo/users>
>>> <http://lists.ovirt.org/mailman/listinfo/users
>>> <http://lists.ovirt.org/mailman/listinfo/users>>
>>>
>>>
>>>
>>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt AD integration problems

2016-10-13 Thread cmc
Hi Ondra,

That is good to know that we don't need Kerberos - it complicates things a
lot.

I think the errors might be the options I'd selected during the setup. I
was thrown a bit that
it passed all the internal tests provided by the setup script, but failed
on the web GUI. When
I've seen 'unspecified GSS failure' and 'peer not authenticated' it's
usually been due to
Kerberos (though admittedly these are just generic errors). So I tried the
Redhat guide for SSO at:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Administration_Guide/Configuring_LDAP_and_Kerberos_for_Single_Sign-on.html

which uses Kerberos (in ovirt-sso.conf) I had to remove the symlink to the
Apache
config it says to create, as it results in internal server errors in
Apache. It uses an SPN for
Apache in the keytab.

Now that you've confirmed that it can actually work without any need for
the Kerberos stuff,
I will start afresh from a clean setup and apply what I've learnt during
this process.

I'll try it out and let you know either way.

Many thanks for all the help!

Kind regards,

Cam



> Yes, you really do not need anything kerberos related to securely bind
> to AD via LDAP simple bind over TLS/SSL. This is really strange to me
> what errors you are getting, but you probably configured apache (or
> something else?) to require keytab, but you don't have to, and you can
> remove that configuration.
>
>
>> Thanks,
>>
>> Cam
>>
>>
>>
>>
>> Thanks,
>>
>> Cam
>>
>> ___
>>
>> Users mailing list
>> Users@ovirt.org 
>> >
>> http://lists.ovirt.org/mailman/listinfo/users
>> 
>> > >
>>
>>
>>
>>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt AD integration problems

2016-10-12 Thread cmc
Hi Ondra,

It's not, but you need to use insecure connection then (you need to have
> following line in /etc/ovirt-engine/aaa/domain.properties):
>
>  pool.default.ssl.insecure = true
>

I ended up generating a cert on one of the AD machines, copying it to the
host, and then specified it in the setup process via
ovirt-engine-extension-aaa-ldap-setup.
It seems to create a .jks file. It still gave me the same 'peer not
authenticated' so I checked the krb5.keytab and saw that there was no SPN
for http, so I rejoined the domain and specified http as a service name via
adcli, and then things worked.


>
> So double check that, and if it still won't work, the logs from
> ovirt-engine-extensions-tool would help, you can generate them as follows:
>
>  $ ovirt-engine-extensions-tool --log-level=FINEST --log-file=/tmp/aaa.log
> aaa 
>
>
>> Do I need to set up Apache separately to use LDAP auth? The service
>> principals exist in the krb5.keytab, but I don't if that is only if you
>> are using SSO.
>>
>
> Yes, that's only if you use SSO. If you use plain LDAP simple bind, you
> don't need anything related to kerberos.
>

I think I was under the impression that you needed to join the domain in
order to auth via AD. However, I've now seen one HOWTO that says that you
just need the cert from AD to be able to auth securely though I'm not
entirely clear whether that works for Apache. Is that correct - Kerberos,
binding etc is not needed for the oVirt web interface to auth securely?

Thanks,

Cam


>
>
>> Thanks,
>>
>> Cam
>>
>> ___
>>
>> Users mailing list
>> Users@ovirt.org 
>> http://lists.ovirt.org/mailman/listinfo/users
>> 
>>
>>
>>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt AD integration problems

2016-10-11 Thread cmc
Hi Ondra,



>
> Not really. aaa-ldap by default uses just simple bind, no gssapi.
> If you have any problems with certificate I would suggest you to check if
> you are using the correct one, correctly. More info for it can be
> found here:
>
>
> https://gerrit.ovirt.org/gitweb?p=ovirt-engine-extension-aaa
> -ldap.git;a=blob;f=README;h=1f4381e4f0d22acdda63c56a84863f
> cb0f72bc3a;hb=HEAD#l397
>
>

I've run the following tests in that README you posted above, and all
worked fine:

ovirt-engine-extensions-tool aaa login-user --profile=mydomain.com
--user-name=myuser
ovirt-engine-extensions-tool aaa search --extension-name=mydomain.com-authz
--entity=principal --entity-name=myuser
LDAPTLS_REQCERT=never ldapsearch -ZZ -H ldap://ad.mydomain.com -x -D
"CN=myuser,CN=Users,DC=mydomain,DC=com" -W -b "dc=mydomain,dc=com"

I thought I wouldn't need to import any certificate from AD - is that a
requirement?

Do I need to set up Apache separately to use LDAP auth? The service
principals exist in the krb5.keytab, but I don't if that is only if you are
using SSO.

Thanks,

Cam

___

> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] oVirt AD integration problems

2016-09-28 Thread cmc
Hi,

I'm trying to use the directory services provided by the
ovirt-engine-extension-aaa-ldap, and I can get it to successfully login
when I run the tests in the setup script, but when I login via the GUI, it
gives me:

unexpected error was encountered during validation processing:
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated'

and fails login. It looks a bit like it is expecting to already be joined
to the domain, so I tried doing that manually via realmd and sssd. It
involved installing a lot of packages, such as kerberos and samba, which I
am nervous about on an engine host. Anyway, once I was joined, it still
gives me the same 'peer not authenticated' message. Does it need to be
separately bound to the domain, i.e., do you need all the other stuff
installed and running for it to work, or is the
ovirt-engine-extension-aaa-ldap package all that is needed?

Anyway, I ran the ovirt-engine-extensions-tool --log-level=FINEST
--log-file=/tmp/aaa.log aaa search --extension-name=domain-authz command
suggested in an earlier post, and it only gave me one exception, which was:

2016-09-28 16:08:15 SEVERE  Extension domain-authz could not be found
2016-09-28 16:08:15 FINEException:
org.ovirt.engine.core.extensions.mgr.ConfigurationException: Extension
domain-authz could not be found

Thanks for any help,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] kerberos and AAA

2016-09-26 Thread cmc
Thanks Rafael. I forgot to mention that this is an AD host, which just uses
kerberos keytabs to establish trust, so it looks like the best option is to
install krb5 tools and sssd.

Cheers,

Cam

On Mon, Sep 26, 2016 at 5:09 PM, Rafael Martins <rmart...@redhat.com> wrote:

> - Original Message -
> > From: "cmc" <iuco...@gmail.com>
> > To: "users" <users@ovirt.org>
> > Sent: Monday, September 26, 2016 6:04:05 PM
> > Subject: [ovirt-users] kerberos and AAA
> >
> > Hi,
> >
> > I've installed the LDAP AAA module for oVirt on the engine host, but I
> > suspect I also need to bind the host to the domain first as I am getting
> > 'peer not authenticated' when I try the auth. Is it ok to install sssd
> and
> > the kerberos tools without on the engine host manually? I know that in
> > general you should avoid installing things manually so wanted to check
> > first.
>
> If you have access to the LDAP server you can just create the keys there
> and transfer to the engine host, or just install the tools in engine host
> and bind. It is not supposed to produce issues.
>
> Rafael
>
> > Thanks,
> >
> > Cam
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] kerberos and AAA

2016-09-26 Thread cmc
Hi,

I've installed the LDAP AAA module for oVirt on the engine host, but I
suspect I also need to bind the host to the domain first as I am getting
'peer not authenticated' when I try the auth. Is it ok to install sssd and
the kerberos tools without on the engine host manually? I know that in
general you should avoid installing things manually so wanted to check
first.

Thanks,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vlan tagging issue

2016-09-15 Thread cmc
Hi Tom,

It turns out that the issue was setting a default aka native VLAN on the
switch port. The switch is an Arista. After I'd tried re-creating the
networks on the oVirt side, I thought I'd just try removing the default
VLAN, and it worked. For whatever reason, our VMWare cluster (that I'm
trying to migrate away from) has this setting, as do our blade centres, and
they have no problem. I'm not sure why you'd want a default Anyway, thanks
for the reply - all sorted now!

Cheers,

Cam

On Thu, Sep 15, 2016 at 1:07 PM, Tom Gamull <tgam...@redhat.com> wrote:

> Can you eliminate the switch or port config as the issue?  I’m a little
> unclear as to how you configured the nodes I have basically use a single
> NIC (some are LACP bonds) with a GENERAL link type (not TRUNK or ACCESS)
> where there is a default VLAN (which I don’t tag) and the rest of the VLANs
> are tagged.  On my switch (TP-LINK) I have to go to the VLANs and say TAG
> on all of them except the DEFAULT one.  I couldn’t get TRUNK working even
> with one untagged and the rest tagged. For me, using GENERAL was the way I
> did it.
>
> I’m not a networking except on hardware but this discussion may clarify.
> I have no idea why TRUNK didn’t work over GENERAL and didn’t spend much
> more time than that but here’s a discussion on the topic
> https://supportforums.cisco.com/discussion/11897946/general-vs-trunk-mode
>
> Tom
>
> On Sep 14, 2016, at 3:08 PM, cmc <iuco...@gmail.com> wrote:
>
> Hi,
>
> I have modified my VM network to have multiple tagged networks. It used to
> be an untagged network and it worked fine, but I needed to add more
> networks on the host. The switch it is connected to has the port configured
> as a trunk port with these VLANs. When a VM sends traffic out (to get a
> DHCP address for instance), it reaches the server but does not get the DHCP
> offer that the server sends. I did a tcpdump on the node that hosts the VM
> and the packets going out do not have a VLAN tag. I assume the VM host
> interface would should not have the tag present, but that the  p2p1.91
> interface should put the VLAN tag on.
>
> The relevant interface configuration on the node that the VM host is on
> looks like:
>
> 27: sohonet_DMZ: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
> state UP
> link/ether a0:36:9f:2a:63:20 brd ff:ff:ff:ff:ff:ff
> 29: p2p1.91@p2p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> noqueue master vmnet state UP
> link/ether a0:36:9f:2a:63:20 brd ff:ff:ff:ff:ff:ff
> 30: vmnet: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
> UP
> link/ether a0:36:9f:2a:63:20 brd ff:ff:ff:ff:ff:ff
> inet6 fe80::a236:9fff:fe2a:6320/64 scope link
>valid_lft forever preferred_lft forever
> 31: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> master vmnet state UNKNOWN qlen 500
> link/ether fe:1a:4a:16:01:58 brd ff:ff:ff:ff:ff:ff
> inet6 fe80::fc1a:4aff:fe16:158/64 scope link
>valid_lft forever preferred_lft forever
> 32: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> master vmnet state UNKNOWN qlen 500
> link/ether fe:1a:4a:16:01:5c brd ff:ff:ff:ff:ff:ff
> inet6 fe80::fc1a:4aff:fe16:15c/64 scope link
>valid_lft forever preferred_lft forever
>
> where vnet1 is the VM interface, and p2p1.91 is the VLAN'd interface for
> the network. The network the VM nic is on is vmnet, and the physical
> interface is p2p1
>
> Configuring an address manually does not help, nor does dropping the
> firewall on the host.
> I've run the vmnet interface in promiscuous mode to see if I can see
> anything coming back, but the return traffic does not appear.
>
> Any ideas as to why the network is not working?
>
> Thanks for any help.
>
> -Cam
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] vlan tagging issue

2016-09-14 Thread cmc
Hi,

I have modified my VM network to have multiple tagged networks. It used to
be an untagged network and it worked fine, but I needed to add more
networks on the host. The switch it is connected to has the port configured
as a trunk port with these VLANs. When a VM sends traffic out (to get a
DHCP address for instance), it reaches the server but does not get the DHCP
offer that the server sends. I did a tcpdump on the node that hosts the VM
and the packets going out do not have a VLAN tag. I assume the VM host
interface would should not have the tag present, but that the  p2p1.91
interface should put the VLAN tag on.

The relevant interface configuration on the node that the VM host is on
looks like:

27: sohonet_DMZ:  mtu 1500 qdisc noqueue
state UP
link/ether a0:36:9f:2a:63:20 brd ff:ff:ff:ff:ff:ff
29: p2p1.91@p2p1:  mtu 1500 qdisc noqueue
master vmnet state UP
link/ether a0:36:9f:2a:63:20 brd ff:ff:ff:ff:ff:ff
30: vmnet:  mtu 1500 qdisc noqueue state
UP
link/ether a0:36:9f:2a:63:20 brd ff:ff:ff:ff:ff:ff
inet6 fe80::a236:9fff:fe2a:6320/64 scope link
   valid_lft forever preferred_lft forever
31: vnet0:  mtu 1500 qdisc pfifo_fast
master vmnet state UNKNOWN qlen 500
link/ether fe:1a:4a:16:01:58 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc1a:4aff:fe16:158/64 scope link
   valid_lft forever preferred_lft forever
32: vnet1:  mtu 1500 qdisc pfifo_fast
master vmnet state UNKNOWN qlen 500
link/ether fe:1a:4a:16:01:5c brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc1a:4aff:fe16:15c/64 scope link
   valid_lft forever preferred_lft forever

where vnet1 is the VM interface, and p2p1.91 is the VLAN'd interface for
the network. The network the VM nic is on is vmnet, and the physical
interface is p2p1

Configuring an address manually does not help, nor does dropping the
firewall on the host.
I've run the vmnet interface in promiscuous mode to see if I can see
anything coming back, but the return traffic does not appear.

Any ideas as to why the network is not working?

Thanks for any help.

-Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users