date:20160719

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?



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.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Question about for oVirt AAA LDAP plugin - configuration file format

2016-07-19 Thread Николаев Алексей

Как насчётhttps://github.com/oVirt/ovirt-engine-extension-aaa-ldap/blob/master/README В частности есть примеры в директории хоста с engine /usr/share/ovirt-engine-extension-aaa-ldap/examples 19.07.2016, 18:40, "Vadim Reutsky" :Good afternoon! First of all, thank you for writing very useful software, which we are applying in our studio project at Innopolis University. It makes our lives much easier. I have one little question about oVirt AAA LDAP plugin. Can you provide structure of configuration file, which can be used by 'ovirt-engine-extension-aaa-ldap-setup' tool by passing '--config=filename' parameter? (Or, please, give me a clue, when I can find this information). Thank you in advance! Respectfully yours,Vadim Reutskiy.E-mail: v.reut...@innopolis.ruSkype: vadim.reutskiyPhone: +7 (927) 289-48-19,___Users mailing listUsers@ovirt.orghttp://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

2016-07-19 Thread 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.
___
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

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.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Migration Failure Due to network

Here are the two Events I can see :
Host Hypervisor has network interface which exceeded the defined threshold 
[95%] (em1: transmit rate[98%], receive rate [4%])
Migration failed  (VM: Clone-ubuntu, Source: Hypervisor, Destination: 
hypervisor22).

Any ideas ?

It it not the first time I have this kind of network saturation issue...
My current temporary setup is this : 2 hosts with only one network physical 
interface used and assigned to ovirtmgmt, used by all VM.
Do migration of a running VM from one host to the other use the network 
assigned to that VM for migration ? Or does it use ovirtmgmt in all cases ?

What minimum network architecture setup would you advice me to avoid this kind 
of issues ?

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

[ovirt-users] Question about for oVirt AAA LDAP plugin - configuration file format

2016-07-19 Thread Vadim Reutsky

Good afternoon!

First of all, thank you for writing very useful software, which we are applying 
in our studio project at Innopolis University. It makes our lives much easier.

I have one little question about oVirt AAA LDAP plugin. Can you provide 
structure of configuration file, which can be used by 
'ovirt-engine-extension-aaa-ldap-setup' tool by passing '--config=filename' 
parameter? (Or, please, give me a clue, when I can find this information).

Thank you in advance!



Respectfully yours,
Vadim Reutskiy.
E-mail: v.reut...@innopolis.ru
Skype: vadim.reutskiy
Phone: +7 (927) 289-48-19
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [RFE][4.1][F24] Fedora 24 support

2016-07-19 Thread Sandro Bonazzola

Hi,
as you know Fedora 24 has been released last month.
I pushed a pull request[1] describing the feature support effort.
Of the detailied description, the following items have been already
implemented:

   - Support building on Fedora 24
   - Create Jenkins jobs for automated build and testing on Fedora 24
   - Create Fedora 24 Jenkins slaves


the following item is still to be done:

   - Verify that all the components have no regressions only due to Fedora
   24

How you can help:

   - Review / comment the pull request for the feature [1]
   - Test oVirt master nightly[2] on Fedora 24
   - Open bugs on issue you see while running master on Fedora 24
   - Verify test cases[4] on Fedora 24

Please use [F24] in the subject if you provide feedback on the mailing
list, it will help tracking discussions related to this feature.

[1] https://github.com/oVirt/ovirt-site/pull/368
[2] http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/
[3] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[4] http://www.ovirt.org/develop/infra/testing/test-cases/

-- 
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] Host non operationnal due to an iSCSI problem


>Normally you should not have to do that. It could be that it was not 
>allowed access, and you'd have to leave it a while for the host to retry.

It looped on retrying to make it work for 24 hours...It was authorized. But 
actually when I first add the host, it didn't have authorization. I added 
authorization, then it looped on retrying without success...Until I did what I 
told you.

>At least you have it working now!

Yes thank you, but I'm a bit disappointed by this instability and I'd really 
like to understand what happened...In case it reproduce again. 


>
>
>
>> If you only have one physical interface on each host, there's not much
>> point doing multipath, as you don't stand to gain any performance or
>> resilience.
> I didn't choose if it was multipath or not, someone only gave me access to 
> this storage, but I understand what you mean. However, I'll certainly add 
> bonding later.
>
>
> Do you have any idea what setting maintenance mode and reactivating does on a 
> host ? Does it restart some services ? I don't really understand what just 
> happened actually...
> All I know is that it is used for backup, reinstall and update.

Maintenance mode will migrate any running VMs off that host and enable 
you to do some tasks (including the ones you mention) that you can't do 
when it's running VMs. I believe it stops certain services as well, not 
sure which ones. It's perfectly safe and routine thing to do in RHEV/oVirt.

Thanks, that's certainly what solved the issue then...Or the Dell Bay doing 
weird random stuff who knows ^^ 
I've often heard people telling others setting up a host or engine to 
maintenance mode then reactivate in case of a lot of various issues, it seems 
to be a method to keep in mind.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Host non operationnal due to an iSCSI problem




On 19/07/16 15:22, Alexis HAUSER wrote:

I'm still finding this hard to understand. If you are using iSCSI, you
/are/ using a server (called the "Target" in SCSI speak). Is the iSCSI
storage actually on the first host?

It's a Dell bay (or "storage array", I think that's the correct name in 
english...)


If it offers iSCSI, it is indeed a "Target". It's effectively a server 
as it's offering up a service on the network! That does explain my 
confusion though...





How did you actually do the
discovery and assign the LUNs? In the storage domain properties you
should be able to see the IP and port of the Targets, something like
"iqn.2012-02:foo-target1,192.168.10.10,3260", and you need to ensure the
second host can reach that IP and port to be able to see the storage.

Actually I jutt made a test : authorize access only to the second host (on the 
Dell bay), it works but only after setting it to maintenance mode and 
reactivate it.
Then authorizing both of the hosts (as initially) make them both working 
now...It doesn't really makes sense...
It is a very strange behavior. Maybe the second host needed to be set in 
maintenance mode then reactivated ?


Normally you should not have to do that. It could be that it was not 
allowed access, and you'd have to leave it a while for the host to retry.


At least you have it working now!






If you only have one physical interface on each host, there's not much
point doing multipath, as you don't stand to gain any performance or
resilience.

I didn't choose if it was multipath or not, someone only gave me access to this 
storage, but I understand what you mean. However, I'll certainly add bonding 
later.


Do you have any idea what setting maintenance mode and reactivating does on a 
host ? Does it restart some services ? I don't really understand what just 
happened actually...
All I know is that it is used for backup, reinstall and update.


Maintenance mode will migrate any running VMs off that host and enable 
you to do some tasks (including the ones you mention) that you can't do 
when it's running VMs. I believe it stops certain services as well, not 
sure which ones. It's perfectly safe and routine thing to do in RHEV/oVirt.


Cheers

Alex


--
This message is intended only for the addressee and may contain
confidential information. Unless you are that person, you may not
disclose its contents or use it in any way and are requested to delete
the message along with any attachments and notify us immediately.
This email is not intended to, nor should it be taken to, constitute advice.
The information provided is correct to our knowledge & belief and must not
be used as a substitute for obtaining tax, regulatory, investment, legal or
any other appropriate advice.

"Transact" is operated by Integrated Financial Arrangements Ltd.
29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300.
(Registered office: as above; Registered in England and Wales under
number: 3727592). Authorised and regulated by the Financial Conduct
Authority (entered on the Financial Services Register; no. 190856).
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Host non operationnal due to an iSCSI problem

>I'm still finding this hard to understand. If you are using iSCSI, you 
>/are/ using a server (called the "Target" in SCSI speak). Is the iSCSI 
>storage actually on the first host?

It's a Dell bay (or "storage array", I think that's the correct name in 
english...)

> How did you actually do the 
>discovery and assign the LUNs? In the storage domain properties you 
>should be able to see the IP and port of the Targets, something like 
>"iqn.2012-02:foo-target1,192.168.10.10,3260", and you need to ensure the 
>second host can reach that IP and port to be able to see the storage.

Actually I jutt made a test : authorize access only to the second host (on the 
Dell bay), it works but only after setting it to maintenance mode and 
reactivate it.
Then authorizing both of the hosts (as initially) make them both working 
now...It doesn't really makes sense...
It is a very strange behavior. Maybe the second host needed to be set in 
maintenance mode then reactivated ? 



>If you only have one physical interface on each host, there's not much 
>point doing multipath, as you don't stand to gain any performance or 
>resilience.

I didn't choose if it was multipath or not, someone only gave me access to this 
storage, but I understand what you mean. However, I'll certainly add bonding 
later.


Do you have any idea what setting maintenance mode and reactivating does on a 
host ? Does it restart some services ? I don't really understand what just 
happened actually...
All I know is that it is used for backup, reinstall and update.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

2016-07-19 Thread Fernando Fuentes

Nir,

Thanks for all the help!
I am on it and will reply with the requested info asap.

Regards,

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

On Tue, Jul 19, 2016, at 07:16 AM, Nir Soffer wrote:
> On Mon, Jul 18, 2016 at 11:16 PM, Fernando Fuentes 
> wrote:
> > Ops... forgot the link:
> >
> > http://pastebin.com/LereJgyw
> >
> > The requested infor is in the pastebin.
> 
> So the issue is clear now, the template on NFS is using raw format, and
> on block
> stoage, qcow format:
> 
> NFS:
> 
> root@zeta ~]# cat
> /rhev/data-center/mnt/172.30.10.5\:_opt_libvirtd_images/ecfaf7ac-5459-4c83-bd97-2bb448e38526/images/3b7d9349-9eb1-42f8-9e04-7bbb97c02b98/25b6b0fe-d416-458f-b89f-
> ...
> FORMAT=RAW
> ...
> 
> [root@alpha ~]# qemu-img info
> /opt/libvirtd/images/ecfaf7ac-5459-4c83-bd97-2bb448e38526/images/3b7d9349-9eb1-42f8-9e04-7bbb97c02b98/25b6b0fe-d416-458f-b89f-363338ee0c0e
> image:
> /opt/libvirtd/images/ecfaf7ac-5459-4c83-bd97-2bb448e38526/images/3b7d9349-9eb1-42f8-9e04-7bbb97c02b98/25b6b0fe-d416-458f-b89f-363338ee0c0e
> ...
> file format: raw
> ...
> 
> iSCSI:
> 
> [root@zeta ~]# qemu-img info
> /dev/0ef17024-0eae-4590-8eea-6ec8494fe223/25b6b0fe-d416-458f-b89f-363338ee0c0e
> image:
> /dev/0ef17024-0eae-4590-8eea-6ec8494fe223/25b6b0fe-d416-458f-b89f-363338ee0c0e
> ...
> file format: qcow2
> ...
> 
> [root@zeta ~]# dd
> if=/dev/0ef17024-0eae-4590-8eea-6ec8494fe223/metadata bs=512 skip=4
> count=1 iflag=direct
> ...
> FORMAT=COW
> ...
> 
> This format conversion is expected, as we don't support raw/sparse on
> block storage.
> 
> It looks like the vm is started with the template disk as "raw"
> format, which is expected
> to fail when the format is actually "qcow2". The guest will see the
> qcow headers instead
> of the actual data.
> 
> The next step to debug this is:
> 
> 1. Copy a disk using this template to the block storage domain
> 2. Create a new vm using this disk
> 3. Start the vm
> 
> Does it start? if not, attach engine and vdsm logs from this timefame.
> 
> If this works, you can try:
> 
> 1. Move vm disk from NFS to block storage
> 2. Start the vm
> 
> Again, it it does not work, add engine and vdsm logs.
> 
> Nir
> 
> >
> > Regards,
> >
> >
> > --
> > Fernando Fuentes
> > ffuen...@txweather.org
> > http://www.txweather.org
> >
> >
> >
> > On Mon, Jul 18, 2016, at 03:16 PM, Fernando Fuentes wrote:
> >
> > Nir,
> >
> > After some playing around with pvscan I was able to get all of the need it
> > information.
> >
> > Please see:
> >
> >
> > --
> > Fernando Fuentes
> > ffuen...@txweather.org
> > http://www.txweather.org
> >
> >
> >
> > On Mon, Jul 18, 2016, at 02:30 PM, Nir Soffer wrote:
> >
> > On Mon, Jul 18, 2016 at 6:48 PM, Fernando Fuentes 
> > wrote:
> >> Nir,
> >>
> >> As requested:
> >>
> >> [root@gamma ~]# lsblk
> >> NAME  MAJ:MIN RM
> >>   SIZE RO TYPE  MOUNTPOINT
> >> sda 8:00
> >>   557G  0 disk
> >> ├─sda1  8:10
> >>   500M  0 part  /boot
> >> └─sda2  8:20
> >> 556.5G  0 part
> >>   ├─vg_gamma-lv_root (dm-0)   253:00
> >>  50G  0 lvm   /
> >>   ├─vg_gamma-lv_swap (dm-1)   253:10
> >>   4G  0 lvm   [SWAP]
> >>   └─vg_gamma-lv_home (dm-2)   253:20
> >>   502.4G  0 lvm   /home
> >> sr011:01
> >>  1024M  0 rom
> >> sdb 8:16   0
> >> 2T  0 disk
> >> └─36589cfc00881b9b93c2623780840 (dm-4)253:40
> >> 2T  0 mpath
> >> sdc 8:32   0
> >> 2T  0 disk
> >> └─36589cfc0050564002c7e51978316 (dm-3)253:30
> >> 2T  0 mpath
> >>   ├─3ccb7b67--8067--4315--9656--d68ba10975ba-metadata (dm-5)  253:50
> >> 512M  0 lvm
> >>   ├─3ccb7b67--8067--4315--9656--d68ba10975ba-outbox (dm-6)253:60
> >> 128M  0 lvm
> >>   ├─3ccb7b67--8067--4315--9656--d68ba10975ba-leases (dm-7)253:70
> >>   2G  0 lvm
> >>   ├─3ccb7b67--8067--4315--9656--d68ba10975ba-ids (dm-8)   253:80
> >> 128M  0 lvm
> >>   ├─3ccb7b67--8067--4315--9656--d68ba10975ba-inbox (dm-9) 253:90
> >> 128M  0 lvm
> >>   └─3ccb7b67--8067--4315--9656--d68ba10975ba-master (dm-10)   253:10   0
> >>   1G  0 lvm
> >> sdd 8:48   0
> >> 4T  0 disk
> >> └─36589cfc0059ccab70662b71c47ef (dm-11)   253:11   0
> >> 4T  0 mpath
> >>   ├─4861322b--352f--41c6--890a--5cbf1c2c1f01-metadata (dm-12) 253:12   0
> >> 512M  0 lvm
> >>

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

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.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

I'm trying to install a new host with quite a long fqdn. I didn't had
issues earlier but installs seem to fail now.

Is this due to the fqdn or just a bug because of it ?


2016-07-19 14:25:35,297 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [1bf7c79c] Correlation ID: 1bf7c79c, Call Stack: null,
Custom Event ID: -1, Message: Installing Host
kvm-01.hosts.services-01.clusters.mycluster-01.dc.ovirt.subdomain.dc-01.dc.my.network.
Enrolling certificate.
2016-07-19 14:25:35,384 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler4) [34afefd0] Fetched 0 VMs from VDS
'11fe3c2e-1cc9-42e2-bca3-83eb12373b0b'
2016-07-19 14:25:35,766 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler7) [] Fetched 1 VMs from VDS
'a01e6b4a-63ee-45a8-9973-49bc781c2426'
2016-07-19 14:25:35,846 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler10) [] Fetched 2 VMs from VDS
'a033da48-ff15-4ca5-a4fb-86116df4be72'
2016-07-19 14:25:36,143 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler2) [60c10eb0] Fetched 1 VMs from VDS
'b9842e0b-5bc5-4315-b066-4b07ab6e19d9'
2016-07-19 14:25:36,304 ERROR
[org.ovirt.engine.core.utils.hostinstall.OpenSslCAWrapper] (VdsDeploy)
[1bf7c79c] Sign Certificate request failed with exit code 1
2016-07-19 14:25:36,304 ERROR
[org.ovirt.engine.core.utils.hostinstall.OpenSslCAWrapper] (VdsDeploy)
[1bf7c79c] Sign Certificate request script errors:
Using configuration from openssl.conf
Check that the request matches the signature
Signature ok
139681740007328:error:0D07A097:asn1 encoding
routines:ASN1_mbstring_ncopy:string too long:a_mbstr.c:154:maxsize=64
Cannot sign certificate

2016-07-19 14:25:36,304 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy)
[1bf7c79c] Error during deploy dialog: java.lang.RuntimeException:
Certificate enrollment failed
at 
org.ovirt.engine.core.utils.hostinstall.OpenSslCAWrapper.signCertificateRequest(OpenSslCAWrapper.java:61)
[utils.jar:]
at 
org.ovirt.engine.core.bll.hostdeploy.VdsDeployPKIUnit.processEvent(VdsDeployPKIUnit.java:71)
[bll.jar:]
at 
org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.processEvent(VdsDeployBase.java:660)
[bll.jar:]
at 
org.ovirt.engine.core.bll.hostdeploy.VdsDeploy.processEvent(VdsDeploy.java:35)
[bll.jar:]
at 
org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.threadMain(VdsDeployBase.java:319)
[bll.jar:]
at 
org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.lambda$new$0(VdsDeployBase.java:383)
[bll.jar:]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]

2016-07-19 14:25:36,309 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase]
(org.ovirt.thread.pool-8-thread-20) [1bf7c79c] Error during host
kvm-01.hosts.services-01.clusters.mycluster-01.dc.ovirt.subdomain.dc-01.dc.my.network
install: java.lang.RuntimeException: Certificate enrollment failed
at 
org.ovirt.engine.core.utils.hostinstall.OpenSslCAWrapper.signCertificateRequest(OpenSslCAWrapper.java:61)
[utils.jar:]
at 
org.ovirt.engine.core.bll.hostdeploy.VdsDeployPKIUnit.processEvent(VdsDeployPKIUnit.java:71)
[bll.jar:]
at 
org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.processEvent(VdsDeployBase.java:660)
[bll.jar:]
at 
org.ovirt.engine.core.bll.hostdeploy.VdsDeploy.processEvent(VdsDeploy.java:35)
[bll.jar:]
at 
org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.threadMain(VdsDeployBase.java:319)
[bll.jar:]
at 
org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.lambda$new$0(VdsDeployBase.java:383)
[bll.jar:]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]

2016-07-19 14:25:36,321 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(org.ovirt.thread.pool-8-thread-20) [1bf7c79c] Correlation ID:
1bf7c79c, Call Stack: null, Custom Event ID: -1, Message: Failed to
install Host 
kvm-01.hosts.services-01.clusters.mycluster-01.dc.ovirt.subdomain.dc-01.dc.my.network.
Certificate enrollment failed.
2016-07-19 14:25:36,322 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase]
(org.ovirt.thread.pool-8-thread-20) [1bf7c79c] Error during host
kvm-01.hosts.services-01.clusters.mycluster-01.dc.ovirt.subdomain.dc-01.dc.my.network
install, prefering first exception: Certificate enrollment failed

Thanks!

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

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

2016-07-19 Thread Logan Kuhn

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

Re: [ovirt-users] disk not bootable

2016-07-19 Thread Nir Soffer

On Mon, Jul 18, 2016 at 11:16 PM, Fernando Fuentes  wrote:
> Ops... forgot the link:
>
> http://pastebin.com/LereJgyw
>
> The requested infor is in the pastebin.

So the issue is clear now, the template on NFS is using raw format, and on block
stoage, qcow format:

NFS:

root@zeta ~]# cat
/rhev/data-center/mnt/172.30.10.5\:_opt_libvirtd_images/ecfaf7ac-5459-4c83-bd97-2bb448e38526/images/3b7d9349-9eb1-42f8-9e04-7bbb97c02b98/25b6b0fe-d416-458f-b89f-
...
FORMAT=RAW
...

[root@alpha ~]# qemu-img info
/opt/libvirtd/images/ecfaf7ac-5459-4c83-bd97-2bb448e38526/images/3b7d9349-9eb1-42f8-9e04-7bbb97c02b98/25b6b0fe-d416-458f-b89f-363338ee0c0e
image: 
/opt/libvirtd/images/ecfaf7ac-5459-4c83-bd97-2bb448e38526/images/3b7d9349-9eb1-42f8-9e04-7bbb97c02b98/25b6b0fe-d416-458f-b89f-363338ee0c0e
...
file format: raw
...

iSCSI:

[root@zeta ~]# qemu-img info
/dev/0ef17024-0eae-4590-8eea-6ec8494fe223/25b6b0fe-d416-458f-b89f-363338ee0c0e
image: 
/dev/0ef17024-0eae-4590-8eea-6ec8494fe223/25b6b0fe-d416-458f-b89f-363338ee0c0e
...
file format: qcow2
...

[root@zeta ~]# dd
if=/dev/0ef17024-0eae-4590-8eea-6ec8494fe223/metadata bs=512 skip=4
count=1 iflag=direct
...
FORMAT=COW
...

This format conversion is expected, as we don't support raw/sparse on
block storage.

It looks like the vm is started with the template disk as "raw"
format, which is expected
to fail when the format is actually "qcow2". The guest will see the
qcow headers instead
of the actual data.

The next step to debug this is:

1. Copy a disk using this template to the block storage domain
2. Create a new vm using this disk
3. Start the vm

Does it start? if not, attach engine and vdsm logs from this timefame.

If this works, you can try:

1. Move vm disk from NFS to block storage
2. Start the vm

Again, it it does not work, add engine and vdsm logs.

Nir

>
> Regards,
>
>
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
>
>
>
> On Mon, Jul 18, 2016, at 03:16 PM, Fernando Fuentes wrote:
>
> Nir,
>
> After some playing around with pvscan I was able to get all of the need it
> information.
>
> Please see:
>
>
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
>
>
>
> On Mon, Jul 18, 2016, at 02:30 PM, Nir Soffer wrote:
>
> On Mon, Jul 18, 2016 at 6:48 PM, Fernando Fuentes 
> wrote:
>> Nir,
>>
>> As requested:
>>
>> [root@gamma ~]# lsblk
>> NAME  MAJ:MIN RM
>>   SIZE RO TYPE  MOUNTPOINT
>> sda 8:00
>>   557G  0 disk
>> ├─sda1  8:10
>>   500M  0 part  /boot
>> └─sda2  8:20
>> 556.5G  0 part
>>   ├─vg_gamma-lv_root (dm-0)   253:00
>>  50G  0 lvm   /
>>   ├─vg_gamma-lv_swap (dm-1)   253:10
>>   4G  0 lvm   [SWAP]
>>   └─vg_gamma-lv_home (dm-2)   253:20
>>   502.4G  0 lvm   /home
>> sr011:01
>>  1024M  0 rom
>> sdb 8:16   0
>> 2T  0 disk
>> └─36589cfc00881b9b93c2623780840 (dm-4)253:40
>> 2T  0 mpath
>> sdc 8:32   0
>> 2T  0 disk
>> └─36589cfc0050564002c7e51978316 (dm-3)253:30
>> 2T  0 mpath
>>   ├─3ccb7b67--8067--4315--9656--d68ba10975ba-metadata (dm-5)  253:50
>> 512M  0 lvm
>>   ├─3ccb7b67--8067--4315--9656--d68ba10975ba-outbox (dm-6)253:60
>> 128M  0 lvm
>>   ├─3ccb7b67--8067--4315--9656--d68ba10975ba-leases (dm-7)253:70
>>   2G  0 lvm
>>   ├─3ccb7b67--8067--4315--9656--d68ba10975ba-ids (dm-8)   253:80
>> 128M  0 lvm
>>   ├─3ccb7b67--8067--4315--9656--d68ba10975ba-inbox (dm-9) 253:90
>> 128M  0 lvm
>>   └─3ccb7b67--8067--4315--9656--d68ba10975ba-master (dm-10)   253:10   0
>>   1G  0 lvm
>> sdd 8:48   0
>> 4T  0 disk
>> └─36589cfc0059ccab70662b71c47ef (dm-11)   253:11   0
>> 4T  0 mpath
>>   ├─4861322b--352f--41c6--890a--5cbf1c2c1f01-metadata (dm-12) 253:12   0
>> 512M  0 lvm
>>   ├─4861322b--352f--41c6--890a--5cbf1c2c1f01-ids (dm-13)  253:13   0
>> 128M  0 lvm
>>   ├─4861322b--352f--41c6--890a--5cbf1c2c1f01-leases (dm-14)   253:14   0
>>   2G  0 lvm
>>   ├─4861322b--352f--41c6--890a--5cbf1c2c1f01-outbox (dm-15)   253:15   0
>> 128M  0 lvm
>>   ├─4861322b--352f--41c6--890a--5cbf1c2c1f01-inbox (dm-16)253:16   0
>> 128M  0 lvm
>>   └─4861322b--352f--41c6--890a--5cbf1c2c1f01-master (dm-17)   253:17   0
>>   1G  0 lvm
>
> So you have 2 storage domains:
>
> - 3ccb7b67-8067-4315-9656-d68ba10975ba
> -

Re: [ovirt-users] Host non operationnal due to an iSCSI problem

On 19/07/16 11:13, Alexis HAUSER wrote:

I don't understand. iSCSI is a network storage protocol. What do you
mean by "I access it directly"? When you set up the first host with an
iSCSI storage domain, you would have had to point it to an IP address,
"discover" the LUNs and then attach to them. This sets up the domain.

As I explained, I don't use an iSCSI server, that's what I call accessing it
"directly".
Yes, my iSCSI storage is working on my first Host, it has been discovered
successfully, some VM are working on it etc...
The second host can discover it so I don't think it's a network issue.

From the vdsm logs from second host ("the non working one") it looks like it
can even see the LVM on it, right ?

Thread-32::DEBUG::2016-07-19 08:41:37,935::lvm::290::Storage.Misc.excCmd::(cmd) FAILED: =
' Volume group "091e0526-1ff3-4ca3-863c-b911cf69277b" not found\n Cannot process volume
group 091e0526-1ff3-4ca3-863c-b911cf69277b\n'; = 5

It knows there there are volume groups from the database. You are
correct, in that it cannot access the VGs/LVs.

On the second host, to access iSCSI storage you will have to have an
interface (defined in "Networks" in oVirt) that can connect to the same
IP and port the first host used.

Yes I have an network interface working on the second host, which is ovirtmgmt.
I can access all other storage correctly from that host without errors. I can
discover the iSCSI.

As it is a multipath iSCSI, does it need to acces one different path for each
host ? I didn't set anything about iSCSI bonding, I use only one single
interface on each host.

I'm still finding this hard to understand. If you are using iSCSI, you
/are/ using a server (called the "Target" in SCSI speak). Is the iSCSI
storage actually on the first host? How did you actually do the
discovery and assign the LUNs? In the storage domain properties you
should be able to see the IP and port of the Targets, something like
"iqn.2012-02:foo-target1,192.168.10.10,3260", and you need to ensure the
second host can reach that IP and port to be able to see the storage.

Multipath should not make any difference right now, but in order to use
it effectively you should probably set up an iSCSI bond. The requirement
for multipath to work properly is that the two physical interfaces on
the host and initiator are in different IP subnets (and should ideally
travel via different switches but that is not a hard requirement).

If you only have one physical interface on each host, there's not much
point doing multipath, as you don't stand to gain any performance or
resilience.

Cheers

Alex
--
This message is intended only for the addressee and may contain
confidential information. Unless you are that person, you may not
disclose its contents or use it in any way and are requested to delete
the message along with any attachments and notify us immediately.
This email is not intended to, nor should it be taken to, constitute advice.
The information provided is correct to our knowledge & belief and must not
be used as a substitute for obtaining tax, regulatory, investment, legal or
any other appropriate advice.

"Transact" is operated by Integrated Financial Arrangements Ltd.
29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300.
(Registered office: as above; Registered in England and Wales under
number: 3727592). Authorised and regulated by the Financial Conduct
Authority (entered on the Financial Services Register; no. 190856).
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Host non operationnal due to an iSCSI problem


> I don't understand. iSCSI is a network storage protocol. What do you 
> mean by "I access it directly"? When you set up the first host with an 
> iSCSI storage domain, you would have had to point it to an IP address, 
> "discover" the LUNs and then attach to them. This sets up the domain.

As I explained, I don't use an iSCSI server, that's what I call accessing it 
"directly".
Yes, my iSCSI storage is working on my first Host, it has been discovered 
successfully, some VM are working on it etc...
The second host can discover it so I don't think it's a network issue.

>From the vdsm logs from second host ("the non working one") it looks like it 
>can even see the LVM on it, right ? 

Thread-32::DEBUG::2016-07-19 08:41:37,935::lvm::290::Storage.Misc.excCmd::(cmd) 
FAILED:  = '  Volume group "091e0526-1ff3-4ca3-863c-b911cf69277b" not 
found\n  Cannot process volume group 091e0526-1ff3-4ca3-863c-b911cf69277b\n'; 
 = 5



> On the second host, to access iSCSI storage you will have to have an 
> interface (defined in "Networks" in oVirt) that can connect to the same 
> IP and port the first host used.

Yes I have an network interface working on the second host, which is ovirtmgmt. 
I can access all other storage correctly from that host without errors. I can 
discover the iSCSI.

As it is a multipath iSCSI, does it need to acces one different path for each 
host ? I didn't set anything about iSCSI bonding, I use only one single 
interface on each host.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

2016-07-19 Thread Qiong.Wu

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::(handl
e_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::(handl
e_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


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

Re: [ovirt-users] Host non operationnal due to an iSCSI problem




On 19/07/16 10:38, Alexis HAUSER wrote:



Sounds like a possible networking problem. Have you assigned IP
addresses to the storage interfaces on this new host?

hum, What do you mean by storage interfaces ? The other host on the same 
network can access it.


If you're using
VLANs, are they set up correctly on your switch ports for the SAN network?

Yes

I don't use a server to share the iSCSI storage to the hosts, (I access it 
directly). Do I need it ? I saw that in the RHEV doc, on first part of the 
iSCSI section...


I don't understand. iSCSI is a network storage protocol. What do you 
mean by "I access it directly"? When you set up the first host with an 
iSCSI storage domain, you would have had to point it to an IP address, 
"discover" the LUNs and then attach to them. This sets up the domain.


On the second host, to access iSCSI storage you will have to have an 
interface (defined in "Networks" in oVirt) that can connect to the same 
IP and port the first host used.


Alex
--
This message is intended only for the addressee and may contain
confidential information. Unless you are that person, you may not
disclose its contents or use it in any way and are requested to delete
the message along with any attachments and notify us immediately.
This email is not intended to, nor should it be taken to, constitute advice.
The information provided is correct to our knowledge & belief and must not
be used as a substitute for obtaining tax, regulatory, investment, legal or
any other appropriate advice.

"Transact" is operated by Integrated Financial Arrangements Ltd.
29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300.
(Registered office: as above; Registered in England and Wales under
number: 3727592). Authorised and regulated by the Financial Conduct
Authority (entered on the Financial Services Register; no. 190856).
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Host non operationnal due to an iSCSI problem



>Sounds like a possible networking problem. Have you assigned IP 
>addresses to the storage interfaces on this new host? 

hum, What do you mean by storage interfaces ? The other host on the same 
network can access it. 

> If you're using 
> VLANs, are they set up correctly on your switch ports for the SAN network?

Yes

I don't use a server to share the iSCSI storage to the hosts, (I access it 
directly). Do I need it ? I saw that in the RHEV doc, on first part of the 
iSCSI section...
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [DOC] Upgrade guide from 3.6 el6 to 4.0 el7

2016-07-19 Thread Sandro Bonazzola

Hi,
for those who missed it, a guide has been created to help migrating from
3.6 running on EL6 to 4.0 running on EL7 which also applies to 3.6 on FC22
to 4.0 on FC23.

You can find the guide here:
http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/

For hosted engine a guide is under review on GitHub here:
https://github.com/oVirt/ovirt-site/pull/296
pending to fix some issue with travis build.

If you're doing an upgrade with OS migration, feedback, suggestions and
improvements are welcome.

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

Re: [ovirt-users] Host non operationnal due to an iSCSI problem




On 19/07/16 09:52, Alexis HAUSER wrote:

Hi,


I just added a second host but it can't become operational, because it can't 
access to the iSCSI storage domain. My first question : is it normal or not, is 
RHEV really able to manage the fact an iSCSI LUN can be accessed from multiple 
hosts ?

Yes, each VM disk is a Logical Volume on that LUN.

Sounds like a possible networking problem. Have you assigned IP 
addresses to the storage interfaces on this new host? If you're using 
VLANs, are they set up correctly on your switch ports for the SAN network?


Alex


--
This message is intended only for the addressee and may contain
confidential information. Unless you are that person, you may not
disclose its contents or use it in any way and are requested to delete
the message along with any attachments and notify us immediately.
This email is not intended to, nor should it be taken to, constitute advice.
The information provided is correct to our knowledge & belief and must not
be used as a substitute for obtaining tax, regulatory, investment, legal or
any other appropriate advice.

"Transact" is operated by Integrated Financial Arrangements Ltd.
29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300.
(Registered office: as above; Registered in England and Wales under
number: 3727592). Authorised and regulated by the Financial Conduct
Authority (entered on the Financial Services Register; no. 190856).
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Host non operationnal due to an iSCSI problem