In 5.1 I could do the following: (undercloud) [stack@undercloud-0 ~]$ cat /home/stack/initial-ceph.conf [global] public_network = '172.120.3.0/24,172.117.3.0/24,172.118.3.0/24,172.119.3.0/24' cluster_network = '172.120.4.0/24,172.117.4.0/24,172.118.4.0/24,172.119.4.0/24' ms_bind_ipv4 = true ms_bind_ipv6 = false (undercloud) [stack@undercloud-0 ~]$ ./cephadm bootstrap --config initial-ceph.conf ... and my Ceph cluster was able to bootstrap without a problem. However with cephadm-16.2.8-79.el9cp.noarch and 5-259 from the Ceph 5.2 beta, I intead see the following error and the bootstrap fails: ERROR: Invalid public_network '172.120.3.0/24,172.117.3.0/24,172.118.3.0/24,172.119.3.0/24' parameter: '172.120.3.0/24 invalid: \"'172.120.3.0/24\" does not appear to be an IPv4 or IPv6 network, 172.119.3.0/24' is not in CIDR format (address/netmask)
WORKAROUND: bootstrap with "--config initial-ceph.conf" and then use command like the following: ceph config set global public_network '172.117.3.0/24,172.118.3.0/24,172.119.3.0/24,172.120.3.0/24' ceph config set global cluster_network '172.117.4.0/24,172.118.4.0/24,172.119.4.0/24,172.120.4.0/24' The OSDs (which are on Ceph Storage Nodes on a routed network) are then able to join the ceph cluster. Though customers can use a workaround, OpenStack documentation has supported the comma delimited method in the initial ceph.conf for a "one command deploy". Thus, they might perceive this as a regression.
(In reply to John Fulton from comment #1) > WORKAROUND: > > bootstrap with "--config initial-ceph.conf" and then use.. I meant bootstrap WITHOUT the initial ceph conf.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat Ceph Storage 6.1 security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:3623