- Devel - oVirt List Archives

master CQ: random failures for add_master_storage_domain
by Dusan Fodor 20 Sep '19

20 Sep '19

Hello all, lately i witnessed multiple failures for add_master_storage_domain test, which were not related to changes themselves, nor any infra issue. One example can be found here [1]. After investigation with huge help of Milan, issue is that Host falls from up state to whatever-but-not-up suddenly. 1. add_storage_domain picks a random host that is in up state 2. meantime engine starts fence action for it, so probably something gone bad with the host; the fence action fails with: *[org.ovirt.engine.core.bll.pm.FenceProxyLocator] (EE-ManagedThreadFactory-engineScheduled-Thread-38) [6692895f] Can not run fence action on host 'lago-basic-suite-master-host-0', no suitable proxy host was found.* 3. test fails on not being able to attach the domain to non-up host: *[org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [Cannot add storage server connection when Host status is not up]* For better orientation in failed job's engine log [1], fence action for host fails at :46:12,842-04 engine learns it cannot connect storage to host at :46:16,105-04 The test itself add_master_storage_domain starts at ~ :46:13,753 (according to lago log). Could you please check this? Thanks [1] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15829 [2] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15829/artifa…

3 6

FYI: RAM needed to compile the engine
by Fedor Gavrilov 19 Sep '19

19 Sep '19

Hi, This is all out of curiosity and just FYI. I noticed that most recent engine master on CentOS 7.7 now requires about 8 GB of memory to compile. Otherwise it will fail during GWT part. 6 GB - not good enough. Strange thing is about a month ago it worked perfectly fine for me on 4 GB. Also, I am running it on VM, so old rule applies: it is 8 gigs starting memory, not max memory. I wonder if someone had similar experience. Fedor

1 0

CentOS 7.7 has been released: note it's not supported for oVirt 4.2
by Sandro Bonazzola 19 Sep '19

19 Sep '19

CentOS 7.7 has been released this week. Please note that CentOS 7.7 is not supported for oVirt 4.2 and older releases. If you want to upgrade to CentOS 7.7 please upgrade to oVirt 4.3 too. If you don't plan to upgrade to oVirt 4.3 please be sure your yum repo files points to http://mirror.centos.org/centos/7.6.1810/ instead of http://mirror.centos.org/centos/7/. The http://mirror.centos.org/centos/7/ URL is now pointing to http://mirror.centos.org/centos/7.7.1908/ so yum upgrade will bring you 7.7 content which may break your 4.2 installation. 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.*

2 1

Removing big (hc-* and metrics) suits from OST's check-patch (How to make OST faster in CI)
by Barak Korren 19 Sep '19

19 Sep '19

If you have been using or monitoring any OST suits recently, you may have noticed we've been suffering from long delays in allocating CI hardware resources for running OST suits. I'd like to briefly discuss the reasons behind this, what are planning to do to resolve this and the implication of those actions for big suit owners. As you might know, we have moved a while ago from running OST suits each on its own dedicated server to running them inside containers managed by OpenShift. That had allowed us to run multiple OST suits on the same bare-metal host which in turn increased our overall capacity by 50% while still allowing us to free up hardware for accommodating the kubevirt project on our CI hardware. Our infrastructure is currently built in a way where we use the exact same POD specification (and therefore resource settings) for all suits. Making it more flexible at this point would require significant code changes we are not likely to make. What this means is that we need to make sure our PODs have enough resources to run the most demanding suits. It also means we waste some resources when running less demanding ones. Given the set of OST suits we have ATM, we sized our PODs to allocate 32Gibs of RAM. Given the servers we have, this means we can run 15 suits at a time in parallel. This was sufficient for a while, but given increasing demand, and the expectation for it to increase further once we introduce the patch gating features we've been working on, we must find a way to significantly increase our suit running capacity. We have measured the amount of RAM required by each suit and came to the conclusion that for the vast majority of suits, we could settle for PODs that allocate only 14Gibs of RAM. If we make that change, we would be able to run a total of 40 suits at a time, almost tripling our current capacity. The downside of making this change is that our STDCI V2 infrastructure will no longer be able to run suits that require more then 14Gib of RAM. This effectively means it would no longer be possible to run these suits from OST's check-patch job or from the OST manual job. The list of relevant suits that would be affected follows, the suit owners, as documented in the CI configuration, have be added as "to" recipients to the message: - hc-basic-suite-4.3 - hc-basic-suite-master - metrics-suite-4.3 Since we're aware people would still like to be able to work with the bigger suits, we will leverage the nightly suit invocation jobs to enable then to be run in the CI infra. We will support the following use cases: - *Periodically running the suit on the latest oVirt packages* - this will be done by the nightly job like it is done today - *Running the suit to test changes to the suit`s code* - while currently this is done automatically by check-patch, this would have to be done manually in the future by manually triggering the nightly job and setting the REFSPEC parameter to point to the examined patch - *Triggering the suit manually* - This would be done by triggering the suit-specific nightly job (as opposed to the general OST manual job) The patches listed below implement the changes outlined above: - 102757 <https://gerrit.ovirt.org/102757> nightly-system-tests: big suits -> big containers - 102771 <https://gerrit.ovirt.org/102771>: stdci: Drop `big` suits from check-patch We know that making the changes we presented will make things a little less convenient for users and maintainers of the big suits, but we believe the benefits of having vastly increased execution capacity for all other suits outweigh those shortcomings. We would like to hear all relevant comment and questions from the quite owners and other interested parties, especially is you think we should not carry out the changes we propose. Please take the time to respond on this thread, or on the linked patches. Thanks, -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 4

OST fails
by Vojtech Juranek 19 Sep '19

19 Sep '19

Hi, OST has started to fail during today, fails with unsatisfied rpm dependencies, e.g. + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' otopi-debug-plugins cronie Error: Package: rsyslog-mmjsonparse-8.24.0-38.el7.x86_64 (alocalsync) Requires: rsyslog = 8.24.0-38.el7 Installed: rsyslog-8.24.0-34.el7.x86_64 (installed) rsyslog = 8.24.0-34.el7 and many more, see [1] for more details. Any idea what's wrong? Thanks Vojta [1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5601/console

2 3

[User is not authorized to perform this action.]
by smidhunraj＠gmail.com 19 Sep '19

19 Sep '19

I am getting error as User is not authorized to perform this action.I am using oVirt api to manually attach a disk and snapshot to another virtual machine.This the code i used.The API i followed is '<disk_attachment> <active>true</active> <bootable>false</bootable> <interface>virtio</interface> <disk id="a94106b7-d348-4088-aaa1-5dfc46dc094e"> <snapshot id="6ecbb953-c4fb-4294-9988-e7cd2bd9b038"/> <description>My disk</description> <format>cow</format> <name>mydisk</name> </disk> </disk_attachment> ============================== The php code i have tried is ... public function attachSnapshotandActivateDisk( ) { $data = array(); $xmlStr = '<disk_attachment> <active>true</active> <bootable>false</bootable> <interface>virtio</interface> <disk id="a94106b7-d348-4088-aaa1-5dfc46dc094e"> <snapshot id="6ecbb953-c4fb-4294-9988-e7cd2bd9b038"/> <description>My disk</description> <format>cow</format> <name>mydisk</name> </disk> </disk_attachment> '; $curlParam = array( "url" => "vms/74a1a99f-87d1-4444-b394-f90e4f29f51f/diskattachments", "method" => "POST", "data" => $xmlStr ); // $text = print_r($curlParam, true); //echo "<script>console.log( 'curl Parameter".json_encode($text)."');</script>"; $data = $this->processCurlRequest($curlParam, "vm-create"); // if instance update failed if ($data['status'] != 'success') { Common::ovirtLog(array( "requestParam" => $curlParam, "responseParam" => $data, )); } // show the output of print_r function as a string // $text = print_r($data, true); echo $data['message']; die; echo "<script type='text/javascript'> console.log('checking the attach snapshot activate disk function diskid=" . json_encode($data) . "') </script>"; //Detach the disk // $this->detachSnapshotDisk() ; return $data; } Please help me.

2 1

vdsm has been tagged (v4.30.31)
by Milan Zamazal 19 Sep '19

19 Sep '19

4 5

how to login into ovirts particular virtualmachine from a remote client
by smidhunraj＠gmail.com 19 Sep '19

19 Sep '19

Is there any way i can login into the virtual machine in ovirt from my local machine.Please help me.

1 0

how to login into ovirts particular virtualmachine from a remote client
by smidhunraj＠gmail.com 19 Sep '19

19 Sep '19

Is there any way i can login into the virtual machine in ovirt from my local machine.Please help me.

1 0

How to use ovirt-imageio api for downloading snapshot to our localmachine.
by smidhunraj＠gmail.com 19 Sep '19

19 Sep '19

CAn anyone give me a working example of api on how to download snapshot to our local machine using ovirt using ovirt-imageio using api.Do we need to setup some certificate at our ovirt engine side.Please help me

1 0