- Devel - oVirt List Archives

Unable to Build (Unable to find 'org/ovirt/engine/ui/webadmin/WebAdmin.gwt.xml)
by Ritesh Chikatwar 21 Oct '19

21 Oct '19

Hey Guys, Please do let me know what is causing me this issue. *NOTE:* I have not changed anything in this file. info register aspect org.ovirt.engine.ui.gwtaop.DontPrune [INFO] Loading inherited module 'org.ovirt.engine.ui.webadmin.WebAdmin' *[INFO] [ERROR] Unable to find 'org/ovirt/engine/ui/webadmin/WebAdmin.gwt.xml' on your classpath; could be a typo, or maybe you forgot to include a classpath entry for source?* [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for WebAdmin 4.4.0-SNAPSHOT: [INFO] [INFO] WebAdmin ........................................... FAILURE [ 1.548 s] [INFO] oVirt Server EAR ................................... SKIPPED [INFO] ovirt-engine maven make ............................ SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1.918 s [INFO] Finished at: 2019-10-21T11:30:20+05:30 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.8.0:compile (default-cli) on project webadmin: Command [[ [ERROR] /bin/sh -c '/usr/local/jdk-11.0.2/bin/java' '-javaagent:/home/ritesh/.m2/repository/org/aspectj/aspectjweaver/1.9.3.RC1/aspectjweaver-1.9.3.RC1.jar' '-Dgwt.jjs.permutationWorkerFactory=com.google.gwt.dev.ThreadedPermutationWorkerFactory' '-Dgwt.jjs.maxThreads=4' '-Djava.io.tmpdir=/home/ritesh/build/ovirt-engine/frontend/webadmin/modules/webadmin/target/tmp' '-Djava.util.prefs.systemRoot=/home/ritesh/build/ovirt-engine/frontend/webadmin/modules/webadmin/target/tmp' '-Djava.util.prefs.userRoot=/home/ritesh/build/ovirt-engine/frontend/webadmin/modules/webadmin/target/tmp' '-Djava.util.logging.config.class=org.ovirt.engine.ui.gwtaop.JavaLoggingConfig' '-Xms1024M' '-Xmx8192M' '-Dgwt.dontPrune=org\.ovirt\.engine\.core\.(common|compat)\..*' 'com.google.gwt.dev.Compiler' '-logLevel' 'INFO' '-war' '/home/ritesh/build/ovirt-engine/frontend/webadmin/modules/webadmin/target/webadmin-4.4.0-SNAPSHOT' '-localWorkers' '8' '-failOnError' '-XfragmentCount' '-1' '-sourceLevel' 'auto' '-gen' '/home/ritesh/build/ovirt-engine/frontend/webadmin/modules/webadmin/gen' 'org.ovirt.engine.ui.webadmin.WebAdmin' [ERROR] ]] failed with status 1. Thanks And Regards Ritesh Chikatwar

1 0

[oVirt] [CQ weekly status] [20-10-2019]
by Dusan Fodor 20 Oct '19

20 Oct '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.3*: GREEN (#1) Last failure was on 17-10 for ovirt-node-ng-image due to an issue with host it was building on. Next run passed well. . *CQ-Master:* YELLOW (#1 Last failure was on 18-10 caused by known, random add storage domain failure (test issue). Current running jobs for 4.3 [1] and master [2] can be found here: [1] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Have a nice week! Dusan ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3) _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-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/devel@ovirt.org/message/YCNCKRK3G4EJX…

1 0

Add existing Affinity Label to Host
by scott.fitzgerald＠oracle.com 18 Oct '19

18 Oct '19

As the title, have tried to add it using sysService.hostsService().hostService(hostID).affinityLabelsService().add().label(sysService.affinityLabelsService().labelService(labelID).get().send().label()).send(); and similar variants with no luck. TIA

2 2

Retrieve cluster status using the SDK
by Jamie Holohan 18 Oct '19

18 Oct '19

Using the SDK how can I retrieve a clusters (network) status. I am able to retrieve a cluster object using code like this: Cluster cluster = sysService.clustersService().clusterService(DataCenterUtils.getClusterObjectFromName(sysService, DEFAULT_CLUSTER_NAME).id()).get().send().cluster(); However I cannot see any variables associated with this object type that relate to its Network Status. The information i'm referring to can be found on the UI after creating a custom network. Starting on the left panel Navigate to Network -> Networks -> Custom Network -> Clusters Tab

2 1

vdsm has been tagged (v4.30.34)
by Milan Zamazal 17 Oct '19

17 Oct '19

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.7.0)
by Piotr Kliczewski 17 Oct '19

17 Oct '19

1 0

Clarifications on support@
by Marc Dequènes (Duck) 16 Oct '19

16 Oct '19

Quack, We do as a community provide help on the MLs and reply to JIRA tickets but there is no customer support as it is not a product but a community project. Historically, probably for some other purpose, support@ was created, but noone remembers why. Anyway, the alias redirected to postmaster so it was not very useful. There was also a ML which could not receive mails because of the alias but probably got noticed in the new ML UI when we migrated. Recently more people subscribed and posted requests using the UI. After discussing with the infra team, and to avoid confusion and unreplied requests on this channel, we decided to remove it. I thus unsubscribed people from the list so that they would notice it and then purged the list and alias. Regards. \_o<

1 0

Problem with vdsm 'make check'
by Kaustav Majumder 15 Oct '19

15 Oct '19

Hi, I am having an issue running make check on vdsm master. ` if [ -n "$NOSE_WITH_COVERAGE" ]; then \ mv .coverage .coverage-nose-py27; \ fi Traceback (most recent call last): File "../tests/testrunner.py", line 70, in <module> from vdsm import constants File "/home/kmajumde/work/git/vdsm/lib/vdsm/constants.py", line 29, in <module> from vdsm.common.constants import * # NOQA: F401, F403 ` Am I missing something? Do I need to run tests differently? -- Thanks, Kaustav Majumder

5 14

Re: Problem with vdsm 'make check'
by Prajith Kesava Prasad 15 Oct '19

15 Oct '19

hey, even im facing a issue with make check, i have installed all the libraries, the following occurs on fedora 29, IDE:Pycharm could some one help me with this? Thanks, Prajith Kesava Prasad

2 3

Need to install lago plugin but get circular issue with dependancies
by raymond.francis＠oracle.com 15 Oct '19

15 Oct '19

Having setup Lago and wishing to run the system tests ./run_suite.sh basic-suite-4.3 I get the below error which leads to a circular issue... @ Initialize and populate prefix: ERROR (in 0:00:00) Unknown VM type: ovirt-engine, available types: default, maybe you need to install lago plugin + on_exit + [[ 2 -ne 0 ]] + logger.error 'on_exit: Exiting with a non-zero status' + logger.log ERROR 'on_exit: Exiting with a non-zero status' + set +x 2019-10-14 18:09:43.202994574+0100 run_suite.sh::on_exit::ERROR:: on_exit: Exiting with a non-zero status + logger.info 'Dumping lago env status' + logger.log INFO 'Dumping lago env status' + set +x 2019-10-14 18:09:43.207157153+0100 run_suite.sh::on_exit::INFO:: Dumping lago env status + env_status + cd /root/pip-19.2.3/ovirt-system-tests/deployment-basic-suite-4.3 ./run_suite.sh: line 265: cd: /root/pip-19.2.3/ovirt-system-tests/deployment-basic-suite-4.3: No such file or directory + lago status Unable to find workdir in /root/pip-19.2.3/ovirt-system-tests + cd - When i try to install lago, i get this Error: Package: python-lago-0.46.0-1.el7.noarch (lago) Requires: qemu-kvm-rhev >= 2.1.2 Error: Package: python-lago-0.46.0-1.el7.noarch (lago) Requires: qemu-img-rhev >= 2.1.2 Trying to install either gets this [root@dub-mgrfarm113 ovirt-system-tests]# yum install -y qemu-img-rhev Loaded plugins: ulninfo, versionlock Package 10:qemu-img-ev-2.6.0-28.el7_3.3.1.x86_64 is obsoleted by 15:qemu-3.1.0-5.el7.x86_64 which is already installed Nothing to do [root@dub-mgrfarm113 ovirt-system-tests]# yum install -y qemu-kvm-rhev Loaded plugins: ulninfo, versionlock Package 10:qemu-kvm-ev-2.6.0-28.el7_3.3.1.x86_64 is obsoleted by 15:qemu-3.1.0-5.el7.x86_64 which is already installed Nothing to do Chicken and egg issue,any ideas?

2 2