Issue #4562
closed
Source installs should fail if a plugin requires a newer version of pulpcore-plugin or pulpcore than is checked out
Description
This occurs when:
- A plugin is being installed
- pulpcore-plugin is being installed from source
- the plugin requires version X of pulpcore-plugin
- checked out pulpcore-plugin is older than X
When these factors are all true, pulpcore-plugin is installed from PyPI, which is surprising. If pulp_plugin_source_dir is set, and pulpcore-plugin is installed during the plugin installation, the installer should raise an error.
An alternate implementation could be to check the requirements of each plugin early in the installation. If they are not compatible, it could fail quickly.
Related issues
Updated by amacdona@redhat.com about 5 years ago
- Tags Dev Environment, Pulp 3, Pulp 3 installer added
Updated by amacdona@redhat.com about 5 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 50
Updated by amacdona@redhat.com almost 5 years ago
- Related to Issue #4793: Locking does not work as expected with Publications added
Updated by amacdona@redhat.com almost 5 years ago
- Related to deleted (Issue #4793: Locking does not work as expected with Publications)
Updated by amacdona@redhat.com almost 5 years ago
- Related to Issue #4794: Pulp handles incompatible plugins poorly added
Updated by amacdona@redhat.com almost 5 years ago
- Sprint changed from Sprint 53 to Sprint 54
Updated by rchan almost 5 years ago
This issue won't get moved forward to Sprint 55 because it impacts developers only and isn't a high enough priority given other stakeholder needs. Will consider later.
Updated by bmbouter almost 4 years ago
- Category set to Installer - Moved to GitHub issues
- Tags deleted (
Pulp 3 installer)
Updated by dkliban@redhat.com over 3 years ago
- Status changed from NEW to CLOSED - CURRENTRELEASE
The installer does not allow plugins to upgrade pulpcore and as a result it halts installation. The constraints file is used for this.
.