What were you trying to do that didn't work?

Using the ceph service to open a wide enough port range for ceph.

What is the impact of this issue to you?

The ceph service files contain an older range, ceph changed it's defaults to accomodate a higher count of services per node.

Please provide the package NVR for which the bug is seen:

?

How reproducible is this bug?:

Always

Steps to reproduce

N/A

Expected results

N/A

Actual results

N/A

Details:
```
[rai@server ~]$ rpm -ql firewalld-2.1.1-1.fc40.noarch | grep ceph
/usr/lib/firewalld/services/ceph-exporter.xml
/usr/lib/firewalld/services/ceph-mon.xml
/usr/lib/firewalld/services/ceph.xml

[rai@server ~]$ cat /usr/lib/firewalld/services/ceph.xml
<?xml version="1.0" encoding="utf-8"?>
<service>
<short>ceph</short>
<description>Ceph is a distributed object store and file system. Enable this option to support Ceph's Object Storage Daemons (OSD), Metadata Server Daemons (MDS), or Manager Daemons (MGR).</description>
<port protocol="tcp" port="6800-7300"/>
</service>
```

Ceph raised the port range to "6800-7568"
```

1. ceph config help ms_bind_port_max
   ms_bind_port_max - Highest port number to bind daemon(s) to
   (int, advanced)
   Default: 7568 ## 7568
   Can update at runtime: true
   ```

CU using firewalld and reaching more than 64 services on a Node (for example 4 OSDs per NVME, having more than 16 NVMEs, you go over this amount of services on the node, as each OSD uses 8 ports).

I request to raise the range to the same current ceph default value.