Same situation.
I had to remove port 5900 from the host to complete the installation.
firewall-cmd --zone public --remove-port 5900/tcp --permanent
As you have already mentioned there is no access to the hosted-engine vm, so as
a workaround I commented out the open port task in the following
I don't see 6900 in
https://github.com/gluster/glusterfs/blob/devel/extras/firewalld/glusterfs.xml
Best Regards,Strahil Nikolov___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement:
Hi,
On Wed, May 12, 2021 at 8:53 PM Charles Kozler wrote:
>
> Yep! I thought the error was reporting as the port already configured inside
> the seed engine and not on the actual host. I deleted the firewalld 6900 port
> addition and everything seems to be flowing through
>
> On Wed, May 12,
Yep! I thought the error was reporting as the port already configured
inside the seed engine and not on the actual host. I deleted the firewalld
6900 port addition and everything seems to be flowing through
On Wed, May 12, 2021 at 1:36 PM Patrick Lomakin
wrote:
> Hello. I know this error.
Hello. I know this error. Please see which ports are used in firewalld
configuration (6900). In gluster wizard click "Edit" button and remove gluster
firewall config string like "port 6900". Save your configuration and try to
deploy. Regards!
___
I also just upgraded to 4.6.6.1 and it is still occurring
On Wed, May 12, 2021 at 12:36 PM Charles Kozler
wrote:
> Hello -
>
> Deployed fresh ovirt node 4.4.6 and the only thing I did to the system was
> configure the NIC with nmtui
>
> During the gluster install the install errored out with
6 matches
Mail list logo
