mdepaulo@redhat.com - Pulp

mdepaulo@redhat.com

Registered on: 02/25/2019
Last connection: 10/19/2020

Issues

Assigned issues: 42
Reported issues: 236

Projects

Pulp (Developer, Private Access, Contributor, 02/25/2019)
RPM Support (Developer, Private Access, Contributor, 02/25/2019)
Puppet Support (Developer, Private Access, Contributor, 02/25/2019)
Docker Support (Developer, Private Access, Contributor, 02/25/2019)
Python Support (Developer, Private Access, Contributor, 02/25/2019)
Packaging (Developer, Private Access, Contributor, 02/25/2019)
Crane (Developer, Private Access, Contributor, 02/25/2019)
OSTree Support (Developer, Private Access, Contributor, 02/25/2019)
Debian Support (Developer, Private Access, Contributor, 02/25/2019)
Nectar (Developer, Private Access, Contributor, 02/25/2019)
File Support (Developer, Private Access, Contributor, 02/25/2019)
Infrastructure (Developer, 02/25/2019)
Ansible Plugin (Developer, Contributor, 02/25/2019)
Maven Plugin (Developer, 09/18/2019)
Pulp CLI (Developer, Contributor, 05/07/2020)
CertGuard (Developer, Contributor, 04/06/2020)
Container Support (Developer, Private Access, Contributor, 12/06/2019)
NPM Plugin (Developer, Contributor, 05/11/2020)
Migration Plugin (Developer, Private Access, Contributor, 01/14/2020)

Activity

10/21/2020

mdepaulo@redhat.com Pulp
08:40 PM · Commented on issue

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 in... Issue #6696: pulp_installer fails to run "Collect static content" task when pulp_source_dir is set
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...

10/20/2020

mdepaulo@redhat.com Pulp
09:20 PM · Closed issue

Closing as the combined fix is part of the RPM packaging, and the pulpcore-selinux policy releases 1.1.3 / 1.1.2 . Issue #7663 (CLOSED - CURRENTRELEASE): SELinux policies not being applied when using RPM based installation
As a user I am deploying pulpcore using the pulp_installer (3.7.1) and the upstream packages located at https://yum.theforeman.org/pulpcore/3.7/el7/x86_64/
After installation the services are started as `unconfined_service_t` rather t...
mdepaulo@redhat.com Pulp
05:56 PM · Closed issue

Released in 3.6.0 Story #7098 (CLOSED - CURRENTRELEASE): pulp_installer needs to install keys for token authentication as needed by pulp_container
Users should be able to provide their existing keys or have new keys generated by the installer.
mdepaulo@redhat.com Pulp
05:53 PM · Closed issue

Issue #7328 (CLOSED - CURRENTRELEASE): pulp_installer and ssl docs disagree
pulp_installer is generating SSL certs under /etc/pulp, but the SSL docs[1] say:
> The default location for the CA certificate is /etc/pulp/certs/root.crt. The default location for the SSL certificate is /etc/pulp/certs/pulp_webserver...
mdepaulo@redhat.com Released in pulp_installer 3.6.0-1 .
05:53 PM · Commented on issue

10/19/2020

mdepaulo@redhat.com Pulp
05:01 PM · Commented on issue

spredzy wrote:
> Current SELinux policy (pulp/pulpcore-selinux) is missing some rules
>
>
> -> SELinux is preventing /usr/libexec/platform-python3.6 from read access on the file stat
>
> ~~~ text
> kernel_getattr_proc(pulpcore_... Story #7043: As a user, I have pulp_installer compile and install the pulpcore-selinux policy
## Overview
On Red Hat systems, Pulp installer needs to clone pulpcore-selinux repository[0], compile the policy inside of it, and install the policy, label all the ports used by pulp services[1].
[0] https://github.com/pulp/pulpco...
mdepaulo@redhat.com Pulp
04:59 PM · Closed issue

This was implemented in pulpcore-selinux 1.1.0:
https://github.com/pulp/pulpcore-selinux/tags
It addresses "install from RPM" mode, which the reporter was using. That mode by default installs `pulpcore-selinux` as an RPM package. So ... Story #7075 (CLOSED - CURRENTRELEASE): As a user I want Pulp to run on EL8 with SELinux enforced
As a user I want to be able to deploy Pulp on a vanilla CentOS8/RHEL8 box with SELinux enforced and things should just work. TM.

10/08/2020

mdepaulo@redhat.com Pulp
05:39 PM · Closed issue

OBE - we haven't had a need for this yet due to reduced branching in pulp_installer and pulp_rpm_prerequisites being merged into pulp_installer. So let's remove it from our backlog. Task #6557 (CLOSED - WONTFIX): Add "Required PR" support for pulpcore & plugins to pulp_installer
It should be added to pulp_installer.git/molecule/prepare.yml , which git clones the repos withhin the molecule VM-like container.
This was not part of the original scope of the parent task, but it will be necessary at some point.
mdepaulo@redhat.com Pulp
05:06 PM · Closed issue

OBE - scope reduced due to pulp_rpm_prerequisites being part of pulp_installer now, and not badly needed at this time as we have yet to seriously rely on pulp_installer branching. Task #6552 (CLOSED - WONTFIX): pulp_installer CI: Create docs or scripts to help maintain which branches & tests get used
Since the branches used will be controlled by variables in files that get modified, these need to be made easy enough to maintain.

10/07/2020

mdepaulo@redhat.com Pulp
09:10 PM · Commented on issue

Per our IRC convo, I'm letting the updated packages get released. I just reviewed:
https://github.com/theforeman/pulpcore-packaging/pull/38 Issue #7663: SELinux policies not being applied when using RPM based installation
As a user I am deploying pulpcore using the pulp_installer (3.7.1) and the upstream packages located at https://yum.theforeman.org/pulpcore/3.7/el7/x86_64/
After installation the services are started as `unconfined_service_t` rather t...

Also available in: Atom