Project

Profile

Help

Story #4651

As a user, I can install pulp 3 on a RHEL host

Added by kersom 6 months ago. Updated 10 days ago.

Status:
MODIFIED
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
No
Tags:
Pulp 3 installer
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 60

Description

As a user, I can install pulp 3 on a RHEL host using the Ansible installer.

The scope of this story is limited to using the ansible installer against a RHEL machine with the subscription already enabled.

This story does not include testing/CI. Covered here (https://pulp.plan.io/issues/4659)


Subtasks

Task #5557: Add ansible-pulp logic to add the RHEL7 optional repoMODIFIEDmdepaulo@redhat.com

Actions
Task #5558: Add ansible-pulp logic to grab epel-release from the internetMODIFIEDmdepaulo@redhat.com

Actions

Related issues

Related to RPM Support - Issue #5496: installer fails on el7 installing pulp_rpm ON_QA Actions
Blocks Pulp - Test #4659: Add RHEL to the ansible-pulp molecule CI NEW Actions

Associated revisions

Revision d65ab89b View on GitHub
Added by Mike DePaulo 10 days ago

Add CentOS -> RedHat vars symlinks

Fixes: #4651
As a user, I can install pulp 3 on a RHEL host
https://pulp.plan.io/issues/4651

Revision 01f740bd View on GitHub
Added by Mike DePaulo 10 days ago

Add CentOS -> RedHat vars symlinks

Fixes: #4651
As a user, I can install pulp 3 on a RHEL host
https://pulp.plan.io/issues/4651

Revision 391802c4 View on GitHub
Added by Mike DePaulo 9 days ago

Add CentOS -> RedHat vars symlinks

Fixes: #4651
As a user, I can install pulp 3 on a RHEL host
https://pulp.plan.io/issues/4651

History

#1 Updated by amacdona@redhat.com 6 months ago

  • Tracker changed from Issue to Story
  • % Done set to 0

#2 Updated by bmbouter 6 months ago

Since the installer works on CentOS I imagine it already works on RHEL. If the installer doesn't work for some reason that would be good to fix.

Since I believe it works I read this not as a Story but as a Test activity. Also how will we assure this stays working over time?

#3 Updated by amacdona@redhat.com 6 months ago

This isn't just a test activity. New OS vars files will be created in the ansible-pulp repo for RHEL that will be necessary even if installing by hand.

#4 Updated by amacdona@redhat.com 6 months ago

  • Description updated (diff)

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

  • Blocks Test #4659: Add RHEL to the ansible-pulp molecule CI added

#6 Updated by bmbouter 6 months ago

This rewrite looks good to me. Thanks!

#7 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

#8 Updated by kersom 3 months ago

I attempted to use the installer to install Pulp 3 on RHEL7.6 subscribed box.

TASK [pulp : Load OS specific variables] *****************************************************************************
fatal: [192.168.122.7]: FAILED! => changed=false 
  ansible_facts: {}
  ansible_included_var_files: []
  message: |-
    Could not find or access 'RedHat.yml'
    Searched in:
            /tmp/tmp.1eoSX7RspC/ansible-pulp/roles/pulp/vars/RedHat.yml
            /tmp/tmp.1eoSX7RspC/ansible-pulp/roles/pulp/RedHat.yml
            /tmp/tmp.1eoSX7RspC/ansible-pulp/roles/pulp-database/vars/RedHat.yml
            /tmp/tmp.1eoSX7RspC/ansible-pulp/roles/pulp-database/RedHat.yml
            /tmp/tmp.1eoSX7RspC/ansible-pulp/roles/pulp/tasks/vars/RedHat.yml
            /tmp/tmp.1eoSX7RspC/ansible-pulp/roles/pulp/tasks/RedHat.yml
            /tmp/tmp.1eoSX7RspC/vars/RedHat.yml
            /tmp/tmp.1eoSX7RspC/RedHat.yml on the Ansible Controller.
    If you are using a module and expect the file to exist on the remote, see the remote_src option

PLAY RECAP ***********************************************************************************************************
192.168.122.7              : ok=5    changed=0    unreachable=0    failed=1   

Same playbook was used to install Pulp 3 on a CentOS7 box.

#9 Updated by mdepaulo@redhat.com 2 months ago

  • Groomed changed from No to Yes
  • Sprint set to Sprint 57

#10 Updated by mdepaulo@redhat.com 2 months ago

Some tips:

1. Until we have a need for them to differ, RedHat.yml should be a symlink to CentOS.yml .
2. You'll have to use different logic to add epel, because epel-release is not in RHEL.

#11 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 57 to Sprint 58

#12 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 58 to Sprint 59

#13 Updated by rchan about 1 month ago

  • Assignee set to mdepaulo@redhat.com

#14 Updated by rchan about 1 month ago

For the RPM plugin, we will need createrepo_c 0.13.0+ , the most important functionality which we need there is a modular errata support. The motivation for this issue is to allow testing of the migration tool. We don't want to block testing of the tool for content types that are ready, so we can create a separate issue to handle RPM if necessary.

#15 Updated by daviddavis about 1 month ago

  • Status changed from NEW to ASSIGNED

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

rchan wrote:

For the RPM plugin, we will need createrepo_c 0.13.0+ , the most important functionality which we need there is a modular errata support. The motivation for this issue is to allow testing of the migration tool. We don't want to block testing of the tool for content types that are ready, so we can create a separate issue to handle RPM if necessary.

1. As we discussed on IRC, for RHEL7 they do not build the python3-createrepo_c subpackage of "createrepo_c". This is a packaging change for the overall "createrepo_c" source RPM.

2. RHEL8 & 8.1 beta have python3-createrepo_c, but only at 0.11.0-1 . So we need the the overall createrepo_c package upgraded on RHEL8 as well.

#17 Updated by mdepaulo@redhat.com 21 days ago

  • % Done changed from 0 to 70

As part of https://pulp.plan.io/issues/5496 , we managed to install the Pulp-maintained PyPI-hosted createrepo_c, and thus pulp_rpm, on CentOS 7.7 .

I will make 1 more change (add a variable for the RHEL7 extras repo, which will default to "rhel-7-server-extras-rpms" but can be set to blank or another value) for this PR.

#18 Updated by rchan 21 days ago

  • Sprint changed from Sprint 59 to Sprint 60

#19 Updated by kersom 18 days ago

  • Related to Issue #5496: installer fails on el7 installing pulp_rpm added

#20 Updated by mdepaulo@redhat.com 14 days ago

I realized that the only RHEL repo we need to enable now is actually optional, not extras, since we are not trying to get libmodulemd from RHEL.

There are several common names for that repo, and many possible ones if managed by Katello/Satellite or other custom repo management.

I am working on enabling a list of several common names; the 1st one found only. It is more complex than you'd expect (yum-config-manager is easy to make idempotent.) It also lets users specify a list, or a specific name, instead.
https://github.com/pulp/ansible-pulp/pull/172

Other remaining work:
  • Symlink/check CentOS vars yml files as RedHat ones.
  • Similar list logic for "epel-release" vs the epel URL (the URL is equivalent to a package name)

#21 Updated by Anonymous 10 days ago

  • Status changed from ASSIGNED to MODIFIED

Please register to edit this issue

Also available in: Atom PDF