Bug #19994
closedceph-mgr upstart issue on trusy - HEALTH_ERR no active mgr
0%
Description
on trusty the ceph-deploy tests fails, there is nothing special we currently do to enable/start ceph-mgr
the same steps work for centos 7.3 and ubuntu 16.04
on 14.04, I tried to see if i can start manually to fix the tests but the daemons dont come up
ubuntu@ubu14:~/cd$ sudo start ceph-mon id=ubu14 ceph-mon (ceph/ubu14) start/running, process 11121 ubuntu@ubu14:~/cd$ ps -eaf | grep ceph ceph 11121 1 1 00:31 ? 00:00:00 /usr/bin/ceph-mon --cluster=ceph -i ubu14 -f --setuser ceph --setgroup ceph ubuntu 11159 1326 0 00:31 pts/0 00:00:00 grep --color=auto ceph ubuntu@ubu14:~/cd$ sudo start ceph-mgr id=ubu14 ceph-mgr stop/waiting ubuntu@ubu14:~/cd$ ps -eaf | grep ceph ceph 11121 1 0 00:31 ? 00:00:00 /usr/bin/ceph-mon --cluster=ceph -i ubu14 -f --setuser ceph --setgroup ceph ubuntu 11166 1326 0 00:39 pts/0 00:00:00 grep --color=auto ceph
Updated by Greg Farnum almost 7 years ago
- Priority changed from Normal to Urgent
Updated by Greg Farnum almost 7 years ago
- Project changed from Ceph to mgr
- Category deleted (
110)
Updated by Sage Weil almost 7 years ago
- Status changed from New to 12
- Priority changed from Urgent to Immediate
need to confirm this works on trusty before luminous release
Updated by Sage Weil almost 7 years ago
- Status changed from 12 to 4
The automatic mgr-creation-from-mon upgrade magic is not implemented for upstart (trusty). we could either
1. mention that explicitly in the upgrade notes
2. remove that behavior from systemd too
3. implement it for upstart.
I'm not sure how painful (3) is, but pretty sure it'll be at least as ugly as the systemd version.
Updated by Vasu Kulkarni almost 7 years ago
I think mentioning that in upgrade notes is sufficient, but it will also need steps to start it, in my case the steps i tried above to start ceph-mgr didn't work, probably i am missing something.
If the steps work, I can fix the ceph-deploy test and check on luminous build.
Updated by Sage Weil almost 7 years ago
- Status changed from 4 to Fix Under Review
Updated by Sage Weil almost 7 years ago
- Status changed from Fix Under Review to Resolved
Updated by Vasu Kulkarni almost 7 years ago
Tested here and its fixed for trusty.