cockpit-ovirt is deprecated for hosted-engine deployment, try cli using
"hosted-engine --deploy" instead.
if it fails, please share ovirt-hosted-engine-setup log files located in
/var/log/ovirt-hosted-engine-setup/ (especially the
ovirt-hosted-engine-setup-ansible-get_network_interfaces-*.log)
On
Hi,
can you please share the output of:
# ansible --version
# rpm -qa | grep ovirt-hosted-engine-setup
# rpm -qa | grep ovirt-ansible-collection
# ansible -m firewalld -a state=enabled localhost -e
'ansible_python_interpreter=/usr/bin/python3'
On Tue, May 24, 2022 at 12:15 PM wrote:
>
Hi,
The link you attached is for installing the engine on a stand alone machine.
In case you want to have the engine and the host on the same machine you
should install hosted-engine:
https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/
Regards,
Hi Tommy,
You can use the following command to install hosted-engine without an
internet connection:
#hosted-engine --deploy --ansible-extra-vars=he_offline_deployment=true
And after the installation is finished you can configure the yum server and
update the packages.
Another option is to use
Hi,
Seems like you hit https://bugzilla.redhat.com/show_bug.cgi?id=1903567.
The fix for that is https://gerrit.ovirt.org/c/cockpit-ovirt/+/112450,
which should be included in the next release.
Regards,
Asaf
On Sun, Dec 6, 2020 at 3:52 AM wrote:
> Just for information, I performed the
Hi,
Yes, I can see the thread.
We just reproduced it with the latest ovirt-cockpit package [1].
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1903567
Regards,
Asaf
On Wed, Dec 2, 2020 at 12:09 PM Patrick Lomakin
wrote:
> Hi Asaf. Thanks for quick answer. I am sorry, but I have installed
Hi Patrick,
I checked the cockpit-ovirt code, and it seems you are right.
Ansible changed the module's behavior in the 2.9.14 version and the module
no longer returns 'ansible_facts'.
I believe [1] should fix that, but I didn't check it yet.
Can you please provide the ovirt-hosted-engine-setup
Hi Lee,
The bug is still under investigation.
Meantime you can use the WA in patch [1] for the upgrade.
[1] https://github.com/oVirt/ovirt-ansible-collection/pull/158
Regards,
Asaf
On Thu, Oct 22, 2020 at 8:23 PM wrote:
> Greetings,
>
> I'm trying to preform an upgrade from 4.3 to 4.4 using
Hi,
Can you please share ansible version and logs from
/var/log/ovirt-hosted-engine-setup.
If the ansible version < 2.9.11, please upgrade it and try again.
Regards,
Asaf
On Mon, Aug 10, 2020 at 10:17 AM wrote:
> Hello, everyone
> I am using these versions for my test :
> -
Hi Jonas,
Can you please share the full log file located in
/var/log/ovirt-hosted-engine-setup ?
My guess you hit [1], this is the fix for that [2] (not merged yet).
You can install the rpm with the fix from Jenkins CI [3] and then run the
following command:
hosted-engine --deploy
Teaming is not supported in 4.4, please use bonding instead.
Regards,
Asaf
On Thu, Jun 11, 2020 at 12:31 AM Chris Adams wrote:
> Once upon a time, Louis Bohm said:
> > Unless I have learned wrong all these years Teaming is the Windows term
> for Linux Bonding.
>
> Linux has two methods (or
In addition to what Didi suggested, you can enable DEBUG level in order to
get more details in broker.log:
1. Edit /etc/ovirt-hosted-engine-ha/broker-log.conf
2. In [logger_root] section change the level parameter to level=DEBUG
3. Restart the service: systemctl restart ovirt-ha-broker
Regards,
Which oVirt version are you using?
>From 4.2 you don't need to wait, you should be able to update the HE memory
via UI:
1. Enable global maintenance
2. Change HE VM memory via UI
3. On the HE, run: # hosted-engine --vm-shutdown
4. Wait for HE VM to be down: # hosted-engine --vm-status
5. Start HE
Hi,
Can you please provide the log files?
Regards,
Asaf
On Fri, Jun 14, 2019 at 7:43 PM PS Kazi wrote:
> I am getting error while Ovirt Engine Setup:
> Ovirt Node version 4.3.4
>
> [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 90, "changed":
14 matches
Mail list logo
