[Pulp-dev] pulp-manage-db bug blocking 2.11.0
bbouters at redhat.com
Wed Dec 7 16:20:52 UTC 2016
+1 to reopening 2468 and excluding pulp_celerybeat records from the check,
and holding 2.11 until this is resolved
Note that ^ would allow us to remove the known issues problem from the
release notes which should also be done
+1 to removing the y/N interactive prompt which would also allow us to
close this PR .
Also, we should close 2472 as NOTABUG or WORKSFORME as I commented on here
On Wed, Dec 7, 2016 at 10:02 AM, Michael Hrivnak <mhrivnak at redhat.com>
> We've re-opened issue #2468, and Bihan is going to make the PR that
> implements this change. If there are any additional questions or concerns,
> please bring them up ASAP.
> On Wed, Dec 7, 2016 at 9:51 AM, Sean Myers <sean.myers at redhat.com> wrote:
>> On 12/07/2016 08:59 AM, Bihan Zhang wrote:
>> > +1 excluding pulp_celerybeat
>> > Also since we have the --ignore-running-workers flag and are ignoring
>> > celerybeat I would like to propose we stop prompting the user to
>> > and instead just display an error message when we detect running
>> > 'Migration halted because there are still running workers, please stop
>> > workers before re-running this command. If you believe this message was
>> > given in error please re-run the command with the
>> > flag'
>> I think doing what's proposed would fix #2472. Add that to the fixes
>> from #2768 and #2769 and this should be good to ship another RC.
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev