we are going to merge a series of patches to master branch, which
integrates ansible-runner with oVirt engine. When the patches will be
merged you will need to install new package called ansible-runner-
service-dev, and follow instructions so your dev-env will keep working
smoothly(all relevant info will be also in README.adoc):
1) sudo dnf update ovirt-release-master
2) sudo dnf install -y ansible-runner-service-dev
3) Edit `/etc/ansible-runner-service/config.yaml` file as follows:
Where `$PREFIX` is the prefix of your development environment prefix,
which you've specified during the compilation of the engine.
4) Restart and enable ansible-runner-service:
# systemctl restart ansible-runner-service
# systemctl enable ansible-runner-service
That's it, your dev-env should start using the ansible-runner-service
for host-deployment etc.
Please note that only Fedora 30/31 and Centos7 was packaged, and are
just noticed that over time check-patch and build-artifacts script diverged
Due to this, check-patch passed on fc30 but failed after merge on
I'm fixing the immediate failure but a deeper review from java developers
would be helpful.
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.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.*
Where iscsiDetailsBuilder is IscsiDetailsBuilder iscsiDetailsBuilder = new IscsiDetailsBuilder().address(address).port(port);
I can fetch an iSCSI details container list, which contains the list of iSCSI targets. However, all values, except the address, port, portal and target string are null. I need the iSCSI LUN ID for automation of iSCSI creation. How can this be done via the SDK?
Thanks in advance.
I am trying to complete a task using the Java SDK which involves attaching networks to an interface, and then bonding another interface to the attached one. This can be done using the OVM UI in one step.
The SDK requires you to remove any attached networks from the interfaces before bonding them. The issue I am having comes after this part, where I try to reattach the networks to the interface which is a slave of the bond that was created. The specific error is as follows:
Fault reason is "Operation Failed". Fault detail is "[Interface already in use]". HTTP response code is "400". HTTP response message is "Bad Request"
To create the bond I am using the setpNetworks() function, where the interfaces are supplied in a list (nics), as follows:
Option bondOptionBuilder = new OptionBuilder().name("mode").value("4").build();
Option miimonOptionBuilder = new OptionBuilder().name(""miimon).value("100").build();
List<Option> options = new ArrayList<>();
BondingBuilder bondingBuilder = new BondingBuilder().options(options).slaves(nics);
HostNicBuilder hostNicBuilder = new
To reattach the networks (supplied by netAttachmentsToAdd) to the interface, I use the setupNetworks function as follows:
I am wondering how I can assign networks to NICs which are slaves of a bond using the SDK. Can I attach them to the interfaces directly or is this the wrong approach?
I am having an issue. I am building a test case and one step involves adding a network to a NIC object. When I perform this step in the UI by navigating from Hosts -> hostToAttachNetwork -> Network Interfaces -> Setup Host Networks . And I drag the required network to NIC object and press ok, after the operation is complete, an event log is registered in the engine.log containing this text: "Network changes were saved on host"
When I perform the same step in the automated test case, using the following code:
The operation is performed correctly, the network is attached to the appropriate NIC, but there is no log registered in the engine.log.
I am wondering is there a better way to perform the above task that will register an event in the log file. Or is it possible that this a bug in the SDK?
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:
I hit an issue recently (after reinstalling the engine based on the recent master branch) when I couldn't connect the host I used before. I don't have the exception message at hand now, but basically it had null instead of host-level logs and I decided to not dwell on it but rather update host as well.
I used CentOS 7 previously and continued to do so this time. I tried to follow https://ovirt.org/documentation/install-guide/chap-Enterprise_Linux_Hosts... but this time yum gives me this:
No package vdsm available.
No package cockpit-ovirt-dashboard available.
Just in case I checked and http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm is not providing either.
What is strange is I had this exact setup working already for quite a while (not counting minor version OS upgrades). Do you know what am I doing wrong?
Upon trying to install oVirt development environment on a new Fedora 31
installation (using the oVirt dependency repos of Fedora 30 as 31 is not
supported yet) I've found out that these packages are missing from the
Fedora 30 repo:
Didi, can you please build them for the Fedora 30 repo?
the maven clean build .... in ovirt suddenly started throwing this error :-
i tried a few fix but nothing seems to work, does anyone else have met with
Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.8.0:compile
(default-cli) on project webadmin: Command [[
[ERROR] /bin/sh -c
'com.google.gwt.dev.Compiler' '-logLevel' 'INFO' '-war'
'-localWorkers' '1' '-failOnError' '-XfragmentCount' '-1' '-sourceLevel'
[ERROR] ]] failed with status 1
Any help is appreciated,
The major update on the new VirtIO drivers is awesome. Way easier to install and it works with UEFI VM’s.
The only complaint that I’ve is that the driver is not digitally signed with a verified certificate inside Windows. So I can’t put my VM’s with secure boot on, only UEFI.