[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2020-02-12 Thread James Page
This bug was fixed in the package ceph - 12.2.12-0ubuntu0.18.04.4~cloud0
---

 ceph (12.2.12-0ubuntu0.18.04.4~cloud0) xenial-queens; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 ceph (12.2.12-0ubuntu0.18.04.4) bionic; urgency=medium
 .
   [ Billy Olsen ]
   * Do not validate fs caps on authorize (LP: #1847822):
 - d/p/dont-validate-fs-caps-on-authorize.patch: Do not validate
   the filesystem caps with a new client connection to the monitor
   when authorizing a client connection.
 .
   [ Dan Hill ]
   * d/p/issue38454.patch: Cherry pick of fixes for misc RGW bugs
 and cleanup of garbage collection code (LP: #1843085).
 .
   [ Dariusz Gadomski ]
   * d/p/issue37490.patch: Cherry pick fix to optimize LVM queries
 in ceph-volume, resolving performance issues in systems under
 heavy load or with large numbers of disks (LP: #1850754).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2020-01-21 Thread James Page
This bug was fixed in the package ceph - 12.2.12-0ubuntu0.18.04.4~cloud0
---

 ceph (12.2.12-0ubuntu0.18.04.4~cloud0) xenial-queens; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 ceph (12.2.12-0ubuntu0.18.04.4) bionic; urgency=medium
 .
   [ Billy Olsen ]
   * Do not validate fs caps on authorize (LP: #1847822):
 - d/p/dont-validate-fs-caps-on-authorize.patch: Do not validate
   the filesystem caps with a new client connection to the monitor
   when authorizing a client connection.
 .
   [ Dan Hill ]
   * d/p/issue38454.patch: Cherry pick of fixes for misc RGW bugs
 and cleanup of garbage collection code (LP: #1843085).
 .
   [ Dariusz Gadomski ]
   * d/p/issue37490.patch: Cherry pick fix to optimize LVM queries
 in ceph-volume, resolving performance issues in systems under
 heavy load or with large numbers of disks (LP: #1850754).


** Changed in: cloud-archive/queens
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2020-01-20 Thread Launchpad Bug Tracker
This bug was fixed in the package ceph - 12.2.12-0ubuntu0.18.04.4

---
ceph (12.2.12-0ubuntu0.18.04.4) bionic; urgency=medium

  [ Billy Olsen ]
  * Do not validate fs caps on authorize (LP: #1847822):
- d/p/dont-validate-fs-caps-on-authorize.patch: Do not validate
  the filesystem caps with a new client connection to the monitor
  when authorizing a client connection.

  [ Dan Hill ]
  * d/p/issue38454.patch: Cherry pick of fixes for misc RGW bugs
and cleanup of garbage collection code (LP: #1843085).

  [ Dariusz Gadomski ]
  * d/p/issue37490.patch: Cherry pick fix to optimize LVM queries
in ceph-volume, resolving performance issues in systems under
heavy load or with large numbers of disks (LP: #1850754).

 -- James Page   Thu, 28 Nov 2019 10:27:34 +

** Changed in: ceph (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2020-01-16 Thread Dan Hill
Sorry, I should have clearly indicated that the test cases were
exercised.

Verification has been completed on both bionic and queens.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2020-01-16 Thread Ɓukasz Zemczak
I see there's a very specific test-case here in the bug to verify if the
issue is resolved, but I don't see any mention of it being ran as part
of verification. Was it part of the general regression testing? Could
you perform those steps and only then switch the bug to -verified? Thank
you!

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2020-01-15 Thread Dan Hill
** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2020-01-14 Thread Dan Hill
** Description changed:

  [Impact]
  Cancelling large S3/Swift object puts may result in garbage collection 
entries with zero-length chains. Rados gateway garbage collection does not 
efficiently process and clean up these zero-length chains.
  
  A large number of zero-length chains will result in rgw processes
  quickly spinning through the garbage collection lists doing very little
  work. This can result in abnormally high cpu utilization and op
  workloads.
  
  [Test Case]
  Modify garbage collection parameters by editing ceph.conf on the target rgw:
  ```
- [client.rgw.juju-29f238-sf00242079-4]
  rgw enable gc threads = false
  rgw gc obj min wait = 60
  rgw gc processor period = 60
  ```
  
  Restart the ceph-radosgw service to apply the new configuration:
- `sudo systemctl restart ceph-rado...@rgw.juju-29f238-sf00242079-4`
+ `sudo systemctl restart ceph-radosgw@rgw.$HOSTNAME`
  
  Repeatedly interrupt 512MB object put requests for randomized object names:
  ```
  for i in {0..1000}; do 
f=$(mktemp); fallocate -l 512M $f
-   s3cmd put $f s3://test_bucket.juju-29f238-sf00242079-4 --disable-multipart &
+   s3cmd put $f s3://test_bucket --disable-multipart &
pid=$!
sleep $((RANDOM % 7 + 3)); kill $pid
rm $f
  done
  ```
  
  Delete all objects in the bucket index:
  ```
- for f in $(s3cmd ls s3://test_bucket.juju-29f238-sf00242079-4 | awk '{print 
$4}'); do
+ for f in $(s3cmd ls s3://test_bucket | awk '{print $4}'); do
s3cmd del $f
  done
  ```
  
  By default rgw_max_gc_objs splits the garbage collection list into 32 shards.
  Capture omap detail and verify zero-length chains were left over:
  ```
+ export CEPH_ARGS="--id=rgw.$HOSTNAME"
  for i in {0..31}; do 
-   sudo rados -p default.rgw.log --namespace gc listomapvals gc.$i
+   sudo -E rados -p default.rgw.log --namespace gc listomapvals gc.$i
  done
  ```
  
  Confirm the garbage collection list contains expired objects by listing 
expiration timestamps:
- `sudo radosgw-admin gc list | grep time; date`
+ `sudo -E radosgw-admin gc list | grep time; date`
  
  Raise the debug level and process the garbage collection list:
- `CEPH_ARGS="--debug-rgw=20 --err-to-stderr" sudo -E radosgw-admin gc process`
+ `sudo -E radosgw-admin --debug-rgw=20 --err-to-stderr gc process`
  
  Use the logs to verify the garbage collection process iterates through all 
remaining omap entry tags. Then confirm all rados objects have been cleaned up:
- `sudo rados -p default.rgw.buckets.data ls`
- 
+ `sudo -E rados -p default.rgw.buckets.data ls`
  
  [Regression Potential]
  Backport has been accepted into the Luminous release stable branch upstream.
  
  [Other Information]
  This issue has been reported upstream [0] and was fixed in Nautilus alongside 
a number of other garbage collection issues/enhancements in pr#26601 [1]:
  * adds additional logging to make future debugging easier.
  * resolves bug where the truncated flag was not always set correctly in 
gc_iterate_entries
  * resolves bug where marker in RGWGC::process was not advanced
  * resolves bug in which gc entries with a zero-length chain were not trimmed
  * resolves bug where same gc entry tag was added to list for deletion 
multiple times
  
  These fixes were slated for back-port into Luminous and Mimic, but the
  Luminous work was not completed because of a required dependency: AIO GC
  [2]. This dependency has been resolved upstream, and is pending SRU
  verification in Ubuntu packages [3].
  
  [0] https://tracker.ceph.com/issues/38454
  [1] https://github.com/ceph/ceph/pull/26601
  [2] https://tracker.ceph.com/issues/23223
  [3] https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1838858

** Tags removed: verification-queens-needed
** Tags added: verification-queens-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2020-01-13 Thread Dan Hill
** Description changed:

  [Impact]
  Cancelling large S3/Swift object puts may result in garbage collection 
entries with zero-length chains. Rados gateway garbage collection does not 
efficiently process and clean up these zero-length chains.
  
  A large number of zero-length chains will result in rgw processes
  quickly spinning through the garbage collection lists doing very little
  work. This can result in abnormally high cpu utilization and op
  workloads.
  
  [Test Case]
- Disable garbage collection:
- `juju config ceph-radosgw config-flags='{"rgw": {"rgw enable gc threads": 
"false"}}'`
+ Modify garbage collection parameters by editing ceph.conf on the target rgw:
+ ```
+ [client.rgw.juju-29f238-sf00242079-4]
+ rgw enable gc threads = false
+ rgw gc obj min wait = 60
+ rgw gc processor period = 60
+ ```
  
- Repeatedly kill 256MB object put requests for randomized object names.
- `for i in {0.. 1000}; do f=$(mktemp); fallocate -l 256M $f; s3cmd put $f 
s3://test_bucket &; pid=$!; sleep $((RANDOM % 3)); kill $pid; rm $f; done`
+ Restart the ceph-radosgw service to apply the new configuration:
+ `sudo systemctl restart ceph-rado...@rgw.juju-29f238-sf00242079-4`
  
- Capture omap detail. Verify zero-length chains were created:
- `for i in $(seq 0 ${RGW_GC_MAX_OBJS:-32}); do rados -p default.rgw.log 
--namespace gc listomapvals gc.$i; done`
+ Repeatedly interrupt 512MB object put requests for randomized object names:
+ ```
+ for i in {0..1000}; do 
+   f=$(mktemp); fallocate -l 512M $f
+   s3cmd put $f s3://test_bucket.juju-29f238-sf00242079-4 --disable-multipart &
+   pid=$!
+   sleep $((RANDOM % 7 + 3)); kill $pid
+   rm $f
+ done
+ ```
  
- Raise radosgw debug levels, and enable garbage collection:
- `juju config ceph-radosgw config-flags='{"rgw": {"rgw enable gc threads": 
"false"}}' loglevel=20`
+ Delete all objects in the bucket index:
+ ```
+ for f in $(s3cmd ls s3://test_bucket.juju-29f238-sf00242079-4 | awk '{print 
$4}'); do
+   s3cmd del $f
+ done
+ ```
  
- Verify zero-lenth chains are processed correctly by inspecting radosgw
- logs.
+ By default rgw_max_gc_objs splits the garbage collection list into 32 shards.
+ Capture omap detail and verify zero-length chains were left over:
+ ```
+ for i in {0..31}; do 
+   sudo rados -p default.rgw.log --namespace gc listomapvals gc.$i
+ done
+ ```
+ 
+ Confirm the garbage collection list contains expired objects by listing 
expiration timestamps:
+ `sudo radosgw-admin gc list | grep time; date`
+ 
+ Raise the debug level and process the garbage collection list:
+ `CEPH_ARGS="--debug-rgw=20 --err-to-stderr" sudo -E radosgw-admin gc process`
+ 
+ Use the logs to verify the garbage collection process iterates through all 
remaining omap entry tags. Then confirm all rados objects have been cleaned up:
+ `sudo rados -p default.rgw.buckets.data ls`
+ 
  
  [Regression Potential]
  Backport has been accepted into the Luminous release stable branch upstream.
  
  [Other Information]
  This issue has been reported upstream [0] and was fixed in Nautilus alongside 
a number of other garbage collection issues/enhancements in pr#26601 [1]:
  * adds additional logging to make future debugging easier.
  * resolves bug where the truncated flag was not always set correctly in 
gc_iterate_entries
  * resolves bug where marker in RGWGC::process was not advanced
  * resolves bug in which gc entries with a zero-length chain were not trimmed
  * resolves bug where same gc entry tag was added to list for deletion 
multiple times
  
  These fixes were slated for back-port into Luminous and Mimic, but the
  Luminous work was not completed because of a required dependency: AIO GC
  [2]. This dependency has been resolved upstream, and is pending SRU
  verification in Ubuntu packages [3].
  
  [0] https://tracker.ceph.com/issues/38454
  [1] https://github.com/ceph/ceph/pull/26601
  [2] https://tracker.ceph.com/issues/23223
  [3] https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1838858

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2019-12-10 Thread James Page
General regression testing of bionic/proposed completed OK:

==
Totals
==
Ran: 92 tests in 668.7828 sec.
 - Passed: 84
 - Skipped: 8
 - Expected Fail: 0
 - Unexpected Success: 0
 - Failed: 0
Sum of execute time for each test: 779.9697 sec.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2019-11-29 Thread Timo Aaltonen
Hello Kellen, or anyone else affected,

Accepted ceph into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ceph/12.2.12-0ubuntu0.18.04.4 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ceph (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2019-11-26 Thread James Page
** Description changed:

  [Impact]
  Cancelling large S3/Swift object puts may result in garbage collection 
entries with zero-length chains. Rados gateway garbage collection does not 
efficiently process and clean up these zero-length chains.
  
  A large number of zero-length chains will result in rgw processes
  quickly spinning through the garbage collection lists doing very little
  work. This can result in abnormally high cpu utilization and op
  workloads.
  
  [Test Case]
  Disable garbage collection:
  `juju config ceph-radosgw config-flags='{"rgw": {"rgw enable gc threads": 
"false"}}'`
  
  Repeatedly kill 256MB object put requests for randomized object names.
  `for i in {0.. 1000}; do f=$(mktemp); fallocate -l 256M $f; s3cmd put $f 
s3://test_bucket &; pid=$!; sleep $((RANDOM % 3)); kill $pid; rm $f; done`
  
  Capture omap detail. Verify zero-length chains were created:
  `for i in $(seq 0 ${RGW_GC_MAX_OBJS:-32}); do rados -p default.rgw.log 
--namespace gc listomapvals gc.$i; done`
  
  Raise radosgw debug levels, and enable garbage collection:
  `juju config ceph-radosgw config-flags='{"rgw": {"rgw enable gc threads": 
"false"}}' loglevel=20`
  
  Verify zero-lenth chains are processed correctly by inspecting radosgw
  logs.
  
  [Regression Potential]
- {Pending} Back-port still needs to be accepted upstream. Need complete fix to 
assess regression potential.
+ Backport has been accepted into the Luminous release stable branch upstream.
  
  [Other Information]
  This issue has been reported upstream [0] and was fixed in Nautilus alongside 
a number of other garbage collection issues/enhancements in pr#26601 [1]:
  * adds additional logging to make future debugging easier.
  * resolves bug where the truncated flag was not always set correctly in 
gc_iterate_entries
  * resolves bug where marker in RGWGC::process was not advanced
  * resolves bug in which gc entries with a zero-length chain were not trimmed
  * resolves bug where same gc entry tag was added to list for deletion 
multiple times
  
  These fixes were slated for back-port into Luminous and Mimic, but the
  Luminous work was not completed because of a required dependency: AIO GC
  [2]. This dependency has been resolved upstream, and is pending SRU
  verification in Ubuntu packages [3].
  
  [0] https://tracker.ceph.com/issues/38454
  [1] https://github.com/ceph/ceph/pull/26601
  [2] https://tracker.ceph.com/issues/23223
  [3] https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1838858

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2019-11-21 Thread Dan Hill
Upstream back-port is being tracked by issue#38714, and the pr#31664 [1]
is pending upstream review.

[0] https://tracker.ceph.com/issues/38714
[1] https://github.com/ceph/ceph/pull/31664

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2019-10-14 Thread Edward Hope-Morley
** Tags added: sts-sru-needed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2019-09-19 Thread James Page
** Changed in: cloud-archive
   Status: New => Invalid

** Changed in: ceph (Ubuntu)
   Status: New => Invalid

** Changed in: cloud-archive/queens
   Status: New => Triaged

** Changed in: ceph (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: cloud-archive/rocky
   Importance: Undecided => High

** Changed in: cloud-archive/queens
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2019-09-18 Thread Dan Hill
Want to clearly state that while AIO GC is a dependency, these fixes do
not address anything introduced by that feature.

The fixes address bugs that existed prior to AIO GC.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2019-09-17 Thread Dan Hill
** Changed in: ceph (Ubuntu Bionic)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2019-09-17 Thread Billy Olsen
Adding to UCA queens for luminous backport. Fix is in the mimic series
(UCA rocky) already.

** Also affects: cloud-archive/queens
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/rocky
   Importance: Undecided
   Status: New

** Changed in: cloud-archive/rocky
   Status: New => Fix Released

** Changed in: cloud-archive/queens
 Assignee: (unassigned) => Dan Hill (hillpd)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843085] Re: Backport of zero-length gc chain fixes to Luminous

2019-09-17 Thread Dan Hill
pr#30367 [0] is currently pending upstream review, but needs to have
build issues resolved.

[0] https://github.com/ceph/ceph/pull/30367

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085

Title:
  Backport of zero-length gc chain fixes to Luminous

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1843085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs