I want to remove inactive contributors from vdsm-master-maintainers.
I suggest the simple rule of 2 years of inactivity for removing from this
based on git log.
See the list below for current status:
Dear Ladies and Gentlemen!
I am currently working with the java-sdk and I encountered a problem.
If I would like to retrieve the disk details, I get the following error:
Disk currDisk = ovirtConnection.followLink(diskAttachment.disk());
The Error is occurring in this line:
The getResponst looks quiet ok. (I inspected: [cid:image002.png@01D44537.AF127FD0] and it looks ok).
wrong number of arguments
The code is quiet similar to what you published on github (https://github.com/oVirt/ovirt-engine-sdk-java/blob/master/sdk/src/test/j... ).
Can you confirm the defect?
Hi, I've experienced a problem with host deploy and oVirt master last
week in an environment with TLS disabled. When I install/reinstall a
4.4 host, it removes the following options from
As a result, libvirt refuses to start, complaining about missing
certificates and keys in their default locations.
Does anybody who uses a non-TLS environment experience the same problem?
Can it be related to the fact that we require libvirtd-tls service from
the split libvirtd services now?
(Yes, I know TLS should always be used, but that is a shared development
environment where TLS is disabled for whatever reason.)
If I do e.g.:
1. Install CentOS
2. yum install ovirt-releaseSOMETHING
3. yum install vdsm
Then reboot the machine, vdsm starts, and for this, it does all kinds of
things to the system (such as configure various services using vdsm-tool
etc.). Are we sure we want/need this? Why would we want vdsm
configured/running at all at this stage, before being added to an engine?
In particular, if (especially during development) we have a bug in this
configuration process, and then fix it, it might not be enough to upgrade
vdsm - the tooling will then also have to fix the changes done by the buggy
previous version, or require a full machine reinstall.
Thanks and best regards,
After I screwed up my dev environment beyond repair I have to set it up again and I see something I haven't last time (CentOS 7):
$ sudo yum install ansible-runner-service-dev
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.hosting90.cz
* centos-sclo-rh: mirror.hosting90.cz
* centos-sclo-sclo: mirror.hosting90.cz
* extras: mirror.hosting90.cz
* ovirt-master-epel: mirror.hosting90.cz
* ovirt-master-snapshot: ftp.nluug.nl
* ovirt-master-snapshot-static: ftp.nluug.nl
* updates: mirror.hosting90.cz
No package ansible-runner-service-dev available.
Maybe something's missing from my notes, but where did it go? Should I add some repo?
Looks like infrastructure issue setting up storage on engine host.
Here are 2 failing builds with unrelated changes:
Is this a known issue?
AssertionError: setup_storage.sh failed. Exit code is 1 assert 1 == 0 -1
prefix = <ovirtlago.prefix.OvirtPrefix object at 0x7f6fd2b998d0>
engine = prefix.virt_env.engine_vm()
result = engine.ssh(
> assert result.code == 0, 'setup_storage.sh failed. Exit code is %s'
E AssertionError: setup_storage.sh failed. Exit code is 1
E assert 1 == 0
The pytest traceback is nice, but in this case it is does not show any
Since we run a script using ssh, the error message should include the
process stdout and stderr
which probably can explain the failure.
Also I wonder why this code is called as a test (test_configure_storage).
This looks like setup
step so it should run as a fixture.
Software factory (Zuul is one of their products) has been migrated to a
new host, and because of it Zuul is currently unavailable.
At the moment you can directly merge the projects that are currently being
gated - OST + ovirt-provider-ovn.
I will update you once the issue is resolved.