On Fri, Jul 17, 2020 at 8:20 PM Edward Berger wrote:
> cockpit hosted-engine deploy fails after defining VM name with static
> address with similar python2 error.
>
>
Yes I already reported both here and in the bugzilla, but to fix that it
would be necessary to trick with the engine VM (aka the a
cockpit hosted-engine deploy fails after defining VM name with static
address with similar python2 error.
[image: engine-deploy-fail.JPG]
On Fri, Jul 17, 2020 at 6:44 AM Gobinda Das wrote:
> Hi Gianluca,
> Thanks for opening the bug.
> Adding @Prajith Kesava Prasad to look into it.
>
>
> On Fr
On Thu, Jul 16, 2020 at 11:33 AM Arsène Gschwind
wrote:
> It looks like the Pivot completed successfully, see attached vdsm.log.
> Is there a way to recover that VM?
> Or would it be better to recover the VM from Backup?
This what we see in the log:
1. Merge request recevied
2020-07-13 11:18:3
They should be in the log files I attached to the bugzilla, if you download
the tar,gz file
Gianluca
On Fri, Jul 17, 2020 at 4:45 PM Strahil Nikolov
wrote:
> Can you provide the target's facts in the bug report ?
>
> Best Regards,
> Strahil Nikolov
>
> На 17 юли 2020 г. 14:48:39 GMT+03:00, Gian
On Thu, Jul 16, 2020 at 11:33 AM Arsène Gschwind
wrote:
>
> On Wed, 2020-07-15 at 22:54 +0300, Nir Soffer wrote:
>
> On Wed, Jul 15, 2020 at 7:54 PM Arsène Gschwind
>
> <
>
> arsene.gschw...@unibas.ch
>
> > wrote:
>
>
> On Wed, 2020-07-15 at 17:46 +0300, Nir Soffer wrote:
>
>
> What we see in the
Can you provide the target's facts in the bug report ?
Best Regards,
Strahil Nikolov
На 17 юли 2020 г. 14:48:39 GMT+03:00, Gianluca Cecchi
написа:
>On Fri, Jul 17, 2020 at 1:34 PM Dominique Deschênes <
>dominique.desche...@gcgenicom.com> wrote:
>
>> Hi,
>>
>> I use ovirt ISO file ovirt-node-ng-
Hello,
I have env1 and env2, both in 4.3 and both configured as single host HCI
environments.
On both I have the predefined hosted_storage, data and vmstore gluster
storage domains.
On env1 I have hosted_storage and data on a disk, and vmstore on a whole
different disk. I also have a "big2" gluste
Definitely it's not a resolve issue.
Have you made changes to sshd_config on sia-svr-ct02 ?
Is root login opened ?
Best Regards,
Strahil Nikolov
На 17 юли 2020 г. 13:58:09 GMT+03:00, lu.alfo...@almaviva.it написа:
>This is the output from the engine:
>
>[root@dacs-ovirt ~]# host sia-svr-ct02
>s
On Fri, Jul 17, 2020 at 1:34 PM Dominique Deschênes <
dominique.desche...@gcgenicom.com> wrote:
> Hi,
>
> I use ovirt ISO file ovirt-node-ng-installer-4.4.1-2020070811.el8.iso
> (July 8).
>
> I just saw that there is a new version of July 13 (4.4.1-2020071311). I will
> try it.
>
>
>
No. See my t
Hi,
I use ovirt ISO file ovirt-node-ng-installer-4.4.1-2020070811.el8.iso (July 8).
I just saw that there is a new version of July 13 (4.4.1-2020071311). I will
try it.
Dominique Deschênes
Ingénieur chargé de projets, Responsable TI
816, boulevard Guimond, Longueuil J4G 1T5
450 670-8383 x105
This is the output from the engine:
[root@dacs-ovirt ~]# host sia-svr-ct02
sia-svr-ct02.afis has address 10.234.50.134
[root@dacs-ovirt ~]# nslookup sia-svr-ct02
Server: 10.249.20.21
Address:10.249.20.21#53
Name: sia-svr-ct02.afis
Address: 10.234.50.134
Hi Gianluca,
Thanks for opening the bug.
Adding @Prajith Kesava Prasad to look into it.
On Fri, Jul 17, 2020 at 4:02 PM Gianluca Cecchi
wrote:
> On Fri, Jul 17, 2020 at 12:13 PM Martin Perina wrote:
>
>> I've reverified that install new host, check for upgrades, upgrade host
>> and enroll ce
On Fri, Jul 17, 2020 at 12:13 PM Martin Perina wrote:
> I've reverified that install new host, check for upgrades, upgrade host
> and enroll certificates work fine even with ansible 2.9.10 on standalone
> engine installation. So there is some issue inside HCI installer, which
> doesn't handle pyt
I've reverified that install new host, check for upgrades, upgrade host and
enroll certificates work fine even with ansible 2.9.10 on standalone engine
installation. So there is some issue inside HCI installer, which doesn't
handle python interpreter correctly.
Gianluca, could you please create a
Hm...
but then setting that variable to python3 should work, but based on the list
reports - it doesn't work.
Best Regards,
Strahil Nikolov
На 17 юли 2020 г. 12:35:52 GMT+03:00, Gianluca Cecchi
написа:
>On Fri, Jul 17, 2020 at 11:25 AM Gianluca Cecchi
>
>wrote:
>
>> On Fri, Jul 17, 2020 at 11
What is the output of:
host sia-svr-ct02
nslookup sia-svr-ct02
Best Regards,
Strahil Nikolov
На 17 юли 2020 г. 10:46:08 GMT+03:00, lu.alfo...@almaviva.it написа:
>2020-07-15 11:41:58,968+02 ERROR
>[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
>(EE-ManagedThreadFactory-engineSchedule
On Fri, Jul 17, 2020 at 11:25 AM Gianluca Cecchi
wrote:
> On Fri, Jul 17, 2020 at 11:04 AM Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Fri, Jul 17, 2020 at 10:58 AM Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>> On Fri, Jul 17, 2020 at 10:54 AM Martin Perina
>>>
On Fri, Jul 17, 2020 at 11:04 AM Gianluca Cecchi
wrote:
> On Fri, Jul 17, 2020 at 10:58 AM Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Fri, Jul 17, 2020 at 10:54 AM Martin Perina
>> wrote:
>>
>>> Hi Gianluca,
>>>
>>> that's very strange error, because I'm 100% sure we are using
On Fri, Jul 17, 2020 at 10:58 AM Gianluca Cecchi
wrote:
> On Fri, Jul 17, 2020 at 10:54 AM Martin Perina wrote:
>
>> Hi Gianluca,
>>
>> that's very strange error, because I'm 100% sure we are using yum module
>> with Python3 in several other roles including adding host to engine or
>> upgrading
On Fri, Jul 17, 2020 at 10:54 AM Martin Perina wrote:
> Hi Gianluca,
>
> that's very strange error, because I'm 100% sure we are using yum module
> with Python3 in several other roles including adding host to engine or
> upgrading host and so far I haven't heard any issue with ansible 2.9.10 and
Hi Gianluca,
that's very strange error, because I'm 100% sure we are using yum module
with Python3 in several other roles including adding host to engine or
upgrading host and so far I haven't heard any issue with ansible 2.9.10 and
yum module.
Gobinda, wouldn't enforcing python interpreter versi
Same problem for the next stage
[ INFO ] TASK [ovirt.hosted_engine_setup : Install oVirt Hosted Engine
packages]
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 10, "changed": false,
"msg": "The Python 2 yum module is needed for this module. If you require
Python 3 support use the `dnf` Ansi
On Fri, Jul 17, 2020 at 10:09 AM Strahil Nikolov via Users
wrote:
> What version of CentOS 8 are you using -> Stream or regular, version ?
>
> Best Regards,
> Strahil Nikolov
Strahil, see the other thread I have just opened.
It happens also to me with latest oVirt node iso for 4.4.1.1 dated 13/
What version of CentOS 8 are you using -> Stream or regular, version ?
Best Regards,
Strahil Nikolov
На 16 юли 2020 г. 21:07:57 GMT+03:00, "Dominique Deschênes"
написа:
>
>
>HI,
>Thank you for your answers
>
>I tried to replace the "package" with "dnf". the installation of the
>gluster seems
Hello,
today I wanted to test a single host hci install using
ovirt-node-ng-installer-4.4.1-2020071311.el8.iso
On this same environment 4.4.0 gui wizard worked ok, apart a final problem
with cpu flags and final engine boot up, so I wanted to verify if all is ok
now, because that problem should have
2020-07-15 11:41:58,968+02 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
(EE-ManagedThreadFactory-engineScheduled-Thread-79) [] Unable to
RefreshCapabilities: VDSNetworkException: VDSGenericException:
VDSNetworkException: Message timeout which can be caused by communication
Il giorno gio 16 lug 2020 alle ore 15:55 Florian Schmid via Users <
users@ovirt.org> ha scritto:
> Hi,
>
> I have a problem with Ubuntu 20.04 VM reporting the correct FQDN to the
> engine.
> Starting with this release, the ovirt-guest-agent is not available anymore.
>
> Therefore, I have installed
27 matches
Mail list logo
