Roger, was this a test cluster that was already running Luminous? The
auto-assignment logic won't work in that case (it's already got the
CEPH_RELEASE_LUMINOUS feature set which we're using to run it).

I'm not sure if there's a good way to do that upgrade that's worth the
effort.
-Greg

On Fri, Aug 4, 2017 at 9:21 AM Gregory Farnum <gfar...@redhat.com> wrote:

> Yes. https://github.com/ceph/ceph/blob/master/src/mon/OSDMonitor.cc#L1069
>
> On Fri, Aug 4, 2017 at 9:14 AM David Turner <drakonst...@gmail.com> wrote:
>
>> Should they be auto-marked if you upgraded an existing cluster to
>> Luminous?
>>
>> On Fri, Aug 4, 2017 at 12:13 PM Gregory Farnum <gfar...@redhat.com>
>> wrote:
>>
>>> All those pools should have been auto-marked as owned by rgw though. We
>>> do have a ticket around that (http://tracker.ceph.com/issues/20891) but
>>> so far it's just confusing.
>>> -Greg
>>>
>>> On Fri, Aug 4, 2017 at 9:07 AM Roger Brown <rogerpbr...@gmail.com>
>>> wrote:
>>>
>>>> Got it, thanks!
>>>>
>>>> On Fri, Aug 4, 2017 at 9:48 AM David Turner <drakonst...@gmail.com>
>>>> wrote:
>>>>
>>>>> In the 12.1.2 release notes it stated...
>>>>>
>>>>>   Pools are now expected to be associated with the application using
>>>>> them.
>>>>>   Upon completing the upgrade to Luminous, the cluster will attempt to
>>>>> associate
>>>>>   existing pools to known applications (i.e. CephFS, RBD, and RGW).
>>>>> In-use pools
>>>>>   that are not associated to an application will generate a health
>>>>> warning. Any
>>>>>   unassociated pools can be manually associated using the new
>>>>>   "ceph osd pool application enable" command. For more details see
>>>>>   "Associate Pool to Application" in the documentation.
>>>>>
>>>>> It is always a good idea to read the release notes before upgrading to
>>>>> a new version of Ceph.
>>>>>
>>>>> On Fri, Aug 4, 2017 at 10:29 AM Roger Brown <rogerpbr...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Is this something new in Luminous 12.1.2, or did I break something?
>>>>>> Stuff still seems to function despite the warnings.
>>>>>>
>>>>>> $ ceph health detail
>>>>>> <snip>
>>>>>> POOL_APP_NOT_ENABLED application not enabled on 14 pool(s)
>>>>>>     application not enabled on pool 'default.rgw.buckets.non-ec'
>>>>>>     application not enabled on pool 'default.rgw.control'
>>>>>>     application not enabled on pool 'default.rgw.data.root'
>>>>>>     application not enabled on pool 'default.rgw.gc'
>>>>>>     application not enabled on pool 'default.rgw.lc'
>>>>>>     application not enabled on pool 'default.rgw.log'
>>>>>>     application not enabled on pool 'default.rgw.users.uid'
>>>>>>     application not enabled on pool 'default.rgw.users.email'
>>>>>>     application not enabled on pool 'default.rgw.users.keys'
>>>>>>     application not enabled on pool 'default.rgw.buckets.index'
>>>>>>     application not enabled on pool 'default.rgw.users.swift'
>>>>>>     application not enabled on pool '.rgw.root'
>>>>>>     application not enabled on pool 'default.rgw.reshard'
>>>>>>     application not enabled on pool 'default.rgw.buckets.data'
>>>>>>     use 'ceph osd pool application enable <pool-name> <app-name>',
>>>>>> where <app-name> is 'cephfs', 'rbd', 'rgw', or freeform for custom
>>>>>> applications.
>>>>>>
>>>>>> _______________________________________________
>>>>>> ceph-users mailing list
>>>>>> ceph-users@lists.ceph.com
>>>>>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>>>>>>
>>>>> _______________________________________________
>>>> ceph-users mailing list
>>>> ceph-users@lists.ceph.com
>>>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>>>>
>>>
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to