- Users - oVirt List Archives

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