Can't set long node name! using kubernetes

[venkateshcontus]

Hi,

we started the ejabberd node with the below command
**sbin/ejabberdctl --node ejabberd@10.0.1.18** 

it works and verified by logs in PSI+ . After that try to check the status getting error.
**sbin/ejabberdctl --node ejabberd@10.0.1.18 status **

IP is created dynamically in kubernetes cluster so we can't able to set in ejabberd.cfg file.

Environment

• ejabberd version: 24.02
• Erlang version: 24
• OS: Linux (Debian)
• Installed from: source

Configuration (only if needed): grep -Ev '^$|^\s*#' ejabberd.yml

loglevel: 4
...

Errors from error.log/crash.log

--
=INFO REPORT==== 21-Mar-2024::10:05:33.064535 ===
Can't set long node name!
Please check your configuration

=SUPERVISOR REPORT==== 21-Mar-2024::10:05:33.064570 ===
supervisor: {local,net_sup}
errorContext: start_error
reason: {'EXIT',nodistribution}
offender: [{pid,undefined},
{id,net_kernel},
{mfargs,{net_kernel,start_link,
[#{clean_halt => true,name => undefined,
name_domain => longnames,
supervisor => net_sup}]}},
{restart_type,permanent},
{significant,false},
{shutdown,2000},
{child_type,worker}]

{"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}})

Crash dump is being written to: /opt/ejabberd/var/log/ejabberd/erl_crash_20240321-100532.dump...done

Bug description

IP address not able assign a node name ejabberd@10.0.1.18, ejabberd@10.0.1.20