date:20161017

[ovirt-users] fakevdsm vs ovirt engine 4.0.4

2016-10-17 Thread joost


Hi All,
I am trying to start load tests against my newly installed ovirt engine 
version 4.0.4
I can run fakevdsm as follows (minor changes to pom.xml (mainly jetty 
plugin version)

i also changed vdsm-jsonrpc-java-client to match that of the server.

org.ovirt.vdsm-jsonrpc-java

vdsm-jsonrpc-java-client

1.2.5

i can run the app using

mvn jetty:run -Dfake.host=0.0.0.0 -DjsonListenPort=54321 
-DvdsmPort=54322



fakevdsm runs but keeps on looping over the following operations. I 
have not add vms yet.


I sincerely hope someone can help me , i really need to stress test 
this install urgently and fakevdsm looks like the perfect tool to use 
for this.

thanks, joost

2016-10-17 22:24:59,505 CONNECT
accept-version:1.2
heart-beat:0,21234
host:null


2016-10-17 22:24:59,506 CONNECT
accept-version:1.2
heart-beat:0,21234
host:null


2016-10-17 22:24:59,507 CONNECTED
heart-beat:21234,0
session:196ed7d6-5125-4608-8299-bcaef308db87


2016-10-17 22:24:59,507 Message sent: CONNECTED
heart-beat:21234,0
session:196ed7d6-5125-4608-8299-bcaef308db87


2016-10-17 22:24:59,636 SUBSCRIBE
destination:jms.topic.vdsm_responses
ack:auto
id:9c734bb3-2dc4-4181-a049-2b77133b521f

SEND
destination:jms.topic.vdsm_requests
reply-to:jms.topic.vdsm_responses
content-length:105

{"jsonrpc":"2.0","method":"Host.getCapabilities","params":{},"id":"9f78265b-21c3-4e77-9b11-7c126c2d84ed"}
2016-10-17 22:24:59,636 SUBSCRIBE
destination:jms.topic.vdsm_responses
ack:auto
id:9c734bb3-2dc4-4181-a049-2b77133b521f


2016-10-17 22:24:59,636 ACK
id:9c734bb3-2dc4-4181-a049-2b77133b521f


2016-10-17 22:24:59,636 Message sent: ACK
id:9c734bb3-2dc4-4181-a049-2b77133b521f


2016-10-17 22:24:59,636 SEND
destination:jms.topic.vdsm_requests
reply-to:jms.topic.vdsm_responses
content-length:105

{"jsonrpc":"2.0","method":"Host.getCapabilities","params":{},"id":"9f78265b-21c3-4e77-9b11-7c126c2d84ed"}
2016-10-17 22:24:59,637 client policy identifier null
2016-10-17 22:24:59,714 Request is Host.getCapabilities got response 
{"jsonrpc":"2.0","result":{"version_name":"Snow 
Man","operatingSystem":{"name":"Fedora","release":"1","version":"17"},"cpuSpeed":"1200.000","clusterLevels":["3.0","3.1","3.2","3.3","3.4","3.5","3.6","4.0","4.1"],"hooks":{},"ISCSIInitiatorName":"iqn.1994-05.com.example:ef52ec17bb0","cpuSockets":"1","kvmEnabled":"true","reservedMem":"321","lastClientIface":"ovirtmgmt","numaNodes":{"1":{"cpus":[0,2,4,6,8,10,12,14],"totalMemory":3988},"0":{"cpus":[1,3,5,7,9,11,13,15],"totalMemory":3988}},"cpuFlags":"fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ss,syscall,nx,pdpe1gb,rdtscp,lm,constant_tsc,rep_good,nopl,eagerfpu,pni,pclmulqdq,vmx,ssse3,fma,cx16,pcid,sse4_1,sse4_2,x2apic,movbe,popcnt,tsc_deadline_timer,aes,xsave,avx,f16c,rdrand,hypervisor,lahf_lm,abm,tpr_shadow,vnmi,flexpriority,ept,fsgsbase,bmi1,avx2,smep,bmi2,erms,invpcid,xsaveopt,model_Haswell-noTSX,model_Nehalem,model_Conroe,model_Penryn,model_Westmere,model_SandyBridge","HBAInventory":{"iSCSI":[{"InitiatorName":"iqn.1994-0

5.com.ex
ample:ef52ec17bb0"}],"FC":[]},"lastClient":"10.36.6.76","selinux":{"mode":"1"},"vlans":{},"software_version":"4.10","kdumpStatus":"1","emulatedMachines":["pc-0.10","pc-0.11","pc-0.12","pc-0.13","pc-0.14","pc-0.15","pc-1.0","pc-1.0","pc-i440fx-2.1","pseries-rhel7.2.0","pc-i440fx-rhel7.2.0","rhel6.4.0","rhel6.5.0","rhel6.6.0","rhel6.7.0","rhel6.8.0","rhel6.9.0","rhel7.0.0","rhel7.2.0","rhel7.5.0","pc","isapc"],"vmTypes":["kvm"],"software_revision":"0.141","bridges":{"ovirtmgmt":{"mtu":"1500","ports":["em1"],"gateway":"252.197.29.20","addr":"186.190.35.84","cfg":{"DELAY":"0","DEVICE":"ovirtmgmt","ONBOOT":"yes","BOOTPROTO":"dhcp","TYPE":"Ethernet"},"stp":"off","netmask":"255.255.252.0"}},"netConfigDirty":"False","autoNumaBalancing":"1","guestOverhead":"65","networks":{"ovirtmgmt":{"mtu":"1500","ports":["em1"],"iface":"ovirtmgmt","gateway":"10.34.63.254","bridged":true,"switch":"legacy","addr":"186.190.35.84","stp":"off","cfg":{"DELAY":"0","DEVICE":"ovirtmgmt","ONBOOT":"yes","BOOT
PROTO":"
dhcp","TYPE":"Ethernet"},"netmask":"255.255.252.0"}},"memSize":"7976","rngSources":["RANDOM"],"management_ip":"","supportedENGINEs":["3.0","3.1","3.2","3.3","3.4","3.5","3.6","4.0","4.1"],"cpuModel":"Intel(R) 
Xeon(R) CPU E5606 @

Re: [ovirt-users] Can't restart hosted-engine installation: vdsm did not start

2016-10-17 Thread gregor

Because the server has to be finished and shipped to my customer I
decided to reinstall the whole operating-system.
This is a very bad solution but after 20 hours of try-and-error I have
to find any solution.

Thanks for your help.

cheers
gregor

On 17/10/16 10:36, gregor wrote:
> Hi,
> 
> sadly this did not help.
> 
> cheers
> gregor
> 
> On 17/10/16 09:54, Simone Tiraboschi wrote:
>>
>>
>> On Sun, Oct 16, 2016 at 10:47 PM, gregor > > wrote:
>>
>> How can I completely remove all the problematic VDSM remains to get a
>> clean system again without wiping the whole machine?
>>
>>
>> You can try following this:
>> https://www.ovirt.org/documentation/how-to/hosted-engine/#recoving-from-failed-install
>>
>>  
>>
>> chees
>> gregor
>>
>> On 16/10/16 20:58, gregor wrote:
>> > Hi,
>> >
>> > after a failed hosted-engine installation I removed all the ovirt and
>> > vdsm packages, rebooted the system and started from scratch.
>> > But when I run "hosted-engine --deploy" it stuck's during starting
>> vdsm.
>> >
>> > The logfile /var/log/vdsm/supervdsm.log gives me the following
>> >
>> > ...
>> > MainThread::DEBUG::2016-10-16
>> > 20:54:42,065::storage_log::69::blivet::(log_exception_info) IGNORED:
>> >Caught exception, continuing.
>> > MainThread::DEBUG::2016-10-16
>> > 20:54:42,065::storage_log::72::blivet::(log_exception_info) IGNORED:
>> >Problem description: failed to get initiator name from iscsi
>> firmware
>> > MainThread::DEBUG::2016-10-16
>> > 20:54:42,065::storage_log::73::blivet::(log_exception_info) IGNORED:
>> >Begin exception details.
>> > MainThread::DEBUG::2016-10-16
>> > 20:54:42,066::storage_log::76::blivet::(log_exception_info) IGNORED:
>> >Traceback (most recent call last):
>> > MainThread::DEBUG::2016-10-16
>> > 20:54:42,066::storage_log::76::blivet::(log_exception_info) IGNORED:
>> >  File "/usr/lib/python2.7/site-packages/blivet/iscsi.py", line
>> > 142, in __init__
>> > MainThread::DEBUG::2016-10-16
>> > 20:54:42,066::storage_log::76::blivet::(log_exception_info) IGNORED:
>> >initiatorname = libiscsi.get_firmware_initiator_name()
>> > MainThread::DEBUG::2016-10-16
>> > 20:54:42,066::storage_log::76::blivet::(log_exception_info) IGNORED:
>> >IOError: Unknown error
>> > MainThread::DEBUG::2016-10-16
>> > 20:54:42,066::storage_log::77::blivet::(log_exception_info) IGNORED:
>> >End exception details.
>> > ...
>> >
>> > Can anybody help? I found a old are close again like so many other bug
>> > reports with "CLOSED CURRENTRELEASE":
>> > https://bugzilla.redhat.com/show_bug.cgi?id=1238239
>> 
>> >
>> > cheers
>> > gregor
>> > ___
>> > 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
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Problem with backing-file, how to fix the backing-chain ?

2016-10-17 Thread Adam Litke



Have you tried a qemu-img 'unsafe' rebase?

Let's say you have the chain:
   base <- middle <- top

and due to the old backing chain links we have

base parent: None
middle parent: ../uuid/../uuid/../uuid/base
top parent: ../uuid/../uuid/middle

Since the volumes are always stored in the same directory, the
repeated ../uuid/ parts of the path are unnecessary and can always be
replaced with just the last part.  Once making the LVs available on
the system you should be able to fix the paths with the following
commands:

qemu-img rebase -u -b base middle
qemu-img rebase -u -b middle top

You can then verify the whole backing chain by: 


qemu-img info --backing-chain top

Let me know if this helps.


On 17/10/16 10:34 +0200, Dael Maselli wrote:

Hi all,

We run an ovirt environment before with engine v3.6.5 (if remember good)
and now with v4.0.4 (we upgraded because we read the bug with
backing-file was resolved with v4).

We upgraded some of the hosts machines (but not all still) at v4.0.4 too
to see if this would fix the problem, but nothing.

The problem is that we have several VMs with snapshots, we do daily,
weekly and monthly snapshots, keep some of them (usually the fresh ones)
and remove the olds (that in the case they are weekly snapshots, they
are in the middle of a series of snapshots), this in the time has
produced the famous

Backing file too long bug.

So we upgraded the engine from 3.6.5 to 4.0.4 (latest available).

We discovered this bug, when we tried to upgrade an host to v4.0.4,
doing so a VM in the host didn't migrate, so we shutdown it and tried to
run on another host, but never succeded for the bug.

We don't know if we have more VMs in this situation because we upgraded
only 2 hosts on 10.

Investigating the problem we discovered that the backing file indicated
in each of LVM snapshots report a path very long with
/dev/storage-domain-id/../image-group-id/ with ../image-group-id/
repeated a lot of times and at the end /parentid.

So to understand which was the right path that it would contain, we
cloned a VM in the v4.0.4 and then we did 4 snapshots, now the backing
file path is

/dev/storage-domain-id/parentid

Is there a way to modify the path in the backing-file or a way to
recover the VM from this state ?

Where do reside the informations about the backing-file path ?

I attach here all the commands we run

On the ovirt manager (host with the engine only) we run

ovirt-shell

[oVirt shell (connected)]# list disks --parent-vm-name vm1

id : 2df25a13-6958-40a8-832f-9a26ce65de0f
name   : vm1_Disk2

id : 8cda0aa6-9e25-4b50-ba00-b877232a1983
name   : vm1_Disk1

[oVirt shell (connected)]# show disk 8cda0aa6-9e25-4b50-ba00-b877232a1983

id   : 8cda0aa6-9e25-4b50-ba00-b877232a1983
name : vm1_Disk1
actual_size  : 1073741824
alias: vm1_Disk1
disk_profile-id  : 1731f79a-5034-4270-9a87-94d93025deac
format   : cow
image_id : 7b354e2a-2099-4f2a-80b7-fba7d1fd13ee
propagate_errors : False
provisioned_size : 17179869184
shareable: False
size : 17179869184
sparse   : True
status-state : ok
storage_domains-storage_domain-id: 384f9059-ef2f-4d43-a54f-de71c5d589c8
storage_type : image
wipe_after_delete: False

[root@ovc1mgr ~]# su - postgres
Last login: Fri Oct 14 01:02:14 CEST 2016
-bash-4.2$ psql -d engine -U postgres
psql (9.2.15)
Type "help" for help.

engine=#\x on
engine=# select * from images where image_group_id =
'8cda0aa6-9e25-4b50-ba00-b877232a1983' order by creation_date;

-[ RECORD 1 ]-+-
image_guid| 60ba7acf-58cb-475b-b9ee-15b1be99fee6
creation_date | 2016-03-29 15:12:34+02
size  | 17179869184
it_guid   | ----
parentid  | ----
imagestatus   | 4
lastmodified  | 2016-04-21 11:25:59.972+02
vm_snapshot_id| 27c187cd-989f-4f7a-ac05-49c4410de6c2
volume_type   | 1
volume_format | 5
image_group_id| 8cda0aa6-9e25-4b50-ba00-b877232a1983
_create_date  | 2016-03-29 15:12:31.994065+02
_update_date  | 2016-09-04 01:10:08.773649+02
active| f
volume_classification | 1

-[ RECORD 2 ]-+-
image_guid| 68d764ec-bc2e-4e1d-b8f2-b44afd9fcb2e
creation_date | 2016-07-03 01:01:30+02
size  | 17179869184
it_guid   | ----
parentid  | 60ba7acf-58cb-475b-b9ee-15b1be99fee6
imagestatus   | 1
lastmodified  | 2016-07-04 01:03:33.732+02
vm_snapshot_id|

[ovirt-users] ovirt list's smtp on blacklist?

2016-10-17 Thread Jiří Sléžka


Hello,

it looks like mailserver which serving users@ovirt.org is on blacklist.

line from our smtp server log...

Oct 17 15:31:25 hermes postfix/smtpd[14082]: NOQUEUE: reject: RCPT from 
lists.ovirt.org[2600:3c01::f03c:91ff:fe93:4b0d]: 554 5.7.1 Service 
unavailable; Client host [2600:3c01::f03c:91ff:fe93:4b0d] blocked using 
sbl.spamhaus.org; https://www.spamhaus.org/sbl/query/SBLCSS; 
from= to= proto=ESMTP 
helo=



Cheers,
Jiri



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

Re: [ovirt-users] Unable to get HE up after update

2016-10-17 Thread Susinthiran Sithamparanathan

Now after a long time i got the prompt to login.
What i see is that things are still down and unable to activate anything. I
see
[image: Inline image 1]
This host is in non responding state. Try to Activate it; If the problem
persists, switch Host to Maintenance mode and try to reinstall it.


On Mon, Oct 17, 2016 at 4:51 PM, Susinthiran Sithamparanathan <
chesu...@gmail.com> wrote:

> Thanks.Savior at https://www.mail-archive.com/u
> s...@ovirt.org/msg33874.html.
> When i logged into the web UI, i couldn't bring up storage, datacenter,
> cluster, everything was down.
> I restarted the host and now when i enter admin portal, it spins for ever.
> Seems to be some SSL communciation issues: https://paste.fedoraproject.
> org/453944/76715737/
> Any hints are appreciated!
>
>
>
> On Mon, Oct 17, 2016 at 4:15 PM, Simone Tiraboschi 
> wrote:
>
>>
>>
>> On Mon, Oct 17, 2016 at 3:48 PM, Susinthiran Sithamparanathan <
>> chesu...@gmail.com> wrote:
>>
>>> Got the engine up finally :)
>>> But now met with The client is not authorized to request an
>>> authorization. It's required to access the system using FQDN. It worked
>>> fine prior to upgrade!
>>>
>>
>> This is a new feature of 4.0; you cannot login anymore with the IP
>> address if the cert has been signed for an fqdn.
>>
>>
>>> Found https://bugzilla.redhat.com/show_bug.cgi?id=1351217, but not sure
>>> if i have FQDN case issues.
>>> Any idea how to fix this?
>>>
>>> On Mon, Oct 17, 2016 at 3:33 PM, Susinthiran Sithamparanathan <
>>> chesu...@gmail.com> wrote:
>>>
 Analyzed the log to find out that the problem was in the creation of
 the certs with openssl (missing distinguished name in config). And
 /etc/pki/ovirt-engine/{cacert,openssl}.conf were empty!
 That lead me to:
 yum provides  /etc/pki/ovirt-engine/{cacert,openssl}.conf
 yum remove  ovirt-engine-backend
 yum install ovirt-engine-backend ovirt-engine  ovirt-engine-dashboard
 ovirt-engine-setup ovirt-engine-tools  ovirt-engine-userportal
 ovirt-engine-webadmin-portal  ovirt-engine-restapi  ovirt-engine-dashboard

 Now i was able to successfully run engine-setup and exit maintenance
 mode on the host. Let's see how things unfold within a 30 min. Will keep
 you updated!









 On Mon, Oct 17, 2016 at 3:14 PM, Susinthiran Sithamparanathan <
 chesu...@gmail.com> wrote:

> Hi,
> i tried that and ended up with : https://paste.fedoraproject.or
> g/453892/71003314/  :(
> Log ovirt-engine-setup-20161017150800-drmayj.log uploaded to
> https://my.owndrive.com/index.php/s/3Dcyho9bqo7oZs8?path=%2Fengine-vm
>
>
>
> On Mon, Oct 17, 2016 at 11:54 AM, Simone Tiraboschi <
> stira...@redhat.com> wrote:
>
>>
>>
>> On Mon, Oct 17, 2016 at 9:55 AM, Susinthiran Sithamparanathan <
>> chesu...@gmail.com> wrote:
>>
>>> Hi guys,
>>> let me know if there anything else you need for further debugging
>>> purpose.
>>> Thanks!
>>>
>>
>> Can you please try reinstalling all the oVirt rpms on the engine VM
>> and re-executing engine-setup there?
>>
>>
>>>
>>> On Thu, Oct 13, 2016 at 7:53 PM, Susinthiran Sithamparanathan <
>>> chesu...@gmail.com> wrote:
>>>
 On Thu, Oct 13, 2016 at 3:23 PM, Yedidyah Bar David <
 d...@redhat.com> wrote:

>
> OK. Can you please attach the output of:
>
> grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>

  [root@ovirt01 ~]# grep MANUAL /etc/ovirt-engine/engine.conf.
 d/*.conf
 [root@ovirt01 ~]# ssh 192.168.0.101
 root@192.168.0.101's password:
 Last login: Thu Oct 13 19:50:02 2016 from ovirt01
 [root@engine ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
 [root@engine ~]#

 I.e nothing found by grep for that search on the host and the
 engine-vm.


 --

 Susinthiran Sithamparanathan

>>>
>>>
>>>
>>> --
>>>
>>> Susinthiran Sithamparanathan
>>>
>>
>>
>
>
> --
>
> Susinthiran Sithamparanathan
>



 --

 Susinthiran Sithamparanathan

>>>
>>>
>>>
>>> --
>>>
>>> Susinthiran Sithamparanathan
>>>
>>
>>
>
>
> --
>
> Susinthiran Sithamparanathan
>



-- 

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

Re: [ovirt-users] Unable to get HE up after update

2016-10-17 Thread Susinthiran Sithamparanathan

Thanks.Savior at https://www.mail-archive.com/users@ovirt.org/msg33874.html.
When i logged into the web UI, i couldn't bring up storage, datacenter,
cluster, everything was down.
I restarted the host and now when i enter admin portal, it spins for ever.
Seems to be some SSL communciation issues:
https://paste.fedoraproject.org/453944/76715737/
Any hints are appreciated!



On Mon, Oct 17, 2016 at 4:15 PM, Simone Tiraboschi 
wrote:

>
>
> On Mon, Oct 17, 2016 at 3:48 PM, Susinthiran Sithamparanathan <
> chesu...@gmail.com> wrote:
>
>> Got the engine up finally :)
>> But now met with The client is not authorized to request an
>> authorization. It's required to access the system using FQDN. It worked
>> fine prior to upgrade!
>>
>
> This is a new feature of 4.0; you cannot login anymore with the IP address
> if the cert has been signed for an fqdn.
>
>
>> Found https://bugzilla.redhat.com/show_bug.cgi?id=1351217, but not sure
>> if i have FQDN case issues.
>> Any idea how to fix this?
>>
>> On Mon, Oct 17, 2016 at 3:33 PM, Susinthiran Sithamparanathan <
>> chesu...@gmail.com> wrote:
>>
>>> Analyzed the log to find out that the problem was in the creation of the
>>> certs with openssl (missing distinguished name in config). And
>>> /etc/pki/ovirt-engine/{cacert,openssl}.conf were empty!
>>> That lead me to:
>>> yum provides  /etc/pki/ovirt-engine/{cacert,openssl}.conf
>>> yum remove  ovirt-engine-backend
>>> yum install ovirt-engine-backend ovirt-engine  ovirt-engine-dashboard
>>> ovirt-engine-setup ovirt-engine-tools  ovirt-engine-userportal
>>> ovirt-engine-webadmin-portal  ovirt-engine-restapi  ovirt-engine-dashboard
>>>
>>> Now i was able to successfully run engine-setup and exit maintenance
>>> mode on the host. Let's see how things unfold within a 30 min. Will keep
>>> you updated!
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Oct 17, 2016 at 3:14 PM, Susinthiran Sithamparanathan <
>>> chesu...@gmail.com> wrote:
>>>
 Hi,
 i tried that and ended up with : https://paste.fedoraproject.or
 g/453892/71003314/  :(
 Log ovirt-engine-setup-20161017150800-drmayj.log uploaded to
 https://my.owndrive.com/index.php/s/3Dcyho9bqo7oZs8?path=%2Fengine-vm



 On Mon, Oct 17, 2016 at 11:54 AM, Simone Tiraboschi <
 stira...@redhat.com> wrote:

>
>
> On Mon, Oct 17, 2016 at 9:55 AM, Susinthiran Sithamparanathan <
> chesu...@gmail.com> wrote:
>
>> Hi guys,
>> let me know if there anything else you need for further debugging
>> purpose.
>> Thanks!
>>
>
> Can you please try reinstalling all the oVirt rpms on the engine VM
> and re-executing engine-setup there?
>
>
>>
>> On Thu, Oct 13, 2016 at 7:53 PM, Susinthiran Sithamparanathan <
>> chesu...@gmail.com> wrote:
>>
>>> On Thu, Oct 13, 2016 at 3:23 PM, Yedidyah Bar David >> > wrote:
>>>

 OK. Can you please attach the output of:

 grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf

>>>
>>>  [root@ovirt01 ~]# grep MANUAL /etc/ovirt-engine/engine.conf.
>>> d/*.conf
>>> [root@ovirt01 ~]# ssh 192.168.0.101
>>> root@192.168.0.101's password:
>>> Last login: Thu Oct 13 19:50:02 2016 from ovirt01
>>> [root@engine ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>>> [root@engine ~]#
>>>
>>> I.e nothing found by grep for that search on the host and the
>>> engine-vm.
>>>
>>>
>>> --
>>>
>>> Susinthiran Sithamparanathan
>>>
>>
>>
>>
>> --
>>
>> Susinthiran Sithamparanathan
>>
>
>


 --

 Susinthiran Sithamparanathan

>>>
>>>
>>>
>>> --
>>>
>>> Susinthiran Sithamparanathan
>>>
>>
>>
>>
>> --
>>
>> Susinthiran Sithamparanathan
>>
>
>


-- 

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

Re: [ovirt-users] Unable to get HE up after update

2016-10-17 Thread Simone Tiraboschi

On Mon, Oct 17, 2016 at 3:48 PM, Susinthiran Sithamparanathan <
chesu...@gmail.com> wrote:

> Got the engine up finally :)
> But now met with The client is not authorized to request an authorization.
> It's required to access the system using FQDN. It worked fine prior to
> upgrade!
>

This is a new feature of 4.0; you cannot login anymore with the IP address
if the cert has been signed for an fqdn.


> Found https://bugzilla.redhat.com/show_bug.cgi?id=1351217, but not sure
> if i have FQDN case issues.
> Any idea how to fix this?
>
> On Mon, Oct 17, 2016 at 3:33 PM, Susinthiran Sithamparanathan <
> chesu...@gmail.com> wrote:
>
>> Analyzed the log to find out that the problem was in the creation of the
>> certs with openssl (missing distinguished name in config). And
>> /etc/pki/ovirt-engine/{cacert,openssl}.conf were empty!
>> That lead me to:
>> yum provides  /etc/pki/ovirt-engine/{cacert,openssl}.conf
>> yum remove  ovirt-engine-backend
>> yum install ovirt-engine-backend ovirt-engine  ovirt-engine-dashboard
>> ovirt-engine-setup ovirt-engine-tools  ovirt-engine-userportal
>> ovirt-engine-webadmin-portal  ovirt-engine-restapi  ovirt-engine-dashboard
>>
>> Now i was able to successfully run engine-setup and exit maintenance mode
>> on the host. Let's see how things unfold within a 30 min. Will keep you
>> updated!
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Oct 17, 2016 at 3:14 PM, Susinthiran Sithamparanathan <
>> chesu...@gmail.com> wrote:
>>
>>> Hi,
>>> i tried that and ended up with : https://paste.fedoraproject.or
>>> g/453892/71003314/  :(
>>> Log ovirt-engine-setup-20161017150800-drmayj.log uploaded to
>>> https://my.owndrive.com/index.php/s/3Dcyho9bqo7oZs8?path=%2Fengine-vm
>>>
>>>
>>>
>>> On Mon, Oct 17, 2016 at 11:54 AM, Simone Tiraboschi >> > wrote:
>>>


 On Mon, Oct 17, 2016 at 9:55 AM, Susinthiran Sithamparanathan <
 chesu...@gmail.com> wrote:

> Hi guys,
> let me know if there anything else you need for further debugging
> purpose.
> Thanks!
>

 Can you please try reinstalling all the oVirt rpms on the engine VM and
 re-executing engine-setup there?


>
> On Thu, Oct 13, 2016 at 7:53 PM, Susinthiran Sithamparanathan <
> chesu...@gmail.com> wrote:
>
>> On Thu, Oct 13, 2016 at 3:23 PM, Yedidyah Bar David 
>> wrote:
>>
>>>
>>> OK. Can you please attach the output of:
>>>
>>> grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>>>
>>
>>  [root@ovirt01 ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>> [root@ovirt01 ~]# ssh 192.168.0.101
>> root@192.168.0.101's password:
>> Last login: Thu Oct 13 19:50:02 2016 from ovirt01
>> [root@engine ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>> [root@engine ~]#
>>
>> I.e nothing found by grep for that search on the host and the
>> engine-vm.
>>
>>
>> --
>>
>> Susinthiran Sithamparanathan
>>
>
>
>
> --
>
> Susinthiran Sithamparanathan
>


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

Re: [ovirt-users] Unable to get HE up after update

2016-10-17 Thread Susinthiran Sithamparanathan

Got the engine up finally :)
But now met with The client is not authorized to request an authorization.
It's required to access the system using FQDN. It worked fine prior to
upgrade!
Found https://bugzilla.redhat.com/show_bug.cgi?id=1351217, but not sure if
i have FQDN case issues.
Any idea how to fix this?

On Mon, Oct 17, 2016 at 3:33 PM, Susinthiran Sithamparanathan <
chesu...@gmail.com> wrote:

> Analyzed the log to find out that the problem was in the creation of the
> certs with openssl (missing distinguished name in config). And
> /etc/pki/ovirt-engine/{cacert,openssl}.conf were empty!
> That lead me to:
> yum provides  /etc/pki/ovirt-engine/{cacert,openssl}.conf
> yum remove  ovirt-engine-backend
> yum install ovirt-engine-backend ovirt-engine  ovirt-engine-dashboard
> ovirt-engine-setup ovirt-engine-tools  ovirt-engine-userportal
> ovirt-engine-webadmin-portal  ovirt-engine-restapi  ovirt-engine-dashboard
>
> Now i was able to successfully run engine-setup and exit maintenance mode
> on the host. Let's see how things unfold within a 30 min. Will keep you
> updated!
>
>
>
>
>
>
>
>
>
> On Mon, Oct 17, 2016 at 3:14 PM, Susinthiran Sithamparanathan <
> chesu...@gmail.com> wrote:
>
>> Hi,
>> i tried that and ended up with : https://paste.fedoraproject.or
>> g/453892/71003314/  :(
>> Log ovirt-engine-setup-20161017150800-drmayj.log uploaded to
>> https://my.owndrive.com/index.php/s/3Dcyho9bqo7oZs8?path=%2Fengine-vm
>>
>>
>>
>> On Mon, Oct 17, 2016 at 11:54 AM, Simone Tiraboschi 
>> wrote:
>>
>>>
>>>
>>> On Mon, Oct 17, 2016 at 9:55 AM, Susinthiran Sithamparanathan <
>>> chesu...@gmail.com> wrote:
>>>
 Hi guys,
 let me know if there anything else you need for further debugging
 purpose.
 Thanks!

>>>
>>> Can you please try reinstalling all the oVirt rpms on the engine VM and
>>> re-executing engine-setup there?
>>>
>>>

 On Thu, Oct 13, 2016 at 7:53 PM, Susinthiran Sithamparanathan <
 chesu...@gmail.com> wrote:

> On Thu, Oct 13, 2016 at 3:23 PM, Yedidyah Bar David 
> wrote:
>
>>
>> OK. Can you please attach the output of:
>>
>> grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>>
>
>  [root@ovirt01 ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
> [root@ovirt01 ~]# ssh 192.168.0.101
> root@192.168.0.101's password:
> Last login: Thu Oct 13 19:50:02 2016 from ovirt01
> [root@engine ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
> [root@engine ~]#
>
> I.e nothing found by grep for that search on the host and the
> engine-vm.
>
>
> --
>
> Susinthiran Sithamparanathan
>



 --

 Susinthiran Sithamparanathan

>>>
>>>
>>
>>
>> --
>>
>> Susinthiran Sithamparanathan
>>
>
>
>
> --
>
> Susinthiran Sithamparanathan
>



-- 

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

Re: [ovirt-users] Unable to get HE up after update

2016-10-17 Thread Susinthiran Sithamparanathan

Analyzed the log to find out that the problem was in the creation of the
certs with openssl (missing distinguished name in config). And
/etc/pki/ovirt-engine/{cacert,openssl}.conf were empty!
That lead me to:
yum provides  /etc/pki/ovirt-engine/{cacert,openssl}.conf
yum remove  ovirt-engine-backend
yum install ovirt-engine-backend ovirt-engine  ovirt-engine-dashboard
ovirt-engine-setup ovirt-engine-tools  ovirt-engine-userportal
ovirt-engine-webadmin-portal  ovirt-engine-restapi  ovirt-engine-dashboard

Now i was able to successfully run engine-setup and exit maintenance mode
on the host. Let's see how things unfold within a 30 min. Will keep you
updated!

On Mon, Oct 17, 2016 at 3:14 PM, Susinthiran Sithamparanathan <
chesu...@gmail.com> wrote:

> Hi,
> i tried that and ended up with : https://paste.fedoraproject.
> org/453892/71003314/  :(
> Log ovirt-engine-setup-20161017150800-drmayj.log uploaded to
> https://my.owndrive.com/index.php/s/3Dcyho9bqo7oZs8?path=%2Fengine-vm
>
>
>
> On Mon, Oct 17, 2016 at 11:54 AM, Simone Tiraboschi 
> wrote:
>
>>
>>
>> On Mon, Oct 17, 2016 at 9:55 AM, Susinthiran Sithamparanathan <
>> chesu...@gmail.com> wrote:
>>
>>> Hi guys,
>>> let me know if there anything else you need for further debugging
>>> purpose.
>>> Thanks!
>>>
>>
>> Can you please try reinstalling all the oVirt rpms on the engine VM and
>> re-executing engine-setup there?
>>
>>
>>>
>>> On Thu, Oct 13, 2016 at 7:53 PM, Susinthiran Sithamparanathan <
>>> chesu...@gmail.com> wrote:
>>>
 On Thu, Oct 13, 2016 at 3:23 PM, Yedidyah Bar David 
 wrote:

>
> OK. Can you please attach the output of:
>
> grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>

  [root@ovirt01 ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
 [root@ovirt01 ~]# ssh 192.168.0.101
 root@192.168.0.101's password:
 Last login: Thu Oct 13 19:50:02 2016 from ovirt01
 [root@engine ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
 [root@engine ~]#

 I.e nothing found by grep for that search on the host and the
 engine-vm.

 --

 Susinthiran Sithamparanathan

>>>
>>>
>>>
>>> --
>>>
>>> Susinthiran Sithamparanathan
>>>
>>
>>
>
>
> --
>
> Susinthiran Sithamparanathan
>

-- 

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

[ovirt-users] problem with changing cluster compatibility version to 4.0

2016-10-17 Thread Jiří Sléžka


Hello,


I am trying to change cluster compatibility version on one of our 
clusters in our oVirt 4.0.4.4-1.el7.centos installation and I am getting 
this error:



Error while executing action Edit Cluster properties: Internal Engine Error


(btw. it would be realy nice make all texts/logs in manager copyable in 
some easy way (simple ctrl+c does not usually work))



In engine.log I found this interesting lines


2016-10-17 15:02:50,415 WARN [org.ovirt.engine.core.bll.UpdateVmCommand] 
(default task-51) [2921f45e] Validation of action 'UpdateVm' failed for 
user user@auth. Reasons: 
VAR__ACTION__UPDATE,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_SINGLE_DEVICE_DISPLAY_TYPE
2016-10-17 15:02:50,417 ERROR 
[org.ovirt.engine.core.bll.UpdateVmCommand] (default task-51) [2921f45e] 
Transaction rolled-back for command 
'org.ovirt.engine.core.bll.UpdateVmCommand'.
2016-10-17 15:02:50,417 ERROR 
[org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-51) 
[2921f45e] Transaction rolled-back for command 
'org.ovirt.engine.core.bll.UpdateClusterCommand'.
2016-10-17 15:02:50,421 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(default task-51) [2921f45e] Correlation ID: 11011a71, Call Stack: null, 
Custom Event ID: -1, Message: Failed to update Host cluster (User: 
user@auth)
2016-10-17 15:02:50,422 INFO 
[org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-51) 
[2921f45e] Lock freed to object 'EngineLock:{exclusiveLocks='null', 
sharedLocks='[27161d3d-01ef-4446-aa7a-be5483fdbdf5=, 0323b12f-a515-4759-9bae-cf53336a7756=, 1c6d0ce4-bdcd-4f77-906b-65e4f6415cc3=, 8240ebe8-388c-4a5b-996e-f9e5c77e6375=, e6fab9a1-8f45-4565-8483-363137536334=, 7a5de3e0-ecbd-4ed6-bf98-2e7a45e96027=, 6db37ee2-0ff0-4642-9907-666376b13bda=, dccb8bc9-4760-487b-a2bf-100906a50502=, ea63bea8-f41d-4878-814e-fa62b123a89f=, 885b9641-fda5-4e90-889e-488b858bc37b=, 886a6b86-1bf9-43a0-b7ee-2c43640f8f42=, f4fa4a7e-d0eb-44d8-8ed3-00c2b2705cb4=, 9d4673af-6fba-4b62-bdbf-0864dac65941=, 5ef8560e-bf35-4dfb-8677-3b444fcb9a5d=, 2dfc397f-7230-4517-b143-0bec13b3cd55=, f9d1161f-0d7e-4da5-b45f-1796f87ddab5=, 2b0afe1d-1196-4c99-ab61-43e3764fe1ac=, 08016bb0-e638-431c-a429-0a8f3272632b=, 0a4596ec-fa40-46a1-9d2a-7dcaf0127136=, 9f0bb9a0-374f-41ec-9bec-e35fec4275a1=, 606f3257-7d38-405f-8fc9-b56ff6d36684=, 64976d4e-a64d-453b-8bcb-514c687ae208=, 833ebee2-7e8f-480c-877d-3bbdbf78c7ca=, 7dcabc9d-0d61-4bb0-a532-39655caa900d=, 9eaceca3-4e48-4bde-8cfb-024219d226a9=]'}'



It looks to me like one of our vm has 
"ILLEGAL_SINGLE_DEVICE_DISPLAY_TYPE" set which fail upgrade. But which 
one and which setting correspond to this? :-)



I have no idea if changing cluster compatibility version should fail due 
this error. Should I fill Bugreport for this?



Cheers,

Jiri






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

Re: [ovirt-users] Unable to get HE up after update

2016-10-17 Thread Susinthiran Sithamparanathan

Hi,
i tried that and ended up with :
https://paste.fedoraproject.org/453892/71003314/  :(
Log ovirt-engine-setup-20161017150800-drmayj.log uploaded to
https://my.owndrive.com/index.php/s/3Dcyho9bqo7oZs8?path=%2Fengine-vm



On Mon, Oct 17, 2016 at 11:54 AM, Simone Tiraboschi 
wrote:

>
>
> On Mon, Oct 17, 2016 at 9:55 AM, Susinthiran Sithamparanathan <
> chesu...@gmail.com> wrote:
>
>> Hi guys,
>> let me know if there anything else you need for further debugging purpose.
>> Thanks!
>>
>
> Can you please try reinstalling all the oVirt rpms on the engine VM and
> re-executing engine-setup there?
>
>
>>
>> On Thu, Oct 13, 2016 at 7:53 PM, Susinthiran Sithamparanathan <
>> chesu...@gmail.com> wrote:
>>
>>> On Thu, Oct 13, 2016 at 3:23 PM, Yedidyah Bar David 
>>> wrote:
>>>

 OK. Can you please attach the output of:

 grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf

>>>
>>>  [root@ovirt01 ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>>> [root@ovirt01 ~]# ssh 192.168.0.101
>>> root@192.168.0.101's password:
>>> Last login: Thu Oct 13 19:50:02 2016 from ovirt01
>>> [root@engine ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>>> [root@engine ~]#
>>>
>>> I.e nothing found by grep for that search on the host and the engine-vm.
>>>
>>>
>>> --
>>>
>>> Susinthiran Sithamparanathan
>>>
>>
>>
>>
>> --
>>
>> Susinthiran Sithamparanathan
>>
>
>


-- 

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

Re: [ovirt-users] oVirt AD integration problems

2016-10-17 Thread cmc

Hi Ondra,

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

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

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

Cheers,

Cam

On Mon, Oct 17, 2016 at 10:06 AM, Ondra Machacek 
wrote:

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

Re: [ovirt-users] Unable to get HE up after update

2016-10-17 Thread Simone Tiraboschi

On Mon, Oct 17, 2016 at 9:55 AM, Susinthiran Sithamparanathan <
chesu...@gmail.com> wrote:

> Hi guys,
> let me know if there anything else you need for further debugging purpose.
> Thanks!
>

Can you please try reinstalling all the oVirt rpms on the engine VM and
re-executing engine-setup there?


>
> On Thu, Oct 13, 2016 at 7:53 PM, Susinthiran Sithamparanathan <
> chesu...@gmail.com> wrote:
>
>> On Thu, Oct 13, 2016 at 3:23 PM, Yedidyah Bar David 
>> wrote:
>>
>>>
>>> OK. Can you please attach the output of:
>>>
>>> grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>>>
>>
>>  [root@ovirt01 ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>> [root@ovirt01 ~]# ssh 192.168.0.101
>> root@192.168.0.101's password:
>> Last login: Thu Oct 13 19:50:02 2016 from ovirt01
>> [root@engine ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>> [root@engine ~]#
>>
>> I.e nothing found by grep for that search on the host and the engine-vm.
>>
>>
>> --
>>
>> Susinthiran Sithamparanathan
>>
>
>
>
> --
>
> Susinthiran Sithamparanathan
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt AD integration problems

2016-10-17 Thread Ondra Machacek

Hi Cam,

this is OK, because we use user principal name(UPN)[1] for the
'username' field of the oVirt. So the result username will consist of
UPN@authz-extension, so if your user's UPN is 'user@domain' and you
will name your authz extension as 'domain', then the result username
will be 'user@domain@domain'.

The problem, that you can't get authorized is that you didn't assigned
any permissions to your user.

[1] https://msdn.microsoft.com/en-us/library/ms680857(v=vs.85).aspx

On 10/14/2016 04:30 PM, cmc wrote:

Hi Ondra,

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

Cheers,

Cam

On Thu, Oct 13, 2016 at 2:04 PM, cmc > wrote:

Hi Ondra,

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

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

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

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

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

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

Many thanks for all the help!

Kind regards,

Cam

Yes, you really do not need anything kerberos related to
securely bind
to AD via LDAP simple bind over TLS/SSL. This is really strange
to me
what errors you are getting, but you probably configured apache (or
something else?) to require keytab, but you don't have to, and
you can
remove that configuration.

Thanks,

Cam

Thanks,

Cam

___

Users mailing list
Users@ovirt.org
>

http://lists.ovirt.org/mailman/listinfo/users

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

[ovirt-users] Problem with backing-file, how to fix the backing-chain ?

2016-10-17 Thread Dael Maselli


Hi all,

We run an ovirt environment before with engine v3.6.5 (if remember good)
and now with v4.0.4 (we upgraded because we read the bug with
backing-file was resolved with v4).

We upgraded some of the hosts machines (but not all still) at v4.0.4 too
to see if this would fix the problem, but nothing.

The problem is that we have several VMs with snapshots, we do daily,
weekly and monthly snapshots, keep some of them (usually the fresh ones)
and remove the olds (that in the case they are weekly snapshots, they
are in the middle of a series of snapshots), this in the time has
produced the famous

Backing file too long bug.

So we upgraded the engine from 3.6.5 to 4.0.4 (latest available).

We discovered this bug, when we tried to upgrade an host to v4.0.4,
doing so a VM in the host didn't migrate, so we shutdown it and tried to
run on another host, but never succeded for the bug.

We don't know if we have more VMs in this situation because we upgraded
only 2 hosts on 10.

Investigating the problem we discovered that the backing file indicated
in each of LVM snapshots report a path very long with
/dev/storage-domain-id/../image-group-id/ with ../image-group-id/
repeated a lot of times and at the end /parentid.

So to understand which was the right path that it would contain, we
cloned a VM in the v4.0.4 and then we did 4 snapshots, now the backing
file path is

/dev/storage-domain-id/parentid

Is there a way to modify the path in the backing-file or a way to
recover the VM from this state ?

Where do reside the informations about the backing-file path ?

I attach here all the commands we run

On the ovirt manager (host with the engine only) we run

ovirt-shell

[oVirt shell (connected)]# list disks --parent-vm-name vm1

id : 2df25a13-6958-40a8-832f-9a26ce65de0f
name   : vm1_Disk2

id : 8cda0aa6-9e25-4b50-ba00-b877232a1983
name   : vm1_Disk1

[oVirt shell (connected)]# show disk 8cda0aa6-9e25-4b50-ba00-b877232a1983

id   : 8cda0aa6-9e25-4b50-ba00-b877232a1983
name : vm1_Disk1
actual_size  : 1073741824
alias: vm1_Disk1
disk_profile-id  : 1731f79a-5034-4270-9a87-94d93025deac
format   : cow
image_id : 7b354e2a-2099-4f2a-80b7-fba7d1fd13ee
propagate_errors : False
provisioned_size : 17179869184
shareable: False
size : 17179869184
sparse   : True
status-state : ok
storage_domains-storage_domain-id: 384f9059-ef2f-4d43-a54f-de71c5d589c8
storage_type : image
wipe_after_delete: False

[root@ovc1mgr ~]# su - postgres
Last login: Fri Oct 14 01:02:14 CEST 2016
-bash-4.2$ psql -d engine -U postgres
psql (9.2.15)
Type "help" for help.

engine=#\x on
engine=# select * from images where image_group_id =
'8cda0aa6-9e25-4b50-ba00-b877232a1983' order by creation_date;

-[ RECORD 1 ]-+-
image_guid| 60ba7acf-58cb-475b-b9ee-15b1be99fee6
creation_date | 2016-03-29 15:12:34+02
size  | 17179869184
it_guid   | ----
parentid  | ----
imagestatus   | 4
lastmodified  | 2016-04-21 11:25:59.972+02
vm_snapshot_id| 27c187cd-989f-4f7a-ac05-49c4410de6c2
volume_type   | 1
volume_format | 5
image_group_id| 8cda0aa6-9e25-4b50-ba00-b877232a1983
_create_date  | 2016-03-29 15:12:31.994065+02
_update_date  | 2016-09-04 01:10:08.773649+02
active| f
volume_classification | 1

-[ RECORD 2 ]-+-
image_guid| 68d764ec-bc2e-4e1d-b8f2-b44afd9fcb2e
creation_date | 2016-07-03 01:01:30+02
size  | 17179869184
it_guid   | ----
parentid  | 60ba7acf-58cb-475b-b9ee-15b1be99fee6
imagestatus   | 1
lastmodified  | 2016-07-04 01:03:33.732+02
vm_snapshot_id| 175c2071-a06b-4b0e-a069-5cc4bb236a34
volume_type   | 2
volume_format | 4
image_group_id| 8cda0aa6-9e25-4b50-ba00-b877232a1983
_create_date  | 2016-07-03 01:01:15.069585+02
_update_date  | 2016-09-11 02:06:04.420965+02
active| f
volume_classification | 1

-[ RECORD 3 ]-+-
image_guid| 37ca6494-e990-44e5-8597-28845a0a19b5
creation_date | 2016-08-07 01:06:15+02
size  | 17179869184
it_guid   | ----
parentid  | 68d764ec-bc2e-4e1d-b8f2-b44afd9fcb2e
imagestatus   | 1
lastmodified  | 2016-08-08 01:00:03.778+02
vm_snapshot_id| 4c0e5ac0-2ef3-4996-b3e9-7fd566d97b1a

Re: [ovirt-users] Can't restart hosted-engine installation: vdsm did not start

2016-10-17 Thread gregor

Hi,

sadly this did not help.

cheers
gregor

On 17/10/16 09:54, Simone Tiraboschi wrote:
> 
> 
> On Sun, Oct 16, 2016 at 10:47 PM, gregor  > wrote:
> 
> How can I completely remove all the problematic VDSM remains to get a
> clean system again without wiping the whole machine?
> 
> 
> You can try following this:
> https://www.ovirt.org/documentation/how-to/hosted-engine/#recoving-from-failed-install
> 
>  
> 
> chees
> gregor
> 
> On 16/10/16 20:58, gregor wrote:
> > Hi,
> >
> > after a failed hosted-engine installation I removed all the ovirt and
> > vdsm packages, rebooted the system and started from scratch.
> > But when I run "hosted-engine --deploy" it stuck's during starting
> vdsm.
> >
> > The logfile /var/log/vdsm/supervdsm.log gives me the following
> >
> > ...
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,065::storage_log::69::blivet::(log_exception_info) IGNORED:
> >Caught exception, continuing.
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,065::storage_log::72::blivet::(log_exception_info) IGNORED:
> >Problem description: failed to get initiator name from iscsi
> firmware
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,065::storage_log::73::blivet::(log_exception_info) IGNORED:
> >Begin exception details.
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,066::storage_log::76::blivet::(log_exception_info) IGNORED:
> >Traceback (most recent call last):
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,066::storage_log::76::blivet::(log_exception_info) IGNORED:
> >  File "/usr/lib/python2.7/site-packages/blivet/iscsi.py", line
> > 142, in __init__
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,066::storage_log::76::blivet::(log_exception_info) IGNORED:
> >initiatorname = libiscsi.get_firmware_initiator_name()
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,066::storage_log::76::blivet::(log_exception_info) IGNORED:
> >IOError: Unknown error
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,066::storage_log::77::blivet::(log_exception_info) IGNORED:
> >End exception details.
> > ...
> >
> > Can anybody help? I found a old are close again like so many other bug
> > reports with "CLOSED CURRENTRELEASE":
> > https://bugzilla.redhat.com/show_bug.cgi?id=1238239
> 
> >
> > cheers
> > gregor
> > ___
> > 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] Unable to get HE up after update

2016-10-17 Thread Susinthiran Sithamparanathan

Hi guys,
let me know if there anything else you need for further debugging purpose.
Thanks!

On Thu, Oct 13, 2016 at 7:53 PM, Susinthiran Sithamparanathan <
chesu...@gmail.com> wrote:

> On Thu, Oct 13, 2016 at 3:23 PM, Yedidyah Bar David 
> wrote:
>
>>
>> OK. Can you please attach the output of:
>>
>> grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
>>
>
>  [root@ovirt01 ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
> [root@ovirt01 ~]# ssh 192.168.0.101
> root@192.168.0.101's password:
> Last login: Thu Oct 13 19:50:02 2016 from ovirt01
> [root@engine ~]# grep MANUAL /etc/ovirt-engine/engine.conf.d/*.conf
> [root@engine ~]#
>
> I.e nothing found by grep for that search on the host and the engine-vm.
>
>
> --
>
> Susinthiran Sithamparanathan
>



-- 

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

Re: [ovirt-users] Can't restart hosted-engine installation: vdsm did not start

2016-10-17 Thread Simone Tiraboschi

On Sun, Oct 16, 2016 at 10:47 PM, gregor  wrote:

> How can I completely remove all the problematic VDSM remains to get a
> clean system again without wiping the whole machine?
>
>
You can try following this:
https://www.ovirt.org/documentation/how-to/hosted-engine/#recoving-from-failed-install



> chees
> gregor
>
> On 16/10/16 20:58, gregor wrote:
> > Hi,
> >
> > after a failed hosted-engine installation I removed all the ovirt and
> > vdsm packages, rebooted the system and started from scratch.
> > But when I run "hosted-engine --deploy" it stuck's during starting vdsm.
> >
> > The logfile /var/log/vdsm/supervdsm.log gives me the following
> >
> > ...
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,065::storage_log::69::blivet::(log_exception_info) IGNORED:
> >Caught exception, continuing.
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,065::storage_log::72::blivet::(log_exception_info) IGNORED:
> >Problem description: failed to get initiator name from iscsi firmware
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,065::storage_log::73::blivet::(log_exception_info) IGNORED:
> >Begin exception details.
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,066::storage_log::76::blivet::(log_exception_info) IGNORED:
> >Traceback (most recent call last):
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,066::storage_log::76::blivet::(log_exception_info) IGNORED:
> >  File "/usr/lib/python2.7/site-packages/blivet/iscsi.py", line
> > 142, in __init__
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,066::storage_log::76::blivet::(log_exception_info) IGNORED:
> >initiatorname = libiscsi.get_firmware_initiator_name()
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,066::storage_log::76::blivet::(log_exception_info) IGNORED:
> >IOError: Unknown error
> > MainThread::DEBUG::2016-10-16
> > 20:54:42,066::storage_log::77::blivet::(log_exception_info) IGNORED:
> >End exception details.
> > ...
> >
> > Can anybody help? I found a old are close again like so many other bug
> > reports with "CLOSED CURRENTRELEASE":
> > https://bugzilla.redhat.com/show_bug.cgi?id=1238239
> >
> > cheers
> > gregor
> > ___
> > 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

[ovirt-users] fakevdsm vs ovirt engine 4.0.4

Re: [ovirt-users] Can't restart hosted-engine installation: vdsm did not start

Re: [ovirt-users] Problem with backing-file, how to fix the backing-chain ?

[ovirt-users] ovirt list's smtp on blacklist?

Re: [ovirt-users] Unable to get HE up after update

Re: [ovirt-users] Unable to get HE up after update

Re: [ovirt-users] Unable to get HE up after update

Re: [ovirt-users] Unable to get HE up after update

Re: [ovirt-users] Unable to get HE up after update

[ovirt-users] problem with changing cluster compatibility version to 4.0

Re: [ovirt-users] Unable to get HE up after update

Re: [ovirt-users] oVirt AD integration problems

Re: [ovirt-users] Unable to get HE up after update

Re: [ovirt-users] oVirt AD integration problems

[ovirt-users] Problem with backing-file, how to fix the backing-chain ?

Re: [ovirt-users] Can't restart hosted-engine installation: vdsm did not start

Re: [ovirt-users] Unable to get HE up after update

Re: [ovirt-users] Can't restart hosted-engine installation: vdsm did not start

18 matches

Site Navigation

Mail list logo

Footer information