From: Sage Weil <sage@redhat.com>
Date: Wed, 12 Aug 2015 20:54:55 +0000 (-0400)
Subject: PendingReleaseNotes: more notes about the 'ceph' user
X-Git-Tag: v9.1.0~294^2~6
X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=7cd07490f219925efcbbfbd66625cd89ab9be19c;p=ceph.git

PendingReleaseNotes: more notes about the 'ceph' user

Signed-off-by: Sage Weil <sage@redhat.com>
---

diff --git a/PendingReleaseNotes b/PendingReleaseNotes
index 6108ee9eb63d..e91ded961dba 100644
--- a/PendingReleaseNotes
+++ b/PendingReleaseNotes
@@ -7,18 +7,27 @@ v9.0.4
 Upgrading
 ---------
 
-* Ceph daemons now run as user and group ceph by default.  During upgrade,
-  administrators have two options:
+* Ceph daemons now run as user and group ceph by default.  The ceph user has a
+  static UID assigned by Fedora and Debian (also used by derivative distributions
+  like RHEL/CentOS and Ubuntu).  On SUSE the ceph user will currently get a
+  dynamically assigned UID when the user is created.
+
+  If your systems already have a ceph user, upgrading the package will cause
+  problems.  We suggest you first remove or rename the existing 'ceph' user
+  before upgrading.
+
+  When upgrading, administrators have two options:
 
    #. Add the following line to ``ceph.conf`` on all hosts::
 
         setuser match path = /var/lib/ceph/$type/$cluster-$id
 
-      This will make the daemon remain root (i.e., not drop privileges and
-      switch to user ceph) if the daemon's data directory is still owned by
-      root.  Newly deployed daemons will be created with data owned by user
-      ceph and will run with reduced privileges, but upgraded daemons will
-      continue to run as root.
+      This will make the Ceph daemons run as root (i.e., not drop
+      privileges and switch to user ceph) if the daemon's data
+      directory is still owned by root.  Newly deployed daemons will
+      be created with data owned by user ceph and will run with
+      reduced privileges, but upgraded daemons will continue to run as
+      root.
 
    #. Fix the data ownership during the upgrade.  This is the preferred option,
       but is more work.  The process for each host would be to: