Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Don't include all rgws in ceph conf
See original GitHub issueBug Report
What happened:
In deploying rgw it will add all rgw hosts to ceph conf. It seems to be okay but when you run ansible with --limit it will add just the limitations and when you can’t run ansible on all your nodes at a same time, each node will have different and messy ceph conf.
What you expected to happen:
Won’t it better to no loop on rgws host here and just add each host config to it’s ceph conf?
https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-config/templates/ceph.conf.j2#L108
I mean for example host1 just have client.rgw.host1 config instead of having both host1 and host2?
This loop was added to solve #49 but I think it could be solve without loop on rgw instances!
How to reproduce it (minimal and precise):
deploy rgw with --limit on one or two hosts
Issue Analytics
- State:
- Created 3 years ago
- Comments:10
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
closed by #5587
@clwluvw I need to figure out a couple of details before merging it to master first, then the backport to stable-4.0 should follow pretty quickly. I can’t give you an accurate due date for now but it shouldn’t be that long. Thanks for your patience!