[Pulp-list] errors with pulp-admin 2.8
Hello, We upgraded pulp to 2.8 from 2.7 and we have some problems with pulp-admin commands. We used puppet to do the upgrade. Login works: # pulp-admin login -u admin -p admin Successfully logged in. Session certificate will expire at Mar 24 07:41:24 2016 GMT. But listing taks, repos and looks like all other commands fail: # pulp-admin tasks list +--+ Tasks +--+ The specified user does not have permission to execute the given command This is the message from journald logs: Mar 17 03:45:49 v-so-repo-01.company.com pulp[7257]: pulp.server.webservices.middleware.exception:INFO: Authentication with username admin:admin:5591d3ef988df07c2cb1c519 failed: preauthenticated remote user is missing. Does anybody know what could be the problem? Thank you, Cristian Falcas ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] New Redmine Field: Target Platform Release
On 03/15/2016 04:53 PM, Sean Myers wrote: > I put together a quick "Next Release" query demonstrating the change in > action: https://pulp.plan.io/issues?query_id=59 On the suggestion of Brian Bouterse, I've renamed this report to be "2.8.1 - Next Bugfix Release". I also created a similar report for the next 'y' release, "2.9 - Next Feature Release". The plan with both reports is to update them as-needed to have the correct name and filtering to match the version number of our next y- and z-stream releases. Here are those links for your bookmarking pleasure: y-stream report - https://pulp.plan.io/issues?query_id=61 z-stream report - https://pulp.plan.io/issues?query_id=59 signature.asc Description: OpenPGP digital signature ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] /var/cache/pulp filling up?
On Wednesday, March 16, 2016 12:23:48 AM EDT Matthew Madey wrote: > I think it's failing to remove the files when they are done. Currently > there are 2G of RPM's in the cache directory, most of them are 0bytes. I'm > syncing with the RHEL7 repository, and I'm seeing every package in the > repository in the cache directory, however, once it had filled /var, the > remaining RPM files were 0 bytes. Is there a way to limit to how much > content is able to be staged in the cache directory before being published > to /var/lib/pulp? Hello again Matthew! I believe that the sync task downloads all the RPMs into /var/cache/ pulp and then moves them into /var/lib/pulp as a later step. Several of us developers want to redesign our plugin API to support stream processing, but in the meantime you will need enough storage in /var/ cache/pulp to support all the bytes for an entire sync. I don't know off the top of my head how large distro repos are, but I'd say they're usually on the scale of 10s of GBs. ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] /var/cache/pulp filling up?
This appears to be a regression in 2.7. In 2.6 (and earlier), at the completion of each rpm download, the file would be moved from its temporary location to the permanent location. That means for any given sync, you would never have more files in that temporary location than you did concurrent downloads. Using the default setting of 5 concurrent downloads, that's a maximum of 5 rpms. No problem so far. This change turned the "move" into a "copy": https://github.com/pulp/pulp_rpm/commit/de1895ede2f24731dcf6f52321beaee6b71c15a4 Now all of the rpm files pile up, and they don't get removed until the end of the task. On quick glance, it appears that 2.8 suffers the same problem, although the code has been refactored. If you don't mind filing a bug report, it should be an easy fix: likely just adding a delete call after the copy. https://pulp.plan.io/projects/pulp_rpm/issues/new Thanks, Michael On Thu, Mar 17, 2016 at 11:39 AM, Randy Barlow wrote: > On Wednesday, March 16, 2016 12:23:48 AM EDT Matthew Madey > wrote: > > I think it's failing to remove the files when they are done. Currently > > there are 2G of RPM's in the cache directory, most of them are > 0bytes. I'm > > syncing with the RHEL7 repository, and I'm seeing every package in > the > > repository in the cache directory, however, once it had filled /var, > the > > remaining RPM files were 0 bytes. Is there a way to limit to how > much > > content is able to be staged in the cache directory before being > published > > to /var/lib/pulp? > > Hello again Matthew! > > I believe that the sync task downloads all the RPMs into /var/cache/ > pulp and then moves them into /var/lib/pulp as a later step. Several of > us developers want to redesign our plugin API to support stream > processing, but in the meantime you will need enough storage in /var/ > cache/pulp to support all the bytes for an entire sync. I don't know off > the top of my head how large distro repos are, but I'd say they're > usually on the scale of 10s of GBs. > > ___ > Pulp-list mailing list > Pulp-list@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-list > ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] Pulp 2.8.0: "pulp-admin rpm repo search" with filters does not work as expected
> Given this inconsistency, this looks like a bug(?) Hello Simon! This is definitely a bug, would you mind reporting it in our ticket tracker? https://pulp.plan.io/projects/pulp/issues/new Thanks for letting us know! ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] errors with pulp-admin 2.8
This seams to be caused by this directive in apache: SSLUsername SSL_CLIENT_S_DN_CN This is the generate certificate by pulp-admin: # openssl x509 -text -in ~/.pulp/user-cert.pem -noout Certificate: Data: Version: 1 (0x0) Serial Number: 2495 (0x9bf) Signature Algorithm: sha1WithRSAEncryption Issuer: CN=v-so-repo-01.company.com, O=PULP Validity Not Before: Mar 17 08:35:33 2016 GMT Not After : Mar 24 08:35:33 2016 GMT Subject: CN=admin:admin:5591d3ef988df07c2cb1c519 Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (1024 bit) Modulus: 00:c1:78:fc:b6:7b:ef:d7:27:d0:ef:c4:4e:c4:24: 27:b2:98:98:d5:ae:88:d4:c0:60:ea:e9:c2:38:00: 06:04:91:d3:a6:c8:d1:92:75:f0:16:43:cb:d9:42: a6:80:8c:96:03:eb:d6:3f:e6:3d:0f:d3:ad:08:67: 5c:f0:7b:d7:0b:5e:d6:c9:6b:52:99:d9:d4:90:9f: 8b:3d:f0:6d:82:8d:a7:4e:d9:80:9b:0f:a5:e9:09: 1a:73:2c:6a:f1:eb:20:22:6d:22:25:47:74:1d:f3: 14:6e:f8:6a:47:7d:8c:e4:c8:81:f1:9b:c1:63:dc: 94:eb:e8:02:41:11:39:a6:bf Exponent: 65537 (0x10001) Signature Algorithm: sha1WithRSAEncryption 12:6c:61:9c:2f:b0:09:1b:3b:6e:a9:96:a7:03:d5:3c:02:a3: d1:c8:d1:b4:6c:4a:c6:6d:2b:8c:18:1f:8d:27:3a:7c:ff:6c: b6:87:83:f3:b0:bb:ff:16:b7:50:0e:7e:9d:04:87:c0:f6:0b: 0d:1f:38:d0:ae:1a:66:e5:3c:ef:55:44:ee:44:b1:ed:09:f0: 8d:f2:bd:b0:cd:31:6a:5c:ce:35:b3:fb:bf:8d:87:72:97:0b: fb:e6:e7:e1:f4:36:9d:06:08:28:b3:9a:15:6d:5c:1e:9f:27: 6e:6f:bd:ad:f9:23:0f:90:35:1a:76:c3:24:a6:4c:73:87:f8: 29:c1:2e:bb:1e:31:57:14:fc:07:2a:44:82:48:fd:22:20:e6: 9d:ac:5a:77:3c:5e:20:51:cb:1a:3b:ea:be:ae:73:46:61:c6: 6c:00:1a:ac:a9:a0:ea:97:1f:83:dd:95:c9:03:b9:b2:b6:b7: b3:d8:5d:47:cb:5e:72:35:3d:67:3c:4c:8a:bf:7e:86:4a:a9: 1f:2f:df:de:5e:a9:13:b0:72:f0:1c:20:32:df:a4:c1:c1:82: 0b:41:42:f9:44:e1:60:c1:20:1f:34:4b:1b:1d:3b:49:83:7e: ee:1f:ed:4b:9f:21:12:c5:b1:2b:c0:96:d0:77:b9:b5:6a:cc: On Thu, Mar 17, 2016 at 9:50 AM, Cristian Falcas wrote: > Hello, > > We upgraded pulp to 2.8 from 2.7 and we have some problems with pulp-admin > commands. We used puppet to do the upgrade. > > Login works: > > # pulp-admin login -u admin -p admin > Successfully logged in. Session certificate will expire at Mar 24 07:41:24 > 2016 > GMT. > > But listing taks, repos and looks like all other commands fail: > > # pulp-admin tasks list > +--+ > Tasks > +--+ > > The specified user does not have permission to execute the given command > > > This is the message from journald logs: > > Mar 17 03:45:49 v-so-repo-01.company.com pulp[7257]: > pulp.server.webservices.middleware.exception:INFO: Authentication with > username admin:admin:5591d3ef988df07c2cb1c519 failed: preauthenticated > remote user is missing. > > Does anybody know what could be the problem? > > Thank you, > Cristian Falcas > > ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list