mdepaulo@redhat.com
mdepaulo@redhat.com- Registered on: 02/25/2019
- Last connection: 07/29/2021
Issues
- Assigned issues: 25
- Reported issues: 283
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)
- 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
07/30/2021
-
I was mistaken, this was already fixed part of #8586 Issue #9182: pulp_installer should support replacing the RPM repo URLWhen a user specifies the 3rd party repo in `pulp_pkg_repo`, like "pulp_pkg_repo: https://yum.theforeman.org/pulpcore/3.11/el8/x86_64/`, changing the URL during a subsequent ansible run has no effect on the system.
If the user were to... -
Actually this is performed by #8586, even on the 3.7 branch.
Maybe I was confused by the fact that the molecule prepare.yml on that branch needed it. Issue #9180 (CLOSED - DUPLICATE): pulp-installer CI doesn't properly test upgrading RPM packagesThe task `pulp_common : Add pulpcore RPM repositories` doesn't replace the old repo URL when users specify a new one `pulp_pkg_repo`. This should be properly fixed, but this bug is written for a CI workaround.
The katello repo had "la...
07/29/2021
-
Issue #9182 (NEW): pulp_installer should support replacing the RPM repo URLWhen a user specifies the 3rd party repo in `pulp_pkg_repo`, like "pulp_pkg_repo: https://yum.theforeman.org/pulpcore/3.11/el8/x86_64/`, changing the URL during a subsequent ansible run has no effect on the system.
If the user were to... -
Issue #9181 (MODIFIED): pulp_installer 3.7 is failing to upgrade the dynaconf RPM with the external repopython3-dynaconf is an RPM that pulp_installer needs in packages mode.
The Foreman / Katello Project's pulpcore repos we (pulp_installer CI) test against used to have python3-dynaconf 3.0.0 rc1, but their pulpcore 3.7 RPM needs 3.0.0 ... -
Issue #9180 (CLOSED - DUPLICATE): pulp-installer CI doesn't properly test upgrading RPM packagesThe task `pulp_common : Add pulpcore RPM repositories` doesn't replace the old repo URL when users specify a new one `pulp_pkg_repo`. This should be properly fixed, but this bug is written for a CI workaround.
The katello repo had "la...
07/28/2021
-
Issue #9166 (MODIFIED): pulp fails to function when installed from RPMs on CentOS 8Observed on master branch, but assumed to affect 3.7 and 3.11 also.
This is caused by:
1. The pulpcore repo hosted by foreman has python3-tablib 3.0.0 and python3-markuppy.
2. The EPEL8 repo used to have python3-tablib 0.12.1, but n... -
> * https://github.com/pulp/pulp_installer/blob/master/roles/pulp_common/templates/requirements.in.j2
This is only supposed to be run for release installs, not source installs. And the git variables are for source installs (`source_d... Issue #9141: pulp/pulp_installer not honoring git_url and git_revision for pulp pluginsBased on the pulp-common roles documentation, one can specify git_url and git_revision when specifying a pulp plugin.
However this is not being honored as part of the installer process.
At least two places are lacking honoring that... -
* https://github.com/pulp/pulp_installer/blob/master/roles/pulp_common/templates/requirements.in.j2· Commented on issue
This is only supposed to be run for release installs, not source installs. And the git variables are for source installs (`source_di...
07/23/2021
-
Issue #9139 (MODIFIED): pulp_installer fails when symlinking webserver snippetsThis appears to be because our check_snippet.py script sometimes produces the following output:
"stdout_lines": ["/home/vagrant/devel/pulp_python/pulp_python/app/webserver_snippets/nginx.conf", "\u001b[0m"]
The 2nd line appears to be...
07/21/2021
-
For future reference, if we have trouble with this role's symlinks, the better solution would be to use wrappers scripts for the postgres binaries:
https://riptutorial.com/bash/example/19492/wrapper-script
We would then point the gee... Story #8154: As an EL7 pulp_installer user, I use a newer version of postgres than 9.6This has been discussed often, but with #8095 / FIPS compliance ([note 7](https://pulp.plan.io/issues/8095#note-7)), it may become more important.
We should change pulp_installer from using Postgres 9.6 on EL7 from the SCL, to either ...
Also available in: Atom
.