Project

Profile

Help

Issue #6696

pulp_installer fails to run "Collect static content" task when pulp_source_dir is set

Added by ironfroggy 7 months ago. Updated 16 days ago.

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

Description

Either needs to be a documented incompatibility and issue an error, or needs to run the correct steps when galaxy_ng is installed and the UI must be part of the installation.

This is not a problem for most uses but will be an issue if we need to test unreleased changes in pulpcore for QA purposes.

Working:

- hosts: all
  vars:
    pulp_settings:
      secret_key: secret
      content_origin: "http://{{ ansible_fqdn }}"
    pulp_default_admin_password: password
    pulp_install_plugins:
      pulp-ansible: {}
      galaxy-ng: {}
      pulp-container: {}
  roles:
    - pulp-database
    - pulp-workers
    - pulp-resource-manager
    - pulp-webserver
    - pulp-content
  environment:
    DJANGO_SETTINGS_MODULE: pulpcore.app.settings

Not Working:

- hosts: all
  vars:
    pulp_settings:
      secret_key: secret
      content_origin: "http://{{ ansible_fqdn }}"
    pulp_default_admin_password: password
    pulp_install_plugins:
      pulp-ansible: {}
      galaxy-ng: {}
      pulp-container: {}
    pulp_source_dir: "git+https://github.com/pulp/pulpcore.git@3.3.0#egg=pulpcore"
  roles:
    - pulp-database
    - pulp-workers
    - pulp-resource-manager
    - pulp-webserver
    - pulp-content
  environment:
    DJANGO_SETTINGS_MODULE: pulpcore.app.settings

Related issues

Related to Pulp - Task #6547: pulp_installer: Add variables for molecule prepare.yml to clone the branchesASSIGNED

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by fao89 7 months ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 72

#2 Updated by bmbouter 7 months ago

  • Category set to Installer
  • Tags deleted (Pulp 3 installer)

#3 Updated by rchan 7 months ago

  • Sprint changed from Sprint 72 to Sprint 73

#4 Updated by rchan 6 months ago

  • Sprint changed from Sprint 73 to Sprint 74

#5 Updated by dkliban@redhat.com 6 months ago

  • Status changed from NEW to CLOSED - WORKSFORME

This problem occurs when the user/group owner of the directory that contains the git source code does not match the 'pulp_user' or 'pulp_group'. This permissions mismatch causes the installer to not behave as expected.

It seems to me that your use case will most likely be alleviated by this issue: https://pulp.plan.io/issues/6903

#6 Updated by dkliban@redhat.com about 1 month ago

  • Status changed from CLOSED - WORKSFORME to NEW
  • Triaged changed from Yes to No

I am reopening because the issue only occurs when the source code is specified using a git URL. My previous comment only makes sense for installations where the path is a directory on the local filesystem.

I suspect that in these cases the installer should not install the package in editable mode.

https://github.com/pulp/pulp_installer/blob/master/roles/pulp_common/tasks/install_pip.yml#L228

#7 Updated by mdepaulo@redhat.com about 1 month ago

What I suggest we do instead is to have a separate variable under pulp_install_plugins, and for pulpcore, like "vcs_url" / "pulp_vcs_url" . If defined, the plugin / pulpcore will be cloned to the "source_dir" / "pulp_source_dir", then installed.

This is mentioned as an implementation here: https://pulp.plan.io/issues/6547

In the meantime, we document/accept this as a limitation.

#8 Updated by mdepaulo@redhat.com about 1 month ago

  • Related to Task #6547: pulp_installer: Add variables for molecule prepare.yml to clone the branches added

#9 Updated by mdepaulo@redhat.com about 1 month ago

  • Assignee set to mdepaulo@redhat.com
  • Triaged changed from No to Yes
  • Sprint changed from Sprint 74 to Sprint 84
  • Tags Documentation added

#10 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 84 to Sprint 85

#11 Updated by rchan 16 days ago

  • Sprint changed from Sprint 85 to Sprint 86

Please register to edit this issue

Also available in: Atom PDF