Project

General

Profile

Bug #47511

rook: 'ceph orch status' returns 403 error

Added by Varsha Rao 4 months ago. Updated 4 months ago.

Status:
Pending Backport
Priority:
Normal
Assignee:
Category:
mgr/rook
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
octopus, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

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}
)

History

#1 Updated by Varsha Rao 4 months ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 37213

#2 Updated by Varsha Rao 4 months ago

  • Backport changed from octopus to octopus, nautilus

#3 Updated by Patrick Donnelly 4 months ago

  • Status changed from Fix Under Review to Pending Backport

Also available in: Atom PDF