This issue is here from before (i.e. not new to 4.14), so we can argue it's not technically a blocker due to regression happening in some previous release, and I can live with it being moved to 4.15.
That being said, would be great to see it solved if this rings any bells for anyone who might have played with the related code... On Mon, 3 Feb 2020 at 13:21, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > People, > A ticket has been raised as a blocker but i don't think anybody here has > the resources to fix it. It is a regression of kinds, and a known issue but > in my not so humble opinion won't block anybody from using a future > release. The Issue [1] describes the problem and a PR [2] gives a partial > solution. It is known to work for a KVM/Ceph environment and thus might be > to specific. > > I move that we either > 1. find the PR that caused this and revert it, and/or > 2. postpone fixing it till after 4.14 (unless someone has the resources and > volunteers to address it) > and as an ugly workaround (creating a cron job for your env that deletes > stale images) exists, unmark it as blocker. > > [1] https://github.com/apache/cloudstack/issues/3646 > [2] https://github.com/apache/cloudstack/pull/3649 > > any comments, please? > -- > Daan > -- Andrija Panić
