- Users - oVirt List Archives

Limitation in using Ovirt SSO Token
by Hari Prasanth Loganathan 08 Mar '18

08 Mar '18

Hi Team, I would like to know, Is there any limitation in using the same sso token for multiple request. I observe that when I use the same sso token for more than 900 HTTP Rest request, the application went down. Is there any limitation in using same SSO token? I could see that my status is showing as ACTIVE and memory and CPU seem fine. Still, the oVirt is not reachable and I need to restart it to access again. sudo systemctl status ovirt-engine.service -l ● ovirt-engine.service - oVirt Engine Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2018-03-08 19:15:10 IST; 30s ago Main PID: 10370 (ovirt-engine.py) CGroup: /system.slice/ovirt-engine.service ├─10370 /usr/bin/python /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify start └─10423 ovirt-engine -server -XX:+TieredCompilation -Xms5961M -Xmx5961M -Djava.awt.headless=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djsse.enableSNIExtension=false -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/ovirt-engine/dump -Djava.util.logging.manager=org.jboss.logmanager -Dlogging.configuration=file:///var/lib/ovirt-engine/jboss_runtime/config/ovirt-engine-logging.properties -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.config=ovirt-engine -Djboss.home.dir=/usr/share/ovirt-engine-wildfly -Djboss.server.base.dir=/usr/share/ovirt-engine -Djboss.server.data.dir=/var/lib/ovirt-engine -Djboss.server.log.dir=/var/log/ovirt-engine -Djboss.server.config.dir=/var/lib/ovirt-engine/jboss_runtime/config -Djboss.server.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp -Djboss.controller.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp -jar /usr/share/ovirt-engine-wildfly/jboss-modules.jar -mp /usr/share/ovirt-engine/modules/common:/usr/share/ovirt-engine-extension-aaa-jdbc/modules:/usr/share/ovirt-engine-wildfly/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -c ovirt-engine.xml Mar 08 19:15:10 ovirtengine.localdomain systemd[1]: Starting oVirt Engine... Mar 08 19:15:10 ovirtengine.localdomain ovirt-engine.py[10370]: 2018-03-08 19:15:10,228+0530 ovirt-engine: INFO _detectJBossVersion:187 Detecting JBoss version. Running: /usr/lib/jvm/jre/bin/java ['ovirt-engine-version', '-server', '-XX:+TieredCompilation', '-Xms5961M', '-Xmx5961M', '-Djava.awt.headless=true', '-Dsun.rmi.dgc.client.gcInterval=3600000', '-Dsun.rmi.dgc.server.gcInterval=3600000', '-Djsse.enableSNIExtension=false', '-XX:+HeapDumpOnOutOfMemoryError', '-XX:HeapDumpPath=/var/log/ovirt-engine/dump', '-Djava.util.logging.manager=org.jboss.logmanager', '-Dlogging.configuration=file:///var/lib/ovirt-engine/jboss_runtime/config/ovirt-engine-logging.properties', '-Dorg.jboss.resolver.warning=true', '-Djboss.modules.system.pkgs=org.jboss.byteman', '-Djboss.server.default.config=ovirt-engine', '-Djboss.home.dir=/usr/share/ovirt-engine-wildfly', '-Djboss.server.base.dir=/usr/share/ovirt-engine', '-Djboss.server.data.dir=/var/lib/ovirt-engine', '-Djboss.server.log.dir=/var/log/ovirt-engine', '-Djboss.server.config.dir=/var/lib/ovirt-engine/jboss_runtime/config', '-Djboss.server.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp', '-Djboss.controller.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp', '-jar', '/usr/share/ovirt-engine-wildfly/jboss-modules.jar', '-mp', '/usr/share/ovirt-engine/modules/common:/usr/share/ovirt-engine-extension-aaa-jdbc/modules:/usr/share/ovirt-engine-wildfly/modules', '-jaxpmodule', 'javax.xml.jaxp-provider', 'org.jboss.as.standalone', '-v'] Mar 08 19:15:10 ovirtengine.localdomain ovirt-engine.py[10370]: 2018-03-08 19:15:10,668+0530 ovirt-engine: INFO _detectJBossVersion:207 Return code: 1, | stdout: '[u'WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final)'], | stderr: '[]' Mar 08 19:15:10 ovirtengine.localdomain systemd[1]: Started oVirt Engine. Anyhelp would be Appreaciated. Thanks, Hari -- DISCLAIMER The information in this e-mail is confidential and may be subject to legal privilege. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you have received this communication in error, please address with the subject heading "Received in error," send to it(a)msystechnologies.com, then delete the e-mail and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. The views, opinions, conclusions and other information expressed in this electronic mail and any attachments are not given or endorsed by the company unless otherwise indicated by an authorized representative independent of this message. MSys cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses, though all reasonable precautions have been taken to ensure no viruses are present in this e-mail. As our company cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments we recommend that you subject these to your virus checking procedures prior to use

1 0

ovirt 4.2 gluster configuration
by Edoardo Mazza 08 Mar '18

08 Mar '18

Hi all, Scenario: 3 nodes each with 3 interfaces: 1 for management, 1 for gluster, 1 for VMs Management interface has it own name and its own ip (es. name = ov1, ip= 192.168.1.1/24), the same is for gluster interface which has its own name and its own ip (es. name = gluster1, ip= 192.168.2.1/24). When configuring bricks from Ovirt Management tools I get the error: "no uuid for the name ov1". Network for gluster communication has been defined on network/interface gluster1. What's wrong with this configuration? Thanks in advance. Edoardo

2 1

Pre-snapshot scripts to run before live snapshot
by Gianluca Cecchi 08 Mar '18

08 Mar '18

Hello, this thread last year (started by me... ;-) was very useful in different aspects involved http://lists.ovirt.org/pipermail/users/2017-March/080322.html We did cover memory save or not and fsfreeze automatically done by guest agent if installed inside the VM. What about pre-snapshot scripts/operations to run inside guest, to have application consistency? Eg if I have a database inside the VM and I have scripted my backup job involving live-snapshot (eg with the backup.py utility of the thread) Can I leverage this kind of functionality with the oVirt guest agent? Or is it mandatory to consider a remote connection to the VM (via ssh or what for windows?) and execute the script/command/bat file? What are you curently doing in this respect? Thanks, Gianluca

2 4

Tunable parameters in ovirt engine
by Hari Prasanth Loganathan 08 Mar '18

08 Mar '18

Hi Team, *Description of problem:* I am trying to achieve 1000 concurrent request to oVirt. What are the tunable parameters to achieve this? I tried to perform the benchmarking for ovirt engine using Apache benchmark using the same SSO token. ab -n 1000 -c 500 -k -H "accept: application/json" -H "Authorization: Bearer SSOTOKEN" https://172.30.56.70/ovirt-engine/ <https://172.30.56.70/ovirt-engine/api/vms/5440271b-afb3-48bb-9ff1-076fc07eb…> When the number of concurrent request is 500, we are getting more than 100 failures with the following error, SSL read failed (1) - closing connection 139620982339352:error: NOTE: It is scaling for concurrent request below 500. I used the profiler to get the memory and CPU and it seems very less, PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 30413 ovirt 20 0 4226664 882396 6776 S 126.0 23.0 27:48.53 java Configuration of the machine in which Ovirt is deployed : RAM - 4GB, Hard disk - 100GB, core processor - 2, OS - Cent7.x. In which 2GB is allocated to oVirt. Version-Release number of selected component (if applicable): 4.2.2 How reproducible: If the number of concurrent requests are above 500, we are easily facing this issue. *Actual results:* SSL read failed (1) - closing connection 139620982339352:error: *Expected results:* Request success. Thanks, Hari -- DISCLAIMER The information in this e-mail is confidential and may be subject to legal privilege. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you have received this communication in error, please address with the subject heading "Received in error," send to it(a)msystechnologies.com, then delete the e-mail and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. The views, opinions, conclusions and other information expressed in this electronic mail and any attachments are not given or endorsed by the company unless otherwise indicated by an authorized representative independent of this message. MSys cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses, though all reasonable precautions have been taken to ensure no viruses are present in this e-mail. As our company cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments we recommend that you subject these to your virus checking procedures prior to use

3 14

Invitation: oVirt System Test Hackathon @ Tue Mar 13, 2018 (users@ovirt.org)
by sbonazzo＠redhat.com 08 Mar '18

08 Mar '18

You have been invited to the following event. Title: oVirt System Test Hackathon Please join us in an ovirt-system-tests hackathon pushing new tests and improving existing ones for testing Hosted Engine. Git repo is available: https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;a=summary Integration, Node and CI team will be available for helping in the effort and reviewing patches. When: Tue Mar 13, 2018 Where: #ovirt IRC channel Calendar: users(a)ovirt.org Who: * sbonazzo(a)redhat.com - organizer * devel(a)ovirt.org * users(a)ovirt.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=MDhuZTY5bXRxbGo0cnNmM… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account users(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Power off VM from VM portal
by Alexandr Krivulya 08 Mar '18

08 Mar '18

Hi, is there any way to power off VM from VM portal (4.2.1.7)? I can't find "power off" button, just "shutdown".

4 6

Fibre Channel Protocol (FCP)
by maoz zadok 08 Mar '18

08 Mar '18

Hello All, I connected existing data center with NFS storage domain to a new Fiber-Channel storage domain according to the following guide, and I have three questions. https://www.ovirt.org/documentation/install-guide/chap-Configuring_Storage/ 1. why does the storage domain asks me to "Use Host"? - does it mean that if this host is down there is no access to the FC storage or the next available host elected to manage the FC storage? - does it mean that all the traffic to my storage is routed via the selected host? - what is the best practice, do I need to split the workload to other hosts as well by letting each host manage one small LUN instead of letting one host manage all LUNs or one big LUN? 2. is it possible to set the newly created fiber-channel storage(data domain) as master? 3. can I easily migrate all VM disks to the FC storage instead of the NFS? Thank you!

2 4

Unable to start VM after upgrade vom 4.1.9 to 4.2.1 - NPE
by Jan Siml 07 Mar '18

07 Mar '18

Hello, we have upgrade one of our oVirt engines to 4.2.1 (from 4.1.9) and afterwards all nodes too. The cluster compatibility level has been set to 4.2. Now we can't start a VM after it has been powered off. The only hint we found in engine.log is: 2018-03-07 14:51:52,504+01 INFO [org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (EE-ManagedThreadFactory-engine-Thread-25) [f855b54a-56d9-4708-8a67-5609438ddadb] START, UpdateVmDynamicDataVDSCommand( UpdateVmDynamicDataVDSCommandParameters:{hostId='null', vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vmDynamic='org.ovirt.engine.core.common.businessentities.VmDynamic@491983e9'}), log id: 7d49849e 2018-03-07 14:51:52,509+01 INFO [org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (EE-ManagedThreadFactory-engine-Thread-25) [f855b54a-56d9-4708-8a67-5609438ddadb] FINISH, UpdateVmDynamicDataVDSCommand, log id: 7d49849e 2018-03-07 14:51:52,531+01 INFO [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-25) [f855b54a-56d9-4708-8a67-5609438ddadb] START, CreateVDSCommand( CreateVDSCommandParameters:{hostId='0add031e-c72f-473f-ab2f-4f7abd1f402b', vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vm='VM [prod-hub-201]'}), log id: 4af1f227 2018-03-07 14:51:52,533+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-25) [f855b54a-56d9-4708-8a67-5609438ddadb] START, CreateBrokerVDSCommand(HostName = prod-node-210, CreateVDSCommandParameters:{hostId='0add031e-c72f-473f-ab2f-4f7abd1f402b', vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vm='VM [prod-hub-201]'}), log id: 71dcc8e7 2018-03-07 14:51:52,545+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-25) [f855b54a-56d9-4708-8a67-5609438ddadb] Failed in 'CreateBrokerVDS' method, for vds: 'prod-node-210'; host: 'prod-node-210': null 2018-03-07 14:51:52,546+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-25) [f855b54a-56d9-4708-8a67-5609438ddadb] Command 'CreateBrokerVDSCommand(HostName = prod-node-210, CreateVDSCommandParameters:{hostId='0add031e-c72f-473f-ab2f-4f7abd1f402b', vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vm='VM [prod-hub-201]'})' execution failed: null 2018-03-07 14:51:52,546+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-25) [f855b54a-56d9-4708-8a67-5609438ddadb] FINISH, CreateBrokerVDSCommand, log id: 71dcc8e7 2018-03-07 14:51:52,546+01 ERROR [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-25) [f855b5 4a-56d9-4708-8a67-5609438ddadb] Failed to create VM: java.lang.NullPointerException at org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.lambda$writeInterfaces$23(LibvirtVmXmlBuilder.java:1066) [vdsbroker.jar:] [...] But this doesn't lead us to the root cause. I haven't found any matching bug tickets in release notes for upcoming 4.2.1. Can anyone help here? Kind regards Jan Siml

4 10

New oVirt blog - Your Container Volumes Served By oVirt
by Yaniv Kaul 07 Mar '18

07 Mar '18

When running a virtualization workload on oVirt, a VM disk is 'natively' a disk somewhere on your network-storage. Entering containers world, on Kubernetes(k8s) or OpenShift, there are many options specifically because the workload can be totally stateless, i.e they are stored on a host supplied disk and can be removed when the container is terminated. The more interesting case is *stateful workloads* i.e apps that persist data (think DBs, web servers/services, etc). k8s/OpenShift designed an API to dynamically provision the container storage (volume in k8s terminology). In this post I want to cover how oVirt can provide volumes for containers running on k8s/OpenShift cluster. Read more @ https://ovirt.org/blog/2018/02/your-container-volumes-served-by-ovirt/

1 0

Re: [ovirt-users] Troubleshooting VM SSO on Windows 10 (ovirt 4.2.1)
by Cristian Mammoli 07 Mar '18

07 Mar '18

Anyone??? Hi, I'm trying to setup sso on Windows 10, vm is domain joined, has agent installed and credential provider registered.Of course I setup an AD domain and the vm has sso enabled Whenever I log to the user portal and open a VM I'm presented with the login screen and nothing happens, it's like the engine doesn't send the command to autologin. In the agent logs there's nothing interesting but the communication between the engine and the agent is ok: for example the command to lock-screen on console close runs and works: Dummy-2::INFO::2018-03-01 09:01:39,124::ovirtagentlogic::322::root::Received an external command: lock-screen... This is an extract from engine logs when I login in the user portal and start a connection: 2018-03-01 11:30:01,558+01 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-30) [] Userc.mammoli at apra.it <http://lists.ovirt.org/mailman/listinfo/users> successfully logged in with scopes: ovirt-app-admin ovirt-app-api ovirt-app-portal ovirt-ext=auth:sequence-priority=~ ovirt-ext=revoke:revoke-all ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2018-03-01 11:30:01,606+01 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-31) [7bc265f] Running command: CreateUserSessionCommand internal: false. 2018-03-01 11:30:01,623+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-31) [7bc265f] EVENT_ID: USER_VDC_LOGIN(30), User c.mammoli at apra.it <http://lists.ovirt.org/mailman/listinfo/users>@apra.it connecting from '192.168.1.100' using session '5NMjCbUiehNLAGMeeWsr4L5TatL+uUGsNHOxQtCvSa9i0DaQ7uoGSi6zaZdXu08vrEk5gyQUJAsB2+COzLwtEw==' logged in. 2018-03-01 11:30:02,163+01 ERROR [org.ovirt.engine.core.bll.GetSystemStatisticsQuery] (default task-39) [14276418-5de7-44a6-bb64-c60965de0acf] Query execution failed due to insufficient permissions. 2018-03-01 11:30:02,664+01 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand] (default task-54) [617f130b] Running command: SetVmTicketCommand internal: false. Entities affected : ID: c0250fe0-5d8b-44de-82bc-04610952f453 Type: VMAction group CONNECT_TO_VM with role type USER 2018-03-01 11:30:02,683+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default task-54) [617f130b] START, SetVmTicketVDSCommand(HostName = r630-01.apra.it, SetVmTicketVDSCommandParameters:{hostId='d99a8356-72e8-4130-a1cc-e148762eca57', vmId='c0250fe0-5d8b-44de-82bc-04610952f453', protocol='SPICE', ticket='u2b1nv+rH+pw', validTime='120', userName='c.mammoli at apra.it <http://lists.ovirt.org/mailman/listinfo/users>', userId='39f9d718-6e65-456a-8a6f-71976bcbbf2f', disconnectAction='LOCK_SCREEN'}), log id: 18fa2ef 2018-03-01 11:30:02,703+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default task-54) [617f130b] FINISH, SetVmTicketVDSCommand, log id: 18fa2ef 2018-03-01 11:30:02,713+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-54) [617f130b] EVENT_ID: VM_SET_TICKET(164), User c.mammoli at apra.it <http://lists.ovirt.org/mailman/listinfo/users>@apra.it initiated console session for VM testvdi02 2018-03-01 11:30:11,558+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-49) [] EVENT_ID: VM_CONSOLE_CONNECTED(167), Userc.mammoli at apra.it <http://lists.ovirt.org/mailman/listinfo/users> is connected to VM testvdi02. Any help would be appreciated

2 2