Hi,
On Wed, May 12, 2021 at 8:53 PM Charles Kozler <charles(a)fixflyer.com> 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, 2021 at 1:36 PM Patrick Lomakin <patrick.lomakin(a)gmail.com> wrote:
>
> 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!
Thanks, Charles and Patrick, for reporting the problem and the solution!
Would one of you like to open a bug on this?
I agree that deploy should not fail on this.
Is it common to use port 6900 for gluster?
Best regards,
--
Didi