- Users - oVirt List Archives

logical_name of virtual machine disk not seen in the ovirt engine
by Punaatua PK 02 Jun '18

02 Jun '18

Hello, i used the vm_backup script as provide here : https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/vm_backu… I understood the process to backup VM. I'm stuck at getting the logical_name of the disk when the snapshot disk is attached in a VM. I checked the flow like this: - The disk is attached on the VM - oVirt guest agent detect the new disk and the mapping seen on the LOG (i did put those log in DEBUG in /etc/ovirt-guest-agent.conf), i also reduce the report_disk_usage to 10 to speed up the process - VDSM on the host get the info from the ovirt guest agent seen by running the following command vdsm-client Host getVMFullList - On the engine the logical_name is empty seen with the following sql request select device,type,device_id, logical_name from vm_device where type='disk' and vm_id='XXX'; ovirt-engine-4.2.3.5-1.el7.centos.noarch vdsm-4.20.27.1-1.el7.centos.x86_64 ovirt-guest-agent-common-1.0.14-1.el7.noarch Do you have an idea ? Is the information request by the engine to VDSM ? VDSM does report to the engine ? What is the flow to get the logical_name populated in the engine DB, python SDK ? I can provide logs if needed. I juste don't know how to enable debug on VDSM (I will take a look for this)

1 3

Ovirt consulting
by Jonathan Del Campo 01 Jun '18

01 Jun '18

Hello, I am looking for a specialized Ovirt partner in France in order to operate a migration of our system from 3.x to 4.x. Can someone recommend an Ovirt service partner to perform this kind of operations ? many thanks. Jonathan

2 1

Updating SSL Certificate for oVirt websocket proxy
by Vrgotic, Marko 01 Jun '18

01 Jun '18

Dear oVirt team, I have successfully updated/replaced SSL certificate for oVirt, following instruction on page: https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL/ However, this did not cover part related to websocketproxy used for spice-html5 web console. The one from: https://www.ovirt.org/documentation/admin-guide/virt/console-client-resourc… Still works, but I would like to update that one as well. Can somebody share instructions with me on how to execute these steps? Thank you. Marko Vrgotic

1 0

ovirt 4.2.3 console.vv provide IP addr, not FQHN for host= (spice connection)
by Oliver Riesener 01 Jun '18

01 Jun '18

Hi, i recently upgraded to ovirt 4.2.3-[78] and noticed that the spice client got and use host=IPAddr from received console.vv file and not host=FQHN of the virtualization host. I need the FQHN because i access ovirt-webui remote via ssh with port forwarding. I added a "127.0.0.1 FQHN" entry in /etc/hosts on client side to access remote ports. Please could everyone provide a < 4.2.3 console.vv file ? How can i change the behavior back to FQHN? How can i re enable WebSocket Proxy ? It's permanent False in engine-setup? Greetings Oliver

3 3

Re: engine UI add user failed
by dhy336＠sina.com 01 Jun '18

01 Jun '18

hi Andrejthanks very much.----- Original Message ----- From: Andrej Krejcir <akrejcir(a)redhat.com> To: dhy336(a)sina.com Cc: users <users(a)ovirt.org> Subject: Re: [ovirt-users] engine UI add user failed Date: 2018-06-01 17:22 Hi, Users are not created using the UI. Ovirt can be connected to various external user domains.The UI can then be used to assign permissions to existing users or groups. Here is the documentation:https://www.ovirt.org/documentation/admin-guide/chap-Users_an… The 'ovirt-aaa-jdbc-tool' can be used to create users locally. Andrej On 1 June 2018 at 09:46, <dhy336(a)sina.com> wrote: Hi I want to add user by engine UI，but failed. is it need other soft package, or should I do ? _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/E37HA64XX7ZPJ…

1 0

engine UI add user failed
by dhy336＠sina.com 01 Jun '18

01 Jun '18

Hi I want to add user by engine UI，but failed. is it need other soft package, or should I do ?

2 1

how to use oVirt engine API to retrieve the attached VM list by a disk id.
by iterjpnic 01 Jun '18

01 Jun '18

Hi all, I use oVirt engine API v4.2 for implementing terraform oVirt provider. And I want to check if a Disk has been attached to a VM, so I need to find all vms attached by this disk. But after I checked the GET-Response data from the "/ovirt-engine/api/disks/<disk-id>" rest url, there has no disk-attachment/vm related properties or links. I could get a trade-off, by the following steps: 1. getting all vms 2. get all disk-attachments of each vm 3. check if the given disk id equals to the `disk` property of each disk-attachment` 4. If equals, append the vm to result list Is there any simpler and smarter way to get this? Thanks.

3 6

Re: [ANN] oVirt 4.2.4 Second Release Candidate is now available
by Karli Sjöberg 31 May '18

31 May '18

1 0

Re: [ANN] oVirt 4.2.4 Second Release Candidate is now available
by Karli Sjöberg 31 May '18

31 May '18

2 1

[ANN] oVirt 4.2.4 Second Release Candidate is now available
by Lev Veyde 31 May '18

31 May '18

The oVirt Project is pleased to announce the availability of the oVirt 4.2.4 Second Release Candidate, as of May 31st, 2018 This update is a release candidate of the fourth 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.5 or later * CentOS Linux (or similar) 7.5 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later 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.4 release highlights: http://www.ovirt.org/release/4.2.4/ * 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.4/ [2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 1

Setting up new VM
by 03ce007＠gmail.com 31 May '18

31 May '18

I have self-hosted-engine (4.2) running on centos (7.4), the engine is running fine so I am trying to deploy a test vm to check ssh connectivity. however, the vm-infra role runs without any issues and I can see the new VM is in "up" state but it does not have any IP assigned eventhough I have defined it in the cloud_init dict. What I have noticed is that the reported_devices array comes out empty and hence the "Wait for VMs IP" task within create_vm.yml is keep getting skipped. TASK [oVirt.vm-infra : Wait for VMs IP] ****************************************************************************************************************************************************************************************************** task path: /ansible/roles/oVirt.vm-infra/tasks/main.yml:102 skipping: [hypervisor-ovirt] => (item={'name': 'mytest01-vm', 'tag': 'httpd_vm', 'profile': {'cluster': 'Default', 'domain': 'node.dev.dw', 'template': 'rhel7', 'memory': '2GiB', 'cores': 2, 'ssh_key': 'ssh-rsa AAA...LGx user@fqdn', 'disks': [{'size': '10GiB', 'name': 'data', 'storage_domain': 'hosted_storage', 'interface': 'virtio'}]}, 'cloud_init': {'host_name': 'mytestvm', 'dns_servers': '10.90.x.y 10.90.x.z', 'nic_boot_protocol': 'static', 'nic_ip_address': '10.90.0.160', 'nic_netmask': '255.255.255.0', 'nic_gateway': '10.90.0.a', 'nic_name': 'eth0', 'nic_on_boot': True, 'custom_script': "write_files:\n - content: |\n Hello, world!\n path: /tmp/greeting.txt\n permissions: '0644'\n", 'user_name': 'root', 'root_password': 'super_pass'}, 'cloud_init_persist': True}) => { "changed": false, "item": { "cloud_init": { "custom_script": "write_files:\n - content: |\n Hello, world!\n path: /tmp/greeting.txt\n permissions: '0644'\n", "dns_servers": "10.90.x.y 10.90.x.z", "host_name": "mytestvm", "nic_boot_protocol": "static", "nic_gateway": "10.90.x.a", "nic_ip_address": "10.90.x.b", "nic_name": "eth0", "nic_netmask": "255.255.255.0", "nic_on_boot": true, "root_password": "super_pass", "user_name": "root" }, "cloud_init_persist": true, "name": "mytest01-vm", "profile": { "cluster": "Default", "cores": 2, "disks": [ { "interface": "virtio", "name": "data", "size": "10GiB", "storage_domain": "hosted_storage" } ], "domain": "node.dev.dw", "memory": "2GiB", "ssh_key": "ssh-rsa AAA...LGx user@fqdn", "template": "rhel7" }, "tag": "httpd_vm" }, "skip_reason": "Conditional result was False" } I think this is the very last stage I am once the ssh connection works, I will be able to use with install yum repo, etc. Please advise.

1 0

Unable to login after upgrade
by Michael Watters 31 May '18

31 May '18

I recently upgraded one of our ovirt engines from 4.1 to the 4.2.3 release and the admin account is no longer able to login. After entering the user name and password I receive a message that states "The user admin@internal is not authorized to perform login". Is there a way to resolve this? Resetting the password did not work.

3 5

CephFS
by Markus Stockhausen 31 May '18

31 May '18

Hi there, coming from Gluster (standalone, mounted on nodes via fuse) and NFS storage domains we want to give Ceph a try. If I understand it right it should be possible to mount it in 3 ways. 1. via Cinder 2. via NFS (ganesha) 3. via CephFS (Posix) We do not need highest performance and want to keep things simple on the OVirt side (like NFS). From management/integration perspective CephFS seems to be the way to go. Any thoughts I missed that could favour the other setups? Best regards. Markus

1 0

Re: Simple API call to start VM
by Kirin van der Veer 31 May '18

31 May '18

Many thanks to: gsswzt, Luca, Andrej, Fred, Karli, Ondra and Bohdan for their replies. A number of people mentioned the need to specify a CA cert, but curl was able to find my organizations CA locally - so that was not an issue. Correcting my url to include ovirt-engine in the path and my username to admin@internal as suggested by Andrej as per below: curl --user "admin@internal:SECRETPASSWORD" --request POST --header "Content-Type: application/xml" --header "Accept: application/xml" --data '</action>' https://ovirt-engine.localnet:443/ovirt-engine/api/vms/69c47a91-bbv1-4eda-b… Got me a new error message: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <fault> <detail>For correct usage, see: https://ovirt-engine.localnet/ovirt-engine/apidoc#services/vm/methods/start </detail> <reason>Request syntactically incorrect.</reason> </fault> I followed the URL, but it just seemed to repeat the information already available at http://ovirt.github.io/ovirt-engine-api-model/4.2/#services/vm/methods/start Here is the relevant section of engine.log on ovirt-engine.localnet: 2018-05-31 10:48:15,550+10 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-25) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2018-05-31 10:48:15,569+10 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-29) [8ffa0f3] Running command: CreateUserSessionCommand internal: false. 2018-05-31 10:48:15,581+10 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-29) [8ffa0f3] EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from '192.168.1.0' using session 'JNweIEHoHhw9U+wMt7Z03Ovb5Pc1zR3WyvTcSfRTpdHjd55CHbcspfDcJgToMVshtlgXamzvUSW2rzHB9ApJHA==' logged in. 2018-05-31 10:48:15,587+10 ERROR [org.ovirt.engine.api.restapi.resource.validation.IOExceptionMapper] (default task-29) [] IO exception while processing "POST" request for path "/vms/69c47a91-bbv1-4eda-b71d-7bddf82ee8ab/start" 2018-05-31 10:48:15,587+10 ERROR [org.ovirt.engine.api.restapi.resource.validation.IOExceptionMapper] (default task-29) [] Exception: java.io.IOException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,2] Message: The markup in the document preceding the root element must be well-formed. at org.ovirt.engine.api.restapi.xml.JAXBProvider.readFrom(JAXBProvider.java:200) [restapi-jaxrs.jar:] at org.ovirt.engine.api.restapi.xml.JAXBProvider.readFrom(JAXBProvider.java:162) [restapi-jaxrs.jar:] at org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.readFrom(AbstractReaderInterceptorContext.java:66) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.interception.ServerReaderInterceptorContext.readFrom(ServerReaderInterceptorContext.java:61) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.proceed(AbstractReaderInterceptorContext.java:56) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.security.doseta.DigitalVerificationInterceptor.aroundReadFrom(DigitalVerificationInterceptor.java:36) [resteasy-crypto-3.0.24.Final.jar:3.0.24.Final] <MANY MANY LINES OF ERRORS SNIPPED> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,2] Message: The markup in the document preceding the root element must be well-formed. at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:604) [rt.jar:1.8.0_171] at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:164) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:415) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:386) at org.ovirt.engine.api.restapi.xml.JAXBProvider.readFrom(JAXBProvider.java:187) [restapi-jaxrs.jar:] ... 104 more 2018-05-31 10:48:15,593+10 INFO [org.ovirt.engine.core.bll.aaa.LogoutSessionCommand] (default task-29) [4531c52a] Running command: LogoutSessionCommand internal: false. 2018-05-31 10:48:15,598+10 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-29) [4531c52a] EVENT_ID: USER_VDC_LOGOUT(31), User admin@internal-authz connected from '192.168.1.0' using session 'JNweIEHoHhw9U+wMt7Z03Ovb5Pc1zR3WyvTcSfRTpdHjd55CHbcspfDcJgToMVshtlgXamzvUSW2rzHB9ApJHA==' logged out. 2018-05-31 10:48:27,542+10 INFO [org.ovirt.engine.core.sso.servlets.OAuthRevokeServlet] (default task-32) [] User admin@internal successfully logged out 2018-05-31 10:48:27,550+10 INFO [org.ovirt.engine.core.bll.aaa.TerminateSessionsForTokenCommand] (default task-35) [76676851] Running command: TerminateSessionsForTokenCommand internal: true. Later I thought that perhaps the problem was that I need to use the VM Name instead of it's UUID, since all of the examples in the official docs use something like "123" or "007". However when I changed the curl request to the below: curl --user "admin@internal:SECRETPASSWORD" --request POST --header "Content-Type: application/xml" --header "Accept: application/xml" --data '</action>' https://ovirt-engine.localnet:443/ovirt-engine/api/vms/name_of_my_vm/start I got no feedback on the commandline. So I checked engine.log, but there were only a few entries as per below: 2018-05-31 11:43:39,940+10 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-49) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2018-05-31 11:43:39,954+10 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-39) [41871d82] Running command: CreateUserSessionCommand internal: false. 2018-05-31 11:43:39,962+10 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-39) [41871d82] EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from '192.168.1.0' using session 'EfiWrbyRpCilceYzJsgOz+E/An7JBAHr2ASziyZyFykop9vO77gc1+u3CQh542eNq/BXOXpOOxKhQLQhIKarEg==' logged in. 2018-05-31 11:43:39,971+10 INFO [org.ovirt.engine.core.bll.aaa.LogoutSessionCommand] (default task-39) [6209f488] Running command: LogoutSessionCommand internal: false. 2018-05-31 11:43:39,976+10 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-39) [6209f488] EVENT_ID: USER_VDC_LOGOUT(31), User admin@internal-authz connected from '192.168.1.0' using session 'EfiWrbyRpCilceYzJsgOz+E/An7JBAHr2ASziyZyFykop9vO77gc1+u3CQh542eNq/BXOXpOOxKhQLQhIKarEg==' logged out. Note that the name I specified does not show up at all. Anyone have any ideas? On Wed, May 30, 2018 at 7:03 PM, Andrej Krejcir <akrejcir(a)redhat.com> wrote: > Hi, > > the URL path is missing 'ovirt-engine', it should be: > https://ovirtengine.localnet:443/ovirt-engine/api/vms/ > dfbba498-e8b6-4fee-a86c-c91ab68eae0d/start > > Also, the admin user name is: 'admin@internal' > > Here is the API documentation, for more info: > http://ovirt.github.io/ovirt-engine-api-model/4.2/# > services/vm/methods/start > > > Andrej > > On 30 May 2018 at 08:07, Kirin van der Veer <kirin.vanderveer@ > planetinnovation.com.au> wrote: > >> Hi oVirt users, >> I have (what I hope) is a simple problem. >> I want to make an https request to start a VM via the oVirt REST API. >> Here is the command that I think should work: >> curl --user "admin:SECRETPASSWORD" --request POST --header "Content-Type: >> application/xml" --header "Accept: application/xml" --data '</action>' >> https://ovirtengine.localnet:443/api/vms/69c47a91-bbv1-4eda- >> b71d-7bddf82ee8ab/start >> >> However I get a 404 in response (see below): >> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >> <html><head> >> <title>404 Not Found</title> >> </head><body> >> <h1>Not Found</h1> >> <p>The requested URL /api/vms/60c47a91-bca1-4eda-b71d-7bddf82ee8ab/start >> was not found on this server.</p> >> </body></html> >> >> Where have I made a mistake here? >> >> >> >> *IMPORTANT NOTE. *If you are NOT AN AUTHORISED RECIPIENT of this e-mail, >> please contact Planet Innovation Pty Ltd by return e-mail or by telephone >> on +613 9945 7510. In this case, you should not read, print, re-transmit, >> store or act in reliance on this e-mail or any attachments, and should >> destroy all copies of them. This e-mail and any attachments are >> confidential and may contain legally privileged information and/or >> copyright material of Planet Innovation Pty Ltd or third parties. You >> should only re-transmit, distribute or commercialise the material if you >> are authorised to do so. Although we use virus scanning software, we deny >> all liability for viruses or alike in any message or attachment. This >> notice should not be removed. >> >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/communit >> y/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archiv >> es/list/users(a)ovirt.org/message/5N6N4BHF6ZFJLEARSEALCON7DJIMXRCZ/ >> >> > -- *IMPORTANT NOTE. *If you are NOT AN AUTHORISED RECIPIENT of this e-mail, please contact Planet Innovation Pty Ltd by return e-mail or by telephone on +613 9945 7510. In this case, you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. This e-mail and any attachments are confidential and may contain legally privileged information and/or copyright material of Planet Innovation Pty Ltd or third parties. You should only re-transmit, distribute or commercialise the material if you are authorised to do so. Although we use virus scanning software, we deny all liability for viruses or alike in any message or attachment. This notice should not be removed. **

2 1

Attaching previously owned storage domain to 4.2 Cluster
by John Nguyen 31 May '18

31 May '18

Hi Guys, I'm working through a disaster recovery of a failed cluster. And I found the documentation for attaching the old storage domain as an import domain to a new Cluster. Both clusters are 4.2. https://ovirt.org/develop/release-management/features/storage/importstorage… The documentation is referencing 3.5 and I would like to know if its still applies to the 4.2 release. When I try to do the import I see warnings below: I know that its really hard to say this operation may not be destructive. But is the general work flow outlined in the 3.5 documentation still valid? Thanks, John

3 2

OVN networks
by Егор Чиж 31 May '18

31 May '18

Hello, Could you help with how to change Switch type in ovirt cluster from Linux Bridge to OVS. I mean, using this link https://ovirt.org/develop/release-management/features/network/provider-phys… I read paragraph Create a cluster with Network Type set to OVS. Now i have cluster with installing type Linux Bridge, how can i changed it to OVS? Best regards, Egor

2 1

Re: Fwd: FreeBSD after 10.3 could not boot (Freeze)
by Karli Sjöberg 30 May '18

30 May '18

2 1

Simple API call to start VM
by Kirin van der Veer 30 May '18

30 May '18

Hi oVirt users, I have (what I hope) is a simple problem. I want to make an https request to start a VM via the oVirt REST API. Here is the command that I think should work: curl --user "admin:SECRETPASSWORD" --request POST --header "Content-Type: application/xml" --header "Accept: application/xml" --data '</action>' https://ovirtengine.localnet:443/api/vms/69c47a91-bbv1-4eda-b71d-7bddf82ee8… However I get a 404 in response (see below): <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /api/vms/60c47a91-bca1-4eda-b71d-7bddf82ee8ab/start was not found on this server.</p> </body></html> Where have I made a mistake here? -- *IMPORTANT NOTE. *If you are NOT AN AUTHORISED RECIPIENT of this e-mail, please contact Planet Innovation Pty Ltd by return e-mail or by telephone on +613 9945 7510. In this case, you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. This e-mail and any attachments are confidential and may contain legally privileged information and/or copyright material of Planet Innovation Pty Ltd or third parties. You should only re-transmit, distribute or commercialise the material if you are authorised to do so. Although we use virus scanning software, we deny all liability for viruses or alike in any message or attachment. This notice should not be removed. **

7 7

Re: Fwd: FreeBSD after 10.3 could not boot (Freeze)
by Karli Sjöberg 30 May '18

30 May '18

1 0

Re: ovirt-node: freshly installed node: network interfaces not visible
by Ales Musil 30 May '18

30 May '18

On Wed, May 30, 2018 at 10:14 AM, Etienne Charlier < Etienne.Charlier(a)reduspaceservices.eu> wrote: > Hello, Thanks for the support > > > log are only sent to you , not to the list !!! > > > Kind Regards, > > Etienne > > Can you also please send the engine log? Regards, Ales > > ------------------------------ > *De :* Ales Musil <amusil(a)redhat.com> > *Envoyé :* mercredi 30 mai 2018 09:02 > *À :* Etienne Charlier > *Cc :* users > *Objet :* Re: [ovirt-users] Re: ovirt-node: freshly installed node: > network interfaces not visible > > > > On Tue, May 29, 2018 at 8:40 AM, <etienne.charlier(a)reduspaceservices.eu> > wrote: > >> Hello Ales, >> >> Thanks for the answer ! >> >> I tried multiple time to refresh capabilities... without success >> >> For the record, the tab named "Host Devices" is also empty >> >> Have a nice Day >> Etienne >> > > Can you please send us the vdsm and supervdsm log from the host? > > > > >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/communit >> y/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archiv >> es/list/users(a)ovirt.org/message/ISBFSCIX7J6INUIKJXUSI6J4DWKA326Q/ >> > > > > -- > > ALES MUSIL > INTERN - rhv network > > Red Hat EMEA <https://www.redhat.com/> > > > amusil(a)redhat.com IM: amusil > <https://red.ht/sig> > -- ALES MUSIL INTERN - rhv network Red Hat EMEA <https://www.redhat.com/> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

1 0

Use an oVirt-VM as a VDSM server
by James Michels 30 May '18

30 May '18

Greetings. In terms of teaching our students how to create and configure an oVirt infrastructure, we're planning to provide each of them a VM that will act as a Manager server, which has no issues so far. The problem is that we don't have enough physical machines to use as virtualization servers (VDSM), therefore we have been trying to use a CentOS7 based oVirt guest to run as a VDSM server. However, when trying to add it as a host, a (logical) error message shows up saying that the VM doesn't allow virtualization. The question is simple: Is there a way to enable virtualization on an oVirt VM, so we can deploy them as VDSM servers? This is oVirt 4.2.2 FWIW. Thanks James

4 3

Re: Simple API call to start VM
by Karli Sjöberg 30 May '18

30 May '18

1 0

FreeBSD after 10.3 could not boot (Freeze)
by Paul.LKW 30 May '18

30 May '18

HI All: Any one have tried to boot up FreeBSD 10.4, I tried 10.3 is all working fine but no lucky in 10.4 at all even boot from DVD !!! Attached is the point freezes. BR, Paul.LKW

3 5

Re: Fwd: FreeBSD after 10.3 could not boot (Freeze)
by Karli Sjöberg 30 May '18

30 May '18

2 1

Re: Gluster quorum
by Sahina Bose 30 May '18

30 May '18

[+users] Can you provide the engine.log to see why the monitoring is not working here. thanks! On Wed, May 16, 2018 at 2:08 PM, Demeter Tibor <tdemeter(a)itsmart.hu> wrote: > Hi, > > Meanwhile, I did the upgrade engine, but the gluster state is same on my > first node. > I've attached some screenshot of my problem. > > Thanks > > Tibor > > > > ----- 2018. máj.. 16., 10:16, Demeter Tibor <tdemeter(a)itsmart.hu> írtaHi, > > > If 4.3.4 will release, i just have to remove the nightly repo and update > to stable? > > I'm sorry for my terrible English, I try to explain what was my problem > with update. > I'm upgraded from 4.1.8. > > I followed up the official hosted-engine update documentation, that was > not clear me, because it has referenced to a lot of old thing (i think). > https://www.ovirt.org/documentation/upgrade-guide/upgrade-guide/ > https://www.ovirt.org/documentation/how-to/hosted- > engine/#upgrade-hosted-engine > > Maybe it need to update, because I had a lot of question under upgrade and > I was not sure in all of necessary steps. For example, If I need to > installing the new, 4.2 repo on the hosts, then need to remove the old repo > from that? > Why I need to do a" yum update -y" on hosts, meanwhile there is an > "Updatehost" menu in the GUI? So, maybe it outdated. > Since upgrade hosted engine, and the first node, I have problems with > gluster. It seems to working fine if you check it from console "gluster > volume status, etc" but not on the Gui, because now it yellow, and the > brick reds in the first node. > > Previously I did a mistake with glusterfs, my gluster config was wrong. I > have corrected them, but it did not helped to me,gluster bricks are reds on > my first node yet.... > > > Now I try to upgrade to nightly, but I'm affraid, because it a living, > productive system, and I don't have downtime. I hope it will help me. > > Thanks for all, > > Regards, > Tibor Demeter > > > > ----- 2018. máj.. 16., 9:58, Sahina Bose <sabose(a)redhat.com> írta: > > > > On Wed, May 16, 2018 at 1:19 PM, Demeter Tibor <tdemeter(a)itsmart.hu> > wrote: > >> Hi, >> >> is it a different, unstable repo? I have a productive cluster, how is >> safe that? >> I don't have any experience with nightly build. How can I use this? It >> have to install to the engine VM or all of my hosts? >> Thanks in advance for help me.. >> > > Only on the engine VM. > > Regarding stability - it passes CI so relatively stable, beyond that there > are no guarantees. > > What's the specific problem you're facing with update? Can you elaborate? > > >> Regards, >> >> Tibor >> >> ----- 2018. máj.. 15., 9:58, Demeter Tibor <tdemeter(a)itsmart.hu> írta: >> >> Hi, >> >> Could you explain how can I use this patch? >> >> R, >> Tibor >> >> >> ----- 2018. máj.. 14., 11:18, Demeter Tibor <tdemeter(a)itsmart.hu> írta: >> >> Hi, >> >> Sorry for my question, but can you tell me please how can I use this >> patch? >> >> Thanks, >> Regards, >> Tibor >> ----- 2018. máj.. 14., 10:47, Sahina Bose <sabose(a)redhat.com> írta: >> >> >> >> On Sat, May 12, 2018 at 1:14 PM, Demeter Tibor <tdemeter(a)itsmart.hu> >> wrote: >> >>> Hi, >>> >>> Could someone help me please ? I can't finish my upgrade process. >>> >> >> https://gerrit.ovirt.org/91164 should fix the error you're facing. >> >> Can you elaborate why this is affecting the upgrade process? >> >> >>> Thanks >>> R >>> Tibor >>> >>> >>> >>> ----- 2018. máj.. 10., 12:51, Demeter Tibor <tdemeter(a)itsmart.hu> írta: >>> >>> Hi, >>> >>> I've attached the vdsm and supervdsm logs. But I don't have engine.log >>> here, because that is on hosted engine vm. Should I send that ? >>> >>> Thank you >>> >>> Regards, >>> >>> Tibor >>> ----- 2018. máj.. 10., 12:30, Sahina Bose <sabose(a)redhat.com> írta: >>> >>> There's a bug here. Can you log one attaching this engine.log and also >>> vdsm.log & supervdsm.log from n3.itsmart.cloud >>> >>> On Thu, May 10, 2018 at 3:35 PM, Demeter Tibor <tdemeter(a)itsmart.hu> >>> wrote: >>> >>>> Hi, >>>> >>>> I found this: >>>> >>>> >>>> 2018-05-10 03:24:19,096+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] FINISH, GetGlusterVolumeAdvancedDetailsVDSCommand, >>>> return: org.ovirt.engine.core.common.businessentities.gluster. >>>> GlusterVolumeAdvancedDetails@ca97448e, log id: 347435ae >>>> 2018-05-10 03:24:19,097+02 ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] >>>> (DefaultQuartzScheduler7) [43f4eaec] Error while refreshing brick statuses >>>> for volume 'volume2' of cluster 'C6220': null >>>> 2018-05-10 03:24:19,097+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler8) [7715ceda] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 03:24:19,104+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n4.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='3ddef95f-158d-407c-a7d8-49641e012755'}), log id: 6908121d >>>> 2018-05-10 03:24:19,106+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n4.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='3ddef95f-158d-407c-a7d8-49641e012755'})' execution failed: >>>> null >>>> 2018-05-10 03:24:19,106+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 6908121d >>>> 2018-05-10 03:24:19,107+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n1.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='8e737bab-e0bb-4f16-ab85-e24e91882f57'}), log id: 735c6a5f >>>> 2018-05-10 03:24:19,109+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n1.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='8e737bab-e0bb-4f16-ab85-e24e91882f57'})' execution failed: >>>> null >>>> 2018-05-10 03:24:19,109+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 735c6a5f >>>> 2018-05-10 03:24:19,110+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n2.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'}), log id: 6f9e9f58 >>>> 2018-05-10 03:24:19,112+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n2.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'})' execution failed: >>>> null >>>> 2018-05-10 03:24:19,112+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 6f9e9f58 >>>> 2018-05-10 03:24:19,113+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n3.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='fd2ee743-f5d4-403b-ba18-377e309169ec'}), log id: 2ee46967 >>>> 2018-05-10 03:24:19,115+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n3.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='fd2ee743-f5d4-403b-ba18-377e309169ec'})' execution failed: >>>> null >>>> 2018-05-10 03:24:19,116+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 2ee46967 >>>> 2018-05-10 03:24:19,117+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] START, GetGlusterVolumeAdvancedDetailsVDSCommand(HostName >>>> = n1.itsmart.cloud, GlusterVolumeAdvancedDetailsVD >>>> SParameters:{hostId='8e737bab-e0bb-4f16-ab85-e24e91882f57', >>>> volumeName='volume1'}), log id: 7550e5c >>>> 2018-05-10 03:24:20,748+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] FINISH, GetGlusterVolumeAdvancedDetailsVDSCommand, >>>> return: org.ovirt.engine.core.common.businessentities.gluster. >>>> GlusterVolumeAdvancedDetails@4a46066f, log id: 7550e5c >>>> 2018-05-10 03:24:20,749+02 ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] >>>> (DefaultQuartzScheduler7) [43f4eaec] Error while refreshing brick statuses >>>> for volume 'volume1' of cluster 'C6220': null >>>> 2018-05-10 03:24:20,750+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterServersListVDSCommand] >>>> (DefaultQuartzScheduler8) [7715ceda] START, GlusterServersListVDSCommand(HostName >>>> = n2.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'}), log id: 120cc68d >>>> 2018-05-10 03:24:20,930+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterServersListVDSCommand] >>>> (DefaultQuartzScheduler8) [7715ceda] FINISH, GlusterServersListVDSCommand, >>>> return: [10.101.0.2/24:CONNECTED, n1.cloudata.local:CONNECTED, >>>> 10.104.0.3:CONNECTED, 10.104.0.4:CONNECTED], log id: 120cc68d >>>> 2018-05-10 03:24:20,949+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListVDSCommand] >>>> (DefaultQuartzScheduler8) [7715ceda] START, GlusterVolumesListVDSCommand(HostName >>>> = n2.itsmart.cloud, GlusterVolumesListVDSParameter >>>> s:{hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'}), log id: 118aa264 >>>> 2018-05-10 03:24:21,048+02 WARN [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) >>>> [7715ceda] Could not associate brick '10.104.0.1:/gluster/brick/brick1' >>>> of volume 'e0f568fa-987c-4f5c-b853-01bce718ee27' with correct network >>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>> 000000000339' >>>> 2018-05-10 03:24:21,055+02 WARN [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) >>>> [7715ceda] Could not associate brick '10.104.0.1:/gluster/brick/brick2' >>>> of volume 'e0f568fa-987c-4f5c-b853-01bce718ee27' with correct network >>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>> 000000000339' >>>> 2018-05-10 03:24:21,061+02 WARN [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) >>>> [7715ceda] Could not associate brick '10.104.0.1:/gluster/brick/brick3' >>>> of volume 'e0f568fa-987c-4f5c-b853-01bce718ee27' with correct network >>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>> 000000000339' >>>> 2018-05-10 03:24:21,067+02 WARN [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) >>>> [7715ceda] Could not associate brick '10.104.0.1:/gluster2/brick/brick1' >>>> of volume '68cfb061-1320-4042-abcd-9228da23c0c8' with correct network >>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>> 000000000339' >>>> 2018-05-10 03:24:21,074+02 WARN [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) >>>> [7715ceda] Could not associate brick '10.104.0.1:/gluster2/brick/brick2' >>>> of volume '68cfb061-1320-4042-abcd-9228da23c0c8' with correct network >>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>> 000000000339' >>>> 2018-05-10 03:24:21,080+02 WARN [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) >>>> [7715ceda] Could not associate brick '10.104.0.1:/gluster2/brick/brick3' >>>> of volume '68cfb061-1320-4042-abcd-9228da23c0c8' with correct network >>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>> 000000000339' >>>> 2018-05-10 03:24:21,081+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListVDSCommand] >>>> (DefaultQuartzScheduler8) [7715ceda] FINISH, GlusterVolumesListVDSCommand, >>>> return: {68cfb061-1320-4042-abcd-9228da23c0c8=org.ovirt.engine. >>>> core.common.businessentities.gluster.GlusterVolumeEntity@7a6720d, >>>> e0f568fa-987c-4f5c-b853-01bce718ee27=org.ovirt.engine. >>>> core.common.businessentities.g >>>> luster.GlusterVolumeEntity@f88c521b}, log id: 118aa264 >>>> >>>> >>>> >>>> 2018-05-10 11:59:26,047+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n1.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='8e737bab-e0bb-4f16-ab85-e24e91882f57'})' execution failed: >>>> null >>>> 2018-05-10 11:59:26,047+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 14a71ef0 >>>> 2018-05-10 11:59:26,048+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n4.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='3ddef95f-158d-407c-a7d8-49641e012755'}), log id: 28d9e255 >>>> 2018-05-10 11:59:26,051+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n4.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='3ddef95f-158d-407c-a7d8-49641e012755'})' execution failed: >>>> null >>>> 2018-05-10 11:59:26,051+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 28d9e255 >>>> 2018-05-10 11:59:26,052+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n2.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'}), log id: 4a7b280e >>>> 2018-05-10 11:59:26,054+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n2.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'})' execution failed: >>>> null >>>> 2018-05-10 11:59:26,054+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 4a7b280e >>>> 2018-05-10 11:59:26,055+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n3.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='fd2ee743-f5d4-403b-ba18-377e309169ec'}), log id: 18adc534 >>>> 2018-05-10 11:59:26,057+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n3.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='fd2ee743-f5d4-403b-ba18-377e309169ec'})' execution failed: >>>> null >>>> 2018-05-10 11:59:26,057+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 18adc534 >>>> 2018-05-10 11:59:26,058+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] START, GetGlusterVolumeAdvancedDetailsVDSCommand(HostName >>>> = n3.itsmart.cloud, GlusterVolumeAdvancedDetailsVD >>>> SParameters:{hostId='fd2ee743-f5d4-403b-ba18-377e309169ec', >>>> volumeName='volume1'}), log id: 3451084f >>>> 2018-05-10 11:59:28,050+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:28,060+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:28,062+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:31,054+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:31,054+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:31,062+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:31,064+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:31,465+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] FINISH, GetGlusterVolumeAdvancedDetailsVDSCommand, >>>> return: org.ovirt.engine.core.common.businessentities.gluster. >>>> GlusterVolumeAdvancedDetails@3f1b7f43, log id: 3451084f >>>> 2018-05-10 11:59:31,466+02 ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] >>>> (DefaultQuartzScheduler4) [400fa486] Error while refreshing brick statuses >>>> for volume 'volume1' of cluster 'C6220': null >>>> >>>> >>>> R >>>> Tibor >>>> >>>> ----- 2018. máj.. 10., 11:43, Sahina Bose <sabose(a)redhat.com> írta: >>>> >>>> This doesn't affect the monitoring of state. >>>> Any errors in vdsm.log? >>>> Or errors in engine.log of the form "Error while refreshing brick >>>> statuses for volume" >>>> >>>> On Thu, May 10, 2018 at 2:33 PM, Demeter Tibor <tdemeter(a)itsmart.hu> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> Thank you for your fast reply :) >>>>> >>>>> >>>>> 2018-05-10 11:01:51,574+02 INFO [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterServersListVDSCommand] >>>>> (DefaultQuartzScheduler6) [7f01fc2d] START, GlusterServersListVDSCommand(HostName >>>>> = n2.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>>> {hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'}), log id: 39adbbb8 >>>>> 2018-05-10 11:01:51,768+02 INFO [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterServersListVDSCommand] >>>>> (DefaultQuartzScheduler6) [7f01fc2d] FINISH, GlusterServersListVDSCommand, >>>>> return: [10.101.0.2/24:CONNECTED, n1.cloudata.local:CONNECTED, >>>>> 10.104.0.3:CONNECTED, 10.104.0.4:CONNECTED], log id: 39adbbb8 >>>>> 2018-05-10 11:01:51,788+02 INFO [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListVDSCommand] >>>>> (DefaultQuartzScheduler6) [7f01fc2d] START, GlusterVolumesListVDSCommand(HostName >>>>> = n2.itsmart.cloud, GlusterVolumesListVDSParameter >>>>> s:{hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'}), log id: 738a7261 >>>>> 2018-05-10 11:01:51,892+02 WARN [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler6) >>>>> [7f01fc2d] Could not associate brick '10.104.0.1:/gluster/brick/brick1' >>>>> of volume 'e0f568fa-987c-4f5c-b853-01bce718ee27' with correct network >>>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>>> 000000000339' >>>>> 2018-05-10 11:01:51,898+02 WARN [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler6) >>>>> [7f01fc2d] Could not associate brick '10.104.0.1:/gluster/brick/brick2' >>>>> of volume 'e0f568fa-987c-4f5c-b853-01bce718ee27' with correct network >>>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>>> 000000000339' >>>>> 2018-05-10 11:01:51,905+02 WARN [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler6) >>>>> [7f01fc2d] Could not associate brick '10.104.0.1:/gluster/brick/brick3' >>>>> of volume 'e0f568fa-987c-4f5c-b853-01bce718ee27' with correct network >>>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>>> 000000000339' >>>>> 2018-05-10 11:01:51,911+02 WARN [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler6) >>>>> [7f01fc2d] Could not associate brick '10.104.0.1:/gluster2/brick/brick1' >>>>> of volume '68cfb061-1320-4042-abcd-9228da23c0c8' with correct network >>>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>>> 000000000339' >>>>> 2018-05-10 11:01:51,917+02 WARN [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler6) >>>>> [7f01fc2d] Could not associate brick '10.104.0.1:/gluster2/brick/brick2' >>>>> of volume '68cfb061-1320-4042-abcd-9228da23c0c8' with correct network >>>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>>> 000000000339' >>>>> 2018-05-10 11:01:51,924+02 WARN [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler6) >>>>> [7f01fc2d] Could not associate brick '10.104.0.1:/gluster2/brick/brick3' >>>>> of volume '68cfb061-1320-4042-abcd-9228da23c0c8' with correct network >>>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>>> 000000000339' >>>>> 2018-05-10 11:01:51,925+02 INFO [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListVDSCommand] >>>>> (DefaultQuartzScheduler6) [7f01fc2d] FINISH, GlusterVolumesListVDSCommand, >>>>> return: {68cfb061-1320-4042-abcd-9228da23c0c8=org.ovirt.engine. >>>>> core.common.businessentities.gluster.GlusterVolumeEntity@7a6720d, >>>>> e0f568fa-987c-4f5c-b853-01bce718ee27=org.ovirt.engine. >>>>> core.common.businessentities.gluster.GlusterVolumeEntity@f88c521b}, >>>>> log id: 738a7261 >>>>> >>>>> >>>>> This happening continuously. >>>>> >>>>> Thanks! >>>>> Tibor >>>>> >>>>> >>>>> >>>>> ----- 2018. máj.. 10., 10:56, Sahina Bose <sabose(a)redhat.com> írta: >>>>> >>>>> Could you check the engine.log if there are errors related to getting >>>>> GlusterVolumeAdvancedDetails ? >>>>> >>>>> On Thu, May 10, 2018 at 2:02 PM, Demeter Tibor <tdemeter(a)itsmart.hu> >>>>> wrote: >>>>> >>>>>> Dear Ovirt Users, >>>>>> I've followed up the self-hosted-engine upgrade documentation, I >>>>>> upgraded my 4.1 system to 4.2.3. >>>>>> I upgaded the first node with yum upgrade, it seems working now fine. >>>>>> But since upgrade, the gluster informations seems to displayed incorrect on >>>>>> the admin panel. The volume yellow, and there are red bricks from that node. >>>>>> I've checked in console, I think my gluster is not degraded: >>>>>> >>>>>> root@n1 ~]# gluster volume list >>>>>> volume1 >>>>>> volume2 >>>>>> [root@n1 ~]# gluster volume info >>>>>> >>>>>> Volume Name: volume1 >>>>>> Type: Distributed-Replicate >>>>>> Volume ID: e0f568fa-987c-4f5c-b853-01bce718ee27 >>>>>> Status: Started >>>>>> Snapshot Count: 0 >>>>>> Number of Bricks: 3 x 3 = 9 >>>>>> Transport-type: tcp >>>>>> Bricks: >>>>>> Brick1: 10.104.0.1:/gluster/brick/brick1 >>>>>> Brick2: 10.104.0.2:/gluster/brick/brick1 >>>>>> Brick3: 10.104.0.3:/gluster/brick/brick1 >>>>>> Brick4: 10.104.0.1:/gluster/brick/brick2 >>>>>> Brick5: 10.104.0.2:/gluster/brick/brick2 >>>>>> Brick6: 10.104.0.3:/gluster/brick/brick2 >>>>>> Brick7: 10.104.0.1:/gluster/brick/brick3 >>>>>> Brick8: 10.104.0.2:/gluster/brick/brick3 >>>>>> Brick9: 10.104.0.3:/gluster/brick/brick3 >>>>>> Options Reconfigured: >>>>>> transport.address-family: inet >>>>>> performance.readdir-ahead: on >>>>>> nfs.disable: on >>>>>> storage.owner-uid: 36 >>>>>> storage.owner-gid: 36 >>>>>> performance.quick-read: off >>>>>> performance.read-ahead: off >>>>>> performance.io-cache: off >>>>>> performance.stat-prefetch: off >>>>>> performance.low-prio-threads: 32 >>>>>> network.remote-dio: enable >>>>>> cluster.eager-lock: enable >>>>>> cluster.quorum-type: auto >>>>>> cluster.server-quorum-type: server >>>>>> cluster.data-self-heal-algorithm: full >>>>>> cluster.locking-scheme: granular >>>>>> cluster.shd-max-threads: 8 >>>>>> cluster.shd-wait-qlength: 10000 >>>>>> features.shard: on >>>>>> user.cifs: off >>>>>> server.allow-insecure: on >>>>>> >>>>>> Volume Name: volume2 >>>>>> Type: Distributed-Replicate >>>>>> Volume ID: 68cfb061-1320-4042-abcd-9228da23c0c8 >>>>>> Status: Started >>>>>> Snapshot Count: 0 >>>>>> Number of Bricks: 3 x 3 = 9 >>>>>> Transport-type: tcp >>>>>> Bricks: >>>>>> Brick1: 10.104.0.1:/gluster2/brick/brick1 >>>>>> Brick2: 10.104.0.2:/gluster2/brick/brick1 >>>>>> Brick3: 10.104.0.3:/gluster2/brick/brick1 >>>>>> Brick4: 10.104.0.1:/gluster2/brick/brick2 >>>>>> Brick5: 10.104.0.2:/gluster2/brick/brick2 >>>>>> Brick6: 10.104.0.3:/gluster2/brick/brick2 >>>>>> Brick7: 10.104.0.1:/gluster2/brick/brick3 >>>>>> Brick8: 10.104.0.2:/gluster2/brick/brick3 >>>>>> Brick9: 10.104.0.3:/gluster2/brick/brick3 >>>>>> Options Reconfigured: >>>>>> nfs.disable: on >>>>>> performance.readdir-ahead: on >>>>>> transport.address-family: inet >>>>>> cluster.quorum-type: auto >>>>>> network.ping-timeout: 10 >>>>>> auth.allow: * >>>>>> performance.quick-read: off >>>>>> performance.read-ahead: off >>>>>> performance.io-cache: off >>>>>> performance.stat-prefetch: off >>>>>> performance.low-prio-threads: 32 >>>>>> network.remote-dio: enable >>>>>> cluster.eager-lock: enable >>>>>> cluster.server-quorum-type: server >>>>>> cluster.data-self-heal-algorithm: full >>>>>> cluster.locking-scheme: granular >>>>>> cluster.shd-max-threads: 8 >>>>>> cluster.shd-wait-qlength: 10000 >>>>>> features.shard: on >>>>>> user.cifs: off >>>>>> storage.owner-uid: 36 >>>>>> storage.owner-gid: 36 >>>>>> server.allow-insecure: on >>>>>> [root@n1 ~]# gluster volume status >>>>>> Status of volume: volume1 >>>>>> Gluster process TCP Port RDMA Port >>>>>> Online Pid >>>>>> ------------------------------------------------------------ >>>>>> ------------------ >>>>>> Brick 10.104.0.1:/gluster/brick/brick1 49152 0 Y >>>>>> 3464 >>>>>> Brick 10.104.0.2:/gluster/brick/brick1 49152 0 Y >>>>>> 68937 >>>>>> Brick 10.104.0.3:/gluster/brick/brick1 49161 0 Y >>>>>> 94506 >>>>>> Brick 10.104.0.1:/gluster/brick/brick2 49153 0 Y >>>>>> 3457 >>>>>> Brick 10.104.0.2:/gluster/brick/brick2 49153 0 Y >>>>>> 68943 >>>>>> Brick 10.104.0.3:/gluster/brick/brick2 49162 0 Y >>>>>> 94514 >>>>>> Brick 10.104.0.1:/gluster/brick/brick3 49154 0 Y >>>>>> 3465 >>>>>> Brick 10.104.0.2:/gluster/brick/brick3 49154 0 Y >>>>>> 68949 >>>>>> Brick 10.104.0.3:/gluster/brick/brick3 49163 0 Y >>>>>> 94520 >>>>>> Self-heal Daemon on localhost N/A N/A Y >>>>>> 54356 >>>>>> Self-heal Daemon on 10.104.0.2 N/A N/A Y >>>>>> 962 >>>>>> Self-heal Daemon on 10.104.0.3 N/A N/A Y >>>>>> 108977 >>>>>> Self-heal Daemon on 10.104.0.4 N/A N/A Y >>>>>> 61603 >>>>>> >>>>>> Task Status of Volume volume1 >>>>>> ------------------------------------------------------------ >>>>>> ------------------ >>>>>> There are no active volume tasks >>>>>> >>>>>> Status of volume: volume2 >>>>>> Gluster process TCP Port RDMA Port >>>>>> Online Pid >>>>>> ------------------------------------------------------------ >>>>>> ------------------ >>>>>> Brick 10.104.0.1:/gluster2/brick/brick1 49155 0 Y >>>>>> 3852 >>>>>> Brick 10.104.0.2:/gluster2/brick/brick1 49158 0 Y >>>>>> 68955 >>>>>> Brick 10.104.0.3:/gluster2/brick/brick1 49164 0 Y >>>>>> 94527 >>>>>> Brick 10.104.0.1:/gluster2/brick/brick2 49156 0 Y >>>>>> 3851 >>>>>> Brick 10.104.0.2:/gluster2/brick/brick2 49159 0 Y >>>>>> 68961 >>>>>> Brick 10.104.0.3:/gluster2/brick/brick2 49165 0 Y >>>>>> 94533 >>>>>> Brick 10.104.0.1:/gluster2/brick/brick3 49157 0 Y >>>>>> 3883 >>>>>> Brick 10.104.0.2:/gluster2/brick/brick3 49160 0 Y >>>>>> 68968 >>>>>> Brick 10.104.0.3:/gluster2/brick/brick3 49166 0 Y >>>>>> 94541 >>>>>> Self-heal Daemon on localhost N/A N/A Y >>>>>> 54356 >>>>>> Self-heal Daemon on 10.104.0.2 N/A N/A Y >>>>>> 962 >>>>>> Self-heal Daemon on 10.104.0.3 N/A N/A Y >>>>>> 108977 >>>>>> Self-heal Daemon on 10.104.0.4 N/A N/A Y >>>>>> 61603 >>>>>> >>>>>> Task Status of Volume volume2 >>>>>> ------------------------------------------------------------ >>>>>> ------------------ >>>>>> There are no active volume tasks >>>>>> >>>>>> I think ovirt can't read valid informations about gluster. >>>>>> I can't contiune upgrade of other hosts until this problem exist. >>>>>> >>>>>> Please help me:) >>>>>> >>>>>> >>>>>> Thanks >>>>>> >>>>>> Regards, >>>>>> >>>>>> Tibor >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Users mailing list -- users(a)ovirt.org >>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>> >>>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> >>> >> >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> >> >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community- >> guidelines/ >> List Archives: >> >> >

4 16

Does ovirt engine itself support high scalability (such as Load Balancing)?
by simiam 30 May '18

30 May '18

Hi, Does ovirt engine itself support high scalability (such as Load Balancing)? It means that i can add one or many engine servers to balance the load easily. Thanks.

1 1

start vm without engine
by David David 29 May '18

29 May '18

hi. How to start VM directly in hypervisor? ovirt-engine was crashed. VM's id is known. vdsclient VM, hasn't argumets for starting vm. Thanks.

3 2

Updated ovirt-engine packages were released for oVirt 4.2
by Lev Veyde 29 May '18

29 May '18

Hi, We have added an updated oVirt engine (4.2.3.8) to the oVirt 4.2 stable yum repo. It fixes BZ#1582483 [1]. [1] https://bugzilla.redhat.com/1582483 Thanks in advance, -- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Ovirt 4.2.4 - Trouble installing additional self hosted engine hosts
by Maton, Brett 29 May '18

29 May '18

Adding regular, non SHE hosts works fine, however I can't seem to add Self Hosted Engine to additional physical hosts. I think this is the problem, but I don't know what the solution is: 2018-05-29 08:00:52,502+0100 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Misc configuration': Cannot resolve ovirt_hosted_engine_ha module Deploy log attached.

3 4

CVE-2018-3639 - Important - oVirt - Speculative Store Bypass
by Sandro Bonazzola 29 May '18

29 May '18

As you may have already heard, an industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of Load & Store instructions. This issue is well described by CVE-2018-3639 announce available at https://access.redhat.com/security/cve/cve-2018-3639. oVirt team has released right now an update of ovirt-engine to version 4.2.3.7 which add support for SSBD CPUs in order to mitigate the security issue. If you are running oVirt on Red Hat Enterprise Linux, please apply updates described in https://access.redhat.com/security/cve/cve-2018-3639. If you are running oVirt on CentOS Linux please apply updated described by: CESA-2018:1629 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022843.html> CESA-2018:1632 Important CentOS 7 libvirt Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022840.html> CESA-2018:1649 Important CentOS 7 java-1.8.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022839.html> CESA-2018:1648 Important CentOS 7 java-1.7.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022838.html> An update for qemu-kvm-ev has been also tagged for release and announced with CESA-2018:1655 Important: qemu-kvm-ev security update <https://lists.centos.org/pipermail/centos-virt/2018-May/005804.html> but due to some issues in CentOS release process for Virt SIG content, it is not yet available on mirrors. We are working with CentOS community to get the packages signed and published as soon as possible. In the meanwhile you can still get the update package by enabling the test repository https://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common/ on your systems or manually installing the package from the repository. If you're running oVirt on a different Linux distribution, please check with your vendor for available updates. Please note that to fully mitigate this vulnerability, system administrators must apply both hardware “microcode” updates and software patches that enable new functionality. At this time, microprocessor microcode will be delivered by the individual manufacturers. The oVirt team recommends end users and systems administrator to apply any available updates as soon as practical. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

6 10

SSH into guest VM
by 03ce007＠gmail.com 29 May '18

29 May '18

I have self-hosted-engine (4.2) deployed successfully on cento (7.4) server. The physical server has 'ovirt' as hostname and the self-hosted engineVM deployed and running on it has 'engine.ovirt' as fdqn. I can successfully create new VM using the oVirt.vm-infra example playbook. But what other config/var i need to add in them so that I can ssh into this new VM. Some example, tips, hints would be helpful. Thank you.

3 4

cache and viodiskcache parameters in documentation
by stefanos＠prismatelecomtesting.com 28 May '18

28 May '18

Hi, on chapter 6.13.1 "Live Migration Prerequisites" [1] of the RHV 4.2 Virtual Machine Management Guide, there is written: ____________ At a minimum, for successful live migration of virtual machines to be possible: [...] The migrating virtual machine must not have the cache!=none custom property set. ____________ However I can't find any custom property called "cache" under Edit Virtual Machine --> Custom Properties but only "viodiskcache". As a matter of fact, Appendix A of the same guide [2] reports the following statement: "If viodiskcache is enabled, the virtual machine cannot be live migrated" that suggest viodiskcache as the correct parameter. Are the two statements contradictory? Thank you. Stefano Stagnaro [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… [2] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht…

2 2

Bad volume specification
by Bryan Sockel 28 May '18

28 May '18

Hi, I am having to rebuild my ovirt instance for a couple of reasons. I have setup a temporary ovirt portal to migrate my setup to while i rebuild my production portal. I have run int a couple of VM's that will no longer start. Everything that i am seeing is identical to this article - https://access.redhat.com/solutions/2423391 VM devel-build is down with error. Exit message: Bad volume specification {'serial': 'ec7a3258-7a99-4813-aa7d-dceb727a1975', 'index': 0, 'iface': 'virtio', 'apparentsize': '1835008', 'specParams': {}, 'cache': 'none', 'imageID': 'ec7a3258-7a99-4813-aa7d-dceb727a1975', 'truesize': '1777664', 'type': 'disk', 'domainID': '2b79768f-a329-4eab-81e0-120a81ac8906', 'reqsize': '0', 'format': 'cow', 'poolID': '9e7d643c-592d-11e8-82eb-005056b41d15', 'device': 'disk', 'path': '/rhev/data-center/9e7d643c-592d-11e8-82eb-005056b41d15/2b79768f-a329-4eab-81e0-120a81ac8906/images/ec7a3258-7a99-4813-aa7d-dceb727a1975/8f4ddee4-68b3-48e9-be27-0231557f5218', 'propagateErrors': 'off', 'name': 'vda', 'bootOrder': '1', 'volumeID': '8f4ddee4-68b3-48e9-be27-0231557f5218', 'diskType': 'file', 'alias': 'ua-ec7a3258-7a99-4813-aa7d-dceb727a1975', 'discard': False}. Currently running version 4.2.3.5-1 Is there anyway to recover the image, or even just be able to mount the drive to another vm to extract data. Thank You

2 2

second deploy hosted engine, engine VM is shut dwon
by dhy336＠sina.com 28 May '18

28 May '18

HiI first deploy hosted engine is failed， then deploy hosted engine, after ansible run "name: Add host ovirt_hosts:"(bootstrap_local_vm.yml), engine VM is shut dwon, why to shutown engine VM?

1 0

Reference architecture for oVirt Gluster HCI
by Karli Sjöberg 28 May '18

28 May '18

1 0

ovirt guest agent epel 6 and rhevm in the name
by Gianluca Cecchi 28 May '18

28 May '18

Hello, I have updated one test environment to 4.2 (it was in 4.1.9) I have a guest in Oracle Linux 6 and epel 6 repo enabled. After powering down and start the VM, I saw the exclamation mark regarding ovirt-guest-agent latest version needed. On the VM the process was dead and I took the time of updatng it from ovirt-guest-agent-1.0.12-4.el6.noarch to ovirt-guest-agent-1.0.13-2.el6.noarch and start the agent. All seems ok; no exclamation mark now and I see the ip addresses of the guest in 4.2 web admin gui. But in log of ovirt-guest-agent I see: MainThread::ERROR::2018-05-28 14:34:55,711::ovirt-guest-agent::140::root::Unhandled exception in oVirt guest agent! Traceback (most recent call last): File "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 134, in <module> agent.run(daemon, pidfile) File "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 65, in run self.agent = LinuxVdsAgent(config) File "/usr/share/ovirt-guest-agent/GuestAgentLinux2.py", line 466, in __init__ AgentLogicBase.__init__(self, config) File "/usr/share/ovirt-guest-agent/OVirtAgentLogic.py", line 188, in __init__ self.vio = VirtIoChannel(config.get("virtio", "device")) File "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 151, in __init__ self._stream = VirtIoStream(vport_name) File "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 132, in __init__ self._vport = os.open(vport_name, os.O_RDWR) OSError: [Errno 2] No such file or directory: '/dev/virtio-ports/com.redhat.rhevm.vdsm' MainThread::INFO::2018-05-28 14:42:45,535::ovirt-guest-agent::59::root::Starting oVirt guest agent The status of files under the indicated directory is: # ll /dev/virtio-ports/ total 0 lrwxrwxrwx 1 root root 11 May 28 14:34 com.redhat.spice.0 -> ../vport0p3 lrwxrwxrwx 1 root root 11 May 28 14:34 org.qemu.guest_agent.0 -> ../vport0p2 lrwxrwxrwx 1 root root 11 May 28 14:42 ovirt-guest-agent.0 -> ../vport0p1 # Anything to be done at my side at guest/host configuration level? Thanks, Gianluca

1 1

Does ovirt engine itself support high scalability
by simiam 28 May '18

28 May '18

Does ovirt engine itself support high scalability?

1 0

CentOS7 Install Failure to Shutdown
by Matthew Wimpelberg 28 May '18

28 May '18

I have ovirt 4.2.3.5-1.el7.centos installed and am unable to cleanly reboot the host machine. The only way I can reboot is to press and hold the power button which causes an unclean shutdown of the engine vm. I can upload logs if necessary I'm just not sure where to upload them to.

2 1

Fwd: External ceph storage
by Leo David 27 May '18

27 May '18

---------- Forwarded message --------- From: Leo David <leoalex(a)gmail.com> Date: Sun, May 27, 2018, 20:01 Subject: Re: [ovirt-users] External ceph storage To: Luca 'remix_tj' Lorenzetto <lorenzetto.luca(a)gmail.com> Indeed, you right. Will setup the gws while waiting for a maybe future native ceph connection, which in my oppinion would bring a lot of power to oVirt. On Sun, May 27, 2018, 19:48 Luca 'remix_tj' Lorenzetto < lorenzetto.luca(a)gmail.com> wrote: > I think is the best option. Setting up a sma openstack setup only for it > is not worth the hassle. > > Luca > > Il dom 27 mag 2018, 18:44 Leo David <leoalex(a)gmail.com> ha scritto: > >> Ok, so since i dont have openstack installed (which would put cinder >> between ceph and ovirt ), the only option remains the iscsi gw... >> Thank you very much ! >> >> On Sun, May 27, 2018, 18:14 Luca 'remix_tj' Lorenzetto < >> lorenzetto.luca(a)gmail.com> wrote: >> >>> No, >>> >>> The only way you have is to configure cinder to manage ceph pool or in >>> alternative you have to deploy an iscsi gateway, no other ways are >>> available at the moment. >>> >>> So you can't use rbd directly. >>> >>> Luca >>> >>> Il dom 27 mag 2018, 16:54 Leo David <leoalex(a)gmail.com> ha scritto: >>> >>>> Thank you Luca, >>>> At the moment i would try the cinder storage provider, since we already >>>> have a proxmox cluster directly connecting to ceph. The problem is that I >>>> just could not find a straight way to do this. >>>> ie: Specify the ceph monitors and ceph pool to connect to. Can oVirt >>>> directly connect to ceph monitors ? How the configuration should be done if >>>> so ? >>>> Thank you very much ! >>>> >>>> >>>> On Sun, May 27, 2018, 17:20 Luca 'remix_tj' Lorenzetto < >>>> lorenzetto.luca(a)gmail.com> wrote: >>>> >>>>> Hello, >>>>> >>>>> Yes, using cinder or through iscsi gateway. >>>>> >>>>> For a simpler setup i suggest the second option. >>>>> >>>>> Luca >>>>> >>>>> Il dom 27 mag 2018, 16:08 Leo David <leoalex(a)gmail.com> ha scritto: >>>>> >>>>>> Hello everyone, >>>>>> I am new to ovirt and very impressed of its features. I would like to >>>>>> levereage on our existing ceph cluster to provide rbd images for vm hdds, >>>>>> is this possible to achieve ? >>>>>> Thank you very much ! >>>>>> Regards, >>>>>> Leo >>>>>> _______________________________________________ >>>>>> Users mailing list -- users(a)ovirt.org >>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>> >>>>>

1 0

Failed to complete VM name creation fills the log every minute
by acavasiljevic＠gmail.com 27 May '18

27 May '18

Hi, Could you please help. Every 30 seconds I get an error "Failed to complete VM name creation" The task was started but stopped after a while. I have killed all tasks : $ su - postgres $ psql -d engine -U postgres > select * from job order by start_time desc; > select DeleteJob('702e9f6a-e2a3-4113-bd7d-3757ba6bc4ef'); I run: oVirt Engine Version: 4.1.9.1-1.el7.centos Thank you very much. Best regards,

1 0

Re: External ceph storage
by Luca 'remix_tj' Lorenzetto 27 May '18

27 May '18

Remember always to reply to the list, youur feedback will return back to the devs! Il dom 27 mag 2018, 19:01 Leo David <leoalex(a)gmail.com> ha scritto: > Indeed, you right. Will setup the gws while waiting for a maybe future > native ceph connection, which in my oppinion would bring a lot of power to > oVirt. > > On Sun, May 27, 2018, 19:48 Luca 'remix_tj' Lorenzetto < > lorenzetto.luca(a)gmail.com> wrote: > >> I think is the best option. Setting up a sma openstack setup only for it >> is not worth the hassle. >> >> Luca >> >> Il dom 27 mag 2018, 18:44 Leo David <leoalex(a)gmail.com> ha scritto: >> >>> Ok, so since i dont have openstack installed (which would put cinder >>> between ceph and ovirt ), the only option remains the iscsi gw... >>> Thank you very much ! >>> >>> On Sun, May 27, 2018, 18:14 Luca 'remix_tj' Lorenzetto < >>> lorenzetto.luca(a)gmail.com> wrote: >>> >>>> No, >>>> >>>> The only way you have is to configure cinder to manage ceph pool or in >>>> alternative you have to deploy an iscsi gateway, no other ways are >>>> available at the moment. >>>> >>>> So you can't use rbd directly. >>>> >>>> Luca >>>> >>>> Il dom 27 mag 2018, 16:54 Leo David <leoalex(a)gmail.com> ha scritto: >>>> >>>>> Thank you Luca, >>>>> At the moment i would try the cinder storage provider, since we >>>>> already have a proxmox cluster directly connecting to ceph. The problem is >>>>> that I just could not find a straight way to do this. >>>>> ie: Specify the ceph monitors and ceph pool to connect to. Can oVirt >>>>> directly connect to ceph monitors ? How the configuration should be done if >>>>> so ? >>>>> Thank you very much ! >>>>> >>>>> >>>>> On Sun, May 27, 2018, 17:20 Luca 'remix_tj' Lorenzetto < >>>>> lorenzetto.luca(a)gmail.com> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> Yes, using cinder or through iscsi gateway. >>>>>> >>>>>> For a simpler setup i suggest the second option. >>>>>> >>>>>> Luca >>>>>> >>>>>> Il dom 27 mag 2018, 16:08 Leo David <leoalex(a)gmail.com> ha scritto: >>>>>> >>>>>>> Hello everyone, >>>>>>> I am new to ovirt and very impressed of its features. I would like >>>>>>> to levereage on our existing ceph cluster to provide rbd images for vm >>>>>>> hdds, is this possible to achieve ? >>>>>>> Thank you very much ! >>>>>>> Regards, >>>>>>> Leo >>>>>>> _______________________________________________ >>>>>>> Users mailing list -- users(a)ovirt.org >>>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>>> >>>>>>

1 0

Re: External ceph storage
by Luca 'remix_tj' Lorenzetto 27 May '18

27 May '18

I think is the best option. Setting up a sma openstack setup only for it is not worth the hassle. Luca Il dom 27 mag 2018, 18:44 Leo David <leoalex(a)gmail.com> ha scritto: > Ok, so since i dont have openstack installed (which would put cinder > between ceph and ovirt ), the only option remains the iscsi gw... > Thank you very much ! > > On Sun, May 27, 2018, 18:14 Luca 'remix_tj' Lorenzetto < > lorenzetto.luca(a)gmail.com> wrote: > >> No, >> >> The only way you have is to configure cinder to manage ceph pool or in >> alternative you have to deploy an iscsi gateway, no other ways are >> available at the moment. >> >> So you can't use rbd directly. >> >> Luca >> >> Il dom 27 mag 2018, 16:54 Leo David <leoalex(a)gmail.com> ha scritto: >> >>> Thank you Luca, >>> At the moment i would try the cinder storage provider, since we already >>> have a proxmox cluster directly connecting to ceph. The problem is that I >>> just could not find a straight way to do this. >>> ie: Specify the ceph monitors and ceph pool to connect to. Can oVirt >>> directly connect to ceph monitors ? How the configuration should be done if >>> so ? >>> Thank you very much ! >>> >>> >>> On Sun, May 27, 2018, 17:20 Luca 'remix_tj' Lorenzetto < >>> lorenzetto.luca(a)gmail.com> wrote: >>> >>>> Hello, >>>> >>>> Yes, using cinder or through iscsi gateway. >>>> >>>> For a simpler setup i suggest the second option. >>>> >>>> Luca >>>> >>>> Il dom 27 mag 2018, 16:08 Leo David <leoalex(a)gmail.com> ha scritto: >>>> >>>>> Hello everyone, >>>>> I am new to ovirt and very impressed of its features. I would like to >>>>> levereage on our existing ceph cluster to provide rbd images for vm hdds, >>>>> is this possible to achieve ? >>>>> Thank you very much ! >>>>> Regards, >>>>> Leo >>>>> _______________________________________________ >>>>> Users mailing list -- users(a)ovirt.org >>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>> >>>>

1 0

Re: Failing to install self hosted engine - 4.2.4
by Simone Tiraboschi 27 May '18

27 May '18

On Sun, May 27, 2018 at 11:32 AM, Maton, Brett <matonb(a)ltresources.co.uk> wrote: > Thanks Simone, > > I think the problem is that /tmp is mounted noexec by default on my > servers. > Remounting and enabling exec seems to fix the problem. > > I think that allowing users to specify a working temp space would be > better than assuming that /tmp is mounted exec and also in my case big > enough to store the hosted engine vm (which the installer doesn't check, it > just fails late in the install process). > > If you execute hosted-engine-setup from CLI it will honor TMPDIR env variable (with /var/tmp as default) but I don't think your issue is there indeed your bootstrap engine VM was running. Your issue was related to the execution of host-deploy code: host-deploy is the code used to configure the host to be used as an hypervisor, the engine copies it over ssh to the host under /tmp and executes it there so your issue with noexec on /tmp. I'm not aware of any way to customize host-deploy location. > Regards, > Brett > > On 26 May 2018 at 21:25, Simone Tiraboschi <stirabos(a)redhat.com> wrote: > >> >> >> On Sat, May 26, 2018 at 11:10 AM, Maton, Brett <matonb(a)ltresources.co.uk> >> wrote: >> >>> Hi, >>> >>> I can't see in the log what the problem is, I expect it's something >>> simple though... >>> Hoping that someone can see what the problem is. >>> >>> engine setup log attached. >>> >> >> 2018-05-26 09:56:09,676+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils >> ansible_utils._process_output:98 fatal: [localhost]: FAILED! => >> {"ansible_facts": {"ovirt_hosts": [{"address": "node1.example.com", >> "affinity_labels": [], "auto_numa_status": "unknown", "certificate": >> {"organization": "testlab.lan", "subject": "O=testlab.lan,CN=node1.exampl >> e.com"}, "cluster": {"href": "/ovirt-engine/api/clusters/dd >> a509fe-60c0-11e8-ac4e-00163e2285d7", "id": "dda509fe-60c0-11e8-ac4e-00163e2285d7"}, >> "comment": "", "cpu": {"speed": 0.0, "topology": {}}, "device_passthrough": >> {"enabled": false}, "devices": [], "external_network_provider_configurations": >> [], "external_status": "ok", "hardware_information": >> {"supported_rng_sources": []}, "hooks": [], "href": >> "/ovirt-engine/api/hosts/b0976daa-e4b5-4881-a59b-49f9eb51f7c5", "id": >> "b0976daa-e4b5-4881-a59b-49f9eb51f7c5", "katello_errata": [], >> "kdump_status": "unknown", "ksm": {"enabled": false}, >> "max_scheduling_memory": 0, "memory": 0, "name": "node1.example.com", >> "network_attachments": [], "nics": [], "numa_nodes": [], "numa_supported": >> false, "os": {"custom_kernel_cmdline": ""}, "permissions": [], "port": >> 54321, "power_management": {"automatic_pm_enabled": true, "enabled": false, >> "kdump_detection": true, "pm_proxies": []}, "protocol": "stomp", >> "se_linux": {}, "spm": {"priority": 5, "status": "none"}, "ssh": >> {"fingerprint": "SHA256:xh1kvHMx+qp3q2L4lxf4fwra9lCAVxlfAGiVBVa7I7M", >> "port": 22}, "statistics": [], "status": "install_failed", >> "storage_connection_extensions": [], "summary": {"total": 0}, "tags": >> [], "transparent_huge_pages": {"enabled": false}, "type": "rhel", >> "unmanaged_networks": [], "update_available": false}]}, "attempts": 120, >> "changed": false} >> >> The engine failed to deploy your host and indeed we see "status": >> "install_failed" >> but to understand why it failed you have to consult host-deploy logs. >> You can find them under /var/log/ovirt-engine/host-deploy on the engine >> VM or also on your host in a directory inside hosted-engine-setup logs dir >> if hosted-engine-setup correctly managed to fetch them from the engine VM. >> >> >> >>> >>> Regards, >>> Brett >>> >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> >>> >> >

1 0

External ceph storage
by Leo David 27 May '18

27 May '18

Hello everyone, I am new to ovirt and very impressed of its features. I would like to levereage on our existing ceph cluster to provide rbd images for vm hdds, is this possible to achieve ? Thank you very much ! Regards, Leo

2 1

Re: hosted engine setup error
by dhy336＠sina.com 27 May '18

27 May '18

hi Yanirthis is my vdsm.log vdsm run prepareForShutdown lead to engine VM shudown? why shutdown engine VM,when deploy hosted engine? thanks 2018-05-27 18:24:16,020+0800 INFO (MainThread) [vds] Received signal 15, shutting down (vdsmd:67)2018-05-27 18:24:21,028+0800 INFO (MainThread) [jsonrpc.JsonRpcServer] Stopping JsonRPC Server (__init__:703)2018-05-27 18:24:21,030+0800 INFO (MainThread) [vds] Stopping http server (http:79)2018-05-27 18:24:21,030+0800 INFO (http) [vds] Server stopped (http:69)2018-05-27 18:24:21,031+0800 INFO (MainThread) [root] Unregistering all secrets (secret:91)2018-05-27 18:24:21,031+0800 INFO (MainThread) [vds] Stopping QEMU-GA poller (qemuguestagent:116)2018-05-27 18:24:21,032+0800 INFO (MainThread) [vdsm.api] START prepareForShutdown(options=None) from=internal, task_id=d3137135-e4f8-44ef-ac4c-d1687606fb02 (api:46)2018-05-27 18:24:21,094+0800 INFO (MainThread) [storage.Monitor] Shutting down domain monitors (monitor:222)2018-05-27 18:24:21,094+0800 INFO (MainThread) [storage.check] Stopping check service (check:104)2018-05-27 18:24:21,094+0800 INFO (check/loop) [storage.asyncevent] Stopping <EventLoop running=True closed=False at 0x43126736> (asyncevent:220) ----- Original Message ----- From: <dhy336(a)sina.com> To: "Yanir Quinn" <yquinn(a)redhat.com> Cc: users <users(a)ovirt.org> Subject: [ovirt-users] Re: hosted engine setup error Date: 2018-05-27 18:51 thanks, I find when hosted-engine -deloy run [Get ovirtmgmt route table id], my engine VM is shutdown,and /var/log/message show my engine vm is powered down by guest-shutdown,[ INFO ] TASK [Get ovirtmgmt route table id][ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "ip rule list | grep ovirtmgmt | sed s/\\\\[.*\\\\]\\ //g | awk '{ print $9 }'", "delta": "0:00:00.004175", "end": "2018-05-26 17:41:11.892218", "rc": 0, "start": "2018-05-26 17:41:11.888043", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}[ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook[ INFO ] Stage: Clean up[ INFO ] Cleaning temporary resources[ INFO ] TASK [Gathering Facts][ INFO ] ok: [localhost][ INFO ] TASK [Remove local vm dir] /var/log/message May 26 09:32:23 engine systemd: Reloading.May 26 09:32:24 engine python: ansible-file Invoked with directory_mode=None force=False remote_src=None path=/root/heanswers.conf owner=None follow=False group=None unsafe_writes=None state=absent content=NOT_LOGGING_PARAMETER serole=None diff_peek=None setype=None selevel=None original_basename=None regexp=None validate=None src=None seuser=None recurse=False delimiter=None mode=None attributes=None backup=NoneMay 26 09:32:38 engine systemd-logind: Removed session 3.May 26 09:32:48 engine qemu-ga: info: guest-shutdown called, mode: powerdownMay 26 09:32:48 engine systemd: Started Delayed Shutdown Service.May 26 09:32:48 engine systemd: Starting Delayed Shutdown Service...May 26 09:32:48 engine systemd-shutdownd: Shutting down at Sat 2018-05-26 17:32:48 CST (poweroff)...May 26 09:32:48 engine systemd-shutdownd: Creating /run/nologin, blocking further logins...May 26 09:32:48 engine systemd: Stopping QEMU Guest Agent...May 26 09:32:48 engine systemd: Stopping Session 1 of user root.May 26 09:32:48 engine systemd: Stopped target Multi-User System.May 26 09:32:48 engine systemd: Stopping Multi-User System.May 26 09:32:48 engine systemd: Stopped Execute cloud user/final scripts.May 26 09:32:48 engine systemd: Stopping Execute cloud user/final scripts...May 26 09:32:48 engine systemd: Stopping oVirt Engine...May 26 09:32:48 engine sshd[24523]: Received signal 15; terminating.May 26 09:32:48 engine systemd: Stopping OpenSSH server daemon...May 26 09:32:48 engine systemd: Stopping The Apache HTTP Server...----- Original Message ----- From: Yanir Quinn <yquinn(a)redhat.com> To: dhy336(a)sina.com Cc: users <users(a)ovirt.org> Subject: Re: Re: [ovirt-users] hosted engine setup error Date: 2018-05-27 16:46 According to BZ : https://bugzilla.redhat.com/show_bug.cgi?id=1540451#c19you should retry with a newer kernel >= -851 if possible .If you still get the error please provide full setup and vdsm logs. On Fri, May 25, 2018 at 11:54 AM, <dhy336(a)sina.com> wrote: Hi thanks for your reponse, I try to do by your guide, but it is not work. my kernel version is 3.10.0-693.11.1.el7.x86_64.besides, I try to do hosted-engine --deploy in my Virtual machine is work. but it is not work in Physical Machine ----- Original Message ----- From: Yanir Quinn <yquinn(a)redhat.com> To: dhy336(a)sina.com Cc: users <users(a)ovirt.org> Subject: Re: [ovirt-users] hosted engine setup error Date: 2018-05-24 18:35 Hi There is a BZ with a similar issue: https://bugzilla.redhat.com/show_bug.cgi?id=1546839 To sum things up, try stopping the network manager and restarting your network if you are using a RH distribution, e,g. : systemctl stop NetworkManager systemctl restart networkAnd check what is your kernel version. On Wed, May 23, 2018 at 5:03 PM, <dhy336(a)sina.com> wrote: hiI deploy ovirt-engine-4.2.2 hosted-engine by #hosted-engine --deploy, but face some error bridge ovirtmgmt is not configure, i should how to do? thanks [ INFO ] TASK [Get ovirtmgmt route table id][ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "ip rule list | grep ovirtmgmt | sed s/\\\\[.*\\\\]\\ //g | awk '{ print $9 }'", "delta": "0:00:00.010899", "end": "2018-05-23 20:03:21.222559", "rc": 0, "start": "2018-05-23 20:03:21.211660", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}[ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook[ INFO ] Stage: Clean up[ INFO ] Cleaning temporary resources vdsm.log 2018-05-23 19:55:15,305+0800 INFO (vm/bfc6f7cf) [virt.vm] (vmId='bfc6f7cf-3e8d-4368-97f8-78a5c74a5175') VM wrapper has started (vm:2619)2018-05-23 19:55:15,454+0800 INFO (vm/bfc6f7cf) [virt.vm] (vmId='bfc6f7cf-3e8d-4368-97f8-78a5c74a5175') Starting connection (guestagent:245)2018-05-23 19:55:15,458+0800 ERROR (vm/bfc6f7cf) [virt.vm] (vmId='bfc6f7cf-3e8d-4368-97f8-78a5c74a5175') Failed to connect to guest agent channel (vm:2403)Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2401, in _vmDependentInit self.guestAgent.start() File "/usr/lib/python2.7/site-packages/vdsm/virt/guestagent.py", line 246, in start self._prepare_socket() File "/usr/lib/python2.7/site-packages/vdsm/virt/guestagent.py", line 288, in _prepare_socket supervdsm.getProxy().prepareVmChannel(self._socketName) File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in __call__ return callMethod() File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda> **kwargs) File "<string>", line 2, in prepareVmChannel File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod raise convert_to_error(kind, result)OSError: [Errno 2] No such file or directory: '/var/lib/libvirt/qemu/channels/bfc6f7cf-3e8d-4368-97f8-78a5c74a5175.com.redhat.rhevm.vdsm'2018-05-23 19:55:15,480+0800 INFO (vm/bfc6f7cf) [virt.vm] (vmId='bfc6f7cf-3e8d-4368-97f8-78a5c74a5175') CPU running: domain initialization (vm:5908) [root@hosted-engine-test1 ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 52:54:00:6c:ee:a8 brd ff:ff:ff:ff:ff:ff inet 192.168.122.217/24 brd 192.168.122.255 scope global dynamic eth0 valid_lft 2936sec preferred_lft 2936sec inet6 fe80::834a:9cc1:df2:83f/64 scope link valid_lft forever preferred_lft forever18: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 9a:d1:bc:96:cc:c0 brd ff:ff:ff:ff:ff:ff19: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN qlen 1000 link/ether 52:54:00:55:06:26 brd ff:ff:ff:ff:ff:ff inet 192.168.124.1/24 brd 192.168.124.255 scope global virbr0 valid_lft forever preferred_lft forever20: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN qlen 1000 link/ether 52:54:00:55:06:26 brd ff:ff:ff:ff:ff:ff _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org

1 0

Re: hosted engine setup error
by dhy336＠sina.com 27 May '18

27 May '18

thanks, I find when hosted-engine -deloy run [Get ovirtmgmt route table id], my engine VM is shutdown,and /var/log/message show my engine vm is powered down by guest-shutdown,[ INFO ] TASK [Get ovirtmgmt route table id][ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "ip rule list | grep ovirtmgmt | sed s/\\\\[.*\\\\]\\ //g | awk '{ print $9 }'", "delta": "0:00:00.004175", "end": "2018-05-26 17:41:11.892218", "rc": 0, "start": "2018-05-26 17:41:11.888043", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}[ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook[ INFO ] Stage: Clean up[ INFO ] Cleaning temporary resources[ INFO ] TASK [Gathering Facts][ INFO ] ok: [localhost][ INFO ] TASK [Remove local vm dir] /var/log/message May 26 09:32:23 engine systemd: Reloading.May 26 09:32:24 engine python: ansible-file Invoked with directory_mode=None force=False remote_src=None path=/root/heanswers.conf owner=None follow=False group=None unsafe_writes=None state=absent content=NOT_LOGGING_PARAMETER serole=None diff_peek=None setype=None selevel=None original_basename=None regexp=None validate=None src=None seuser=None recurse=False delimiter=None mode=None attributes=None backup=NoneMay 26 09:32:38 engine systemd-logind: Removed session 3.May 26 09:32:48 engine qemu-ga: info: guest-shutdown called, mode: powerdownMay 26 09:32:48 engine systemd: Started Delayed Shutdown Service.May 26 09:32:48 engine systemd: Starting Delayed Shutdown Service...May 26 09:32:48 engine systemd-shutdownd: Shutting down at Sat 2018-05-26 17:32:48 CST (poweroff)...May 26 09:32:48 engine systemd-shutdownd: Creating /run/nologin, blocking further logins...May 26 09:32:48 engine systemd: Stopping QEMU Guest Agent...May 26 09:32:48 engine systemd: Stopping Session 1 of user root.May 26 09:32:48 engine systemd: Stopped target Multi-User System.May 26 09:32:48 engine systemd: Stopping Multi-User System.May 26 09:32:48 engine systemd: Stopped Execute cloud user/final scripts.May 26 09:32:48 engine systemd: Stopping Execute cloud user/final scripts...May 26 09:32:48 engine systemd: Stopping oVirt Engine...May 26 09:32:48 engine sshd[24523]: Received signal 15; terminating.May 26 09:32:48 engine systemd: Stopping OpenSSH server daemon...May 26 09:32:48 engine systemd: Stopping The Apache HTTP Server...----- Original Message ----- From: Yanir Quinn <yquinn(a)redhat.com> To: dhy336(a)sina.com Cc: users <users(a)ovirt.org> Subject: Re: Re: [ovirt-users] hosted engine setup error Date: 2018-05-27 16:46 According to BZ : https://bugzilla.redhat.com/show_bug.cgi?id=1540451#c19you should retry with a newer kernel >= -851 if possible .If you still get the error please provide full setup and vdsm logs. On Fri, May 25, 2018 at 11:54 AM, <dhy336(a)sina.com> wrote: Hi thanks for your reponse, I try to do by your guide, but it is not work. my kernel version is 3.10.0-693.11.1.el7.x86_64.besides, I try to do hosted-engine --deploy in my Virtual machine is work. but it is not work in Physical Machine ----- Original Message ----- From: Yanir Quinn <yquinn(a)redhat.com> To: dhy336(a)sina.com Cc: users <users(a)ovirt.org> Subject: Re: [ovirt-users] hosted engine setup error Date: 2018-05-24 18:35 Hi There is a BZ with a similar issue: https://bugzilla.redhat.com/show_bug.cgi?id=1546839 To sum things up, try stopping the network manager and restarting your network if you are using a RH distribution, e,g. : systemctl stop NetworkManager systemctl restart networkAnd check what is your kernel version. On Wed, May 23, 2018 at 5:03 PM, <dhy336(a)sina.com> wrote: hiI deploy ovirt-engine-4.2.2 hosted-engine by #hosted-engine --deploy, but face some error bridge ovirtmgmt is not configure, i should how to do? thanks [ INFO ] TASK [Get ovirtmgmt route table id][ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "ip rule list | grep ovirtmgmt | sed s/\\\\[.*\\\\]\\ //g | awk '{ print $9 }'", "delta": "0:00:00.010899", "end": "2018-05-23 20:03:21.222559", "rc": 0, "start": "2018-05-23 20:03:21.211660", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}[ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook[ INFO ] Stage: Clean up[ INFO ] Cleaning temporary resources vdsm.log 2018-05-23 19:55:15,305+0800 INFO (vm/bfc6f7cf) [virt.vm] (vmId='bfc6f7cf-3e8d-4368-97f8-78a5c74a5175') VM wrapper has started (vm:2619)2018-05-23 19:55:15,454+0800 INFO (vm/bfc6f7cf) [virt.vm] (vmId='bfc6f7cf-3e8d-4368-97f8-78a5c74a5175') Starting connection (guestagent:245)2018-05-23 19:55:15,458+0800 ERROR (vm/bfc6f7cf) [virt.vm] (vmId='bfc6f7cf-3e8d-4368-97f8-78a5c74a5175') Failed to connect to guest agent channel (vm:2403)Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2401, in _vmDependentInit self.guestAgent.start() File "/usr/lib/python2.7/site-packages/vdsm/virt/guestagent.py", line 246, in start self._prepare_socket() File "/usr/lib/python2.7/site-packages/vdsm/virt/guestagent.py", line 288, in _prepare_socket supervdsm.getProxy().prepareVmChannel(self._socketName) File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in __call__ return callMethod() File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda> **kwargs) File "<string>", line 2, in prepareVmChannel File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod raise convert_to_error(kind, result)OSError: [Errno 2] No such file or directory: '/var/lib/libvirt/qemu/channels/bfc6f7cf-3e8d-4368-97f8-78a5c74a5175.com.redhat.rhevm.vdsm'2018-05-23 19:55:15,480+0800 INFO (vm/bfc6f7cf) [virt.vm] (vmId='bfc6f7cf-3e8d-4368-97f8-78a5c74a5175') CPU running: domain initialization (vm:5908) [root@hosted-engine-test1 ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 52:54:00:6c:ee:a8 brd ff:ff:ff:ff:ff:ff inet 192.168.122.217/24 brd 192.168.122.255 scope global dynamic eth0 valid_lft 2936sec preferred_lft 2936sec inet6 fe80::834a:9cc1:df2:83f/64 scope link valid_lft forever preferred_lft forever18: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 9a:d1:bc:96:cc:c0 brd ff:ff:ff:ff:ff:ff19: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN qlen 1000 link/ether 52:54:00:55:06:26 brd ff:ff:ff:ff:ff:ff inet 192.168.124.1/24 brd 192.168.124.255 scope global virbr0 valid_lft forever preferred_lft forever20: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN qlen 1000 link/ether 52:54:00:55:06:26 brd ff:ff:ff:ff:ff:ff _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org

1 0

Re: Need advice using pacemaker on VMs for application HA
by wodel youchi 27 May '18

27 May '18

Hi, Thank you both for your responses, In a conclusion : - Don't mix up several solution that provide HA : - either choose oVirt HA. - or use software HA inside a VM. And since I need to monitor a service inside the VM for HA purpose, the implementation will be : - Create two VMs (nodes) without oVirt HA enabled. - Create the shared storage. - Configure pacemaker with stonith using fence rhev. - Test the configuration and my be try to test a hypervisor crash to see the behavior of the solution. Regards. 2018-05-24 17:12 GMT+01:00 Gianluca Cecchi <gianluca.cecchi(a)gmail.com>: > On Thu, May 24, 2018 at 6:05 PM, Gianluca Cecchi < > gianluca.cecchi(a)gmail.com> wrote: > >> >> >> >>> >>>> - What about the shared storage, we will use a shared disk on oVirt >>>> which does not support snapshot >>>> >>> >>> What is the question? >>> >> >> >> In the past I had to configure a virtual CentOS 6 cluster because I >> needed to replicate a problem I had in a physical production cluster and to >> verify if some actions/updates would have solved the problem. >> I had no more spare hw to configure an so using the poor-man method (dd + >> reconfigure) I had the cluster up and running with two twin nodes identical >> to the physical ones. >> I also opened this bugzilla to backport the el7 package to el6: >> https://bugzilla.redhat.com/show_bug.cgi?id=1446474 >> >> The intracluster network has been put on OVN btw >> >> But honestly I doubt I will use a virtual-cluster software stack to >> provide high availability to production services inside a VM. Too many >> inter-relations >> >> > I didn't complete the answer about storage. > Indeed if the cluster services need also a storage (eg a filesystem), you > should create dedicated virtual disks that you mark as shared and assign to > all the nodes of the virtual-cluster. > This compromise the snapshot functionality (of only the shared disks, you > can snapshot the boot disk and the not shared disks). > > HIH, > Gianluca > >

1 0

Ovirt 4.2.4 upgrade
by Maton, Brett 27 May '18

27 May '18

The 4.2.4 upgrade appears to have a database issue, i'm seeing these errors in the postgresql logs: 2018-05-24 16:27:08.292 UTC ERROR: relation "provider_binding_host_id" does not exist at character 15 2018-05-24 16:27:08.292 UTC QUERY: SELECT 1 FROM provider_binding_host_id WHERE vds_id = v_vds_id FOR UPDATE 2018-05-24 16:27:08.292 UTC CONTEXT: PL/pgSQL function updatehostproviderbinding(uuid,character varying[],character varying[]) line 3 at PERFORM Any suggestions ?

4 6

Re: hosted engine setup error
by dhy336＠sina.com 27 May '18

27 May '18

Hi thanks for your reponse, I try to do by your guide, but it is not work. my kernel version is 3.10.0-693.11.1.el7.x86_64.besides, I try to do hosted-engine --deploy in my Virtual machine is work. but it is not work in Physical Machine ----- Original Message ----- From: Yanir Quinn <yquinn(a)redhat.com> To: dhy336(a)sina.com Cc: users <users(a)ovirt.org> Subject: Re: [ovirt-users] hosted engine setup error Date: 2018-05-24 18:35 Hi There is a BZ with a similar issue: https://bugzilla.redhat.com/show_bug.cgi?id=1546839 To sum things up, try stopping the network manager and restarting your network if you are using a RH distribution, e,g. : systemctl stop NetworkManager systemctl restart networkAnd check what is your kernel version. On Wed, May 23, 2018 at 5:03 PM, <dhy336(a)sina.com> wrote: hiI deploy ovirt-engine-4.2.2 hosted-engine by #hosted-engine --deploy, but face some error bridge ovirtmgmt is not configure, i should how to do? thanks [ INFO ] TASK [Get ovirtmgmt route table id][ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "ip rule list | grep ovirtmgmt | sed s/\\\\[.*\\\\]\\ //g | awk '{ print $9 }'", "delta": "0:00:00.010899", "end": "2018-05-23 20:03:21.222559", "rc": 0, "start": "2018-05-23 20:03:21.211660", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}[ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook[ INFO ] Stage: Clean up[ INFO ] Cleaning temporary resources vdsm.log 2018-05-23 19:55:15,305+0800 INFO (vm/bfc6f7cf) [virt.vm] (vmId='bfc6f7cf-3e8d-4368-97f8-78a5c74a5175') VM wrapper has started (vm:2619)2018-05-23 19:55:15,454+0800 INFO (vm/bfc6f7cf) [virt.vm] (vmId='bfc6f7cf-3e8d-4368-97f8-78a5c74a5175') Starting connection (guestagent:245)2018-05-23 19:55:15,458+0800 ERROR (vm/bfc6f7cf) [virt.vm] (vmId='bfc6f7cf-3e8d-4368-97f8-78a5c74a5175') Failed to connect to guest agent channel (vm:2403)Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2401, in _vmDependentInit self.guestAgent.start() File "/usr/lib/python2.7/site-packages/vdsm/virt/guestagent.py", line 246, in start self._prepare_socket() File "/usr/lib/python2.7/site-packages/vdsm/virt/guestagent.py", line 288, in _prepare_socket supervdsm.getProxy().prepareVmChannel(self._socketName) File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in __call__ return callMethod() File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda> **kwargs) File "<string>", line 2, in prepareVmChannel File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod raise convert_to_error(kind, result)OSError: [Errno 2] No such file or directory: '/var/lib/libvirt/qemu/channels/bfc6f7cf-3e8d-4368-97f8-78a5c74a5175.com.redhat.rhevm.vdsm'2018-05-23 19:55:15,480+0800 INFO (vm/bfc6f7cf) [virt.vm] (vmId='bfc6f7cf-3e8d-4368-97f8-78a5c74a5175') CPU running: domain initialization (vm:5908) [root@hosted-engine-test1 ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 52:54:00:6c:ee:a8 brd ff:ff:ff:ff:ff:ff inet 192.168.122.217/24 brd 192.168.122.255 scope global dynamic eth0 valid_lft 2936sec preferred_lft 2936sec inet6 fe80::834a:9cc1:df2:83f/64 scope link valid_lft forever preferred_lft forever18: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 9a:d1:bc:96:cc:c0 brd ff:ff:ff:ff:ff:ff19: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN qlen 1000 link/ether 52:54:00:55:06:26 brd ff:ff:ff:ff:ff:ff inet 192.168.124.1/24 brd 192.168.124.255 scope global virbr0 valid_lft forever preferred_lft forever20: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN qlen 1000 link/ether 52:54:00:55:06:26 brd ff:ff:ff:ff:ff:ff _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org

2 1

Upload Image Error
by Peter Harman 27 May '18

27 May '18

Ovirt Users, I am running into a strange problem with uploading images through the webUI. When I test the connection on an upload I get “Connection to ovirt-imageio-proxy service has failed. Make sure the service is installed, configured, and ovirt-engine certificate is registered as a valid CA in the browser.” I have conducted this operation on several computers using both chrome and firefox and ensuring the certs were loaded into the browsers. I went to this page: https://ovirt.org/develop/release-management/features/infra/pki/ to find cert info and checked both the engine and hosts for the certificates and the identity of the certificates - everything seemed to match up. Next thing I looked at was the ovirt-imageio-proxy service. I checked it and restarted it below is a status output from one of the failed operations: [root@hpm-engine ~]# systemctl status ovirt-imageio-proxy ● ovirt-imageio-proxy.service - oVirt ImageIO Proxy Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2018-05-24 13:25:38 CDT; 1h 13min ago Main PID: 21239 (ovirt-imageio-p) Tasks: 2 CGroup: /system.slice/ovirt-imageio-proxy.service └─21239 /usr/bin/python /usr/bin/ovirt-imageio-proxy May 24 13:25:38 hpm-engine.server.local systemd[1]: Starting oVirt ImageIO Proxy... May 24 13:25:38 hpm-engine.server.local systemd[1]: Started oVirt ImageIO Proxy. May 24 14:38:02 hpm-engine.server.local ovirt-imageio-proxy[21239]: 127.0.0.1 - - [24/May/2018 14:38:02] "PUT /tickets/ HTTP/1.1" 200 0 ovirt-imageio-proxy service seems to check out. So, next step was checking out VDSM process output is below (NOTE: I redacted a bunch of unrelated warnings): [root@mothership ~]# systemctl status vdsmd -l ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-05-24 08:12:40 CDT; 6h ago Main PID: 3359 (vdsmd) Tasks: 58 CGroup: /system.slice/vdsmd.service ├─3359 /usr/bin/python2 /usr/share/vdsm/vdsmd └─6731 /usr/libexec/ioprocess --read-pipe-fd 68 --write-pipe-fd 67 --max-threads 10 --max-queued-requests 10 So VDSM doesn’t seem to be the issue. I changed a few settings here and there but mostly forget what I did (I changed it all back to defult) Some background information - I am using /etc/hosts for all the FQDN components - which seems to be working well. I checked the times to be sure the time matched up (I know this important for some security related issues.) In a somewhat funny note I disabled SSL on VDSM in one attempt at the issue and now know why you should not do that when engine is using SSL. Any help is appreciated. I am learning a lot and really thank everyone who develops Ovirt - it’s awesome. Peter Harman - Systems and Safety Cordinator | Homeyer Precision Manufacturing [Description: C:\Users\gruether\AppData\Local\Temp\Temp1_Homeyer Logo (2).zip\Homeyer Logo\Homeyer Logo.jpg] 16051 State Hwy 47, Marthasville, MO 63357| E pharman(a)homeyertool.com |<mailto:pharman@homeyertool.com%20%7C> P 636.433.2244 | F 636.433.5257

3 3