Re: [ceph-users] application not enabled on pool
Ah, yes. This cluster has had all all the versions of Luminous on it. Started with Kraken and went to every Luminous release candidate to date. So I guess I'll just do the `ceph osd pool application enable` commands and be done with it. I appreciate your assistance. Roger On Fri, Aug 4, 2017 at 4:32 PM Gregory Farnum wrote: > 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 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 >> 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 >>> 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 wrote: > Got it, thanks! > > On Fri, Aug 4, 2017 at 9:48 AM David Turner > 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 >> 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 >>> >>> 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 ', >>> where 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
Re: [ceph-users] application not enabled on pool
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 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 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 >> 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 >>> wrote: >>> Got it, thanks! On Fri, Aug 4, 2017 at 9:48 AM David Turner 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 > 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 >> >> 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 ', >> where 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
Re: [ceph-users] application not enabled on pool
Yes. https://github.com/ceph/ceph/blob/master/src/mon/OSDMonitor.cc#L1069 On Fri, Aug 4, 2017 at 9:14 AM David Turner 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 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 wrote: >> >>> Got it, thanks! >>> >>> On Fri, Aug 4, 2017 at 9:48 AM David Turner >>> 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 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 > > 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 ', > where 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
Re: [ceph-users] application not enabled on pool
Should they be auto-marked if you upgraded an existing cluster to Luminous? On Fri, Aug 4, 2017 at 12:13 PM Gregory Farnum 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 wrote: > >> Got it, thanks! >> >> On Fri, Aug 4, 2017 at 9:48 AM David Turner >> 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 >>> 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 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 ', where 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
Re: [ceph-users] application not enabled on pool
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 wrote: > Got it, thanks! > > On Fri, Aug 4, 2017 at 9:48 AM David Turner 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 >> 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 >>> >>> 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 ', where >>> 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
Re: [ceph-users] application not enabled on pool
Got it, thanks! On Fri, Aug 4, 2017 at 9:48 AM David Turner 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 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 >> >> 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 ', where >> 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
Re: [ceph-users] application not enabled on pool
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 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 > > 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 ', where > 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] application not enabled on pool
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 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 ', where 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
