Hi Guys,
I am trying to install oVirt node on a physical machine.
Once selected the option to install oVirt 4.3 it give a screen
"dracut-initqueue time out
And then get into emergency mode & gives dracut cmd line.
if I exit the command line, it continue bootinto the installation window.
However it gives a message "Kickstart file /run/install/ks.config is missing" (Pane is dead).
Tried the same on vmware, it boot fine & am able to install it.
Can someone tell me how could I fix this?

On Fri, Feb 22, 2019 at 11:12 AM Pravin Amin <Pravin.Amin(a)veritas.com> wrote:
>
> Hi Dan,
>
> We have some scripts and test data files which we need to copy to guest VMs and then execute the scripts inside the guest VM and looking for ways to automate this process for data validation testing.
Your description is still scarce of words, but it seems that it can be
handled by ssh into ever-running VMs.
Is there a problem with that approach?

Hi,
We are looking for a way to copy files and execute scripts inside Virtual Machines hosted on oVirt manager (Any supported guest OS) either through REST API or using Guest Tools. Please let me know how we can achieve it.
-Thanks,
Pravin Amin
Principal SQA Engineer
Netbackup
Veritas Technologies LLC
Office: (91) 20 - 66157288 / Mobile: (91) 9881139050
pravin.amin(a)veritas.com<mailto:pravin.amin@veritas.com>
[signature_394478960]<https://www.veritas.com/product/backup-and-recovery/netbackup-8?om_camp_i...>
This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication.

Hi all,
With the generous help of several nice guys, currently the Go SDK related
projects, oVirt/ovirt-engine-sdk-go and oVirt/go-ovirt, are already
available under oVirt org, and the integration of oVirt/ovirt-engine-sdk-go
with oVirt STD-CI is also completed [1]. Sincerely thank you to everyone.
While there is still an issue left that we need a proper solution to
integrate oVirt/ovirt-engine-sdk-go with TravisCI which could push the
auto-generated codes into oVirt/go-ovirt. Previously I adopted my
personal github access token which is stored encrypted [2] to work it out.
But as it's been under oVirt community, we need a more regular way to make
this. As @Evgheni <ederevea(a)redhat.com> suggested, maybe a new access token
from a dedicated github account or via the Jenkins job will work?
Any one could help? Any insights into this would be appreciated and thanks
in advance.
Best regards,
Joey
[1]: https://github.com/oVirt/ovirt-engine-sdk-go/pull/144
[2]:
https://docs.travis-ci.com/user/environment-variables#defining-encrypted-...

Hi,
TL;DR: please don't direct users to feature pages -- direct them to
end-user documentation instead. And maintain content separation between
end-user documentation and technical docs like feature pages.
...
Lately we've cleaned up documentation on ovirt.org, and I wanted to share
some of my thoughts about it. As a user experience focused person, I really
believe that clear and helpful documentation is crucial to the project's
success. I've also seen outdated documentation be a source of extreme
frustration for our users.
In the distant past, most of oVirt's documentation was written by
developers on a wiki, typically in the form of "feature pages." Feature
pages are basically technical design documents with occasionally some user
help sprinkled in.
With oVirt 4.0, we put a great set of clear documentation, written by
technical writers, on the oVirt website (which was also converted from a
wiki to a regular static site). This documentation is up to date with 4.2,
and we'll get the 4.3 content out there soon.
This official documentation lives at https://ovirt.org/documentation
and it should be considered the authoritative place for users to access our
documentation.
Feature pages, on the other hand, are (now) for developers. When you hear
the term "feature page", think "technical design document." Most users
should not be interested in this content.
It helps to think about the personas.
1. oVirt admins -- the person who sets up oVirt on Day 1 and 2. This is the
person who cares about and will read the Installation Guide and the
Administration Guide. These live under /documentation, e.g.
https://ovirt.org/documentation/install-guide/Installation_Guide.html
2. oVirt users -- the people who use oVirt to create, manage, and use
virtual machines, etc. This person will care about and read the VM Portal
Guide, User Guides, and such. These also live under /documentation, e.g.
https://ovirt.org/documentation/vmm-guide/Virtual_Machine_Management_Guid...
3. Developers -- you and I, and occasionally highly curious and technical
admins. These people might care about how the project works under the hood
-- high level designs, code flows, etc. Persona 2, oVirt users, do not care
about these details when they are learning to use oVirt, so end-user
documentation should not be polluted with this type of content. This
content now lives exclusively under /develop, the developer's section of
the site.
https://ovirt.org/develop/release-management/features/
Let's help our users by directing them to the end-user documentation, not
to feature pages. If you would like to contribute end-user documentation,
it should go under /documentation and not in a feature page. If you build a
new feature, the technical stuff goes under
/develop/release-management/features/ and the end-user stuff goes under
/documentation.
Feedback welcome :)
Best wishes,
Greg
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
<https://www.redhat.com/>
gshereme(a)redhat.com IRC: gshereme
<https://red.ht/sig>

Hi,
We are planning to release the first candidate of 4.3.1 on February 20th[1]
and the final release on February 26th.
Please join us testing this release candidate right after it will be
announced!
We are going to coordinate the testing effort with a public Trello board at
https://trello.com/b/5ZNJgPC3
You'll find instructions on how to use the board there.
If you have an environment dedicated to testing, remember you can setup a
few VMs and test the deployment with nested virtualization.
To ease the setup of such environment you can use Lago (
https://github.com/lago-project)
The oVirt team will monitor the Trello board, the #ovirt IRC channel on
irc.oftc.net server and the users(a)ovirt.org mailing list to assist with the
testing.
[1]
https://www.ovirt.org/develop/release-management/releases/4.3.z/release-m...
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://red.ht/sig>

The oVirt Project is pleased to announce the availability of the oVirt
4.3.1 First Release Candidate, as of February 20th, 2019.
This update is a release candidate of the first in a series of
stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used in
production.
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later
* oVirt Node 4.3 (available for x86_64 only)
Experimental tech preview for x86_64 and s390x architectures for Fedora 28
is also included.
See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.
Notes:
- oVirt Appliance is available for EL7 only
- oVirt Node is available for EL7 only [2]
- Fedora 28 based appliance and node couldn't be built due to a bug in
Lorax (the tool used to build the images) affecting Fedora 28.
Additional Resources:
* Read more about the oVirt 4.3.1 release highlights:
http://www.ovirt.org/release/4.3.1/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/
[1] http://www.ovirt.org/release/4.3.1/
[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://red.ht/sig>