Project

General

Profile

Actions
Copy link

Bug #10844

closed

mon: caps validation should rely on EntityName instead of entity_name_t

Added by Joao Eduardo Luis over 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Joao Eduardo Luis
Category:
Monitor
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
firefly, giant
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

More precisely, on MonCapGrand::expand_profile(), we take an entity_name_t to properly fill in config-key's grants on profile osd.

If we happen to need to get/set a config-key for a given osd using a client (e.g., ceph --name osd.X config-key exists daemon-private/osd.X/foo), we'll get an EACCES -- that's because the monitor is using the client's msgr entity (e.g., client.12345) as the entity when expanding the caps profile, instead of osd.X.

Actions
Copy link
 #1

Updated by Joao Eduardo Luis over 9 years ago

  • Status changed from New to Fix Under Review
Actions
Copy link
 #2

Updated by Sage Weil over 9 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #5

Updated by Loïc Dachary about 9 years ago

4427358 mon: MonCap: take EntityName instead when expanding profiles (in giant), 8ef14fc mon: MonCap: take EntityName instead when expanding profiles (in firefly),

Actions
Copy link
 #6

Updated by Loïc Dachary about 9 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF