It seems to me the fix could have been done in a backportable way if
it was planned on being backported. You could introduce a new config
option and deprecate the old one, for example, rather than changing
the existing one.
On Tue, Apr 24, 2018 at 2:11 PM, Chris Gregan
<email address hidden> wrote:
> This issue continues to plague our Pike deployments. The field will
> continue to deploy Pike on Xenial. Is there a reasonable workaround for
> this on Pike? Otherwise any deployment going up in the next month will
> be effected.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1746118
>
> Title:
> Error: Device is mounted
>
> Status in OpenStack ceph-osd charm:
> Fix Committed
>
> Bug description:
> It looks like the ceph-osd charm is trying to initialize my storage
> twice:
>
> 2018-01-29 22:35:21 INFO juju-log mon:43: osdize cmd: ['ceph-disk',
> 'prepare', '--fs-type', 'xfs', '--zap-disk', '--filestore',
> '/dev/sdb']
>
> 2018-01-29 22:36:03 INFO juju-log mon:43: osdize cmd: ['ceph-disk',
> 'prepare', '--fs-type', 'xfs', '--zap-disk', '--filestore',
> '/dev/sdb']
>
> The second time in fails with an error:
> 2018-01-29 22:36:03 DEBUG mon-relation-changed ceph-disk: Error: Device is mounted: /dev/sdb1
>
> ceph-osd/5 log: http://paste.ubuntu.com/26486128/
>
> bundle: http://paste.ubuntu.com/26486149/
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/charm-ceph-osd/+bug/1746118/+subscriptions
It seems to me the fix could have been done in a backportable way if
it was planned on being backported. You could introduce a new config
option and deprecate the old one, for example, rather than changing
the existing one.
On Tue, Apr 24, 2018 at 2:11 PM, Chris Gregan /bugs.launchpad .net/bugs/ 1746118 changed ceph-disk: Error: Device is mounted: /dev/sdb1 paste.ubuntu. com/26486128/ paste.ubuntu. com/26486149/ /bugs.launchpad .net/charm- ceph-osd/ +bug/1746118/ +subscriptions
<email address hidden> wrote:
> This issue continues to plague our Pike deployments. The field will
> continue to deploy Pike on Xenial. Is there a reasonable workaround for
> this on Pike? Otherwise any deployment going up in the next month will
> be effected.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Error: Device is mounted
>
> Status in OpenStack ceph-osd charm:
> Fix Committed
>
> Bug description:
> It looks like the ceph-osd charm is trying to initialize my storage
> twice:
>
> 2018-01-29 22:35:21 INFO juju-log mon:43: osdize cmd: ['ceph-disk',
> 'prepare', '--fs-type', 'xfs', '--zap-disk', '--filestore',
> '/dev/sdb']
>
> 2018-01-29 22:36:03 INFO juju-log mon:43: osdize cmd: ['ceph-disk',
> 'prepare', '--fs-type', 'xfs', '--zap-disk', '--filestore',
> '/dev/sdb']
>
> The second time in fails with an error:
> 2018-01-29 22:36:03 DEBUG mon-relation-
>
> ceph-osd/5 log: http://
>
> bundle: http://
>
> To manage notifications about this bug go to:
> https:/