I'm marking this bug as incomplete while the information requested is collected and shared.
Data needed:
- Run arping from a node on the same L2 network as the radosGW service to verify VIP is correctly configured.
- Collect logs from the node that's attempting to be deployed + radosgw, ideally setting radosgw loglevel to 3, but 2 would be OK too, it all depends on the free disk space available and how busy your radosgw is serving requests
juju config ceph-radosgw loglevel=3
I'm marking this bug as incomplete while the information requested is collected and shared.
Data needed:
- Run arping from a node on the same L2 network as the radosGW service to verify VIP is correctly configured.
- Collect logs from the node that's attempting to be deployed + radosgw, ideally setting radosgw loglevel to 3, but 2 would be OK too, it all depends on the free disk space available and how busy your radosgw is serving requests
juju config ceph-radosgw loglevel=3