You have to set either "version" or "upgrade" for each plugin.
That is a known issue I intend to address.
-Mike
On Thu, Apr 30, 2020 at 6:39 PM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:
> Thanks Brian and Mike for looking into this.
> I tried to set the version in the
Thanks Brian and Mike for looking into this.
I tried to set the version in the pulp_install_plugins below but got the errors
pulp_install_plugins:
pulp-file:
upgrade: true
version: '0.3.0'
pulp-rpm:
upgrade: true
version: '3.3.0'
---
TASK [pulp : Install Pulp
Today we met to discuss some ideas for a technical design for how the CLI
would work. Here's a copy of our notes:
https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig#Technical-discussion
And there is a rough design in the document as well:
https://hackmd.io/aH9RqAS_TrGyxoi1UGRgig#Design
I have also
Hi Bin,
Another user reported a similar error to you, and I've filed this issue
https://pulp.plan.io/issues/6623 The "pre-flight" check is designed to
verify that the pulpcore version being installed/upgraded to is compatible
with all plugins that will be installed prior to any bits installing
I accidently reproduced the issue[0]. We should now be able to fix it.
[0] https://pulp.plan.io/issues/6463#note-5
On Mon, Apr 20, 2020 at 11:25 AM Dennis Kliban wrote:
> The issue does not have any steps to reproduce it. Have you been able to
> consistently reproduce the issue with a
