mdepaulo@redhat.com
- Login: mdepaulo@redhat.com
- Registered on: 02/25/2019
- Last connection: 02/10/2022
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 18 | 194 | 212 |
| Reported issues | 27 | 263 | 290 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Ansible Plugin | Developer, Contributor | 02/25/2019 |
| CertGuard | Developer, Contributor | 04/06/2020 |
| Container Support | Developer, Private Access, Contributor | 12/06/2019 |
| Crane | Developer, Private Access, Contributor | 02/25/2019 |
| Debian Support | Developer, Private Access, Contributor | 02/25/2019 |
| Docker Support | Developer, Private Access, Contributor | 02/25/2019 |
| File Support | Developer, Private Access, Contributor | 02/25/2019 |
| Infrastructure | Developer | 02/25/2019 |
| Maven Plugin | Developer | 09/18/2019 |
| Migration Plugin | Developer, Private Access, Contributor | 01/14/2020 |
| Nectar | Developer, Private Access, Contributor | 02/25/2019 |
| NPM Plugin | Developer, Contributor | 05/11/2020 |
| OSTree Support | Developer, Private Access, Contributor | 02/25/2019 |
| Packaging | Developer, Private Access, Contributor | 02/25/2019 |
| Pulp | Developer, Private Access, Contributor | 02/25/2019 |
| Puppet Support | Developer, Private Access, Contributor | 02/25/2019 |
| Python Support | Developer, Private Access, Contributor | 02/25/2019 |
| RPM Support | Developer, Private Access, Contributor | 02/25/2019 |
Activity
10/13/2021
-
Issue #9232 (CLOSED - NOTABUG): pulp.pulp_installer.pulp : Run pip-compile to check pulpcore/plugin compatibilityWhen running the Ansible installer, I receive an error message in 'pulp.pulp_installer.pulp : Run pip-compile to check pulpcore/plugin compatibility'.
fatal: [c7-pulp1]: FAILED! => {"changed": false, "cmd": ["/usr/local/lib/pulp/bin/p... -
@jcreek, feel free to reopen this when you have the information.· Closed issue
09/29/2021
-
I think this is a regression from:
https://github.com/pulp/pulp_installer/pull/767
https://pulp.plan.io/issues/7006
ppicka reports he hasn't run into though on his latest box.
fao89 would be ideal to work on this since he imp... Issue #9460: pulp3-source-fedora34 can't start pulp with pstart/pstop or with `sudo systemctl restart pulpcore`1. I am using HEAD from pulp_installer, i.e. commit 66239334.
2. I vagrant up with `vagrant up pulp3-source-fedora34`
3. I then enter the virtualenv with `workon pulp`.
4. I observe that `pstop` and `pstop` don't work
```
$ pstop
... -
Hi @jcreek
See the requested info in:
https://pulp.plan.io/issues/9232#note-1 Issue #9232: pulp.pulp_installer.pulp : Run pip-compile to check pulpcore/plugin compatibilityWhen running the Ansible installer, I receive an error message in 'pulp.pulp_installer.pulp : Run pip-compile to check pulpcore/plugin compatibility'.
fatal: [c7-pulp1]: FAILED! => {"changed": false, "cmd": ["/usr/local/lib/pulp/bin/p... -
I will look into this as I look into CI performance improvements. Task #9005: pulp_installer's molecule CI should not always connect as rootThis seems to be a product of, or the default configuration of, the docker plugin for molecule. (molecule uses `docker exec` to talk to the container, not SSH.)
We should look into performance options as we solve this. Even if it mean... -
I'll double check with the bug reporters after I fix other open SELinux issues (see filter for SELinux tag.) Issue #8916: Pulp installer hanging on "Ensure Pulp is up and healthy"I tried to install pulp via the pulp installer v3.13.0 (ansible playbooks) in a fresh vagrant environment running CentOS Stream 8 but the install hangs on:
TASK [pulp_health_check : Ensure Pulp is up and healthy] *********************... -
Story #9470 (MODIFIED): As a Pulp 2 user, I can run Pulp 3's pulp-2to3-migration with SELinux enabledThe Pulp 2 SELinux policy, existing under pulp repo's "server/selinux/server/", needs support for the pulp-2to3-migration being run from Pulp 3 against Pulp 2.
Specifically, read access to rhsm config files.
See parent for more in... -
09/17/2021
-
After [much research](https://alesnosek.com/blog/2016/12/04/controlling-a-multi-service-application-with-systemd/), we need these 2 lines in each of our regular services:
```
# When systemd stops or restarts the meta pulpcore.service, ... Story #7006: As a user, I can use a single systemd service to restart PulpAfter https://pulp.plan.io/issues/7005 is implemented, we should create a single meta service "pulpcore".
It will help with SOA because "pulpcore" will refer to all the pulp services installed on a system, whichever ones they may be.
...
08/25/2021
Also available in: Atom
.