Re: [ovirt-users] vdsm hook noipspoof on interface level

2018-04-13 Thread Eitan Raviv
You might find the following useful:

https://ovirt.org/develop/release-management/features/network/networkfilterparameters/

HTH

On Thu, Apr 12, 2018, 14:52 Peter Hudec  wrote:

> Hi,
>
> I would like to restrict of usage IP address on VMs. Thos could be
> achied by usinf clear-filter instead of vdsm-no-mac-spoofing.
>
> I have found noipspoof vdsm hook,
> https://github.com/oVirt/vdsm/tree/master/vdsm_hooks/noipspoof.
>
> This hook but set the filtering on all interfaces, the setting is on VM
> level, not interface level. So if the there are more interfaces on all
> of them. I would like just restrict the WAN interface on multi homed VMs.
>
> Peter
>
> --
> *Peter Hudec*
> Infraštruktúrny architekt
> phu...@cnc.sk 
>
> *CNC, a.s.*
> Borská 6, 841 04 Bratislava
> Recepcia: +421 2  35 000 100
>
> Mobil:+421 905 997 203
> *www.cnc.sk* 
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] How to recreate lease file for hosted engine

2018-04-13 Thread Ling Ho

This is what I ended up doing and got my hosted-engine VM to come back up:

sanlock direct init -r 
555cd8c2-1565-41e0-a34e-4f4707e68273:1006c1f3-5e59-49b4-b960-3ed369a2d94e:/rhev/data-center/580aae45-01d0-027a-01dc-0132/555cd8c2-1565-41e0-a34e-4f4707e68273/images/c5892e12-7361-4467-a188-d5817510ac4b/1006c1f3-5e59-49b4-b960-3ed369a2d94e.lease:0



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


Re: [ovirt-users] I broke my ovirt real good....

2018-04-13 Thread ~Stack~
On 04/13/2018 07:16 AM, Alexander Wels wrote:
> On Thursday, April 12, 2018 6:26:07 PM EDT ~Stack~ wrote:
>> Greetings,
>>
>> So I did a over-confident-admin-makes-rookie-mistake. I changed a bunch
>> of things all back-to-back and thus don't actually know what broke. :-D
>>
>> The only two real "big" changes were:
>> * Upgrade from 4.2.1 to 4.2.2
>> * change my ovirtmgmt network
>>
>> The update I followed the upgrade procedures and I thought it all went
>> pretty well. Because I am moving it from a testing into what I hope will
>> be a more heavily used environment, I changed my ovirtmgmt network from
>> 192.168.100.0/24 to 192.168.101.0/24 via the web-gui.
>>
>> That was a touch tricker than just a change as I had to poke the
>> management engine host to be reachable on both network for a while, then
>> it just seemed OK.
>>
>> What's happening is:
>> * I can no longer migrate a vm from one host to the other.
>> * If I try to do a "reinstall" it dies.
>> * There is some serious network lag between my hosts on a 10Gb network.
>> * I've got all kinds of python2.4 failures in my vdsm and mom logs.
>>
>> Those are least the biggies.
>>
>> So while I was planning on moving this to a more active use case, right
>> now - it is all still my play ground. I would REALLY hate to lose the
>> VM's but everything else can go and be rebuilt.
>>
>> Given that I've somehow really broke this system pretty good, would it
>> be more advisable to blow away and rebuild it ALL or can I simply delete
>> the hypervisor hosts and rebuild them?
>>
>> Thoughts?
>>
>> Thanks!
>> ~Stack~
> 
> As long as you don't destroy the data on your data domain you can rebuild the 
> engine and hosts and then import the existing data domain without too many 
> issues. I have destroyed my engine database many times, and I am still using 
> the same VMs from the same data domain.
> 
> Here is what I do when I mess up my database to the point I have to make a 
> new 
> one:
> 
> 1. Recreate the engine and database, so that I have basically have an empty 
> engine with no hosts and VMs.
> 1.1 (Optional) make a new DC that is not default. and add a cluster.
> 2. Add my hosts (I only have 2 so that is quick and easy).
> 3. Add a throw away data domain (This is needed to get the DC up so I can 
> import the existing data domain).
> 4. Import (NOT new, import) the existing data domain.
> 5. Do to Storage->Storage Domains->VM import and import the VMs I want.
> 6. Same for templates and disks if needed.
> 7. After you have imported the VMs/Templates/Disks you can detach and remove 
> the throw away data domain and the one you imported becomes the master domain.
> 
> Note if you want to move VMs between your play ground and more serious system 
> you can simply detach your data domain from the play ground, then attach it 
> to 
> the serious engine (so you have 2 engines, one play ground and one serious) 
> and import which VMs you want. That way you won't run into issues with 
> configuring networks and stuff like you experienced.
> 

Thanks for that help. I did that and everything looks fantastic...except
I can't migrate VM's. :-/

It just sits there and in the log files there is the below messages
repeating. It's like it doesn't care for the fact that this was an
imported domain or something.

Thoughts?

Thanks!
~Stack~


2018-04-13 16:58:59,920-0500 ERROR (monitor/232975a) [storage.Monitor]
Setting up monitor for 232975ad-1771-4b6b-afda-958f7b745867 failed
(monitor:329)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line
326, in _setupLoop
self._setupMonitor()
  File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line
348, in _setupMonitor
self._produceDomain()
  File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 158, in
wrapper
value = meth(self, *a, **kw)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line
366, in _produceDomain
self.domain = sdCache.produce(self.sdUUID)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 110,
in produce
domain.getRealDomain()
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 51,
in getRealDomain
return self._cache._realProduce(self._sdUUID)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 134,
in _realProduce
domain = self._findDomain(sdUUID)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 151,
in _findDomain
return findMethod(sdUUID)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 176,
in _findUnfetchedDomain
raise se.StorageDomainDoesNotExist(sdUUID)
StorageDomainDoesNotExist: Storage domain does not exist:
(u'232975ad-1771-4b6b-afda-958f7b745867',)
2018-04-13 16:58:59,923-0500 ERROR (monitor/bc975a4) [storage.Monitor]
Setting up monitor for bc975a4c-6c38-4248-b3f7-a26945f23693 failed
(monitor:329)
Traceback (most recent call last):
  File 

[ovirt-users] Snapshots from User Portal in ovirt 4.2?

2018-04-13 Thread Brian Chow
After upgrading from 4.1 to 4.2, we can no longer find the snapshot
functionality in the User Portal -- the documentation is still referencing
the 4.1 UI.  Was this removed from the user portal?  Moved to a different
area?  Are the required permissions different from 4.1?

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


Re: [ovirt-users] ?= vdsClient is removed and replaced by vdsm-clien

2018-04-13 Thread Arik Hadas
On Fri, Apr 13, 2018 at 6:54 PM, fsoyer  wrote:

> Hi,
> This task is listed (since 2 days) in the GUI / up right "tasks" icon. It
> is visibly freezed as no OVA file has been created, but no errors in GUI,
> just... it runs. Or : it loops :)
> This (test) vm is one on which I have extended the disk (50 -> 100G).
> Before being stopped and trying to export it to OVA, it works fine. All
> other vms around can be well exported but not this one. I've tried to
> restart engine, change SPM, restart one by one each node, but the task is
> always here. I could even restart the vm today without error and it works
> fine ! But... the task runs...
> Today also, I tried to clone the vm : same thing, now I have 2 tasks
> running indefinitly :(


> Strange bug, where no timeout stopped the tasks in error. I can't see any
> revelant things in engine.log or vdsm.log, but probably I've not seen them
> in all the messages.
> No problem to remove this (test) vm and try on another (test) one (extend
> disk to see if this is the reason of the problem). But before I want to
> kill this tasks !
>

Please don't remove that VM yet.
It would be appreciated if you could file a bug and share the engine log
that covers the attempt to export this VM to OVA + the ansible log of that
operation.


>
> Thanks.
> Frank
>
>
>
> Le Vendredi, Avril 13, 2018 16:24 CEST, Arik Hadas  a
> écrit:
>
>
>
>
> On Fri, Apr 13, 2018 at 11:14 AM, fsoyer  wrote:
>>
>> Hi all,
>> I can't find any exhaustive doc for new vdsm-client. My problem actually
>> is a task (export a vm to OVA) blocked.
>
>
> I'm afraid you won't find any task in VDSM for 'export a VM to OVA'.
> Expoting a VM to OVA is comprised of three steps:
> 1. Creating temporary cloned disks - you'll find a task of
> copy-image-group for each disk.
> 2. Creating the OVA file - that's done by a python script executed by
> ansible, there is no task for that in VDSM.
> 3. Removing the temporary cloned disks - you'll find a task of
> remove-image for each disk.
>
> Can you please elaborate on the problem you're having - where do you see
> that task and how can you see that it's blocked?
>
>
>> I found that I can interact with
>> vdsm-client Task getInfo taskID=, and replace getInfo by "stop",
>> BUT : how can I find this UUID ???
>> Old "vdsClient -s 0 getAllTasksStatuses" has no equivalent ??
>>
>> Does someone knows if a complete doc exists dot vdsm-client ?
>> Thanks
>> Frank
>>
>>
>>
>>
>>
>> Le Mercredi, Janvier 25, 2017 12:30 CET, Irit Goihman <
>> igoih...@redhat.com> a écrit:
>>
>>
>> Hi All,
>>
>> vdsClient will be removed from master branch today.
>> It is using XMLRPC protocol which has been deprecated and replaced by
>> JSON-RPC.
>>
>> A new client for vdsm was introduced in 4.1: vdsm-client.
>> This is a simple client that uses JSON-RPC protocol which was introduced
>> in ovirt 3.5.
>>
>> The client is not aware of the available methods and parameters, and you
>> should consult
>> the schema [1] in order to construct the desired command.
>>
>> Future version should parse the schema and provide online help.
>>
>>
>> If you're using vdsClient, we will be happy to assist you in migrating to
>> the new vdsm client.
>>
>>
>>
>> *vdsm-client usage:*
>>
>> vdsm-client [-h] [-a ADDRESS] [-p PORT] [--unsecure] [--timeout TIMEOUT]
>>[-f FILE] namespace method [name=value [name=value]
>> ...]
>>
>>
>> Invoking simple methods:
>>
>> # vdsm-client Host getVMList
>> ['b3f6fa00-b315-4ad4-8108-f73da817b5c5']
>>
>> For invoking methods with many or complex parameters, you can read
>> the parameters from a JSON format file:
>>
>> # vdsm-client Lease info -f lease.json
>>
>> where lease.json file content is:
>>
>> {
>>
>>   "lease": {
>>
>>   "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",
>>
>>   "lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"
>>
>>   }
>>
>>   }
>>
>> It is also possible to read parameters from standard input, creating
>> complex parameters interactively:
>>
>> # cat <>
>>  {
>>
>>  "lease": {
>>
>>  "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",
>>
>>  "lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"
>>
>>  }
>>
>>  }
>>
>> EOF
>>
>>
>> *Constructing a command from vdsm schema:*
>>
>> Let's take VM.getStats as an example.
>> This is the entry in the schema:
>>
>> VM.getStats:
>>
>> added: '3.1'
>>
>> description: Get statistics about a running virtual machine.
>>
>> params:
>>
>> -   description: The UUID of the VM
>>
>> name: vmID
>>
>> type: *UUID
>>
>> return:
>>
>> description: An array containing a single VmStats record
>>
>> type:
>>
>> - *VmStats
>>
>>
>> namespace: VM
>> method name: getStats
>> params: vmID
>>
>> The vdsm-client command is:
>>
>> # vdsm-client VM getStats vmID=b3f6fa00-b315-4ad4-8108-f73da817b5c5
>>
>>
>> *Invoking getVdsCaps 

[ovirt-users] Add nodes to single-node hyperconverged cluster

2018-04-13 Thread Joe DiTommasso
Hi, I'm currently running an out-of-date (3.6) 3-node oVirt cluster, using
NFS storage. I'd like to upgrade to the latest release and move to a
hyperconverged setup, but I've only got the three hosts to play with. I'm
currently thinking of pulling one node from my current cluster, rebuilding
it to start a new cluster, and then migrating VMs/physical hosts over to
the new cluster. Is that something that would seem feasible? I've read the
documentation on setting up a hyperconverged cluster, but didn't see
anything about adding new hosts after cluster deployment.Thanks!

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


[ovirt-users] How to recreate lease file for hosted engine

2018-04-13 Thread Ling Ho

Hello,

I upgraded ovirt-engine to 4.2.2 yesterday, and tried moving hosted 
engine disk to a different domain. I thought the move was sucessful and 
went and shut down my old domain NFS server. After that my hosted engine 
stopped.


Now all NFS is back up, I find that my hosted engine storage is on the 
new domain, but the metadata and lockspace are still on the old domain. 
I am trying to either move the metadata and lockspace to the new domain 
or copy the vm disk back to the old. When the vm disk is in the old, and 
I try starting hosted vm, it complains about incorrect lease name. I 
figure it must be with the .lease file in the vm volume.


libvirtError: resource busy: Failed to acquire lock: Lease lockspace 
name is incorrect
2018-04-13 09:16:28,601-0700 INFO  (vm/20b4ca22) [virt.vm] 
(vmId='20b4ca22-0bd1-46ef-9f9b-31637a93e32f') Changed state to Down: 
resource busy: Failed to acquire lock: Lease lockspace name is incorrect 
(code=1) (vm:1677)


Doing a stings on the lease file:
# strings 1006c1f3-5e59-49b4-b960-3ed369a2d94e.lease
8baf4007-426b-4910-88fe-94ea32f11f55
1006c1f3-5e59-49b4-b960-3ed369a2d94e

The first UUID (8baf4007-426b-4910-88fe-94ea32f11f55) is the UUID of the 
new domain. How do I go about recreating this lease file so it contains 
the UUID of the old domain?


Thanks,

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


Re: [ovirt-users] ?==?utf-8?q? ?==?utf-8?q? ?= vdsClient is removed and replaced by vdsm-clien

2018-04-13 Thread fsoyer

Hi,
This task is listed (since 2 days) in the GUI / up right "tasks" icon. It is 
visibly freezed as no OVA file has been created, but no errors in GUI, just... 
it runs. Or : it loops :)
This (test) vm is one on which I have extended the disk (50 -> 100G). Before 
being stopped and trying to export it to OVA, it works fine. All other vms 
around can be well exported but not this one. I've tried to restart engine, 
change SPM, restart one by one each node, but the task is always here. I could 
even restart the vm today without error and it works fine ! But... the task 
runs...
Today also, I tried to clone the vm : same thing, now I have 2 tasks running 
indefinitly :(

Strange bug, where no timeout stopped the tasks in error. I can't see any 
revelant things in engine.log or vdsm.log, but probably I've not seen them in 
all the messages.
No problem to remove this (test) vm and try on another (test) one (extend disk 
to see if this is the reason of the problem). But before I want to kill this 
tasks !

Thanks.
Frank

 Le Vendredi, Avril 13, 2018 16:24 CEST, Arik Hadas  a écrit:
   On Fri, Apr 13, 2018 at 11:14 AM, fsoyer  wrote:Hi all,
I can't find any exhaustive doc for new vdsm-client. My problem actually is a 
task (export a vm to OVA) blocked. I'm afraid you won't find any task in VDSM 
for 'export a VM to OVA'.Expoting a VM to OVA is comprised of three steps:1. 
Creating temporary cloned disks - you'll find a task of copy-image-group for 
each disk.2. Creating the OVA file - that's done by a python script executed by 
ansible, there is no task for that in VDSM.3. Removing the temporary cloned 
disks - you'll find a task of remove-image for each disk. Can you please 
elaborate on the problem you're having - where do you see that task and how can 
you see that it's blocked? I found that I can interact with
vdsm-client Task getInfo taskID=, and replace getInfo by "stop", BUT : 
how can I find this UUID ???
Old "vdsClient -s 0 getAllTasksStatuses" has no equivalent ??

Does someone knows if a complete doc exists dot vdsm-client ?
Thanks
Frank

 

Le Mercredi, Janvier 25, 2017 12:30 CET, Irit Goihman  a 
écrit:
 Hi All, vdsClient will be removed from master branch today.It is using XMLRPC 
protocol which has been deprecated and replaced by JSON-RPC. A new client for 
vdsm was introduced in 4.1: vdsm-client.This is a simple client that uses 
JSON-RPC protocol which was introduced in ovirt 3.5. The client is not aware of 
the available methods and parameters, and you should consult the schema [1] in 
order to construct the desired command. Future version should parse the schema 
and provide online help.  If you're using vdsClient, we will be happy to assist 
you in migrating to the new vdsm client.   vdsm-client usage: vdsm-client [-h] 
[-a ADDRESS] [-p PORT] [--unsecure] [--timeout TIMEOUT]                   [-f 
FILE] namespace method [name=value [name=value] ...]  Invoking simple methods: 
# vdsm-client Host getVMList['b3f6fa00-b315-4ad4-8108-f73da817b5c5'] For 
invoking methods with many or complex parameters, you can read the parameters 
from a JSON format file: # vdsm-client Lease info -f lease.json where 
lease.json file content is: {                                                   
                                   "lease": {                                   
                                          "sd_id": 
"75ab40e3-06b1-4a54-a825-2df7a40b93b2",                                   
"lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"                             
}                                                                          }   
It is also possible to read parameters from standard input, creating complex 
parameters interactively: # cat 

Re: [ovirt-users] Hosted Engine won't start, how to debug?

2018-04-13 Thread Thomas Klute
Dear Martin,

yes, that worked. Thank you so much!!
We were able to see that the latest kernel update failed and did not
create the initramfs file and thus the boot process failed with a kernel
panic.

Debugging this problem took us many hours... It felt so complicated to
connect a vnc to this vm - compared to a bare metal setup with display
and keyboard.
Wouldn't it be a good idea to have the vnc device in the config by default?

Best regards,
 Thomas

> You need to be in global maintenance, but I think you already know that.
> Then try updating the vm.conf like you already did and add this line:
>
> devices={device:vnc,type:graphics,deviceId:f1d0394e-b077-4ea6-99e5-b9b6b8fe073c,address:None}
>
> Then restart the VM using hosted-engine commands and try the VNC approach 
> again.
>
> Best regards
>
> Martin Sivak
>
> On Fri, Apr 13, 2018 at 2:35 PM, Thomas Klute  wrote:
>> Dear Martin,
>>
>> thanks for the feedback.
>> We already read this and tried it.
>> It seems to me that the graphics device was removed from the hosted
>> engine by some ovirt release.
>>
>> If I try to set a console password I see this message:
>>
>> hosted-engine --add-console-password
>> Enter password:
>> no graphics devices configured
>>
>> Furthermore, there is nothing listening on port 5900 after that.
>> The HostedEngine qemu process shows a " -display none " as parameter and
>> I have no idea where this can be changed.
>>
>> I already created a /var/run/ovirt-hosted-engine-ha/vm-custom.conf
>> containing:
>> display=vnc
>> kvmEnable=true
>>
>> But nothing changed.
>> I also edited the HostedEngine VM config using virsh and added a vnc
>> display:
>> /usr/bin/virsh -c
>> qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf edit
>> HostedEngine
>>
>> 
>>   
>> 
>> 
>>   > heads='1' primary='yes'/>
>>   > function='0x0'/>
>> 
>>
>> But there is still "display none" passed as command line parameter to
>> qemu and thus, I suppose, there's no display.
>>
>> Any help is appreciated, thanks,
>> Thomas
>>
>>
>>> Hi,
>>>
>>> the serial console will show output if the kernel knows to use it.
>>>
>>> The VNC approach is also possible and I believe we already have a
>>> graphical device present. What you are looking for is probably this
>>> (VNC method is described there):
>>> https://www.ovirt.org/documentation/how-to/hosted-engine/#handle-engine-vm-boot-problems
>>>
>>> Best regards
>>>
>>> --
>>> Martin Sivak
>>> SLA / oVirt
>>>
>>> On Fri, Apr 13, 2018 at 11:26 AM, Thomas Klute  wrote:
 Dear oVirt Team,

 after trying to reboot a hosted engine setup on oVirt 4.2 the VM won't
 come up anymore.
 The qemu-kvm process is there but we're unable to access the VM using
 - the serial console (simply does not show anything, does not react to
 characters typed)
 - VNC / Spice because the hosted engine vm.conf does not contain any
 graphics device.

 Before trying to reinstall, we'd like to recover and debug what is going 
 on.
 We mounted a Centos7 install .iso and started the VM using
 hosted-engine --vm-start
 --vm-conf=/var/run/ovirt-hosted-engine-ha/vm-custom.conf
 But we still have to problem, that the serial console does not show
 anything and there is no way to connect using VNC.

 So, what is the recommended way to move forward in such situation?
 IMHO the classical way would be to add a graphics device and connect via
 VNC?
 I did not use the serial console much, up to now. Should the serial
 console show any output during boot?

 Thanks for your help,
  Thomas

 --
 

  Dipl.-Inform. Thomas Klute   kl...@ingenit.com
  Geschäftsführer / CEO
  --
  ingenit GmbH & Co. KG   Tel. +49 (0)231 58 698-120
  Emil-Figge-Strasse 76-80Fax. +49 (0)231 58 698-121
  D-44227 Dortmund   www.ingenit.com

  Registergericht: Amtsgericht Dortmund, HRA 13 914
  Gesellschafter : Thomas Klute, Marc-Christian Schröer
 

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
>> Sollten noch Fragen offen sein, stehen wir Ihnen natürlich jederzeit
>> gerne zur Verfügung.
>>
>> Mit Grüßen aus Dortmund,
>>  Thomas Klute
>>
>> --
>> 
>>
>>  Dipl.-Inform. Thomas Klute   kl...@ingenit.com
>>  Geschäftsführer / CEO
>>  --
>>  ingenit GmbH & Co. KG   Tel. 

Re: [ovirt-users] Engine reports

2018-04-13 Thread Rich Megginson

On 04/13/2018 05:12 AM, Peter Hudec wrote:

thanks, problem was with the selinux. I applied the permission on the
/var/lib/elasticsearch once again.

Deployment is done ;)


Excellent



Right now mi browser is complaining about certificate on SSO.
When I try to reach https://kibana.
I'm redirected to SSO

https:// :8443/oauth/authorize?...

An error occurred during a connection to metrics.ovirt.cnc.sk:8443. You
have received an invalid certificate. Please contact the server
administrator or email correspondent and give them the following
information: Your certificate contains the same serial number as another
certificate issued by the certificate authority. Please get a new
certificate containing a unique serial number. Error code:
SEC_ERROR_REUSED_ISSUER_AND_SERIAL


Uh oh.  That looks like a bug. 
https://github.com/openshift/origin/pull/18713/commits/95e262011438642410959914c3db9868c57739ff
I thought that had been fixed in 3.9, but perhaps the origin 3.9 rpms do 
not yet contain this fix.





Peter

On 12/04/2018 19:47, Rich Megginson wrote:

sudo ls -alrtF -Z /var/lib/elasticsearch

oc logs logging-es-data-master-z6zbv4v2-2-deploy

oc describe pod logging-es-data-master-z6zbv4v2-2-deploy

sudo grep type=AVC /var/log/audit/audit.log | tail

On 04/12/2018 02:32 AM, Peter Hudec wrote:

back to this issue.

something went wrong ;( The status command got error. I'm not familiar
with openshift, so the log processing will took me a while.

[PROD] r...@dipostat01.cnc.sk: ~ # oc project logging
Already on project "logging" on server
"https://metrics.ovirt.cnc.sk:8443;.
[PROD] r...@dipostat01.cnc.sk: ~ # oc adm policy add-scc-to-user
hostmount-anyuid \

    system:serviceaccount:logging:aggregated-logging-elasticsearch

scc "hostmount-anyuid" added to:
["system:serviceaccount:logging:aggregated-logging-elasticsearch"]
[PROD] r...@dipostat01.cnc.sk: ~ # oc rollout cancel $( oc get -n
logging dc -l component=es -o name )
No rollout is in progress (latest rollout #2 failed 3 days ago)
[PROD] r...@dipostat01.cnc.sk: ~ # oc rollout latest $( oc get -n
logging dc -l component=es -o name )
deploymentconfig "logging-es-data-master-z6zbv4v2" rolled out
[PROD] r...@dipostat01.cnc.sk: ~ #  oc rollout status -w $( oc get -n
logging dc -l component=es -o name )
Waiting for rollout to finish: 0 of 1 updated replicas are available...
error: replication controller "logging-es-data-master-z6zbv4v2-3" has
failed progressing


[PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
NAME   READY STATUS    RESTARTS
   AGE
logging-curator-1-c894f    1/1   Running
904    5d
logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error
0  3d
logging-fluentd-x9vzs  1/1   Running
1  5d
logging-kibana-1-6bvvw 2/2   Running
2  5d
logging-mux-1-xxmdj    1/1   Running
1  5d
[PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
NAME   READY STATUS    RESTARTS
   AGE
logging-curator-1-c894f    1/1   Running
904    5d
logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error
0  3d
logging-fluentd-x9vzs  1/1   Running
1  5d
logging-kibana-1-6bvvw 2/2   Running
2  5d
logging-mux-1-xxmdj    1/1   Running
1  5d
[PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
NAME   READY STATUS    RESTARTS
   AGE
logging-curator-1-c894f    1/1   Running
904    5d
logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error
0  3d
logging-fluentd-x9vzs  1/1   Running
1  5d
logging-kibana-1-6bvvw 2/2   Running
2  5d
logging-mux-1-xxmdj    1/1   Running
1  5d
[PROD] r...@dipostat01.cnc.sk: ~ # oc get svc
NAME    TYPE    CLUSTER-IP   EXTERNAL-IP
PORT(S) AGE
logging-es  ClusterIP   172.30.249.174   
9200/TCP    5d
logging-es-cluster  ClusterIP   172.30.114.201   
9300/TCP    5d
logging-es-prometheus   ClusterIP   172.30.203.113   
443/TCP 5d
logging-kibana  ClusterIP   172.30.29.192    
443/TCP 5d
logging-mux ClusterIP   172.30.170.158   192.168.16.17
24284/TCP   5d


On 07/04/2018 01:09, Rich Megginson wrote:

Great!

On 04/06/2018 04:43 PM, Peter Hudec wrote:

Ansible playbook finished OK. The next step after weekend.

  thanks
  Peter

On 06/04/2018 23:34, Rich Megginson wrote:

On 04/06/2018 03:08 PM, Peter Hudec wrote:

Hi,

https://tools.apps.hudecof.net/paste/view/1d493d52

The difference is
- I used latest ansible 2.5 from PIPY source, since the RPM
package do
not fit requirements
- I used GIT repo for openshift-ansible.

I could start it over with the RPM based openshift-ansible

I 

Re: [ovirt-users] ?==?utf-8?q? vdsClient is removed and replaced by vdsm-client

2018-04-13 Thread Arik Hadas
On Fri, Apr 13, 2018 at 11:14 AM, fsoyer  wrote:

> Hi all,
> I can't find any exhaustive doc for new vdsm-client. My problem actually
> is a task (export a vm to OVA) blocked.
>

I'm afraid you won't find any task in VDSM for 'export a VM to OVA'.
Expoting a VM to OVA is comprised of three steps:
1. Creating temporary cloned disks - you'll find a task of copy-image-group
for each disk.
2. Creating the OVA file - that's done by a python script executed by
ansible, there is no task for that in VDSM.
3. Removing the temporary cloned disks - you'll find a task of remove-image
for each disk.

Can you please elaborate on the problem you're having - where do you see
that task and how can you see that it's blocked?


> I found that I can interact with
> vdsm-client Task getInfo taskID=, and replace getInfo by "stop", BUT
> : how can I find this UUID ???
> Old "vdsClient -s 0 getAllTasksStatuses" has no equivalent ??
>
> Does someone knows if a complete doc exists dot vdsm-client ?
> Thanks
> Frank
>
>
>
>
>
> Le Mercredi, Janvier 25, 2017 12:30 CET, Irit Goihman 
> a écrit:
>
>
> Hi All,
>
> vdsClient will be removed from master branch today.
> It is using XMLRPC protocol which has been deprecated and replaced by
> JSON-RPC.
>
> A new client for vdsm was introduced in 4.1: vdsm-client.
> This is a simple client that uses JSON-RPC protocol which was introduced
> in ovirt 3.5.
>
> The client is not aware of the available methods and parameters, and you
> should consult
> the schema [1] in order to construct the desired command.
>
> Future version should parse the schema and provide online help.
>
>
> If you're using vdsClient, we will be happy to assist you in migrating to
> the new vdsm client.
>
>
>
> *vdsm-client usage:*
>
> vdsm-client [-h] [-a ADDRESS] [-p PORT] [--unsecure] [--timeout TIMEOUT]
>[-f FILE] namespace method [name=value [name=value] ...]
>
>
> Invoking simple methods:
>
> # vdsm-client Host getVMList
> ['b3f6fa00-b315-4ad4-8108-f73da817b5c5']
>
> For invoking methods with many or complex parameters, you can read
> the parameters from a JSON format file:
>
> # vdsm-client Lease info -f lease.json
>
> where lease.json file content is:
>
> {
>
>   "lease": {
>
>   "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",
>
>   "lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"
>
>   }
>
>   }
>
> It is also possible to read parameters from standard input, creating
> complex parameters interactively:
>
> # cat <
>  {
>
>  "lease": {
>
>  "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",
>
>  "lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"
>
>  }
>
>  }
>
> EOF
>
>
> *Constructing a command from vdsm schema:*
>
> Let's take VM.getStats as an example.
> This is the entry in the schema:
>
> VM.getStats:
>
> added: '3.1'
>
> description: Get statistics about a running virtual machine.
>
> params:
>
> -   description: The UUID of the VM
>
> name: vmID
>
> type: *UUID
>
> return:
>
> description: An array containing a single VmStats record
>
> type:
>
> - *VmStats
>
>
> namespace: VM
> method name: getStats
> params: vmID
>
> The vdsm-client command is:
>
> # vdsm-client VM getStats vmID=b3f6fa00-b315-4ad4-8108-f73da817b5c5
>
>
> *Invoking getVdsCaps command:*
>
> # vdsm-client Host getCapabilities
>
>
>
> Please consult vdsm-client help and man page for further details and
> options.
>
>
>
> [1] https://github.com/oVirt/vdsm/blob/master/lib/api/vdsm-api.yml
>
> --
> Irit Goihman
> Software Engineer
> Red Hat Israel Ltd.
>
>
>
>
> ___
> 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] ?==?utf-8?q? ?==?utf-8?q? ?= vdsClient is removed and replaced by vdsm-clien

2018-04-13 Thread fsoyer

Ok I see, thank you. 
vdsm-client Host getAllTasksStatuses works on the SPM.
But
vdsm-client Task getInfo TaskID=TaskID=55cbec7f-e7dc-4431-bce9-8ec1d61a7feb
returns :
vdsm-client: Command Task.getInfo with args {'TaskID': 
'55cbec7f-e7dc-4431-bce9-8ec1d61a7feb'} failed:
(code=-32603, message=Internal JSON-RPC error: {'reason': '__init__() takes 
exactly 2 arguments (1 given)'})

There is no examples with tasks below, and the link to github ends in 404...

I'll try to find some docs about API, and tasks management, if you believe 
that's best. Any link to share ?

Thanks,
Frank
 
Le Vendredi, Avril 13, 2018 14:41 CEST, Michal Skrivanek 
 a écrit:
   On 13 Apr 2018, at 10:14, fsoyer  wrote: Hi all,
I can't find any exhaustive doc for new vdsm-client. My problem actually is a 
task (export a vm to OVA) blocked. if you want to interact with that action it 
would always be best to start with engine’s REST API rather than internal 
host-side API I found that I can interact with
vdsm-client Task getInfo taskID=, and replace getInfo by "stop", BUT : 
how can I find this UUID ???Old "vdsClient -s 0 getAllTasksStatuses" has no 
equivalent ?? that’s a Host class api, vdsm-client Host getAllTasksStatuses
Does someone knows if a complete doc exists dot vdsm-client ? the man page 
mentioned below and source code. this is not a public API Thanks,michal Thanks
Frank

 

Le Mercredi, Janvier 25, 2017 12:30 CET, Irit Goihman  a 
écrit:
 Hi All, vdsClient will be removed from master branch today.It is using XMLRPC 
protocol which has been deprecated and replaced by JSON-RPC. A new client for 
vdsm was introduced in 4.1: vdsm-client.This is a simple client that uses 
JSON-RPC protocol which was introduced in ovirt 3.5. The client is not aware of 
the available methods and parameters, and you should consult the schema [1] in 
order to construct the desired command. Future version should parse the schema 
and provide online help.  If you're using vdsClient, we will be happy to assist 
you in migrating to the new vdsm client.   vdsm-client usage: vdsm-client [-h] 
[-a ADDRESS] [-p PORT] [--unsecure] [--timeout TIMEOUT]                   [-f 
FILE] namespace method [name=value [name=value] ...]  Invoking simple methods: 
# vdsm-client Host getVMList['b3f6fa00-b315-4ad4-8108-f73da817b5c5'] For 
invoking methods with many or complex parameters, you can read the parameters 
from a JSON format file: # vdsm-client Lease info -f lease.json where 
lease.json file content is: {                                                   
                                   "lease": {                                   
                                          "sd_id": 
"75ab40e3-06b1-4a54-a825-2df7a40b93b2",                                   
"lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"                             
}                                                                          }   
It is also possible to read parameters from standard input, creating complex 
parameters interactively: # cat 

[ovirt-users] oVirt changing IPs of hosts and engine

2018-04-13 Thread Alex K
Hi all!

I wanted to check from your experience what would be the best approach to
change the IP addresses of the engine and hosts on the management network.
I have a 3 node cluster (in production) on ovirt 4.1 with engine and hosts
resolving through /etc/hosts files on hosts and engine. The hosts have been
added using their fqdn (host.domain) and not IP address, so what I will be
changing is their IP and their domain part at /etc/hosts and to add them
with their new domain at engine.

Example /etc/hosts:
10.10.10.10 engine.domain
10.10.10.9 host1.domain
10.10.10.8 host2.domain
10.10.10.7 host3.domain

I have also gluster storage configured on a separate network which will
remain the same.

How you would go for this with the minimum hassle? Is the engine going to
complain or get confused with these changes?

Many thanx,
Alex
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Hosted Engine won't start, how to debug?

2018-04-13 Thread Martin Sivak
You need to be in global maintenance, but I think you already know that.
Then try updating the vm.conf like you already did and add this line:

devices={device:vnc,type:graphics,deviceId:f1d0394e-b077-4ea6-99e5-b9b6b8fe073c,address:None}

Then restart the VM using hosted-engine commands and try the VNC approach again.

Best regards

Martin Sivak

On Fri, Apr 13, 2018 at 2:35 PM, Thomas Klute  wrote:
> Dear Martin,
>
> thanks for the feedback.
> We already read this and tried it.
> It seems to me that the graphics device was removed from the hosted
> engine by some ovirt release.
>
> If I try to set a console password I see this message:
>
> hosted-engine --add-console-password
> Enter password:
> no graphics devices configured
>
> Furthermore, there is nothing listening on port 5900 after that.
> The HostedEngine qemu process shows a " -display none " as parameter and
> I have no idea where this can be changed.
>
> I already created a /var/run/ovirt-hosted-engine-ha/vm-custom.conf
> containing:
> display=vnc
> kvmEnable=true
>
> But nothing changed.
> I also edited the HostedEngine VM config using virsh and added a vnc
> display:
> /usr/bin/virsh -c
> qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf edit
> HostedEngine
>
> 
>   
> 
> 
>heads='1' primary='yes'/>
>function='0x0'/>
> 
>
> But there is still "display none" passed as command line parameter to
> qemu and thus, I suppose, there's no display.
>
> Any help is appreciated, thanks,
> Thomas
>
>
>> Hi,
>>
>> the serial console will show output if the kernel knows to use it.
>>
>> The VNC approach is also possible and I believe we already have a
>> graphical device present. What you are looking for is probably this
>> (VNC method is described there):
>> https://www.ovirt.org/documentation/how-to/hosted-engine/#handle-engine-vm-boot-problems
>>
>> Best regards
>>
>> --
>> Martin Sivak
>> SLA / oVirt
>>
>> On Fri, Apr 13, 2018 at 11:26 AM, Thomas Klute  wrote:
>>> Dear oVirt Team,
>>>
>>> after trying to reboot a hosted engine setup on oVirt 4.2 the VM won't
>>> come up anymore.
>>> The qemu-kvm process is there but we're unable to access the VM using
>>> - the serial console (simply does not show anything, does not react to
>>> characters typed)
>>> - VNC / Spice because the hosted engine vm.conf does not contain any
>>> graphics device.
>>>
>>> Before trying to reinstall, we'd like to recover and debug what is going on.
>>> We mounted a Centos7 install .iso and started the VM using
>>> hosted-engine --vm-start
>>> --vm-conf=/var/run/ovirt-hosted-engine-ha/vm-custom.conf
>>> But we still have to problem, that the serial console does not show
>>> anything and there is no way to connect using VNC.
>>>
>>> So, what is the recommended way to move forward in such situation?
>>> IMHO the classical way would be to add a graphics device and connect via
>>> VNC?
>>> I did not use the serial console much, up to now. Should the serial
>>> console show any output during boot?
>>>
>>> Thanks for your help,
>>>  Thomas
>>>
>>> --
>>> 
>>>
>>>  Dipl.-Inform. Thomas Klute   kl...@ingenit.com
>>>  Geschäftsführer / CEO
>>>  --
>>>  ingenit GmbH & Co. KG   Tel. +49 (0)231 58 698-120
>>>  Emil-Figge-Strasse 76-80Fax. +49 (0)231 58 698-121
>>>  D-44227 Dortmund   www.ingenit.com
>>>
>>>  Registergericht: Amtsgericht Dortmund, HRA 13 914
>>>  Gesellschafter : Thomas Klute, Marc-Christian Schröer
>>> 
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
> Sollten noch Fragen offen sein, stehen wir Ihnen natürlich jederzeit
> gerne zur Verfügung.
>
> Mit Grüßen aus Dortmund,
>  Thomas Klute
>
> --
> 
>
>  Dipl.-Inform. Thomas Klute   kl...@ingenit.com
>  Geschäftsführer / CEO
>  --
>  ingenit GmbH & Co. KG   Tel. +49 (0)231 58 698-120
>  Emil-Figge-Strasse 76-80Fax. +49 (0)231 58 698-121
>  D-44227 Dortmund   www.ingenit.com
>
>  Registergericht: Amtsgericht Dortmund, HRA 13 914
>  Gesellschafter : Thomas Klute, Marc-Christian Schröer
> 
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] WARN VdsBroker

2018-04-13 Thread Roy Golan
Every VDSM(host) reports the application list per installed vm, every time
the engine asks for the vm statistics. The list probably contains an
illegal value or we fail to convert it , anyhow it doesn't interfere with
the rest of the monitoring process.  Please share the output of this
command from one of your hosts that have running vms:

vdsm-client Host getAllVmStats



On Fri, 13 Apr 2018 at 15:24 Vrgotic, Marko 
wrote:

> Hi oVirt community,
>
>
>
> I have just upgraded from 4.2.0 to 4.2.2 version.
>
>
>
> I noticed a ton of :
>
> *   2018-04-13 11:13:48,857+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-84) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:13:48,857+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-84) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:13:48,857+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-84) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:13:48,857+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-84) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:13:50,056+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-93) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:13:51,482+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:13:51,482+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:13:51,483+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:13:51,483+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:14:03,912+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-24) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:14:03,912+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-24) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:14:03,912+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-24) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:14:03,912+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-24) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:14:05,120+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-50) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:14:06,564+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-60) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:14:06,564+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-60) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:14:06,564+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-60) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
> *2018-04-13 11:14:06,564+02
> WARN  [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
> (EE-ManagedThreadFactory-engineScheduled-Thread-60) [] Failed to convert
> app: [[Ljava.lang.Object;] is not a string*
>
>
>
> Can somebody help me understand or trace where the issue could be?
>
>
>
> Kindly awaiting your reply.
>
>
>
> Marko Vrgotic
>
>
> ___
> Users mailing list
> Users@ovirt.org
> 

Re: [ovirt-users] ?==?utf-8?q? vdsClient is removed and replaced by vdsm-client

2018-04-13 Thread Michal Skrivanek


> On 13 Apr 2018, at 10:14, fsoyer  wrote:
> 
> Hi all,
> I can't find any exhaustive doc for new vdsm-client. My problem actually is a 
> task (export a vm to OVA) blocked.

if you want to interact with that action it would always be best to start with 
engine’s REST API rather than internal host-side API

> I found that I can interact with
> vdsm-client Task getInfo taskID=, and replace getInfo by "stop", BUT : 
> how can I find this UUID ???
> Old "vdsClient -s 0 getAllTasksStatuses" has no equivalent ??

that’s a Host class api, vdsm-client Host getAllTasksStatuses
> 
> Does someone knows if a complete doc exists dot vdsm-client ?

the man page mentioned below and source code. this is not a public API

Thanks,
michal

> Thanks
> Frank
> 
>  
> 
> 
> 
> Le Mercredi, Janvier 25, 2017 12:30 CET, Irit Goihman  a 
> écrit:
>  
>> 
>> Hi All,
>>  
>> vdsClient will be removed from master branch today.
>> It is using XMLRPC protocol which has been deprecated and replaced by 
>> JSON-RPC.
>>  
>> A new client for vdsm was introduced in 4.1: vdsm-client.
>> This is a simple client that uses JSON-RPC protocol which was introduced in 
>> ovirt 3.5.
>>  
>> The client is not aware of the available methods and parameters, and you 
>> should consult 
>> the schema [1] in order to construct the desired command.
>>  
>> Future version should parse the schema and provide online help.
>>  
>>  
>> If you're using vdsClient, we will be happy to assist you in migrating to 
>> the new vdsm client.
>>  
>>  
>>  
>> vdsm-client usage:
>>  
>> vdsm-client [-h] [-a ADDRESS] [-p PORT] [--unsecure] [--timeout TIMEOUT]
>>[-f FILE] namespace method [name=value [name=value] ...]
>>  
>>  
>> Invoking simple methods:
>>  
>> # vdsm-client Host getVMList
>> ['b3f6fa00-b315-4ad4-8108-f73da817b5c5']
>>  
>> For invoking methods with many or complex parameters, you can read the 
>> parameters from a JSON format file:
>>  
>> # vdsm-client Lease info -f lease.json
>>  
>> where lease.json file content is:
>>  
>> {
>>   "lease": { 
>>   
>>   "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",   
>>   
>>   "lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5" 
>>   
>>   }  
>>   
>>   }  
>>  
>> It is also possible to read parameters from standard input, creating complex 
>> parameters interactively:
>>  
>> # cat <>  {   
>>  
>>  "lease": {  
>>  
>>  "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",
>>  
>>  "lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"  
>>  
>>  }   
>>  
>>  }   
>>  
>> EOF  
>>  
>>  
>> Constructing a command from vdsm schema:
>>  
>> Let's take VM.getStats as an example.
>> This is the entry in the schema:
>>  
>> VM.getStats: 
>>
>> added: '3.1' 
>>
>> description: Get statistics about a running virtual machine. 
>>
>> params:  
>>
>> -   description: The UUID of the VM  
>>
>> name: vmID   
>>
>> type: *UUID  
>>
>> return:  
>>
>> description: An array containing a single VmStats record 
>>
>> type:
>>
>> - *VmStats   
>>
>>  
>> namespace: VM
>> method name: getStats
>> params: vmID
>>  
>> The vdsm-client command is:
>>  
>> # vdsm-client VM getStats vmID=b3f6fa00-b315-4ad4-8108-f73da817b5c5
>>  
>>  
>> Invoking getVdsCaps command:
>>  
>> # vdsm-client Host getCapabilities
>>  
>>  
>>  
>> Please consult vdsm-client help and man page for further details and options.
>>  
>>  
>>  
>> [1] https://github.com/oVirt/vdsm/blob/master/lib/api/vdsm-api.yml 
>> 
>>  
>> --
>> Irit Goihman
>> Software Engineer
>> Red Hat Israel Ltd.
> 
> 
> ___
> Users mailing list
> Users@ovirt.org 

Re: [ovirt-users] Hosted Engine won't start, how to debug?

2018-04-13 Thread Thomas Klute
Dear Martin,

thanks for the feedback.
We already read this and tried it.
It seems to me that the graphics device was removed from the hosted
engine by some ovirt release.

If I try to set a console password I see this message:

hosted-engine --add-console-password
Enter password:
no graphics devices configured

Furthermore, there is nothing listening on port 5900 after that.
The HostedEngine qemu process shows a " -display none " as parameter and
I have no idea where this can be changed.

I already created a /var/run/ovirt-hosted-engine-ha/vm-custom.conf
containing:
display=vnc
kvmEnable=true

But nothing changed.
I also edited the HostedEngine VM config using virsh and added a vnc
display:
/usr/bin/virsh -c
qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf edit
HostedEngine

    
  
    
    
  
  
    

But there is still "display none" passed as command line parameter to
qemu and thus, I suppose, there's no display.

Any help is appreciated, thanks,
Thomas


> Hi,
>
> the serial console will show output if the kernel knows to use it.
>
> The VNC approach is also possible and I believe we already have a
> graphical device present. What you are looking for is probably this
> (VNC method is described there):
> https://www.ovirt.org/documentation/how-to/hosted-engine/#handle-engine-vm-boot-problems
>
> Best regards
>
> --
> Martin Sivak
> SLA / oVirt
>
> On Fri, Apr 13, 2018 at 11:26 AM, Thomas Klute  wrote:
>> Dear oVirt Team,
>>
>> after trying to reboot a hosted engine setup on oVirt 4.2 the VM won't
>> come up anymore.
>> The qemu-kvm process is there but we're unable to access the VM using
>> - the serial console (simply does not show anything, does not react to
>> characters typed)
>> - VNC / Spice because the hosted engine vm.conf does not contain any
>> graphics device.
>>
>> Before trying to reinstall, we'd like to recover and debug what is going on.
>> We mounted a Centos7 install .iso and started the VM using
>> hosted-engine --vm-start
>> --vm-conf=/var/run/ovirt-hosted-engine-ha/vm-custom.conf
>> But we still have to problem, that the serial console does not show
>> anything and there is no way to connect using VNC.
>>
>> So, what is the recommended way to move forward in such situation?
>> IMHO the classical way would be to add a graphics device and connect via
>> VNC?
>> I did not use the serial console much, up to now. Should the serial
>> console show any output during boot?
>>
>> Thanks for your help,
>>  Thomas
>>
>> --
>> 
>>
>>  Dipl.-Inform. Thomas Klute   kl...@ingenit.com
>>  Geschäftsführer / CEO
>>  --
>>  ingenit GmbH & Co. KG   Tel. +49 (0)231 58 698-120
>>  Emil-Figge-Strasse 76-80Fax. +49 (0)231 58 698-121
>>  D-44227 Dortmund   www.ingenit.com
>>
>>  Registergericht: Amtsgericht Dortmund, HRA 13 914
>>  Gesellschafter : Thomas Klute, Marc-Christian Schröer
>> 
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>

Sollten noch Fragen offen sein, stehen wir Ihnen natürlich jederzeit
gerne zur Verfügung.

Mit Grüßen aus Dortmund,
 Thomas Klute

-- 


 Dipl.-Inform. Thomas Klute   kl...@ingenit.com
 Geschäftsführer / CEO
 --
 ingenit GmbH & Co. KG   Tel. +49 (0)231 58 698-120
 Emil-Figge-Strasse 76-80Fax. +49 (0)231 58 698-121
 D-44227 Dortmund   www.ingenit.com

 Registergericht: Amtsgericht Dortmund, HRA 13 914
 Gesellschafter : Thomas Klute, Marc-Christian Schröer


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


[ovirt-users] WARN VdsBroker

2018-04-13 Thread Vrgotic, Marko
Hi oVirt community,

I have just upgraded from 4.2.0 to 4.2.2 version.

I noticed a ton of :
   2018-04-13 11:13:48,857+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-84) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:13:48,857+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-84) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:13:48,857+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-84) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:13:48,857+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-84) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:13:50,056+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-93) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:13:51,482+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:13:51,482+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:13:51,483+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:13:51,483+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:14:03,912+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-24) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:14:03,912+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-24) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:14:03,912+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-24) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:14:03,912+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-24) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:14:05,120+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-50) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:14:06,564+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-60) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:14:06,564+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-60) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:14:06,564+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-60) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string
2018-04-13 11:14:06,564+02 WARN  
[org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] 
(EE-ManagedThreadFactory-engineScheduled-Thread-60) [] Failed to convert app: 
[[Ljava.lang.Object;] is not a string

Can somebody help me understand or trace where the issue could be?

Kindly awaiting your reply.

Marko Vrgotic

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


Re: [ovirt-users] I broke my ovirt real good....

2018-04-13 Thread Alexander Wels
On Thursday, April 12, 2018 6:26:07 PM EDT ~Stack~ wrote:
> Greetings,
> 
> So I did a over-confident-admin-makes-rookie-mistake. I changed a bunch
> of things all back-to-back and thus don't actually know what broke. :-D
> 
> The only two real "big" changes were:
> * Upgrade from 4.2.1 to 4.2.2
> * change my ovirtmgmt network
> 
> The update I followed the upgrade procedures and I thought it all went
> pretty well. Because I am moving it from a testing into what I hope will
> be a more heavily used environment, I changed my ovirtmgmt network from
> 192.168.100.0/24 to 192.168.101.0/24 via the web-gui.
> 
> That was a touch tricker than just a change as I had to poke the
> management engine host to be reachable on both network for a while, then
> it just seemed OK.
> 
> What's happening is:
> * I can no longer migrate a vm from one host to the other.
> * If I try to do a "reinstall" it dies.
> * There is some serious network lag between my hosts on a 10Gb network.
> * I've got all kinds of python2.4 failures in my vdsm and mom logs.
> 
> Those are least the biggies.
> 
> So while I was planning on moving this to a more active use case, right
> now - it is all still my play ground. I would REALLY hate to lose the
> VM's but everything else can go and be rebuilt.
> 
> Given that I've somehow really broke this system pretty good, would it
> be more advisable to blow away and rebuild it ALL or can I simply delete
> the hypervisor hosts and rebuild them?
> 
> Thoughts?
> 
> Thanks!
> ~Stack~

As long as you don't destroy the data on your data domain you can rebuild the 
engine and hosts and then import the existing data domain without too many 
issues. I have destroyed my engine database many times, and I am still using 
the same VMs from the same data domain.

Here is what I do when I mess up my database to the point I have to make a new 
one:

1. Recreate the engine and database, so that I have basically have an empty 
engine with no hosts and VMs.
1.1 (Optional) make a new DC that is not default. and add a cluster.
2. Add my hosts (I only have 2 so that is quick and easy).
3. Add a throw away data domain (This is needed to get the DC up so I can 
import the existing data domain).
4. Import (NOT new, import) the existing data domain.
5. Do to Storage->Storage Domains->VM import and import the VMs I want.
6. Same for templates and disks if needed.
7. After you have imported the VMs/Templates/Disks you can detach and remove 
the throw away data domain and the one you imported becomes the master domain.

Note if you want to move VMs between your play ground and more serious system 
you can simply detach your data domain from the play ground, then attach it to 
the serious engine (so you have 2 engines, one play ground and one serious) 
and import which VMs you want. That way you won't run into issues with 
configuring networks and stuff like you experienced.



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


Re: [ovirt-users] Hosted Engine won't start, how to debug?

2018-04-13 Thread Martin Sivak
Hi,

the serial console will show output if the kernel knows to use it.

The VNC approach is also possible and I believe we already have a
graphical device present. What you are looking for is probably this
(VNC method is described there):
https://www.ovirt.org/documentation/how-to/hosted-engine/#handle-engine-vm-boot-problems

Best regards

--
Martin Sivak
SLA / oVirt

On Fri, Apr 13, 2018 at 11:26 AM, Thomas Klute  wrote:
> Dear oVirt Team,
>
> after trying to reboot a hosted engine setup on oVirt 4.2 the VM won't
> come up anymore.
> The qemu-kvm process is there but we're unable to access the VM using
> - the serial console (simply does not show anything, does not react to
> characters typed)
> - VNC / Spice because the hosted engine vm.conf does not contain any
> graphics device.
>
> Before trying to reinstall, we'd like to recover and debug what is going on.
> We mounted a Centos7 install .iso and started the VM using
> hosted-engine --vm-start
> --vm-conf=/var/run/ovirt-hosted-engine-ha/vm-custom.conf
> But we still have to problem, that the serial console does not show
> anything and there is no way to connect using VNC.
>
> So, what is the recommended way to move forward in such situation?
> IMHO the classical way would be to add a graphics device and connect via
> VNC?
> I did not use the serial console much, up to now. Should the serial
> console show any output during boot?
>
> Thanks for your help,
>  Thomas
>
> --
> 
>
>  Dipl.-Inform. Thomas Klute   kl...@ingenit.com
>  Geschäftsführer / CEO
>  --
>  ingenit GmbH & Co. KG   Tel. +49 (0)231 58 698-120
>  Emil-Figge-Strasse 76-80Fax. +49 (0)231 58 698-121
>  D-44227 Dortmund   www.ingenit.com
>
>  Registergericht: Amtsgericht Dortmund, HRA 13 914
>  Gesellschafter : Thomas Klute, Marc-Christian Schröer
> 
>
> ___
> 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] Engine reports

2018-04-13 Thread Peter Hudec
thanks, problem was with the selinux. I applied the permission on the
/var/lib/elasticsearch once again.

Deployment is done ;)

Right now mi browser is complaining about certificate on SSO.
When I try to reach https://kibana.
I'm redirected to SSO

https:// :8443/oauth/authorize?...

An error occurred during a connection to metrics.ovirt.cnc.sk:8443. You
have received an invalid certificate. Please contact the server
administrator or email correspondent and give them the following
information: Your certificate contains the same serial number as another
certificate issued by the certificate authority. Please get a new
certificate containing a unique serial number. Error code:
SEC_ERROR_REUSED_ISSUER_AND_SERIAL


Peter

On 12/04/2018 19:47, Rich Megginson wrote:
> sudo ls -alrtF -Z /var/lib/elasticsearch
> 
> oc logs logging-es-data-master-z6zbv4v2-2-deploy
> 
> oc describe pod logging-es-data-master-z6zbv4v2-2-deploy
> 
> sudo grep type=AVC /var/log/audit/audit.log | tail
> 
> On 04/12/2018 02:32 AM, Peter Hudec wrote:
>> back to this issue.
>>
>> something went wrong ;( The status command got error. I'm not familiar
>> with openshift, so the log processing will took me a while.
>>
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc project logging
>> Already on project "logging" on server
>> "https://metrics.ovirt.cnc.sk:8443;.
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc adm policy add-scc-to-user
>> hostmount-anyuid \
>>>    system:serviceaccount:logging:aggregated-logging-elasticsearch
>> scc "hostmount-anyuid" added to:
>> ["system:serviceaccount:logging:aggregated-logging-elasticsearch"]
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc rollout cancel $( oc get -n
>> logging dc -l component=es -o name )
>> No rollout is in progress (latest rollout #2 failed 3 days ago)
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc rollout latest $( oc get -n
>> logging dc -l component=es -o name )
>> deploymentconfig "logging-es-data-master-z6zbv4v2" rolled out
>> [PROD] r...@dipostat01.cnc.sk: ~ #  oc rollout status -w $( oc get -n
>> logging dc -l component=es -o name )
>> Waiting for rollout to finish: 0 of 1 updated replicas are available...
>> error: replication controller "logging-es-data-master-z6zbv4v2-3" has
>> failed progressing
>>
>>
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
>> NAME   READY STATUS    RESTARTS
>>   AGE
>> logging-curator-1-c894f    1/1   Running  
>> 904    5d
>> logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error
>> 0  3d
>> logging-fluentd-x9vzs  1/1   Running  
>> 1  5d
>> logging-kibana-1-6bvvw 2/2   Running  
>> 2  5d
>> logging-mux-1-xxmdj    1/1   Running  
>> 1  5d
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
>> NAME   READY STATUS    RESTARTS
>>   AGE
>> logging-curator-1-c894f    1/1   Running  
>> 904    5d
>> logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error
>> 0  3d
>> logging-fluentd-x9vzs  1/1   Running  
>> 1  5d
>> logging-kibana-1-6bvvw 2/2   Running  
>> 2  5d
>> logging-mux-1-xxmdj    1/1   Running  
>> 1  5d
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
>> NAME   READY STATUS    RESTARTS
>>   AGE
>> logging-curator-1-c894f    1/1   Running  
>> 904    5d
>> logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error
>> 0  3d
>> logging-fluentd-x9vzs  1/1   Running  
>> 1  5d
>> logging-kibana-1-6bvvw 2/2   Running  
>> 2  5d
>> logging-mux-1-xxmdj    1/1   Running  
>> 1  5d
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc get svc
>> NAME    TYPE    CLUSTER-IP   EXTERNAL-IP
>> PORT(S) AGE
>> logging-es  ClusterIP   172.30.249.174   
>> 9200/TCP    5d
>> logging-es-cluster  ClusterIP   172.30.114.201   
>> 9300/TCP    5d
>> logging-es-prometheus   ClusterIP   172.30.203.113   
>> 443/TCP 5d
>> logging-kibana  ClusterIP   172.30.29.192    
>> 443/TCP 5d
>> logging-mux ClusterIP   172.30.170.158   192.168.16.17
>> 24284/TCP   5d
>>
>>
>> On 07/04/2018 01:09, Rich Megginson wrote:
>>> Great!
>>>
>>> On 04/06/2018 04:43 PM, Peter Hudec wrote:
 Ansible playbook finished OK. The next step after weekend.

  thanks
  Peter

 On 06/04/2018 23:34, Rich Megginson wrote:
> On 04/06/2018 03:08 PM, Peter Hudec wrote:
>> Hi,
>>
>> https://tools.apps.hudecof.net/paste/view/1d493d52
>>
>> The difference is
>> - I used latest ansible 2.5 from PIPY source, since the RPM
>> package do
>> not fit requirements
>> - I used GIT repo 

Re: [ovirt-users] I broke my ovirt real good....

2018-04-13 Thread ~Stack~
On 04/13/2018 03:02 AM, Michael Mortensen (MCMR) wrote:
> Hi Stack,
> 
> Do you use FQDN? Did you perhaps hit this one 
> https://www.ovirt.org/blog/2016/05/modify-ifcfg-files/ ? The discussion in 
> this bug report may be of assistance in that case: 
> https://bugzilla.redhat.com/show_bug.cgi?id=1252534

That looks very interesting! I will investigate that.

> If you've stored the VM disks and templates and whatnot on a network share 
> like NFS, you should be able to start all over and import your old (current) 
> storage domains and start using your templates etc.

I am currently using NFS. I will see how this networking issue you
pointed me to works out, then maybe rebuild.

Thank you for the assistance!
~Stack~



signature.asc
Description: OpenPGP digital signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] OVN between two different datacenters with different networks

2018-04-13 Thread Vasily Lamykin
Very big thanks, In your solution I want fix only one...
" tunneling-IP is IP-of-host-of-engine-2"
For me - works variant is IP of host2 , which can provides access to engine1

Василий Ламыкин
Старший инженер по эксплуатации сетевых сервисов Центра управления сетью Столица
Единый Центр управления сетью
+7 (925) 696-1032
-Original Message-
From: Dominik Holler [mailto:dhol...@redhat.com] 
Sent: Tuesday, April 10, 2018 6:08 PM
To: Vasily Lamykin (GNOC) 
Cc: users@ovirt.org
Subject: Re: [ovirt-users] OVN between two different datacenters with different 
networks

On Tue, 10 Apr 2018 11:48:50 +
Vasily Lamykin  wrote:

> Hi, all
> I try to configure ovn in engine, what I do by step:
> 1.Created network test1 with external ovn provider on engine1 
> 2.Created subnet for this network 3.Connect engine2 to engine1 ovn 
> provider(through “add provider”) 4.Successfully imported network test1 
> on engine2 5.I see subnet’s on all engines 6.Created 2 VM with nic in 
> network test1 on both engines 7.Assigned ips from one 
> subnet(192.168.10.0/24) to all VMs
> 

The subnet is used to configure OVN's internal DHCP server.
This means you use DHCP to assign IPs to the vNICs, which is already a good 
test if the VM is connected as expected.

> Expected results: VM from engine1 can ping VM from engine2 in same 
> subnet in ovn network test1
> 
> Now, I don’t have ping ability between two VMs
> 
> ovn-nbctl show
> switch 54beaa3c-de8f-435f-b132-8542ddeb4b4b (test-ovn-phys)
> port b580d44d-e616-42dd-9e17-63983d0f91e5
> addresses: ["00:1a:4a:16:01:01 dynamic"]
> port cfd5f32c-00a7-419e-8bbe-27518a4c74dc
> addresses: ["00:1a:4a:16:01:00 dynamic"]
> 
> node from engine1 with testVM
> vnet0:  mtu 1500 qdisc pfifo_fast 
> master ovs-system state UNKNOWN qlen 1000 link/ether
> fe:1a:4a:16:01:01 brd ff:ff:ff:ff:ff:ff inet6
> fe80::fc1a:4aff:fe16:101/64 scope link valid_lft forever preferred_lft 
> forever
> 
> node from engine2 with testVM
> vnet0:  mtu 1500 qdisc pfifo_fast 
> master ovs-system state UNKNOWN qlen 1000 link/ether
> fe:1a:4a:16:01:00 brd ff:ff:ff:ff:ff:ff inet6
> fe80::fc1a:4aff:fe16:100/64 scope link valid_lft forever preferred_lft 
> forever
> 
> How can I do ovn connection? What I did wrong?
> 

Please note that per host only a single OVN central is supported!

Please check via
sudo ovn-sbctl show
on engine1 if both hosts are connected to OVN central engine1.

Probably the host of engine2 is configured to use engine2 as it's OVN central. 
Probable the host of engine2 has to be connected to OVN central engine1 and the 
tunneling interface might require some configuration.

Both is handled by executing
/usr/libexec/ovirt-provider-ovn/setup_ovn_controller.sh \  IP-central 
tunneling-IP key_file cert_file ca_file on the host.

Probably
IP-central is IP-of-engine1
tunneling-IP is IP-of-host-of-engine-2
and key_file cert_file ca_file has to be stolen from host of engine1 and copied 
in a new location on host2 and configured on host2.


> 
> 
> Информация в этом сообщении предназначена исключительно для конкретных 
> лиц, которым она адресована. В сообщении может содержаться 
> конфиденциальная информация, которая не может быть раскрыта или 
> использована кем-либо, кроме адресатов. Если вы не адресат этого 
> сообщения, то использование, переадресация, копирование или 
> распространение содержания сообщения или его части незаконно и 
> запрещено. Если Вы получили это сообщение ошибочно, пожалуйста, 
> незамедлительно сообщите отправителю об этом и удалите со всем 
> содержимым само сообщение и любые возможные его копии и приложения.
> 
> The information contained in this communication is intended solely for 
> the use of the individual or entity to whom it is addressed and others 
> authorized to receive it. It may contain confidential or legally 
> privileged information. The contents may not be disclosed or used by 
> anyone other than the addressee. If you are not the intended 
> recipient(s), any use, disclosure, copying, distribution or any action 
> taken or omitted to be taken in reliance on it is prohibited and may 
> be unlawful. If you have received this communication in error please 
> notify us immediately by responding to this email and then delete the 
> e-mail and all attachments and any copies thereof.
> 
> -

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


[ovirt-users] Hosted Engine won't start, how to debug?

2018-04-13 Thread Thomas Klute
Dear oVirt Team,

after trying to reboot a hosted engine setup on oVirt 4.2 the VM won't
come up anymore.
The qemu-kvm process is there but we're unable to access the VM using
- the serial console (simply does not show anything, does not react to
characters typed)
- VNC / Spice because the hosted engine vm.conf does not contain any
graphics device.

Before trying to reinstall, we'd like to recover and debug what is going on.
We mounted a Centos7 install .iso and started the VM using
hosted-engine --vm-start
--vm-conf=/var/run/ovirt-hosted-engine-ha/vm-custom.conf
But we still have to problem, that the serial console does not show
anything and there is no way to connect using VNC.

So, what is the recommended way to move forward in such situation?
IMHO the classical way would be to add a graphics device and connect via
VNC?
I did not use the serial console much, up to now. Should the serial
console show any output during boot?

Thanks for your help,
 Thomas

-- 


 Dipl.-Inform. Thomas Klute   kl...@ingenit.com
 Geschäftsführer / CEO
 --
 ingenit GmbH & Co. KG   Tel. +49 (0)231 58 698-120
 Emil-Figge-Strasse 76-80Fax. +49 (0)231 58 698-121
 D-44227 Dortmund   www.ingenit.com

 Registergericht: Amtsgericht Dortmund, HRA 13 914
 Gesellschafter : Thomas Klute, Marc-Christian Schröer


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


Re: [ovirt-users] Recovering oVirt-Engine with a backup before upgrading to 4.2

2018-04-13 Thread Sven Achtelik
Hi All, 

I got my stuff up and running again. I works like described in the manual and I 
used some extra hardware to jumpstart this. I'm now back on my hosted Engine 
4.1.9 with 3 Hosts running it. The Engine is running on the appliance that is 
pulled by the deployment tool and after having everything stable again I 
thought of upgrading to 4.2. Thing is that this is just not working with the 
appliance because of some issue when upgrading Postgres inside. Looking at the 
logs I found this: 

Creating dump of database schemas
  engine
  ovirt_engine_history
  postgres
  template1
ok

encodings for database "postgres" do not match:  old "SQL_ASCII", new "UTF8"
Failure, exiting
--

After some research I found something here 
https://bugzilla.redhat.com/show_bug.cgi?id=1525976, but I'm not sure what to 
do with that Information. I used the appliance and didn't do anything manual in 
the complete process and I'm wondering why I'm getting this issue now ? Could 
someone advice on how to proceed ? 

Thank you, 
Sven 

> -Ursprüngliche Nachricht-
> Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag
> von Sven Achtelik
> Gesendet: Mittwoch, 28. März 2018 18:28
> An: Yedidyah Bar David
> Cc: users@ovirt.org
> Betreff: Re: [ovirt-users] Recovering oVirt-Engine with a backup before
> upgrading to 4.2
> 
> 
> 
> > -Ursprüngliche Nachricht-
> > Von: Yedidyah Bar David [mailto:d...@redhat.com]
> > Gesendet: Mittwoch, 28. März 2018 10:06
> > An: Sven Achtelik
> > Cc: users@ovirt.org
> > Betreff: Re: [ovirt-users] Recovering oVirt-Engine with a backup
> > before upgrading to 4.2
> >
> > On Tue, Mar 27, 2018 at 9:14 PM, Sven Achtelik
> > 
> > wrote:
> > > Hi All,
> > >
> > >
> > >
> > > I’m still facing issues with my HE engine. Here are the steps that I
> > > took to end up in this situation:
> > >
> > >
> > >
> > > - Update Engine from 4.1.7 to 4.1.9
> > >
> > > o   That worked as expected
> > >
> > > - Automatic Backup of Engine DB in the night
> > >
> > > - Upgraded Engine from 4.1.9 to 4.2.1
> > >
> > > o   That worked fine
> > >
> > > - Noticed Issues with the HA support for HE
> > >
> > > o   Cause was not having the latest ovirt-ha agent/broker version on hosts
> > >
> > > - After updating the first host with the latest packages for the
> > > Agent/Broker engine was started twice
> > >
> > > o   As a result the Engine VM Disk was corrupted and there is no Backup of
> > > the Disk
> > >
> > > o   There is also no Backup of the Engine DB with version 4.2
> > >
> > > - VM disk was repaired with fsck.ext4, but DB is corrupt
> > >
> > > o   Can’t restore the Engine DB because the Backup DB from Engine V 4.1
> > >
> > > - Rolled back all changes on Engine VM to 4.1.9 and imported 
> > > Backup
> > >
> > > o   Checked for HA VMs to set as disabled and started the Engine
> > >
> > > - Login is fine but the Engine is having trouble picking up and
> > > information from the Hosts
> > >
> > > o   No information on running VMs or hosts status
> > >
> > > - Final Situation
> > >
> > > o   2 Hosts have VMs still running and I can’t stop those
> > >
> > > o   I still have the image of my corrupted Engine VM (v4.2)
> > >
> > >
> > >
> > > Since there were no major changes after upgrading from 4.1 to 4.2,
> > > would it be possible to manually restore the 4.1 DB to the 4.2
> > > Engine VM to this up and running again or are there modifications
> > > made to the DB on upgrading that are relevant for this ?
> >
> > engine-backup requires restoring to the same version used to take the
> > backup, with a single exception - on 4.0, it can restore 3.6.
> >
> > It's very easy to patch it to allow also 4.1->4.2, search inside it
> > for "VALID_BACKUP_RESTORE_PAIRS". However, I do not think anyone ever
> > tested this, so no idea might break. In 3.6->4.0 days, we did have to
> > fix a few other things, notably apache httpd and iptables->firewalld:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1318580
> >
> > > All my work on rolling back to 4.1.9 with the DB restore failed as
> > > the Engine is not capable of picking up information from the hosts.
> >
> > No idea why, but not sure it's related to your restore flow.
> >
> > > Lessons learned is to always make a copy/snapshot of the engine VM
> > > disk before upgrading anything.
> >
> > If it's a hosted-engine, this isn't supported - see my reply on the
> > list ~ 1 hour ago...
> >
> > > What are my options on getting
> > > back to a working environment ? Any help or hint is greatly appreciated.
> >
> > Restore again with either methods - what you tried, or patching
> > engine- backup and restore directly into 4.2 - and if the engine fails
> > to talk to the hosts, try to debug/fix this.
> >
> > If you suspect corruption more severe 

Re: [ovirt-users] ?==?utf-8?q? vdsClient is removed and replaced by vdsm-client

2018-04-13 Thread fsoyer

Hi all,
I can't find any exhaustive doc for new vdsm-client. My problem actually is a 
task (export a vm to OVA) blocked.
I found that I can interact with
vdsm-client Task getInfo taskID=, and replace getInfo by "stop", BUT : 
how can I find this UUID ???
Old "vdsClient -s 0 getAllTasksStatuses" has no equivalent ??

Does someone knows if a complete doc exists dot vdsm-client ?
Thanks
Frank

 

Le Mercredi, Janvier 25, 2017 12:30 CET, Irit Goihman  a 
écrit:
 Hi All, vdsClient will be removed from master branch today.It is using XMLRPC 
protocol which has been deprecated and replaced by JSON-RPC. A new client for 
vdsm was introduced in 4.1: vdsm-client.This is a simple client that uses 
JSON-RPC protocol which was introduced in ovirt 3.5. The client is not aware of 
the available methods and parameters, and you should consult the schema [1] in 
order to construct the desired command. Future version should parse the schema 
and provide online help.  If you're using vdsClient, we will be happy to assist 
you in migrating to the new vdsm client.   vdsm-client usage: vdsm-client [-h] 
[-a ADDRESS] [-p PORT] [--unsecure] [--timeout TIMEOUT]                   [-f 
FILE] namespace method [name=value [name=value] ...]  Invoking simple methods: 
# vdsm-client Host getVMList['b3f6fa00-b315-4ad4-8108-f73da817b5c5'] For 
invoking methods with many or complex parameters, you can read the parameters 
from a JSON format file: # vdsm-client Lease info -f lease.json where 
lease.json file content is: {                                                   
                                   "lease": {                                   
                                          "sd_id": 
"75ab40e3-06b1-4a54-a825-2df7a40b93b2",                                   
"lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"                             
}                                                                          }   
It is also possible to read parameters from standard input, creating complex 
parameters interactively: # cat 

Re: [ovirt-users] I broke my ovirt real good....

2018-04-13 Thread Michael Mortensen (MCMR)
Hi Stack,

Do you use FQDN? Did you perhaps hit this one 
https://www.ovirt.org/blog/2016/05/modify-ifcfg-files/ ? The discussion in this 
bug report may be of assistance in that case: 
https://bugzilla.redhat.com/show_bug.cgi?id=1252534

If you've stored the VM disks and templates and whatnot on a network share like 
NFS, you should be able to start all over and import your old (current) storage 
domains and start using your templates etc.


Best wishes
// Mike


-Original Message-
From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of 
~Stack~
Sent: 13. april 2018 00:26
To: users 
Subject: [ovirt-users] I broke my ovirt real good

Greetings,

So I did a over-confident-admin-makes-rookie-mistake. I changed a bunch of 
things all back-to-back and thus don't actually know what broke. :-D

The only two real "big" changes were:
* Upgrade from 4.2.1 to 4.2.2
* change my ovirtmgmt network

The update I followed the upgrade procedures and I thought it all went pretty 
well. Because I am moving it from a testing into what I hope will be a more 
heavily used environment, I changed my ovirtmgmt network from
192.168.100.0/24 to 192.168.101.0/24 via the web-gui.

That was a touch tricker than just a change as I had to poke the management 
engine host to be reachable on both network for a while, then it just seemed OK.

What's happening is:
* I can no longer migrate a vm from one host to the other.
* If I try to do a "reinstall" it dies.
* There is some serious network lag between my hosts on a 10Gb network.
* I've got all kinds of python2.4 failures in my vdsm and mom logs.

Those are least the biggies.

So while I was planning on moving this to a more active use case, right now - 
it is all still my play ground. I would REALLY hate to lose the VM's but 
everything else can go and be rebuilt.

Given that I've somehow really broke this system pretty good, would it be more 
advisable to blow away and rebuild it ALL or can I simply delete the hypervisor 
hosts and rebuild them?

Thoughts?

Thanks!
~Stack~


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


Re: [ovirt-users] [ANN] oVirt 4.2.3 First Release Candidate is now available

2018-04-13 Thread Michal Skrivanek


> On 12 Apr 2018, at 16:21, Lev Veyde  wrote:
> 
> The oVirt Project is pleased to announce the availability of the oVirt 4.2.3 
> First Release Candidate, as of April 12th, 2018
> 
> This update is a release candidate of the third in a series of stabilization 
> updates to the 4.2
> series.
> This is pre-release software. This pre-release should not to be used in 
> production.
> 
> This release is available now for:
> * Red Hat Enterprise Linux 7.4 or later
> * CentOS Linux (or similar) 7.4 or later
> 
> This release supports Hypervisor Hosts running:
> * Red Hat Enterprise Linux 7.4 or later

on RHEL it requires the recent 7.5

> * CentOS Linux (or similar) 7.4 or later
> * oVirt Node 4.2
> 
> See the release notes [1] for installation / upgrade instructions and
> a list of new features and bugs fixed.
> 
> Notes:
> - oVirt Appliance is available
> - oVirt Node is available [2]
> 
> Additional Resources:
> * Read more about the oVirt 4.2.3 release 
> highlights:http://www.ovirt.org/release/4. 
> 2 . 
> 3 / 
> 
> * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt 
> 
> * Check out the latest project news on the oVirt 
> blog:http://www.ovirt.org/blog/ 
> 
> [1] http://www.ovirt.org/release/4. 2 
> . 3 
> / 
> [2] http://resources.ovirt.org/pub/ovirt-4. 
> 2 
> -pre 
> /iso/ 
> 
> -- 
> 
> LEV VEYDE
> SOFTWARE ENGINEER, RHCE | RHCVA | MCITP
> Red Hat Israel
> 
>  
> l...@redhat.com  | lve...@redhat.com 
>   
> TRIED. TESTED. TRUSTED. 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

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