magnum service-list no response if m-cond is down

[Eli Qiao]

shutdown m-cond
magnum service-list no response

[yatin (yatinkarel)]

@Eli are you working on this patch, if not i will start working on it.

[yatin (yatinkarel)]

@Eli, I think it should be a bug, not wishlist.
Because service-list returns services(magnum conductor state(up/down). If magnum conductor is down(magnum api would not give response to get requests), then i think there is no sense to provide magnum-service list api.

[yatin (yatinkarel)]

Also, response is not there for other commands(bay/baymodel) as well because all requests are passed through conductor.
As stated here: magnum/cmd/api.py
base.MagnumObject.indirection_api = base.MagnumObjectIndirectionAPI()

I think, not all requests should be passed through conductor api. Atleast get request can be directly forwarded to db.

[Eli Qiao (taget-9)]

@yatin,
We'v discussed it before, m-api -> m-cond to access data base, if m-cond's down, then m-api can not fetch any results.

To fix it, we need to allow m-api to access data base, I am not sure this is really what we want.

Beside, if m-cond is down, we can not provide any service at all, so it makes sense that m-api won't response.

thought?

Eli.

[yatin (yatinkarel)]

<<<To fix it, we need to allow m-api to access data base, I am not sure this is really what we want.

Yes, i also think this is the only way to do this.

@Eli, then how admin would know conductor is down using service-list api, because it will not respond because conductor is down.
service-list api would make no sense in this case.Following are the output when conductor is up and down:-

ubuntu@ubuntubase:/opt/stack/magnum$ magnum service-list
+----+-----------+------------------+-------+
| id | host | binary | state |
+----+-----------+------------------+-------+
| 1 | localhost | magnum-conductor | up |
+----+-----------+------------------+-------+

When conductor is down:-
ubuntu@ubuntubase:/opt/stack/magnum$ magnum service-list
ERROR: Timed out waiting for a reply to message ID 01d6cdbb802142bda1c33cd28f6a2d35 (HTTP 500) (Request-ID: req-248f2ee3-4633-4768-819a-21c9f1d6ec8b)