- Devel - oVirt List Archives

upgrade-suite in manual system test is broken
by Sandro Bonazzola 20 Nov '19

20 Nov '19

Hi Just executed manual system test on https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6072/ for testing upgrade from latest released to 4.3.7 rc4 and instead of using latest released it used latest rpms passing CI so the test was not useful at all. Who's maintaining the upgrade suite? -- 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

manual system test runner broken
by Sandro Bonazzola 19 Nov '19

19 Nov '19

Hi, just executed basic suite for testing 4.3.7 rc4 and instead of falling back on latest released it was falling back on latest tested which is newer than 4.3.7 rc4 so made the test useless. Job execution is here: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6071/ who's maintaining manual ost runner? I have the feeling it's not a suite bug, but a job bug. -- 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 3

Configure Local Storage On Host
by scott.fitzgerald＠oracle.com 19 Nov '19

19 Nov '19

Hi, I can add a local domain through the domains service portion of the SDK, however, I can't find an endpoint for Configure Local Storage in the management menu of the Host in the UI. Is this missing functionality? If so is there a ticket open for it? TIA

3 6

Manually changing master storage domain
by Strahil Nikolov 17 Nov '19

17 Nov '19

Hello , can someone tell me if I can recover from the following situation (see attachment) and change manually the master storage domain.It seems that How to change the master storage domain to another specific domain - Red Hat Customer Portal is not working for me. Best Regards,Strahil Nikolov

1 0

vdsm has been tagged (v4.30.38)
by Milan Zamazal 15 Nov '19

15 Nov '19

1 0

Not able to open jnlp file
by Ritesh Chikatwar 15 Nov '19

15 Nov '19

Team, Not able to open jnlp files. I tried Icedtea it not working. Suggest any rpm packages... Thanks Ritesh

3 2

Pushing container to dockerhub using podman
by Edward Haas 14 Nov '19

14 Nov '19

Hi All, I'm trying to push an image to dockerhub using podman. Unfortunately, it does not work, giving me the following error: ``` $ sudo podman push 2dfe3d835f08 ovirtorg/vdsm-test-func-network-centos-8 Getting image source signatures Error: Error copying image to the remote destination: Error trying to reuse blob sha256:9e607bb861a7d58bece26dd2c02874beedd6a097c1b6eca5255d5eb0d2236983 at destination: Error checking whether a blob sha256:9e607bb861a7d58bece26dd2c02874beedd6a097c1b6eca5255d5eb0d2236983 exists in docker.io/ovirtorg/vdsm-test-func-network-centos-8: errors: denied: requested access to the resource is denied error parsing HTTP 401 response body: unexpected end of JSON input: "" ``` (podman login docker.io works fine) Has anyone encounter something like this? Thanks, Edy.

3 7

gate pipeline TIMED_OUT
by Dominik Holler 14 Nov '19

14 Nov '19

Hello, how can I interpret the state of https://gerrit.ovirt.org/#/c/103739/ and what is the way to merge it? Just ask Edy to overwrite, or is there a more clean way possible how I can solve this myself? Thanks

2 4

stdout during ovirt-engine unit tests
by Eitan Raviv 14 Nov '19

14 Nov '19

Hi, In some complex unit tests I would like to print the initial state that is being tested to stdout when the test is being run by the ovirt-engine build. The text size is negligible. The reason for the printout is to help visualize the state because it is not straight forward. Does anybody see a reason due to security or some other constraint not to print to stdout from engine unit tests? Thanks

2 2

Container-based CI backend for oVirt
by Barak Korren 14 Nov '19

14 Nov '19

*What are we talking about exactly?* The CI team had been doing work over the last few weeks to create and enable a container-based CI backend that is usable as an alternative for the legacy VM-and-chroot backend we've been using so far. *Why?* 1. *You asked for it: *We've been approached by several developer teams asking for this kind of functionality 2. *Faster:* The new backend requires far less setup overhead then the legacy one, and therefore would allow jobs to start and finish faster 3. *More flexible: *The old backend allowed specifying build/test dependencies in terms of RPM packages, the container based one uses container images for this which are far more flexible 4. *More versatile:* There were some limits to what could be done reliably with chroots. The greater isolation provided by containers would provide better testing capabilities 5. *Less maintenance:* With the legacy backend, the CI team had to take the time and provide support for every new release of a target distribution, the new backend is designed to allow using upstream container images directly therefore letting developers use them as soon as they are released instead of having to wait for the CI team to provide support. *Tell me more!* A pending documentation update describing the new features and how to use them can be found here: - 104660 <https://gerrit.ovirt.org/104660>: Document the new STDCI containers syntax *Great! so can I use this now?* Unfortunately this is not yet enabled in production, while most of the functionality had already been developed and tested, code review efforts are still ongoing. If you'd like to help us move this along, please take the time and help reviewing the following patches: - 103937 <https://gerrit.ovirt.org/103937>: Adda an STDCI DSL option for using containers - 104066 <https://gerrit.ovirt.org/104066>: Add STDCI DSL `podspecs` pseudo option - 104164 <https://gerrit.ovirt.org/104164>: stdci_runner: Support container-based threads I'd like to thank @Marcin Sobczyk <msobczyk(a)redhat.com> and @Miguel Duarte de Mora Barroso <mdbarroso(a)redhat.com> for helping with the review effort so far, further work is needed as changes had been made following the reviews. *Hey, it's nice and all, but I think you forgot to make it do X* Hold on! we are not done yet! While we want to put an initial set of features in the hands of developers as soon as possible, work is already under way to provide more functionality. To check out what is coming down the line (And perhaps help it along), please have a look at the following patches: - 104668 <https://gerrit.ovirt.org/104668>: Document source cloning extension for containers - 104213 <https://gerrit.ovirt.org/104213>: Implement STDCI DSL support for initContainers - 104590 <https://gerrit.ovirt.org/104590>: STDCI DSL: Add the `decorate` option - 104273 <https://gerrit.ovirt.org/104273>: STDCI PODS: Unique UID for each job build's POD -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0