Bug #47511: rook: 'ceph orch status' returns 403 error - Orchestrator - Ceph

Actions

Copy link

Bug #47511

closed

rook: 'ceph orch status' returns 403 error

Added by Varsha Rao over 3 years ago. Updated almost 3 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Varsha Rao

Category:

mgr/rook

Target version:

Ceph - v16.0.0

% Done:

Source:

Development

Tags:

Backport:

octopus, nautilus

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

37213

Crash signature (v1):

Crash signature (v2):

Description

[root@rook-ceph-tools-78cdfd976c-m985m /]# ceph orch status
Backend: rook
Available: False (Cannot reach Kubernetes API: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'Date': 'Thu, 17 Sep 2020 07:07:25 GMT', 'Content-Length': '293'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:rook-ceph:rook-ceph-mgr\" cannot list resource \"pods\" in API group \"\" in the namespace \"my-cluster\"","reason":"Forbidden","details":{"kind":"pods"},"code":403}
)