- Users - oVirt List Archives

Tape Library!
by Nasrum Minallah Manzoor 09 Mar '18

09 Mar '18

--_000_HK2PR0401MB21646A0945881489B9291B0EE2DF0HK2PR0401MB2164_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I need help in configuring Amanda backup in virtual machine added to ovirt = node! How can I assign my FC tape library (TS 3100 in my case) to virtual m= achine! Regards, --_000_HK2PR0401MB21646A0945881489B9291B0EE2DF0HK2PR0401MB2164_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> Hi,<o:p></o:p> <o:p> </o:p> I need help in configuring Amanda backup in virtual = machine added to ovirt node! How can I assign my FC tape library (TS 3100 i= n my case) to virtual machine!<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Regards,<o:p></o:p> </div> </body> </html> --_000_HK2PR0401MB21646A0945881489B9291B0EE2DF0HK2PR0401MB2164_--

3 2

hosted-engine deploy fails at "Wait for the engine to come up on the target VM" step
by Kristian Petersen 09 Mar '18

09 Mar '18

I am trying to deploy oVirt with a self-hosted engine and the setup seems to go well until near the very end when the status message says: [ INFO ] TASK [Wait for the engine to come up on the target VM] [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": true, "cmd": ["hosted-engine", "--vm-status", "--json"], "delta": "0:0 0:00.216412", "end": "2018-03-07 16:02:02.677478", "rc": 0, "start": "2018-03-07 16:02:02.461066", "stderr": "", "stderr_lines": [], "stdout ": "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\": \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntim estamp=4679955 (Wed Mar 7 16:01:50 2018)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=4679956 (Wed Mar 7 16:01:51 2018)\\nconf_on_share d_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", \"hostname\": \"rhv1.cpms.byu.edu\", \"host-id\": 1, \"engin e-status\": {\"reason\": \"vm not running on this host\", \"health\": \"bad\", \"vm\": \"down\", \"detail\": \"unknown\"}, \"score\": 3400, \"stopped\": false, \"maintenance\": false, \"crc32\": \"d3a67cf7\", \"local_conf_timestamp\": 4679956, \"host-ts\": 4679955}, \"global_main tenance\": false}", "stdout_lines": ["{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\": \"metadata_parse_version=1\ \nmetadata_feature_version=1\\ntimestamp=4679955 (Wed Mar 7 16:01:50 2018)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=4679956 (Wed Mar 7 16:01:51 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", \"hostname\": \"rhv1.cpms. byu.edu\", \"host-id\": 1, \"engine-status\": {\"reason\": \"vm not running on this host\", \"health\": \"bad\", \"vm\": \"down\", \"detail\ ": \"unknown\"}, \"score\": 3400, \"stopped\": false, \"maintenance\": false, \"crc32\": \"d3a67cf7\", \"local_conf_timestamp\": 4679956, \" host-ts\": 4679955}, \"global_maintenance\": false}"]} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook Any ideas that might help? -- Kristian Petersen System Administrator Dept. of Chemistry and Biochemistry

2 1

Node Next Install Problem
by Matt Simonsen 08 Mar '18

08 Mar '18

This is a multi-part message in MIME format. --------------E92BB960D76982341190E690 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit I installed based on an older Node Next DVD (4.1.7) that has worked in the past and it doesn't appear to be working when I add it to a cluster. The installer says//it cannot queue package iproute. Is there a repo down or that has changed? Thanks for any suggestions. It appears yum is also broken:/ / /yum update Loaded plugins: fastestmirror, imgbased-persist, package_upload, product-id, : search-disabled-repos, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register. centos-opstools-release | 2.9 kB 00:00 ovirt-4.1 | 3.0 kB 00:00 ovirt-4.1-centos-gluster38 | 2.9 kB 00:00 One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot retrieve metalink for repository: ovirt-4.1-epel/x86_64. Please verify its path and try again / --------------E92BB960D76982341190E690 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> I installed based on an older Node Next DVD (4.1.7) that has worked in the past and it doesn't appear to be working when I add it to a cluster. The installer says it cannot queue package iproute. Is there a repo down or that has changed? Thanks for any suggestions. It appears yum is also broken: yum update Loaded plugins: fastestmirror, imgbased-persist, package_upload, product-id, : search-disabled-repos, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register. centos-opstools-release | 2.9 kB 00:00 ovirt-4.1 | 3.0 kB 00:00 ovirt-4.1-centos-gluster38 | 2.9 kB 00:00 One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot retrieve metalink for repository: ovirt-4.1-epel/x86_64. Please verify its path and try again </body> </html> --------------E92BB960D76982341190E690--

1 1

Re: [ovirt-users] Limitation in using Ovirt SSO Token
by Yaniv Kaul 08 Mar '18

08 Mar '18

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

2 3

Gluster Snapshot Schedule Failing on 4.2.1
by Hesham Ahmed 08 Mar '18

08 Mar '18

I am having issues with the Gluster Snapshot UI since upgrade to 4.2 and now with 4.2.1. The UI doesn't appear as I explained in the bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1530186 I can now see the UI when I clear the cookies and try the snapshots UI from within the volume details screen, however scheduled snapshots are not being created. The engine log shows a single error: 2018-03-07 20:00:00,051+03 ERROR [org.ovirt.engine.core.utils.timer.JobWrapper] (QuartzOvirtDBScheduler1) [12237b15] Failed to invoke scheduled method onTimer: null Anyone scheduling snapshots successfully wtih 4.2?

2 2

Importing VM fails with "No space left on device"
by Nicolas Ecarnot 08 Mar '18

08 Mar '18

Hello, When importing a VM, I'm facing the know bug : https://access.redhat.com/solutions/2770791 QImgError: ecode=1, stdout=[], stderr=['qemu-img: error while writing sector 93569024: No space left on device' The difference between my case and what is described in the RH webpage is that I have no "Failed to flush the refcount block cache". Here is what I see : > ecfbd1a4-f9d2-463a-ade6-def5bd217b43::DEBUG::2018-03-06 09:57:36,460::utils::718::root::(watchCmd) FAILED: <err> = ['qemu-img: error while writing sector 205517952: No space left on device']; <rc> = 1 > ecfbd1a4-f9d2-463a-ade6-def5bd217b43::ERROR::2018-03-06 09:57:36,460::image::865::Storage.Image::(copyCollapsed) conversion failure for volume ac08bc8d-1eea-449a-a102-cf763c6726c8 > Traceback (most recent call last): > File "/usr/share/vdsm/storage/image.py", line 860, in copyCollapsed > volume.fmt2str(dstVolFormat)) > File "/usr/lib/python2.7/site-packages/vdsm/qemuimg.py", line 207, in convert > raise QImgError(rc, out, err) > QImgError: ecode=1, stdout=[], stderr=['qemu-img: error while writing sector 205517952: No space left on device'], message=None > ecfbd1a4-f9d2-463a-ade6-def5bd217b43::ERROR::2018-03-06 09:57:36,461::image::878::Storage.Image::(copyCollapsed) Unexpected error > Traceback (most recent call last): > File "/usr/share/vdsm/storage/image.py", line 866, in copyCollapsed > raise se.CopyImageError(str(e)) > CopyImageError: low level Image copy failed: ("ecode=1, stdout=[], stderr=['qemu-img: error while writing sector 205517952: No space left on device'], message=None",) I followed the advices in the RH webpage (check if the figures are correct between the qemu-img sizes and the meta-data file), and they seem to be correct : root@serv-hv-adm30:/etc# qemu-img info /rhev/data-center/mnt/serv-lin-adm1.sdis.isere.fr\:_home_vmexport3/be2878c9-2c46-476b-bfae-8b02a4679022/images/a5d68d88-3b54-488d-a61e-7995a1906994/ac08bc8d-1eea-449a-a102-cf763c6726c8 image: /rhev/data-center/mnt/serv-lin-adm1.sdis.isere.fr:_home_vmexport3/be2878c9-2c46-476b-bfae-8b02a4679022/images/a5d68d88-3b54-488d-a61e-7995a1906994/ac08bc8d-1eea-449a-a102-cf763c6726c8 file format: qcow2 virtual size: 98G (105226698752 bytes) disk size: 97G cluster_size: 65536 Format specific information: compat: 0.10 refcount bits: 16 root@serv-hv-adm30:/etc# cat /rhev/data-center/mnt/serv-lin-adm1.sdis.isere.fr\:_home_vmexport3/be2878c9-2c46-476b-bfae-8b02a4679022/images/a5d68d88-3b54-488d-a61e-7995a1906994/ac08bc8d-1eea-449a-a102-cf763c6726c8.meta DOMAIN=be2878c9-2c46-476b-bfae-8b02a4679022 CTIME=1520318755 FORMAT=COW DISKTYPE=1 LEGALITY=LEGAL SIZE=205520896 VOLTYPE=LEAF DESCRIPTION= IMAGE=a5d68d88-3b54-488d-a61e-7995a1906994 PUUID=00000000-0000-0000-0000-000000000000 MTIME=0 POOL_UUID= TYPE=SPARSE EOF So I don't see what's wrong? -- Nicolas ECARNOT

2 1

Very Slow Console Performance - Windows 10
by FERNANDO FREDIANI 08 Mar '18

08 Mar '18

This is a multi-part message in MIME format. --------------C64C2289E18148FC52BD4390 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hello Has anyone installed a Windows 10 Virtual Machine ? I am having serious Console Performance issues even after installing the Ted Hat QXL controller from the virtio-win ISO. Someone informed in a forum having similar issues and have resolved by increasing the graphics card memory to 65536 by editing the XML (example below), but how is that possible in oVirt permanently ? <video> <model type='qxl' ram='131072' vram='131072' vgamem='65536' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> Thanks Fernando --------------C64C2289E18148FC52BD4390 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hello Has anyone installed a Windows 10 Virtual Machine ? I am having serious Console Performance issues even after installing the Ted Hat QXL controller from the virtio-win ISO. Someone informed in a forum having similar issues and have resolved by increasing the graphics card memory to 65536 by editing the XML (example below), but how is that possible in oVirt permanently ? <video> <model type='qxl' ram='131072' vram='131072' vgamem='<ins>65536</ins>' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> Thanks Fernando </body> </html> --------------C64C2289E18148FC52BD4390--

3 8

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

08 Mar '18

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

1 0

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

08 Mar '18

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

1 0

ovirt 4.2 gluster configuration
by Edoardo Mazza 08 Mar '18

08 Mar '18

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

2 1