- Devel - oVirt List Archives

Host-passthrough CPU and migration
by Strahil Nikolov 27 Oct '19

27 Oct '19

Hello Community,Dev, does anyone know why only "Manual Migration" allows passing through the CPU from the Host to the VM ? In many environments, the Clusters are having the same CPU model in order to avoid any issues. Have you observed any issues with that ? Best Regards,Strahil Nikolov

2 1

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

26 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 25-10 for ovirt-host due to dependency issue. Patch ( 104248 <https://gerrit.ovirt.org/104248>) is pending to fix this. *CQ-Master:* YELLOW (#1 Last failure was on 25-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

Fwd: [Test-Announce] Fedora 31 Final is GO
by Sandro Bonazzola 24 Oct '19

24 Oct '19

FYI ---------- Forwarded message --------- Da: Ben Cotton <bcotton(a)redhat.com> Date: gio 24 ott 2019 alle ore 17:43 Subject: [Test-Announce] Fedora 31 Final is GO To: <logistics(a)lists.fedoraproject.org>, < test-announce(a)lists.fedoraproject.org>, < devel-announce(a)lists.fedoraproject.org> The Fedora 31 Final RC1.9 compose [1] is GO and will be shipped live on Tuesday, 29 October 2019. For more information please check the Go/No-Go meeting minutes [2] or logs [3]. Thank you to everyone who has worked on this release and getting it out on time. [1] https://dl.fedoraproject.org/pub/alt/stage/31_RC-1.9/ [2] https://meetbot.fedoraproject.org/fedora-meeting/2019-10-24/f31-final-go_no… [3] https://meetbot.fedoraproject.org/fedora-meeting/2019-10-24/f31-final-go_no… -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ test-announce mailing list -- test-announce(a)lists.fedoraproject.org To unsubscribe send an email to test-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedorapro… _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

1 0

VDSM master not building for el8 on ppc64le
by Sandro Bonazzola 24 Oct '19

24 Oct '19

Hi, can you please check why vdsm is not being built for el8 on ppc64le? Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

3 3

Ovirt System Tests: reposync fails during run_suite.sh
by raymond.francis＠oracle.com 24 Oct '19

24 Oct '19

I am currently setting up the Ovirt System Tests using the guide https://ovirt-system-tests.readthedocs.io/en/latest/general/running_tests/i… So we get to the run_suite.sh part. This calls a python script called put_host_image.py which tries to create a symlink to the current repo but hits an issue where the file (internal_repo/host_image) is said to not exist at the time. Output below python /Ray/ovirt-system-tests/common/scripts/put_host_image.py /Ray/ovirt-system-tests/deployment-basic-suite-4.3 /Ray/ovirt-system-tests/deployment-basic-suite-4.3/current/internal_repo/host_image Backing file path is /var/lib/lago/store/phx_repo:el7.6-base-5:v1 dest is /Ray/ovirt-system-tests/deployment-basic-suite-4.3/current/internal_repo/host_image Traceback (most recent call last): File "/Ray/ovirt-system-tests/common/scripts/put_host_image.py", line 66, in <module> main() File "/Ray/ovirt-system-tests/common/scripts/put_host_image.py", line 63, in main add_host_image_to_dest(prefix_path=sys.argv[1], dest=sys.argv[2]) File "/Ray/ovirt-system-tests/common/scripts/put_host_image.py", line 55, in add_host_image_to_dest symlink(backing_file_path, dest) OSError: [Errno 2] No such file or directory + on_exit + [[ 1 -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-16 14:50:14.980898261+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-16 14:50:14.986356383+0100 run_suite.sh::on_exit::INFO:: Dumping lago env status + env_status + cd /Ray/ovirt-system-tests/deployment-basic-suite-4.3 + lago status [Prefix]: Base directory: /Ray/ovirt-system-tests/deployment-basic-suite-4.3/default [Networks]: [lago-basic-suite-4-3-net-bonding]: gateway: 192.168.203.1 management: False status: down [lago-basic-suite-4-3-net-management]: gateway: 192.168.205.1 management: True status: down [lago-basic-suite-4-3-net-storage]: gateway: 192.168.204.1 management: False status: down UUID: d6b67236f01b11e988fc002128a2f0d8 [VMs]: [lago-basic-suite-4-3-engine]: [NICs]: [eth0]: ip: 192.168.205.2 network: lago-basic-suite-4-3-net-management [eth1]: ip: 192.168.204.2 network: lago-basic-suite-4-3-net-storage distro: el7 [metadata]: deploy-scripts: $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_add_local_repo_no_ext_access.sh $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_setup_engine.sh ovirt-engine-password: 123 root password: 123456 status: down [lago-basic-suite-4-3-host-0]: [NICs]: [eth0]: ip: 192.168.205.4 network: lago-basic-suite-4-3-net-management [eth1]: ip: 192.168.204.4 network: lago-basic-suite-4-3-net-storage [eth2]: ip: 192.168.203.4 network: lago-basic-suite-4-3-net-bonding [eth3]: ip: 192.168.203.5 network: lago-basic-suite-4-3-net-bonding distro: el7 [metadata]: deploy-scripts: $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_add_local_repo_no_ext_access.sh $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_setup_host_el7.sh $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_setup_1st_host_el7.sh root password: 123456 status: down [lago-basic-suite-4-3-host-1]: [NICs]: [eth0]: ip: 192.168.205.3 network: lago-basic-suite-4-3-net-management [eth1]: ip: 192.168.204.3 network: lago-basic-suite-4-3-net-storage [eth2]: ip: 192.168.203.2 network: lago-basic-suite-4-3-net-bonding [eth3]: ip: 192.168.203.3 network: lago-basic-suite-4-3-net-bonding distro: el7 [metadata]: deploy-scripts: $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_add_local_repo_no_ext_access.sh $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_setup_host_el7.sh root password: 123456 status: down + cd - /Ray/ovirt-system-tests

2 5

workaround for the lack of native el8 slaves in the CI
by Marcin Sobczyk 23 Oct '19

23 Oct '19

Hi all, we're trying to move vdsm tests to el8. AFAIK we don't have native el8 slaves in the CI yet, so our el8 stages run on el7 with el8 mocked. There are some issues with scripts setting up the env for storage tests - they are refusing to work on older kernel versions. I have an idea for a workaround - until now we were using 'host-distro: same' in our 'stdci.yaml'. I can see that this option can also take a value of 'better/newer' [1], but that won't work for el8. Could we possibly implement something like [2] ? That would allow us to i.e. define an el8 mocked env with 'host-distro: fc30' enforcing native fc30 host. I assume this would be a temporary workaround only, until we have native el8 slaves. Regards, Marcin [1] https://github.com/oVirt/jenkins/blob/a796094bfd15f1a85b9f630aaeb25ce6e0dab… [2] https://gerrit.ovirt.org/#/c/104091/

6 7

Restart a Host
by scott.fitzgerald＠oracle.com 23 Oct '19

23 Oct '19

Hi, I am currently trying to restart a host, ie send it into reboot state, and then up, using the Restart button below SSH Management in the UI. How is this achieved? I don't see a restart option in any of the host endpoints. TIA

3 5

How to remove ovirtmgmt network interface in centOS
by Prajith Kesava Prasad 23 Oct '19

23 Oct '19

Hey everyone, Could someone please point me in the right direction?. Im unable to remove network interface ovirtmgmt, commands like ifdown results in a state where the ip is unreachable and a manual network restart had to be done to bring it back to normal. could someone help me with removing ovirtmgmt network in centos? ___________________________________________________________________ 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovirtmgmt state UP group default qlen 1000 link/ether 00:1a:4a:16:01:9c brd ff:ff:ff:ff:ff:ff 23: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 66:66:f1:c4:52:c7 brd ff:ff:ff:ff:ff:ff 24: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether fe:aa:a4:0d:7a:31 brd ff:ff:ff:ff:ff:ff 25: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether ba:fd:da:db:29:44 brd ff:ff:ff:ff:ff:ff 147: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:1a:4a:16:01:9c brd ff:ff:ff:ff:ff:ff inet 10.70.43.190/22 brd 10.70.43.255 scope global dynamic ovirtmgmt valid_lft 85952sec preferred_lft 85952sec inet6 2620:52:0:4628:21a:4aff:fe16:19c/64 scope global mngtmpaddr dynamic valid_lft 2591937sec preferred_lft 604737sec inet6 fe80::21a:4aff:fe16:19c/64 scope link valid_lft forever preferred_lft forever _________________________________________________________________________ Thanks, Prajith

3 2

Set host as SPM
by scott.fitzgerald＠oracle.com 23 Oct '19

23 Oct '19

System currently has 1 DC, 1 cluster, 2 active hosts in cluster and 1 domain. Host1 is SPM, through UI I can set Host2 to SPM, Host1 becomes Non-SPM host. Through the SDK I can use SpmBuilder spmBuilder = new SpmBuilder().priority(7); sysService.hostsService().hostService(host.id()).update().host(host().spm(spmBuilder)).send(); to update host SPM priority. I cannot find a way to use the SDK to change the Host to SPM mode directly, despite using spm().status in a similar manner as above for the priority. How can I achieve this? TIA

2 2

Processing Conflict: sos-3.7-6.el7.centos.noarch conflicts vdsm <= 4.30.17
by trunet-ovirt＠wsartori.com 23 Oct '19

23 Oct '19

Hello all, good afternoon. I'm new here, my name is Wagner and I live in The Netherlands. I inherited an old 4.2 oVirt cluster and I'm in process of adding new CentOS hypervisors to it. Sadly this isn't working well due to a conflict in vdsm and sos. I did some research, and found this[1] on RedHat and also this thread[2] and this gerrit review[3]. Looks like the sos package now contains vdsm sos module and this needs to be removed on 4.2 version. Current sos package conflicts[4] with vdsm <= 4.30.17. The way forward (if this is accepted by you and CentOS) would be to release a new 4.2 version, and change the conflict on sos package to accept this new 4.2 vdsm version. I can help with pull requests, building packages (.src.rpm) or whatever. What you guys think about it? [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1714509 [2]: https://lists.ovirt.org/archives/list/devel@ovirt.org/thread/AGIX5H4EJQ66FU… [3]: https://gerrit.ovirt.org/#/c/100576/ [4]: https://git.centos.org/rpms/sos/blob/c7/f/SPECS/sos.spec#_20 Best regards, Wagner Sartori Junior

3 2