November 2019 - Devel - oVirt List Archives

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

Fedora 31 support
by Nir Soffer 13 Nov '19

13 Nov '19

We usually support only the most recent version of Fedora, which is now 31. We can use Fedora 30 for a while, but it is really too old (older than CentOS 8) and there is on point to use it. Instead of helping to discover issues early, we waste time on dealing with old packages that nobody maintains. For storage we need Fedora 31 for lvm 2.03, fixing critical issues. Using Fedora 30, we will have to add ugly hacks to have configuration that works with both versions. For network we need newer versions of NetworkManager and initscripts (Edward can add more details). For virt we use virt-preview repo, so we have recent versions of libvirt and qemu on any Fedora version (even 29). I added Fedora 31 builds for imageio, and all tests pass in travis: https://travis-ci.org/nirs/ovirt-imageio/builds/611042648 Adding ioprocess build should be easy, similar to this patch: https://gerrit.ovirt.org/c/104634 On Jenkins the fc31 build fails since there is no mock env for Fedora 31: https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-imageio_standard… When do we plan to support Fedora 31? Nir

2 2

Changing a host name
by Prajith Kesava Prasad 13 Nov '19

13 Nov '19

Hey everyone, So im in need of replacing a host, so the process goes like this , there are 3 hosts called A,B,C with (RHHI setup) (ovirt) and i want to replace A, so I order a new physical machine D and now i have to disable the A's hostname(meaning its not accessible by A anymore) and now i change D's hostname as A(so D is accessible by A's hostname) and then I execute the script to replace host. Now i tried following the steps mentioned in net to change the hostname and if i execute the hostname command in A (it shows the changed hostname) although im unable to ssh with the new hostname and im still able to ssh into A with old hostname.) Also, as far as the other 2 hosts are concerned they dont even know that A's hostname is changed and they still ssh it with A's old hostname (this is i believe because the 3 hosts are connected with ovirtmgmt network , so they still retain A's actual name with ovirt ip) Any help on this is appreciated. Thanks, Prajith

1 0

Yarn build failing
by Ritesh Chikatwar 13 Nov '19

13 Nov '19

Team, Any idea why am i facing this issue when i do *yarn build * for ovirt-engine-ui-extensions 1:1 error Parsing error: 'import' and 'export' may appear only with 'sourceType: module' /home/ritesh/git/ui-extenstion/ovirt-engine-ui-extensions/src/utils/webadmin-dom.js 1:1 error Parsing error: 'import' and 'export' may appear only with 'sourceType: module' /home/ritesh/git/ui-extenstion/ovirt-engine-ui-extensions/src/utils/webadmin-search-test.js 1:1 error Parsing error: 'import' and 'export' may appear only with 'sourceType: module' /home/ritesh/git/ui-extenstion/ovirt-engine-ui-extensions/src/utils/webadmin-search.js 1:1 error Parsing error: 'import' and 'export' may appear only with 'sourceType: module' error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

3 4

Check patch failure in vdsm
by Eyal Shenitzky 12 Nov '19

12 Nov '19

Hi, I encounter the following error for py36 test in vdsm check patch: ... ... 14:03:37 File "/usr/local/lib/python3.7/site-packages/pluggy/callers.py", line 187, in _multicall 14:03:37 res = hook_impl.function(*args) 14:03:37 File "/usr/local/lib/python3.7/site-packages/pluggy/manager.py", line 86, in <lambda> 14:03:37 firstresult=hook.spec.opts.get("firstresult") if hook.spec else False, 14:03:37 File "/usr/local/lib/python3.7/site-packages/pluggy/manager.py", line 92, in _hookexec 14:03:37 return self._inner_hookexec(hook, methods, kwargs) 14:03:37 File "/usr/local/lib/python3.7/site-packages/pluggy/hooks.py", line 286, in __call__ 14:03:37 return self._hookexec(self, self.get_hookimpls(), kwargs) 14:03:37 File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/storage-py37/lib/python3.7/site-packages/_pytest/config/__init__.py", line 82, in main 14:03:37 return config.hook.pytest_cmdline_main(config=config) 14:03:37 File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/storage-py37/bin/pytest", line 8, in <module> 14:03:37 sys.exit(main()) 14:03:37 [Inferior 1 (process 22145) detached] 14:03:37 ============================================================= 14:03:37 = Terminating watched process = 14:03:37 ============================================================= 14:03:37 PROFILE {"command": ["python", "py-watch", "600", "pytest", "-m", "not (slow or stress)", "--durations=10", "--cov=vdsm.storage", "--cov-report=html:htmlcov-storage-py37", "--cov-fail-under=62", "storage"], "cpu": 39.921942808919184, "elapsed": 604.4699757099152, "idrss": 0, "inblock": 1693453, "isrss": 0, "ixrss": 0, "majflt": 2, "maxrss": 331172, "minflt": 5606489, "msgrcv": 0, "msgsnd": 0, "name": "storage-py37", "nivcsw": 139819, "nsignals": 0, "nswap": 0, "nvcsw": 187576, "oublock": 2495645, "start": 1573386812.7961884, "status": 143, "stime": 118.260961, "utime": 123.055197} 14:03:37 ERROR: InvocationError for command /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/storage-py37/bin/python profile storage-py37 python py-watch 600 pytest -m 'not (slow or stress)' --durations=10 --cov=vdsm.storage --cov-report=html:htmlcov-storage-py37 --cov-fail-under=62 storage (exited with code 143) Is there any known issue? -- Regards, Eyal Shenitzky

3 3