![]() With the advent of this fix, what should I do before I upgrade to 17.2.6 (currently on 17.2.5, rocky 8) Thus, if I create a role on the primary, add/delete users or buckets from said role, the role, including the AssumeRolePolicyDocument and policies, gets pushed to the replicated site. Because of the lack of replication for IAM roles, we have set things up so that roles on the primary 'manually' get replicated to the secondary site via a python script. Made it into ceph 17.2.6, as per the change log at: That's great. I paused it on purpose to allow for manipulation of daemons. ![]() "which": "Upgrading all daemon types on all hosts", ceph07 error 2d agoĪny idea how I can get rid of them? Or redeploy them?Īdditionally I'm just in the middle of an true, When I reissue the command itįails saying that the service isn't there. I even was desperateĮnough to delete files for services from hosts before rebooting hoping IĪll I see are the same MDS stuck in "error" state. Scheduled changes, failed mgr, even rebooted hosts. It's the same for other daemons/services. I can plan to restart, redeploy, reconfigure services via cephadm orĭashboard just as I want but services won't react. Investigation with your help I found another issue that might be related. ![]() As you might know, I have a problem with MDS not starting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |