Project

Profile

Help

Issue #9084

Confusion around component versions

Added by daviddavis 5 months ago. Updated 4 months ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

The status api reports the following:

  "versions": [
    {
      "component": "core",
      "version": "3.15.0.dev"
    },
    {
      "component": "python",
      "version": "3.5.0.dev"
    }

This has let to some confusion among users (see here) because they think the server is running Python 3.5 when actually python here refers to the python plugin.

History

#1 Updated by bmbouter 4 months ago

The only way I know to clarify this is in the docs, but I don't think that will effectively clear this up for those confused. Really an API like this would have been clearer:

  "pulp_plugins": [
    {
      "django_app_name": "core",
      "version": "3.15.0.dev"
    },
    {
      "django_app_name": "python",
      "version": "3.5.0.dev"
    }

#2 Updated by bmbouter 4 months ago

We could add a section like that and just have it mirror the data in the other one? It's not great but I do think it's a step in the right direction.

#3 Updated by dkliban@redhat.com 4 months ago

  • Triaged changed from No to Yes

#4 Updated by daviddavis 4 months ago

  • Status changed from NEW to CLOSED - WONTFIX

Discussed today at triage. We resolved the original problem in the CLI and adding a new section with dupe data would be confusing for users so we agreed to close this out.

#5 Updated by quba42 4 months ago

Alternative workaround solution: Bump the pulp_python plugin version to 4.0. Now no one will mistake it for the python version. ;-P

Please register to edit this issue

Also available in: Atom PDF