date:20160720

How about this one? :)

-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org

On Wed, Jul 20, 2016, at 06:04 AM, Fernando Fuentes wrote:
> Is it possible to export all of my vms on my oVirt 3.5 Domain and than
> attach my export domain on my oVirt 4.0 DC and import the vm's?
> 
> Regards,
> 
> -- 
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
> ___
> 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] how to enable

Any body? :)

-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org

On Wed, Jul 20, 2016, at 12:36 PM, Fernando Fuentes wrote:
> Team,
> 
> How can I enable spice-xpi to be supported again on oVirt 4.0?
> 
> Regards,
> 
> -- 
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
> ___
> 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] Hosted Engine oVirt 3.6 iscsi multipath

2016-07-20 Thread Julian De Marchi


On 20/07/2016 5:28 PM, Simone Tiraboschi wrote:

On Wed, Jul 20, 2016 at 7:09 AM, Julian De Marchi
 wrote:

heya--

i have an ovirt 3.6 installation. all my iscsi LUNs are mulipath, however
the hostedengine storage is not.

i tried to import the hostedengine storage domain into my cluster but got a
warning it is controlled via another oVirt cluster. i accepted the warning
and imported anyway, but it crashed my hosted engine and hosted-engine
broker restarted as expected.


You don't have to try manually importing it: the engine will
automatically import once you correctly added your first regular
storage domain.


When I first installed my 3.6 oVirt cluster, there was a bug where the 
storage domain didn't show up after first deploy. I have since upgraded 
the cluster to the latest oVirt 3.6, and the sotrage domain appeared, 
however I never tried to import it until now.





i am curious of how to configure multipath for the hosted engine storage
domain ?


We have an open RFE for that, unfortunately it's still not ready.


Thanks. My reason for looking into this is I need to reboot my prod SAN 
switch. I have the ports split between my two SAN switches, however only 
hostedengine is not multi-path, so during a reboot I will loose access 
to the LUN.


Any solutions to the problem with oVirt? Shutting down the cluster is 
not an option.


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

[ovirt-users] Upgrade 3.6 to 4.0 and "ghost" incompatible cluster version

2016-07-20 Thread Federico Sayd


Hello:

I'm trying to upgrade ovirt 3.6.3 to 4.0, but engine-setup complaints about 
upgrading from incompatible version 3.3

I see in the engine-setup log that  vds_groups table is checked to determine 
the compatibility version. The logs shows that engine-setup detects 2 clusters 
versions: 3.3 and 3.6. Indeed, there is 2 clusters registered in the table: 
"cluster-3.6" and "Default"

"Cluster-3.6" (version 3.6)  is the only cluster in DC in my ovirt setup.
"Default" (version 3.3)  should be a cluster that surely I deleted in a past 
upgrade.

Why a cluster named "Default" (with compatibility version 3.3) is still present 
in vds_group table? Cluster "Default" isn't displayed anywhere in the web 
interface.

Any clue to solve this issue?

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

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

OK, I tried to edit the answerfiles on the other hosts to use another
IP but it doesn't ping and still uses the old GW address.

Any idea ?

2016-07-20 22:27 GMT+02:00 Matt . :
> Maybe it's a good idea to be able to add multiple addresses it should
> ping in order of response.
>
> 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
>> Il 20/Lug/2016 10:06 PM, "Matt ."  ha scritto:
>>>
>>> Hi,
>>>
>>> I'm trying to add a host to a HE installation but my gateway is not
>>> pingable. It's a floating IP which is usable but not pingable in this
>>> case.
>>>
>>> During the first install of the HE I could give any IP to ping and I
>>> used a source IP for the floating GW address.
>>>
>>> What can I do to get around this as the network is OK, even when the
>>> GW is not pingable.
>>
>> I think that gw not pingable will be interpreted as network failure by the
>> agent and will lower the score of the hosts.
>>
>>>
>>> Any idea is welcome!
>>>
>>> Thanks!
>>> ___
>>> 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] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

Maybe it's a good idea to be able to add multiple addresses it should
ping in order of response.

2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
> Il 20/Lug/2016 10:06 PM, "Matt ."  ha scritto:
>>
>> Hi,
>>
>> I'm trying to add a host to a HE installation but my gateway is not
>> pingable. It's a floating IP which is usable but not pingable in this
>> case.
>>
>> During the first install of the HE I could give any IP to ping and I
>> used a source IP for the floating GW address.
>>
>> What can I do to get around this as the network is OK, even when the
>> GW is not pingable.
>
> I think that gw not pingable will be interpreted as network failure by the
> agent and will lower the score of the hosts.
>
>>
>> Any idea is welcome!
>>
>> Thanks!
>> ___
>> 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] trying to upgrade host engine 4.0 to 4.1

2016-07-20 Thread Rafael Almeida

Hello, i'm trying to upgrade my ovirt engine host  4.0.0.6-1 in my 
centos7.2 x64 to 4.1, using:


yum update "ovirt-engine-setup*"

but not work:

No packages marked for update
my repos are:

CentOS-Base.repo   CentOS-Media.repoepel-testing.repo
CentOS-CR.repo CentOS-Sources.repo ovirt-4.0-dependencies.repo
CentOS-Debuginfo.repo  CentOS-Vault.repoovirt-4.0.repo
CentOS-fasttrack.repo  epel.repo
if I try with the command

yum install vdsm*

list the new version (4.1)

vdsm  x86_64 4.18.4.1-0.el7.centos ovirt-4.0

what is the problem? please helpme

Thnx

Rafael Almeida Orellana

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

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

Hi,

Can I change that in some file ? on the HE storage ?

2016-07-20 22:09 GMT+02:00 Yedidyah Bar David :
> On Wed, Jul 20, 2016 at 11:05 PM, Matt .  wrote:
>> Hi,
>>
>> I'm trying to add a host to a HE installation but my gateway is not
>> pingable. It's a floating IP which is usable but not pingable in this
>> case.
>>
>> During the first install of the HE I could give any IP to ping and I
>> used a source IP for the floating GW address.
>>
>> What can I do to get around this as the network is OK, even when the
>> GW is not pingable.
>>
>> Any idea is welcome!
>
> Just provide some other pingable IP address.
>
> HA uses this address to check if the network is ok. It does not mind if
> it's really your router or not.
>
> Best,
> --
> Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

2016-07-20 Thread Sandro Bonazzola

Il 20/Lug/2016 10:06 PM, "Matt ."  ha scritto:
>
> Hi,
>
> I'm trying to add a host to a HE installation but my gateway is not
> pingable. It's a floating IP which is usable but not pingable in this
> case.
>
> During the first install of the HE I could give any IP to ping and I
> used a source IP for the floating GW address.
>
> What can I do to get around this as the network is OK, even when the
> GW is not pingable.

I think that gw not pingable will be interpreted as network failure by the
agent and will lower the score of the hosts.

>
> Any idea is welcome!
>
> Thanks!
> ___
> 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] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

2016-07-20 Thread Yedidyah Bar David

On Wed, Jul 20, 2016 at 11:05 PM, Matt .  wrote:
> Hi,
>
> I'm trying to add a host to a HE installation but my gateway is not
> pingable. It's a floating IP which is usable but not pingable in this
> case.
>
> During the first install of the HE I could give any IP to ping and I
> used a source IP for the floating GW address.
>
> What can I do to get around this as the network is OK, even when the
> GW is not pingable.
>
> Any idea is welcome!

Just provide some other pingable IP address.

HA uses this address to check if the network is ok. It does not mind if
it's really your router or not.

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

[ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

Hi,

I'm trying to add a host to a HE installation but my gateway is not
pingable. It's a floating IP which is usable but not pingable in this
case.

During the first install of the HE I could give any IP to ping and I
used a source IP for the floating GW address.

What can I do to get around this as the network is OK, even when the
GW is not pingable.

Any idea is welcome!

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

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

On Wed, Jul 20, 2016 at 6:18 PM, Nicolás  wrote:

>
>
> El 20/07/16 a las 16:45, Martin Perina escribió:
>
>
>
> On Wed, Jul 20, 2016 at 4:44 PM, Nicolás  wrote:
>
>> Hi Martin,
>>
>> Actually, up until now we had that cert configured in httpd and in
>> websocket proxy. Seems that now in 4.0.x it's not enough, as opening the
>> https://fqdn complains about the cert not being imported in the key
>> chain.
>>
>
> Yes, there's an updated procedure on using external CA in 4.0, for
> details please take a look at Doc Text in
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1336838
> 
>
>
>> So I imported it via keytool, but I don't want to use it in the engine
>> <-> VDSM communication.
>>
>
> Hmm, so that would imply that we have some issue with existing internal
> enigne CA during upgrade ...
> The strange thing is that we test upgrades a lot but so far we haven't
> seen any issues which will broke
> SSL setup between engine and VDSM. You said that you had to downgrade back
> to 3.6.7 (so unfortunately for us we cannot investigate your nonworking
> setup more), but how did you do that?
> Removing all engine packages and configuration, installing back 3.6.7
> packaging and restoring configuration form backup?
> I'm asking to know what changed in your setup between not working 4.0 and
> working 3.6.7 ...
>
>
> Indeed, those are the steps I followed to the point.
>
> To add more strangeness, previously to upgrading this oVirt
> infrastructure, we upgraded another one that we have (also using own cert,
> a different one but from the same CA) and everything went smoothly. And
> what's more, previously to upgrading the engine that failed, I created a
> copy of that engine machine in a sandbox environment to see if upgrade
> process would or not success, and it worked perfectly.
>
> The only difference between the sandbox and the real machine's process was
> that when upgrading the real one, the first time I run "engine-setup" it
> failed because 'systemd' reported PostgreSQL as it was not running
> (actually it was, thougg), so everything rolled back. I had to kill the
> PostgreSQL process, start it again with systemctl and then run
> "engine-setup", where the process completed successfully but the SSL issue
> appeared. Not sure if this rollback could have shattered the whole thing...
>
> Anyhow, tomorrow I'm going to create another copy of the engine machine to
> a sandbox environment and try again. If it works I'll cross my fingers and
> give another try on the real machine...
>
> Thanks!
>

Thanks a lot for you effort. I will try to perform same upgrade tomorrow
in my test env.



>
> Thanks
>
> Martin
>
>
>> Thanks!
>> En 20/7/2016 2:48 p. m., Martin Perina  escribió:
>>
>> Hi,
>>
>> sorry for late response, I overlook your reply :-(
>>
>> I looked at your logs and it seems to me that there's SSL error when
>> engine tries to contact VDSM.
>> You have mentioned that your are using your own custom CA. Are you
>> using it only for HTTPS certificate or do you want to use it also for
>> Engine <-> VDSM communication?
>> 
>> Martin Perina
>>
>>
>> On Wed, Jul 20, 2016 at 9:18 AM,  wrote:
>>
>>> Any hints about this?
>>>
>>> El 2016-07-13 11:13, nico...@devels.es escribió:
>>>
 Hi,

 Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
 Actually, the error changed to 'General SSLEngine problem', but the
 result was the same, like this:

 2016-07-13 09:52:22,010 INFO
 [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
 Reactor) [] Connecting to /10.X.X.X
 2016-07-13 09:52:22,018 ERROR
 [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor)
 [] Unable to process messages: General SSLEngine problem

 It's worth mentioning that we're using our own SSL certificates (not
 self-signed), and I imported the combined certificate into the
 /etc/pki/ovirt-engine/.truststore key file. Not sure if related, but
 just in case.

>>>
 I had to downgrade to 3.6.7. I'm attaching requested logs, if you need
 anything else don't hesitate to ask.

 Regards.

 El 2016-07-13 09:45, Martin Perina escribió:

> Hi,
>
> could you please share also vdsm.log from your hosts and also
> server.log and setup logs from /var/log/ovirt-engine/setup directory?
>
> Thanks
>
> Martin Perina
>
> On Wed, Jul 13, 2016 at 10:36 AM,  wrote:
>
> Hi,
>>
>> We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the
>> engine cannot connect to hosts. In the logs all we see is this
>> error:
>>
>> ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
>> Stomp Reactor) [] Unable to process messages
>>
>> I'm attaching full logs.
>>
>> Could someone help please?
>>
>> Thanks.
>>

Re: [ovirt-users] Import of ova failed

2016-07-20 Thread Richard W.M. Jones

On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> >
> > The import doesn't happen automatically, you have to do the final step
> > manually (when using the command line).  See:
> >
> > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> >
> > However that error shouldn't happen.  It looks like the name is the
> > same as the name of an existing VM.  From virt-v2v you can do the
> > whole conversion/import over again, this time adding the `-on
> > new_name' option to the command line (obviously choosing a name which
> > is not otherwise being used).
> >
> > I don't know if there's a way to get oVirt to change the name when
> > importing from the export domain.  As far as I know you have to start
> > the import from scratch.
> >
> >
> There's no existing VM with that name that I can see. It may have come from
> one of my earlier import attempts,
> though that earlier attempt did not show up in the GUI, it did write files
> to the export domain.
> 
> I re-ran the conversion again with a rename but it failed to import it
> again, with the same error.
> 
> Could there be a record in the DB somewhere, or does it look at the files
> alone? Just trying to work out where the conflict is.

I had a look at the ovirt-engine code where
ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come
from a database check.  However I'm not really familiar enough with
the code to be sure.  Probably best to ask an oVirt developer, or try
dumping the database to see if "wvm2" appears in a column anywhere.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

>
> The import doesn't happen automatically, you have to do the final step
> manually (when using the command line).  See:
>
> http://libguestfs.org/virt-v2v.1.html#output-to-rhev
>
> However that error shouldn't happen.  It looks like the name is the
> same as the name of an existing VM.  From virt-v2v you can do the
> whole conversion/import over again, this time adding the `-on
> new_name' option to the command line (obviously choosing a name which
> is not otherwise being used).
>
> I don't know if there's a way to get oVirt to change the name when
> importing from the export domain.  As far as I know you have to start
> the import from scratch.
>
>
There's no existing VM with that name that I can see. It may have come from
one of my earlier import attempts,
though that earlier attempt did not show up in the GUI, it did write files
to the export domain.

I re-ran the conversion again with a rename but it failed to import it
again, with the same error.

Could there be a record in the DB somewhere, or does it look at the files
alone? Just trying to work out where the conflict is.


Thanks,

-C


> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-p2v converts physical machines to virtual machines.  Boot with a
> live CD or over the network (PXE) and turn machines into KVM guests.
> http://libguestfs.org/virt-v2v
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

2016-07-20 Thread Richard W.M. Jones

On Wed, Jul 20, 2016 at 06:37:38PM +0100, Cam Mac wrote:
> It did show up in the list of importable VMs
> under the 'Import VM' tab under
> the export domain. I tried importing it from there but it gave me:
> 
> 2016-07-20 18:27:24,518 INFO
>  [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (default
> task-317) [27b3ad4b] Lock freed to object
> 'EngineLock:{exclusiveLocks='[wvm2= ACTION_TYPE_FAILED_NAME_ALREADY_USED>,
> 7d40eaee-2f3f-4a4e-8254-4c2c3312ce5c= ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName wvm2>]',
> sharedLocks='[7d40eaee-2f3f-4a4e-8254-4c2c3312ce5c= ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName wvm2>]'}'
> 
> So I guess it is doing the import still.

The import doesn't happen automatically, you have to do the final step
manually (when using the command line).  See:

http://libguestfs.org/virt-v2v.1.html#output-to-rhev

However that error shouldn't happen.  It looks like the name is the
same as the name of an existing VM.  From virt-v2v you can do the
whole conversion/import over again, this time adding the `-on
new_name' option to the command line (obviously choosing a name which
is not otherwise being used).

I don't know if there's a way to get oVirt to change the name when
importing from the export domain.  As far as I know you have to start
the import from scratch.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

Hi Richard,

Sorry for missing that TMPDIR, I was looking rather than actually reading.

I used the original ova I'd exported from VMWare, and that worked fine
(after fixing perms). The command I ran was:

virt-v2v -x -v -i ova /mnt/import-vm/wvm2.ova -o rhev -os
ovirt-engine:/mnt/export-vm -of qcow2

It returned without error and copied it to the export domain ok. It hasn't
appeared in the list of VMs as yet in the GUI. I guess it is
in the process of doing so? It did show up in the list of importable VMs
under the 'Import VM' tab under
the export domain. I tried importing it from there but it gave me:

2016-07-20 18:27:24,518 INFO
 [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (default
task-317) [27b3ad4b] Lock freed to object
'EngineLock:{exclusiveLocks='[wvm2=,
7d40eaee-2f3f-4a4e-8254-4c2c3312ce5c=]',
sharedLocks='[7d40eaee-2f3f-4a4e-8254-4c2c3312ce5c=]'}'

So I guess it is doing the import still.

Cheers,

Campbell


On Wed, Jul 20, 2016 at 4:05 PM, Richard W.M. Jones 
wrote:

> On Wed, Jul 20, 2016 at 03:40:16PM +0100, Cam Mac wrote:
> > Hi Rich,
> >
> >
> > > > >
> > > >
> > > > I can try this but I'm not quite sure how to go about it. The ovf I
> > > created
> > > > via guest-image-ovf-creator is on an NFS mount
>
> Originally you were trying to import OVAs from VMware, which is the
> only source of OVAs we actually test.  If you're trying to import from
> VMware, get VMware to create the OVAs for you using the vSphere Export
> GUI or ovftool:
>
>   http://libguestfs.org/virt-v2v.1.html#ova:-create-ova
>
> > I'm using 'virt-v2v -v -i ova wvm2.ovf -o rhev -os
> > ovirt-engine:/mnt/export-vm' (my export domain), though unfortunately it
> > fails
> >
> > Error is:
> >
> > [root@kvm-ldn-01 tmp]# virt-v2v -v -x -i ova wvm2.ovf -o rhev -os
> > ovirt-engine:/mnt/export-vm
> > virt-v2v: libguestfs 1.28.1 (x86_64)
> > [   0.0] Opening the source -i ova wvm2.ovf
> > tar -xzf 'wvm2.ovf' -C '/var/tmp/ova.dEFSqi'
> > virt-v2v: error: could not parse ovf:Name from OVF document
>
> I had a look at guest-image-ovf-creator.py anyway and the problem is
> that this script doesn't put any  section into the OVF
> document at all.  I couldn't keep my eyes open long enough while
> reading the turgid DTMF OVF standards document to find out if this
> section is required or not, but virt-v2v certainly expects it.  (That
> is just the first failure, there may be more.)
>
> Anyway, use an OVA generated by VMware.
>
> > BTW: is there a way of specifying the extraction directory? My first
> > attempt filled up /var/tmp until I found another host
> > that luckily had a big enough partition.
>
> Yes, you can set TMPDIR as mentioned in the manual.
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-builder quickly builds VMs from scratch
> http://libguestfs.org/virt-builder.1.html
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] how to enable

Team,

How can I enable spice-xpi to be supported again on oVirt 4.0?

Regards,

-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to import pre-configured nfs data domain

2016-07-20 Thread Logan Kuhn

Am I correct in the assumption that importing a previously master data domain 
into a fresh engine without a current master domain is supported? 

Regards, 
Logan 

- On Jul 19, 2016, at 7:16 AM, Logan Kuhn  wrote: 

| We are currently evaluating ovirt for our new VM backend and part of that is
| moving the engine to a physical controller node. So I took the opportunity to
| test a DR scenario where the engine fails and takes more than a reboot to 
bring
| it back up. For the most part it was straight forward to get it up and going,
| but I'm having a hard time getting the previous master data domain to import
| into the new engine. I've attached relevant snippets of the engine and vdsm
| log.

| Engine: http://pastebin.com/xBZ7CBs7

| VDSM: http://pastebin.com/eksVyWBn

| Regards,
| Logan

| ___
| 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] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-20 Thread Nicolás




El 20/07/16 a las 16:45, Martin Perina escribió:



On Wed, Jul 20, 2016 at 4:44 PM, Nicolás > wrote:


Hi Martin,

Actually, up until now we had that cert configured in httpd and in
websocket proxy. Seems that now in 4.0.x it's not enough, as
opening the https://fqdn complains about the cert not being
imported in the key chain.


Yes, there's an updated procedure on using external CA in 4.0, for 
details please take a look at Doc Text in


https://bugzilla.redhat.com/show_bug.cgi?id=1336838


So I imported it via keytool, but I don't want to use it in the
engine <-> VDSM communication.


Hmm, so that would imply that we have some issue with existing 
internal enigne CA during upgrade ...
The strange thing is that we test upgrades a lot but so far we haven't 
seen any issues which will broke
SSL setup between engine and VDSM. You said that you had to downgrade 
back to 3.6.7 (so unfortunately for us we cannot investigate your 
nonworking setup more), but how did you do that?
Removing all engine packages and configuration, installing back 3.6.7 
packaging and restoring configuration form backup?
I'm asking to know what changed in your setup between not working 4.0 
and working 3.6.7 ...




Indeed, those are the steps I followed to the point.

To add more strangeness, previously to upgrading this oVirt 
infrastructure, we upgraded another one that we have (also using own 
cert, a different one but from the same CA) and everything went 
smoothly. And what's more, previously to upgrading the engine that 
failed, I created a copy of that engine machine in a sandbox environment 
to see if upgrade process would or not success, and it worked perfectly.


The only difference between the sandbox and the real machine's process 
was that when upgrading the real one, the first time I run 
"engine-setup" it failed because 'systemd' reported PostgreSQL as it was 
not running (actually it was, thougg), so everything rolled back. I had 
to kill the PostgreSQL process, start it again with systemctl and then 
run "engine-setup", where the process completed successfully but the SSL 
issue appeared. Not sure if this rollback could have shattered the whole 
thing...


Anyhow, tomorrow I'm going to create another copy of the engine machine 
to a sandbox environment and try again. If it works I'll cross my 
fingers and give another try on the real machine...


Thanks!


Thanks

Martin


Thanks!
En 20/7/2016 2:48 p. m., Martin Perina > escribió:

Hi,

sorry for late response, I overlook your reply :-(

I looked at your logs and it seems to me that there's SSL
error when engine tries to contact VDSM.
You have mentioned that your are using your own custom CA.
Are you using it only for HTTPS certificate or do you want to
use it also for Engine <-> VDSM communication?

Martin Perina


On Wed, Jul 20, 2016 at 9:18 AM, > wrote:

Any hints about this?

El 2016-07-13 11:13, nico...@devels.es
 escribió:

Hi,

Unfortunately, upgrading to 4.0.1RC didn't solve the
problem.
Actually, the error changed to 'General SSLEngine
problem', but the
result was the same, like this:

2016-07-13 09:52:22,010 INFO
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient]
(SSL Stomp
Reactor) [] Connecting to /10.X.X.X
2016-07-13 09:52:22,018 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
Stomp Reactor)
[] Unable to process messages: General SSLEngine problem

It's worth mentioning that we're using our own SSL
certificates (not
self-signed), and I imported the combined certificate
into the
/etc/pki/ovirt-engine/.truststore key file. Not sure
if related, but
just in case.


I had to downgrade to 3.6.7. I'm attaching requested
logs, if you need
anything else don't hesitate to ask.

Regards.

El 2016-07-13 09:45, Martin Perina escribió:

Hi,

could you please share also vdsm.log from your
hosts and also
server.log and setup logs from
/var/log/ovirt-engine/setup directory?

Thanks

Martin Perina

On Wed, Jul 13, 2016 at 10:36 AM,
> wrote:

Hi,

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-20 Thread Ariel Perez - BookIt . com System Administrator

On Wed, Jul 20, 2016 at 4:44 PM, Nicolás  wrote:

> Hi Martin,
>
> Actually, up until now we had that cert configured in httpd and in
> websocket proxy. Seems that now in 4.0.x it's not enough, as opening the
> https://fqdn complains about the cert not being imported in the key
> chain.
>

Yes, there's an updated procedure on using external CA in 4.0, for details
please take a look at Doc Text in

https://bugzilla.redhat.com/show_bug.cgi?id=1336838



> So I imported it via keytool, but I don't want to use it in the engine <->
> VDSM communication.
>

Hmm, so that would imply that we have some issue with existing internal
enigne CA during upgrade ...
The strange thing is that we test upgrades a lot but so far we haven't seen
any issues which will broke
SSL setup between engine and VDSM. You said that you had to downgrade back
to 3.6.7 (so unfortunately for us we cannot investigate your nonworking
setup more), but how did you do that?
Removing all engine packages and configuration, installing back 3.6.7
packaging and restoring configuration form backup?
I'm asking to know what changed in your setup between not working 4.0 and
working 3.6.7 ...

Thanks

Martin


> Thanks!
> En 20/7/2016 2:48 p. m., Martin Perina  escribió:
>
> Hi,
>
> sorry for late response, I overlook your reply :-(
>
> I looked at your logs and it seems to me that there's SSL error when
> engine tries to contact VDSM.
> You have mentioned that your are using your own custom CA. Are you using
> it only for HTTPS certificate or do you want to use it also for Engine <->
> VDSM communication?
> 
> Martin Perina
>
>
> On Wed, Jul 20, 2016 at 9:18 AM,  wrote:
>
>> Any hints about this?
>>
>> El 2016-07-13 11:13, nico...@devels.es escribió:
>>
>>> Hi,
>>>
>>> Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
>>> Actually, the error changed to 'General SSLEngine problem', but the
>>> result was the same, like this:
>>>
>>> 2016-07-13 09:52:22,010 INFO
>>> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
>>> Reactor) [] Connecting to /10.X.X.X
>>> 2016-07-13 09:52:22,018 ERROR
>>> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor)
>>> [] Unable to process messages: General SSLEngine problem
>>>
>>> It's worth mentioning that we're using our own SSL certificates (not
>>> self-signed), and I imported the combined certificate into the
>>> /etc/pki/ovirt-engine/.truststore key file. Not sure if related, but
>>> just in case.
>>>
>>
>>> I had to downgrade to 3.6.7. I'm attaching requested logs, if you need
>>> anything else don't hesitate to ask.
>>>
>>> Regards.
>>>
>>> El 2016-07-13 09:45, Martin Perina escribió:
>>>
 Hi,

 could you please share also vdsm.log from your hosts and also
 server.log and setup logs from /var/log/ovirt-engine/setup directory?

 Thanks

 Martin Perina

 On Wed, Jul 13, 2016 at 10:36 AM,  wrote:

 Hi,
>
> We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the
> engine cannot connect to hosts. In the logs all we see is this
> error:
>
> ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
> Stomp Reactor) [] Unable to process messages
>
> I'm attaching full logs.
>
> Could someone help please?
>
> Thanks.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users [1]
>



 Links:
 --
 [1] http://lists.ovirt.org/mailman/listinfo/users

>>>
>>> ___
>>> 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] Cannot configure/save Network Interfaces in a freshly installed oVirt Node 4.0.1

Hi everyone,
I'm trying to save the Network Interfaces configuration in a freshly installed 
hypervisor in version 4.0.1, and I'm getting this error:


Error while executing action:

blade1c1.ism.ld:

  *   Cannot setup Networks. Role (migration/display/gluster) network 
'migration' hasn't boot protocol assigned.


The configuration is exactly the same as in the rest of the nodes (3.6 latest 
one). I've been googling it but nothing.

Thank u in advance,

Ariel

-- 
This email was Virus checked by UTM 9. For issues please contact the Windows 
Systems Admin.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

2016-07-20 Thread Richard W.M. Jones

On Wed, Jul 20, 2016 at 03:40:16PM +0100, Cam Mac wrote:
> Hi Rich,
> 
> 
> > > >
> > >
> > > I can try this but I'm not quite sure how to go about it. The ovf I
> > created
> > > via guest-image-ovf-creator is on an NFS mount

Originally you were trying to import OVAs from VMware, which is the
only source of OVAs we actually test.  If you're trying to import from
VMware, get VMware to create the OVAs for you using the vSphere Export
GUI or ovftool:

  http://libguestfs.org/virt-v2v.1.html#ova:-create-ova

> I'm using 'virt-v2v -v -i ova wvm2.ovf -o rhev -os
> ovirt-engine:/mnt/export-vm' (my export domain), though unfortunately it
> fails
> 
> Error is:
> 
> [root@kvm-ldn-01 tmp]# virt-v2v -v -x -i ova wvm2.ovf -o rhev -os
> ovirt-engine:/mnt/export-vm
> virt-v2v: libguestfs 1.28.1 (x86_64)
> [   0.0] Opening the source -i ova wvm2.ovf
> tar -xzf 'wvm2.ovf' -C '/var/tmp/ova.dEFSqi'
> virt-v2v: error: could not parse ovf:Name from OVF document

I had a look at guest-image-ovf-creator.py anyway and the problem is
that this script doesn't put any  section into the OVF
document at all.  I couldn't keep my eyes open long enough while
reading the turgid DTMF OVF standards document to find out if this
section is required or not, but virt-v2v certainly expects it.  (That
is just the first failure, there may be more.)

Anyway, use an OVA generated by VMware.

> BTW: is there a way of specifying the extraction directory? My first
> attempt filled up /var/tmp until I found another host
> that luckily had a big enough partition.

Yes, you can set TMPDIR as mentioned in the manual.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] ovirt-3.6 : Hosted-engine crashed and can't restart

2016-07-20 Thread Alexis HAUSER

After assigning an IP adress to a VLAN network (it was using DHCP by default) 
that was on the same NIC than ovirtmgmt, my hosted-engine crashed and can't 
start again...I have no idea how to fix this.
I had a similar issue some months ago but with a different error. I tried to 
restart the ha agent that seems to be linked with this error, also restarted 
the host. I also tried to remove the _DIRECT_IO_ lockfile on the engine storage 
as it fixed my problem last time but it didn't help...

Any ideas ? Do you think editing manually the logical network in the host and 
reverting them at it was before crash can help ?






hosted-engine --vm-status
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/vm_status.py", line 
117, in 
if not status_checker.print_status():
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/vm_status.py", line 
60, in print_status
all_host_stats = ha_cli.get_all_host_stats()
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", 
line 160, in get_all_host_stats
return self.get_all_stats(self.StatModes.HOST)
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", 
line 103, in get_all_stats
self._configure_broker_conn(broker)
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", 
line 180, in _configure_broker_conn
dom_type=dom_type)
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", 
line 176, in set_storage_domain
.format(sd_type, options, e))
ovirt_hosted_engine_ha.lib.exceptions.RequestError: Failed to set storage 
domain FilesystemBackend, options {'dom_type': 'nfs3', 'sd_uuid': 
'e41807e5-ee68-40a2-a642-cc226ba0e82d'}: Request failed: 


vdsClient -s 0 list

16450089-911e-4bad-a8b7-98e84a79ef3a
Status = Down
nicModel = rtl8139,pv
statusTime = 4295559350
exitMessage = Unable to get volume size for domain 
e41807e5-ee68-40a2-a642-cc226ba0e82d volume 053df3a6-db18-445a-8f75-61c630ab0003
emulatedMachine = rhel6.5.0
pid = 0
vmName = HostedEngine
devices = [{'index': '0', 'iface': 'virtio', 'format': 'raw', 
'bootOrder': '1', 'address': {'slot': '0x06', 'bus': '0x00', 'domain': 
'0x', 'type': 'pci', 'function': '0x0'}, 'volumeID': 
'053df3a6-db18-445a-8f75-61c630ab0003', 'imageID': 
'b6daa50d-adad-46a5-8f5f-accfb155a1e1', 'readonly': 'false', 'domainID': 
'e41807e5-ee68-40a2-a642-cc226ba0e82d', 'deviceId': 
'b6daa50d-adad-46a5-8f5f-accfb155a1e1', 'poolID': 
'----', 'device': 'disk', 'shared': 
'exclusive', 'propagateErrors': 'off', 'type': 'disk'}, {'nicModel': 'pv', 
'macAddr': '00:16:3e:1c:4b:81', 'linkActive': 'true', 'network': 'ovirtmgmt', 
'deviceId': '0aeaea2f-a419-43cc-92d7-8422f6aa9223', 'address': 'None', 
'device': 'bridge', 'type': 'interface'}, {'index': '2', 'iface': 'ide', 
'readonly': 'true', 'deviceId': '8c3179ac-b322-4f5c-9449-c52e3665e0ae', 
'address': {'bus': '1', 'controller': '0', 'type': 'drive', 'target': '0', 
'unit': '0'}, 'device': 'cdrom', 'shared': 'false', 'path': '', 'type': 
'disk'}, {'device': 'scsi', 'model': 'virtio-scsi', 'type': 'controller', 
'deviceId': '21db0c6e-071c-48ff-b905-95478b37c384', 'address': {'slot': '0x04', 
'bus': '0x00', 'domain': '0x', 'type': 'pci', 'function': '0x0'}}, 
{'device': 'usb', 'type': 'controller', 'deviceId': 
'c0384f68-d0c9-4ebb-a779-8dc9911ce2f8', 'address': {'slot': '0x01', 'bus': 
'0x00', 'domain': '0x', 'type': 'pci', 'function': '0x2'}}, {'device': 
'ide', 'type': 'controller', 'deviceId': 
'd5a2dd13-138a-482b-9bc3-994b10ec4100', 'address': {'slot': '0x01', 'bus': 
'0x00', 'domain': '0x', 'type': 'pci', 'function': '0x1'}}, {'device': 
'virtio-serial', 'type': 'controller', 'deviceId': 
'9e695172-c9b0-47df-bc76-8170219dec28', 'address': {'slot': '0x05', 'bus': 
'0x00', 'domain': '0x', 'type': 'pci', 'function': '0x0'}}]
guestDiskMapping = {}
vmType = kvm
displaySecurePort = -1
exitReason = 1
memSize = 6000
displayPort = -1
clientIp = 
spiceSecureChannels = 
smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir
smp = 4
displayIp = 0
display = vnc
exitCode = 1


systemctl status ovirt-ha-agent.service -l
● ovirt-ha-agent.service - oVirt Hosted Engine High Availability Monitoring 
Agent
   Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-agent.service; enabled; 
vendor preset: disabled)
   Active: active (running) since Wed 2016-07-20 14:56:22 UTC; 2min 29s ago
 Main PID: 20236 (ovirt-ha-agent)
   CGroup: /system.slice/ovirt-ha-agent.service
   └─20236 /usr/bin/python

Re: [ovirt-users] synchronize cache

2016-07-20 Thread Sandro Bonazzola

On Mon, Jul 18, 2016 at 9:41 AM, Markus Scherer  wrote:

> Hi,
>
> on an fresh installed fedora server 23 i got a "Failed to synchronize
> cache for repo 'ovirt-4.0'".
> I have done a "dnf clean all" a "dnf check-update" and a reboot but always
> the same problem.
>
> thx for help
>

I regenerated the metadata within the repo, can you please try again?
Thanks,



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



-- 
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

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-20 Thread Nicolás

Hi Martin,

Actually, up until now we had that cert configured in httpd and in websocket proxy. Seems that now in 4.0.x it's not enough, as opening the https://fqdn complains about the cert not being imported in the key chain. So I imported it via keytool, but I don't want to use it in the engine <-> VDSM communication.

Thanks!En 20/7/2016 2:48 p. m., Martin Perina escribió:Hi,sorry for late response, I overlook your reply :-(I looked at your logs and it seems to me that there's SSL error when engine tries to contact VDSM.You have mentioned that your are using your own custom CA. Are you using it only for HTTPS certificate or do you want to use it also for Engine <-> VDSM communication?Martin Perina On Wed, Jul 20, 2016 at 9:18 AM, wrote:Any hints about this?

El 2016-07-13 11:13, nico...@devels.es escribió:

Hi,

Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
Actually, the error changed to 'General SSLEngine problem', but the
result was the same, like this:

2016-07-13 09:52:22,010 INFO
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
Reactor) [] Connecting to /10.X.X.X
2016-07-13 09:52:22,018 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor)
[] Unable to process messages: General SSLEngine problem

It's worth mentioning that we're using our own SSL certificates (not
self-signed), and I imported the combined certificate into the
/etc/pki/ovirt-engine/.truststore key file. Not sure if related, but
just in case.

I had to downgrade to 3.6.7. I'm attaching requested logs, if you need
anything else don't hesitate to ask.

Regards.

El 2016-07-13 09:45, Martin Perina escribió:

Hi,

could you please share also vdsm.log from your hosts and also
server.log and setup logs from /var/log/ovirt-engine/setup directory?

Thanks

Martin Perina

On Wed, Jul 13, 2016 at 10:36 AM, wrote:

Hi,

We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the
engine cannot connect to hosts. In the logs all we see is this
error:

ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
Stomp Reactor) [] Unable to process messages

I'm attaching full logs.

Could someone help please?

Thanks.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users [1]

Links:
--
[1] http://lists.ovirt.org/mailman/listinfo/users

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

Re: [ovirt-users] Import of ova failed

I tried the GUI first (in 3.6 and later 4.0 after upgrading) and it fails.
I posted to the list about this here:

http://lists.ovirt.org/pipermail/users/2016-June/040442.html

No solution was found so far.

Thanks,

Cam


On Tue, Jul 19, 2016 at 8:51 PM, Richard W.M. Jones 
wrote:

> And I suppose it's worth saying that recent oVirt can import from
> VMware using the oVirt GUI (which works via virt-v2v, but automates
> everything for you).
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-top is 'top' for virtual machines.  Tiny program with many
> powerful monitoring features, net stats, disk stats, logging, etc.
> http://people.redhat.com/~rjones/virt-top
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

Hi Rich,


> > >
> >
> > I can try this but I'm not quite sure how to go about it. The ovf I
> created
> > via guest-image-ovf-creator is on an NFS mount
> > on the engine: do I need to run virt-v2v on one of the nodes? If so, I
> > assume I need to set the output to an export domain.
> > Does '-o local' stick it on the node's VM storage?
>
> Yes, don't use -o local.
>
> virt-v2v has an -o rhev option which will import directly from VMware
> to RHEV or oVirt.  Please see the manual:
>
> http://libguestfs.org/virt-v2v.1.html#convert-from-vmware-to-rhev-m-ovirt
> http://libguestfs.org/virt-v2v.1.html#output-to-rhev
>
>
>
I'm using 'virt-v2v -v -i ova wvm2.ovf -o rhev -os
ovirt-engine:/mnt/export-vm' (my export domain), though unfortunately it
fails

Error is:

[root@kvm-ldn-01 tmp]# virt-v2v -v -x -i ova wvm2.ovf -o rhev -os
ovirt-engine:/mnt/export-vm
virt-v2v: libguestfs 1.28.1 (x86_64)
[   0.0] Opening the source -i ova wvm2.ovf
tar -xzf 'wvm2.ovf' -C '/var/tmp/ova.dEFSqi'
virt-v2v: error: could not parse ovf:Name from OVF document

If reporting bugs, run virt-v2v with debugging enabled and include the
complete output:

  virt-v2v -v -x [...]
[root@kvm-ldn-01 tmp]

I can attach the XML ovf file that is is inside the ovf archive if that is
a help.

BTW: is there a way of specifying the extraction directory? My first
attempt filled up /var/tmp until I found another host
that luckily had a big enough partition.

Thanks,

Cam


> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-top is 'top' for virtual machines.  Tiny program with many
> powerful monitoring features, net stats, disk stats, logging, etc.
> http://people.redhat.com/~rjones/virt-top
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [oVirt/ovirt-site] ovirt-guest-agent install guide Debian - service ovirt-guest-agent enable (#370)

2016-07-20 Thread Yaniv Kaul

Redirecting to ovirt users mailing list.
Y.

On Wed, Jul 20, 2016 at 4:54 PM, Karl Fiabeschi 
wrote:

> according to your guide
>
>
> https://www.ovirt.org/documentation/how-to/guest-agent/install-the-guest-agent-in-debian/
>
> after agent install, i must enable and start it with:
>
> service ovirt-guest-agent enable && service ovirt-guest-agent start
>
> but if i try on debian7/8 i have only:
>
> root@x:~# service ovirt-guest-agent enable
> Usage: /etc/init.d/ovirt-guest-agent {start|stop|status|restart|force-reload}
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> , or mute the thread
> 
> .
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] stuck host in hosted engine migration 3.6->4.0

2016-07-20 Thread Oved Ourfali

Also, this thread seems similar.
Also talking about IPV4/IPV6 issue.
Does it help?

[1] http://lists.ovirt.org/pipermail/users/2016-June/040602.html

On Wed, Jul 20, 2016 at 4:43 PM, Martin Perina  wrote:

> Hi,
>
> could you please create a bug and attach engine host logs (all from
> /var/log/ovirt-engine) and VDSM logs (from /var/log/vdsm)?
>
> Thanks
>
> Martin Perina
>
>
> On Wed, Jul 20, 2016 at 1:50 PM, Gervais de Montbrun <
> gerv...@demontbrun.com
> > wrote:
>
> > Hi Qiong,
> >
> > I am experiencing the exact same issue. All four of my hosts are throwing
> > the same error to the vdsm.log If you find a solution, please let me know
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

Hi,

sorry for late response, I overlook your reply :-(

I looked at your logs and it seems to me that there's SSL error when
engine tries to contact VDSM.
You have mentioned that your are using your own custom CA. Are you using
it only for HTTPS certificate or do you want to use it also for Engine <->
VDSM communication?

Martin Perina


On Wed, Jul 20, 2016 at 9:18 AM,  wrote:

> Any hints about this?
>
> El 2016-07-13 11:13, nico...@devels.es escribió:
>
>> Hi,
>>
>> Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
>> Actually, the error changed to 'General SSLEngine problem', but the
>> result was the same, like this:
>>
>> 2016-07-13 09:52:22,010 INFO
>> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
>> Reactor) [] Connecting to /10.X.X.X
>> 2016-07-13 09:52:22,018 ERROR
>> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor)
>> [] Unable to process messages: General SSLEngine problem
>>
>> It's worth mentioning that we're using our own SSL certificates (not
>> self-signed), and I imported the combined certificate into the
>> /etc/pki/ovirt-engine/.truststore key file. Not sure if related, but
>> just in case.
>>
>
>> I had to downgrade to 3.6.7. I'm attaching requested logs, if you need
>> anything else don't hesitate to ask.
>>
>> Regards.
>>
>> El 2016-07-13 09:45, Martin Perina escribió:
>>
>>> Hi,
>>>
>>> could you please share also vdsm.log from your hosts and also
>>> server.log and setup logs from /var/log/ovirt-engine/setup directory?
>>>
>>> Thanks
>>>
>>> Martin Perina
>>>
>>> On Wed, Jul 13, 2016 at 10:36 AM,  wrote:
>>>
>>> Hi,

 We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the
 engine cannot connect to hosts. In the logs all we see is this
 error:

 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
 Stomp Reactor) [] Unable to process messages

 I'm attaching full logs.

 Could someone help please?

 Thanks.
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users [1]

>>>
>>>
>>>
>>> Links:
>>> --
>>> [1] http://lists.ovirt.org/mailman/listinfo/users
>>>
>>
>> ___
>> 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] stuck host in hosted engine migration 3.6->4.0

Hi,

could you please create a bug and attach engine host logs (all from
/var/log/ovirt-engine) and VDSM logs (from /var/log/vdsm)?

Thanks

Martin Perina


On Wed, Jul 20, 2016 at 1:50 PM, Gervais de Montbrun  wrote:

> Hi Qiong,
>
> I am experiencing the exact same issue. All four of my hosts are throwing
> the same error to the vdsm.log If you find a solution, please let me know.
> I will do the same, of course.
>
> Cheers,
> Gervais
>
>
>
> On Jul 19, 2016, at 6:40 AM, qiong...@telekom.de wrote:
>
> Hi there, I have another issue with ovirt 4.0 after upgrading my hosted
> engine using the recommended method at
> http://www.ovirt.org/documenta…/migration-engine-3.6-to-4.0/
> 
>
> Everything works well, except for the fact that my hosted engine host is
> kind of broken in the engine. It doesnt show up and neither does the hosted
> engine storage domain. The hosted engine host from 3.6 is still there, but
> non responsive.
>
> VDSM.log on the hosted engine host gives me lots of errors:
>
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:56:12,236::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:56:13,468::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:56:13,860::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:56:20,767::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:56:20,944::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
> Reactor thread::ERROR::2016-07-19
> 09:56:23,666::m2cutils::301::ProtocolDetector.SSLHandshakeDispatcher::(handle_read)
> Error during handshake: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:56:25,532::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:56:29,936::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
> Reactor thread::ERROR::2016-07-19
> 09:56:35,640::m2cutils::301::ProtocolDetector.SSLHandshakeDispatcher::(handle_read)
> Error during handshake: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:56:48,277::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:56:49,459::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:56:49,991::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:56:56,862::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:56:57,049::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19
> 09:57:01,611::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
> reading data: (104, 'Connection reset by peer')
>
> Does anyone have an idea how to clean this up? Thanks a lot!
>
> Cheers & Thanks
>
> Qiong Wu
> ___
> 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
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Migration Failure Due to network

2016-07-20 Thread Alexis HAUSER

> Use "Clusters" -> "Logical Networks" -> "Manage Networks" for assigning
> network for migrations. It's ovirtmgmt by default. Note that migration
> network has to have IPs on hosts.

Nice, do you think I should dedicate a link only for migration, for safety ?


>Hosts have VDSM configuration option - [vars]/migration_max_bandwidth
>in /etc/vdsm/vdsm.conf. It's 52MB/s by default. So it looks like your
>network is already highly used.

It's not highly used, it's yet on a 10/100 Mb switch...But it's just temporary. 
Anyway it's interesting because it simulates a highly use network, which can 
happen.


>Your VM migration fails because migration is so slow so it just can't
>migrate without downtime. You can adjust "Use custom migration
>downtime" VM option to make any VM migrated over any network. Please
>note it's a maximal value. Actually it starts with a value 10 times
>lower and increases it automatically. 5000 is good value to start in
>your case.

Thanks, but it doesn't seem to change anything : I added 
max_outgoing_migrations = 1
migration_max_bandwidth = 5
in /etc/vdsm/vdsm.conf
on my concerned host, but it still goes to 98% use of network and migration 
fail...I restart vdsmd.service but it doesn't seem to change anything. Any idea 
?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Migration Failure Due to network

2016-07-20 Thread Michal Skrivanek


> On 20 Jul 2016, at 15:22, Alexis HAUSER  
> wrote:
> 
>> Use "Clusters" -> "Logical Networks" -> "Manage Networks" for assigning
>> network for migrations. It's ovirtmgmt by default. Note that migration
>> network has to have IPs on hosts.
> 
> Nice, do you think I should dedicate a link only for migration, for safety ?
> 
> 
>> Hosts have VDSM configuration option - [vars]/migration_max_bandwidth
>> in /etc/vdsm/vdsm.conf. It's 52MB/s by default. So it looks like your
>> network is already highly used.
> 
> It's not highly used, it's yet on a 10/100 Mb switch...But it's just 
> temporary. Anyway it's interesting because it simulates a highly use network, 
> which can happen.
> 
> 
>> Your VM migration fails because migration is so slow so it just can't
>> migrate without downtime. You can adjust "Use custom migration
>> downtime" VM option to make any VM migrated over any network. Please
>> note it's a maximal value. Actually it starts with a value 10 times
>> lower and increases it automatically. 5000 is good value to start in
>> your case.
> 
> Thanks, but it doesn't seem to change anything : I added 
> max_outgoing_migrations = 1
> migration_max_bandwidth = 5

well this is not going to make it any faster, quite the opposite:)
You need to play with the downtime setting (in UI or in vdsm.conf) to affect 
convergence in your constrained connectivity setup

There’s a lot more intelligence in oVirt 4.0 regarding this, so if it’s an 
option I would recommend to upgrade and change the migration policy to one of 
the new ones

Thanks,
michal

> in /etc/vdsm/vdsm.conf
> on my concerned host, but it still goes to 98% use of network and migration 
> fail...I restart vdsmd.service but it doesn't seem to change anything. Any 
> idea ?
> ___
> 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] stuck host in hosted engine migration 3.6->4.0

2016-07-20 Thread Qiong.Wu

I’m still stuck with the issue unfortunately.

 

I believe its due to the either host or engine not accepting changed SSL 
certificates during VDSM connection?

 

No idea how that could be fixed at the moment, but will keep you posted once I 
know something.

 

Cheers

Qiong

 

Von: Gervais de Montbrun [mailto:gerv...@demontbrun.com] 
Gesendet: Mittwoch, 20. Juli 2016 13:51
An: Wu, Qiong
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] stuck host in hosted engine migration 3.6->4.0

 

Hi Qiong,

 

I am experiencing the exact same issue. All four of my hosts are throwing the 
same error to the vdsm.log If you find a solution, please let me know. I will 
do the same, of course.


Cheers,
Gervais



 

On Jul 19, 2016, at 6:40 AM, qiong...@telekom.de wrote:

 

Hi there, I have another issue with ovirt 4.0 after upgrading my hosted engine 
using the recommended method at 
 
http://www.ovirt.org/documenta…/migration-engine-3.6-to-4.0/

Everything works well, except for the fact that my hosted engine host is kind 
of broken in the engine. It doesnt show up and neither does the hosted engine 
storage domain. The hosted engine host from 3.6 is still there, but non 
responsive.

VDSM.log on the hosted engine host gives me lots of errors:

JsonRpc (StompReactor)::ERROR::2016-07-19 
09:56:12,236::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')
JsonRpc (StompReactor)::ERROR::2016-07-19 
09:56:13,468::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')
JsonRpc (StompReactor)::ERROR::2016-07-19 
09:56:13,860::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')
JsonRpc (StompReactor)::ERROR::2016-07-19 
09:56:20,767::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')
JsonRpc (StompReactor)::ERROR::2016-07-19 
09:56:20,944::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')
Reactor thread::ERROR::2016-07-19 
09:56:23,666::m2cutils::301::ProtocolDetector.SSLHandshakeDispatcher::(handle_read)
 Error during handshake: unexpected eof
JsonRpc (StompReactor)::ERROR::2016-07-19 
09:56:25,532::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')
JsonRpc (StompReactor)::ERROR::2016-07-19 
09:56:29,936::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')
Reactor thread::ERROR::2016-07-19 
09:56:35,640::m2cutils::301::ProtocolDetector.SSLHandshakeDispatcher::(handle_read)
 Error during handshake: unexpected eof
JsonRpc (StompReactor)::ERROR::2016-07-19 
09:56:48,277::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')
JsonRpc (StompReactor)::ERROR::2016-07-19 
09:56:49,459::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')
JsonRpc (StompReactor)::ERROR::2016-07-19 
09:56:49,991::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')
JsonRpc (StompReactor)::ERROR::2016-07-19 
09:56:56,862::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')
JsonRpc (StompReactor)::ERROR::2016-07-19 
09:56:57,049::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')
JsonRpc (StompReactor)::ERROR::2016-07-19 
09:57:01,611::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
reading data: (104, 'Connection reset by peer')

Does anyone have an idea how to clean this up? Thanks a lot!

 

Cheers & Thanks

Qiong Wu

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

 



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] stuck host in hosted engine migration 3.6->4.0

2016-07-20 Thread Gervais de Montbrun

Hi Qiong,

I am experiencing the exact same issue. All four of my hosts are throwing the 
same error to the vdsm.log If you find a solution, please let me know. I will 
do the same, of course.

Cheers,
Gervais



> On Jul 19, 2016, at 6:40 AM, qiong...@telekom.de wrote:
> 
> Hi there, I have another issue with ovirt 4.0 after upgrading my hosted 
> engine using the recommended method 
> athttp://www.ovirt.org/documenta…/migration-engine-3.6-to-4.0/ 
> 
> Everything works well, except for the fact that my hosted engine host is kind 
> of broken in the engine. It doesnt show up and neither does the hosted engine 
> storage domain. The hosted engine host from 3.6 is still there, but non 
> responsive.
> 
> VDSM.log on the hosted engine host gives me lots of errors:
> 
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:56:12,236::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:56:13,468::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:56:13,860::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:56:20,767::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:56:20,944::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> Reactor thread::ERROR::2016-07-19 
> 09:56:23,666::m2cutils::301::ProtocolDetector.SSLHandshakeDispatcher::(handle_read)
>  Error during handshake: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:56:25,532::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:56:29,936::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> Reactor thread::ERROR::2016-07-19 
> 09:56:35,640::m2cutils::301::ProtocolDetector.SSLHandshakeDispatcher::(handle_read)
>  Error during handshake: unexpected eof
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:56:48,277::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:56:49,459::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:56:49,991::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:56:56,862::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:56:57,049::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> JsonRpc (StompReactor)::ERROR::2016-07-19 
> 09:57:01,611::betterAsyncore::113::vds.dispatcher::(recv) SSL error during 
> reading data: (104, 'Connection reset by peer')
> 
> Does anyone have an idea how to clean this up? Thanks a lot!
> 
> 
> Cheers & Thanks
> 
> Qiong Wu
> 
> ___
> 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] Cannot install new host on 4.0, Certificate enrollment failed

Yes, I thought the same, good to have it cleared out!

Thanks a lot, I like to know how it's running :)

2016-07-20 13:26 GMT+02:00 Juan Hernández :
> On 07/20/2016 01:21 PM, Matt . wrote:
>> Hi,
>>
>> Thanks a lot, it's good to know about this.
>>
>> There is no way to shorten the commonname ? or wil it aways used the
>> hostname there, as it's cn I doubt if we can use something else there.
>>
>> Thanks!
>>
>> Matt
>>
>
> I think it can't be shortened, as most TLS/SSL clients check that the
> host name matches exactly the common name inside the certificate, and
> this check would fail if you shorten it.
>
>>
>>
>> 2016-07-20 13:07 GMT+02:00 Juan Hernández :
>>> On 07/20/2016 12:30 PM, Matt . wrote:
 Hi,

 I found out yesterday late I was looking in the certs folder for the
 serial, this was the issue all files are there.

 I need to test a shorter fqdn, which is a pity, but I wonder why it
 should be too long for a cert create.

>>>
>>> Looks like it is a limitation of the X.509 specification:
>>>
>>>   ub-common-name INTEGER ::= 64
>>>   ...
>>>   520CommonName ::= CHOICE {
>>>   teletexString TeletexString   (SIZE (1..ub-common-name)),
>>>   printableString   PrintableString (SIZE (1..ub-common-name)),
>>>   universalString   UniversalString (SIZE (1..ub-common-name)),
>>>   utf8StringUTF8String  (SIZE (1..ub-common-name)),
>>>   bmpString BMPString   (SIZE (1..ub-common-name)) }
>>>
>>> The source is RFC 5280:
>>>
>>>   http://www.ietf.org/rfc/rfc5280.txt
>>>
>>> Maybe we should check these limits during the setup.
>>>


 2016-07-20 10:14 GMT+02:00 Juan Hernández :
> On 07/19/2016 07:59 PM, Matt . wrote:
>> Hi,
>>
>> Thanks for the heads up, I saw this in some thread too and this file
>> was available here with the upcoming number.
>>
>> Which rightsdo the file has?
>>
>> I don't have a ca.pem in that cert folder anymore can that be an issue?
>>
>
> In theory the ca.pem isn't needed to sign certificates, but the fact
> that it isn't in that directory probably means that something has been
> incorrectly manipulated, either manually or by the system itself. These
> are the files/permissions from a working environment:
>
> lrwxrwxrwx. 1 root  root28 Jul  8 11:34 apache-ca.pem ->
> /etc/pki/ovirt-engine/ca.pem
> -rw-r--r--. 1 root  root   384 Jul  8 11:34 cacert.conf
> -rw-r--r--. 1 root  root   384 Jul  8 11:34 cacert.template
> -rw-r--r--. 1 root  root   384 Jul 18 20:46 cacert.template.in
> -rw-r--r--. 1 root  root  4587 Jul  8 11:34 ca.pem
> -rw-r--r--. 1 root  root   923 Jul  8 11:34 cert.conf
> drwxr-xr-x. 2 ovirt ovirt 4096 Jul 18 20:46 certs
> -rw-r--r--. 1 root  root   923 Jul  8 11:34 cert.template
> -rw-r--r--. 1 root  root   717 Jul 18 20:46 cert.template.in
> -rw-r--r--. 1 ovirt ovirt  667 Jul  8 11:42 database.txt
> -rw-r--r--. 1 ovirt ovirt   20 Jul  8 11:42 database.txt.attr
> -rw-r--r--. 1 ovirt ovirt   20 Jul  8 11:42 database.txt.attr.old
> -rw-r--r--. 1 ovirt ovirt  599 Jul  8 11:42 database.txt.old
> drwxr-xr-x. 2 root  root  4096 Jul 18 20:46 keys
> -rw-r--r--. 1 root  root   548 Jul 18 20:46 openssl.conf
> drwxr-x---. 2 ovirt ovirt   19 Jul 18 20:46 private
> drwxr-xr-x. 2 ovirt ovirt 4096 Jul 18 20:46 requests
> -rw-r--r--. 1 ovirt ovirt5 Jul  8 11:42 serial.txt
> -rw-r--r--. 1 ovirt ovirt5 Jul  8 11:42 serial.txt.old
>
>>
>>
>> 2016-07-19 19:08 GMT+02:00 Juan Hernández :
>>> On 07/19/2016 06:16 PM, Matt . wrote:
 Can anyone confirm what max. number of subdomains can be used for a
 certificate ?

 The length of 65 per subdomain should be default.

 2016-07-19 15:06 GMT+02:00 Matt . :
> It's the fqdn indeed, not it's hostname.
>
> Fqdn should be possible I thought as discussed before in the channel
> (while ago).
>
> 2016-07-19 15:04 GMT+02:00 Yaniv Kaul :
>>
>> On Tue, Jul 19, 2016 at 3:43 PM, Matt .  
>> wrote:
>>>
>>>
>>> kvm-01.hosts.services-01.clusters.mycluster-01.dc.ovirt.subdomain.dc-01.dc.my.network
>>
>>
>> Is this the name of the host? perhaps it's a bit too long?
>> Y.
>>>
>>> Not sure if this is relevant, but I had the same problem today, and the
>>> cause was that the /etc/pki/ovirt-engine/serial.txt file was empty, and
>>> openssl refused to open it. I wrote manually a number inside, taking the
>>> value from /etc/pki/ovirt-engine/serial.txt.old (plus one), and then
>>> things started to work.
>>>
>>> --
>>> Dirección Comercial: C/Jose Bardasano

Re: [ovirt-users] Cannot install new host on 4.0, Certificate enrollment failed

2016-07-20 Thread Juan Hernández

On 07/20/2016 01:21 PM, Matt . wrote:
> Hi,
> 
> Thanks a lot, it's good to know about this.
> 
> There is no way to shorten the commonname ? or wil it aways used the
> hostname there, as it's cn I doubt if we can use something else there.
> 
> Thanks!
> 
> Matt
> 

I think it can't be shortened, as most TLS/SSL clients check that the
host name matches exactly the common name inside the certificate, and
this check would fail if you shorten it.

> 
> 
> 2016-07-20 13:07 GMT+02:00 Juan Hernández :
>> On 07/20/2016 12:30 PM, Matt . wrote:
>>> Hi,
>>>
>>> I found out yesterday late I was looking in the certs folder for the
>>> serial, this was the issue all files are there.
>>>
>>> I need to test a shorter fqdn, which is a pity, but I wonder why it
>>> should be too long for a cert create.
>>>
>>
>> Looks like it is a limitation of the X.509 specification:
>>
>>   ub-common-name INTEGER ::= 64
>>   ...
>>   520CommonName ::= CHOICE {
>>   teletexString TeletexString   (SIZE (1..ub-common-name)),
>>   printableString   PrintableString (SIZE (1..ub-common-name)),
>>   universalString   UniversalString (SIZE (1..ub-common-name)),
>>   utf8StringUTF8String  (SIZE (1..ub-common-name)),
>>   bmpString BMPString   (SIZE (1..ub-common-name)) }
>>
>> The source is RFC 5280:
>>
>>   http://www.ietf.org/rfc/rfc5280.txt
>>
>> Maybe we should check these limits during the setup.
>>
>>>
>>>
>>> 2016-07-20 10:14 GMT+02:00 Juan Hernández :
 On 07/19/2016 07:59 PM, Matt . wrote:
> Hi,
>
> Thanks for the heads up, I saw this in some thread too and this file
> was available here with the upcoming number.
>
> Which rightsdo the file has?
>
> I don't have a ca.pem in that cert folder anymore can that be an issue?
>

 In theory the ca.pem isn't needed to sign certificates, but the fact
 that it isn't in that directory probably means that something has been
 incorrectly manipulated, either manually or by the system itself. These
 are the files/permissions from a working environment:

 lrwxrwxrwx. 1 root  root28 Jul  8 11:34 apache-ca.pem ->
 /etc/pki/ovirt-engine/ca.pem
 -rw-r--r--. 1 root  root   384 Jul  8 11:34 cacert.conf
 -rw-r--r--. 1 root  root   384 Jul  8 11:34 cacert.template
 -rw-r--r--. 1 root  root   384 Jul 18 20:46 cacert.template.in
 -rw-r--r--. 1 root  root  4587 Jul  8 11:34 ca.pem
 -rw-r--r--. 1 root  root   923 Jul  8 11:34 cert.conf
 drwxr-xr-x. 2 ovirt ovirt 4096 Jul 18 20:46 certs
 -rw-r--r--. 1 root  root   923 Jul  8 11:34 cert.template
 -rw-r--r--. 1 root  root   717 Jul 18 20:46 cert.template.in
 -rw-r--r--. 1 ovirt ovirt  667 Jul  8 11:42 database.txt
 -rw-r--r--. 1 ovirt ovirt   20 Jul  8 11:42 database.txt.attr
 -rw-r--r--. 1 ovirt ovirt   20 Jul  8 11:42 database.txt.attr.old
 -rw-r--r--. 1 ovirt ovirt  599 Jul  8 11:42 database.txt.old
 drwxr-xr-x. 2 root  root  4096 Jul 18 20:46 keys
 -rw-r--r--. 1 root  root   548 Jul 18 20:46 openssl.conf
 drwxr-x---. 2 ovirt ovirt   19 Jul 18 20:46 private
 drwxr-xr-x. 2 ovirt ovirt 4096 Jul 18 20:46 requests
 -rw-r--r--. 1 ovirt ovirt5 Jul  8 11:42 serial.txt
 -rw-r--r--. 1 ovirt ovirt5 Jul  8 11:42 serial.txt.old

>
>
> 2016-07-19 19:08 GMT+02:00 Juan Hernández :
>> On 07/19/2016 06:16 PM, Matt . wrote:
>>> Can anyone confirm what max. number of subdomains can be used for a
>>> certificate ?
>>>
>>> The length of 65 per subdomain should be default.
>>>
>>> 2016-07-19 15:06 GMT+02:00 Matt . :
 It's the fqdn indeed, not it's hostname.

 Fqdn should be possible I thought as discussed before in the channel
 (while ago).

 2016-07-19 15:04 GMT+02:00 Yaniv Kaul :
>
> On Tue, Jul 19, 2016 at 3:43 PM, Matt .  
> wrote:
>>
>>
>> kvm-01.hosts.services-01.clusters.mycluster-01.dc.ovirt.subdomain.dc-01.dc.my.network
>
>
> Is this the name of the host? perhaps it's a bit too long?
> Y.
>>
>> Not sure if this is relevant, but I had the same problem today, and the
>> cause was that the /etc/pki/ovirt-engine/serial.txt file was empty, and
>> openssl refused to open it. I wrote manually a number inside, taking the
>> value from /etc/pki/ovirt-engine/serial.txt.old (plus one), and then
>> things started to work.
>>
>> --
>> Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
>> 3ºD, 28016 Madrid, Spain
>> Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.


 --
 Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
 3ºD, 28016 Madrid, Spain
 Inscrita en el Reg.

Re: [ovirt-users] Cannot install new host on 4.0, Certificate enrollment failed

Hi,

Thanks a lot, it's good to know about this.

There is no way to shorten the commonname ? or wil it aways used the
hostname there, as it's cn I doubt if we can use something else there.

Thanks!

Matt



2016-07-20 13:07 GMT+02:00 Juan Hernández :
> On 07/20/2016 12:30 PM, Matt . wrote:
>> Hi,
>>
>> I found out yesterday late I was looking in the certs folder for the
>> serial, this was the issue all files are there.
>>
>> I need to test a shorter fqdn, which is a pity, but I wonder why it
>> should be too long for a cert create.
>>
>
> Looks like it is a limitation of the X.509 specification:
>
>   ub-common-name INTEGER ::= 64
>   ...
>   520CommonName ::= CHOICE {
>   teletexString TeletexString   (SIZE (1..ub-common-name)),
>   printableString   PrintableString (SIZE (1..ub-common-name)),
>   universalString   UniversalString (SIZE (1..ub-common-name)),
>   utf8StringUTF8String  (SIZE (1..ub-common-name)),
>   bmpString BMPString   (SIZE (1..ub-common-name)) }
>
> The source is RFC 5280:
>
>   http://www.ietf.org/rfc/rfc5280.txt
>
> Maybe we should check these limits during the setup.
>
>>
>>
>> 2016-07-20 10:14 GMT+02:00 Juan Hernández :
>>> On 07/19/2016 07:59 PM, Matt . wrote:
 Hi,

 Thanks for the heads up, I saw this in some thread too and this file
 was available here with the upcoming number.

 Which rightsdo the file has?

 I don't have a ca.pem in that cert folder anymore can that be an issue?

>>>
>>> In theory the ca.pem isn't needed to sign certificates, but the fact
>>> that it isn't in that directory probably means that something has been
>>> incorrectly manipulated, either manually or by the system itself. These
>>> are the files/permissions from a working environment:
>>>
>>> lrwxrwxrwx. 1 root  root28 Jul  8 11:34 apache-ca.pem ->
>>> /etc/pki/ovirt-engine/ca.pem
>>> -rw-r--r--. 1 root  root   384 Jul  8 11:34 cacert.conf
>>> -rw-r--r--. 1 root  root   384 Jul  8 11:34 cacert.template
>>> -rw-r--r--. 1 root  root   384 Jul 18 20:46 cacert.template.in
>>> -rw-r--r--. 1 root  root  4587 Jul  8 11:34 ca.pem
>>> -rw-r--r--. 1 root  root   923 Jul  8 11:34 cert.conf
>>> drwxr-xr-x. 2 ovirt ovirt 4096 Jul 18 20:46 certs
>>> -rw-r--r--. 1 root  root   923 Jul  8 11:34 cert.template
>>> -rw-r--r--. 1 root  root   717 Jul 18 20:46 cert.template.in
>>> -rw-r--r--. 1 ovirt ovirt  667 Jul  8 11:42 database.txt
>>> -rw-r--r--. 1 ovirt ovirt   20 Jul  8 11:42 database.txt.attr
>>> -rw-r--r--. 1 ovirt ovirt   20 Jul  8 11:42 database.txt.attr.old
>>> -rw-r--r--. 1 ovirt ovirt  599 Jul  8 11:42 database.txt.old
>>> drwxr-xr-x. 2 root  root  4096 Jul 18 20:46 keys
>>> -rw-r--r--. 1 root  root   548 Jul 18 20:46 openssl.conf
>>> drwxr-x---. 2 ovirt ovirt   19 Jul 18 20:46 private
>>> drwxr-xr-x. 2 ovirt ovirt 4096 Jul 18 20:46 requests
>>> -rw-r--r--. 1 ovirt ovirt5 Jul  8 11:42 serial.txt
>>> -rw-r--r--. 1 ovirt ovirt5 Jul  8 11:42 serial.txt.old
>>>


 2016-07-19 19:08 GMT+02:00 Juan Hernández :
> On 07/19/2016 06:16 PM, Matt . wrote:
>> Can anyone confirm what max. number of subdomains can be used for a
>> certificate ?
>>
>> The length of 65 per subdomain should be default.
>>
>> 2016-07-19 15:06 GMT+02:00 Matt . :
>>> It's the fqdn indeed, not it's hostname.
>>>
>>> Fqdn should be possible I thought as discussed before in the channel
>>> (while ago).
>>>
>>> 2016-07-19 15:04 GMT+02:00 Yaniv Kaul :

 On Tue, Jul 19, 2016 at 3:43 PM, Matt .  wrote:
>
>
> kvm-01.hosts.services-01.clusters.mycluster-01.dc.ovirt.subdomain.dc-01.dc.my.network


 Is this the name of the host? perhaps it's a bit too long?
 Y.
>
> Not sure if this is relevant, but I had the same problem today, and the
> cause was that the /etc/pki/ovirt-engine/serial.txt file was empty, and
> openssl refused to open it. I wrote manually a number inside, taking the
> value from /etc/pki/ovirt-engine/serial.txt.old (plus one), and then
> things started to work.
>
> --
> Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
> 3ºD, 28016 Madrid, Spain
> Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
>>>
>>>
>>> --
>>> Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
>>> 3ºD, 28016 Madrid, Spain
>>> Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
> --
> Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
> 3ºD, 28016 Madrid, Spain
> Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 -

[ovirt-users] one export domain two DC

Is it possible to export all of my vms on my oVirt 3.5 Domain and than
attach my export domain on my oVirt 4.0 DC and import the vm's?

Regards,

-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Cannot install new host on 4.0, Certificate enrollment failed