Re: [Pulp-list] goferd on consumers cannot connect to pulp server's queue after 2.7 -> 2.8 upgrade

Documentation is still proposing to remove pulp-server package. I suppose it should be fixed :) 2016-04-05 23:15 GMT+03:00 Jeff Ortel <jor...@redhat.com>: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > > On 04/05/2016 02:40 PM, Konstantin M. Khankin w

Re: [Pulp-list] Dependencies are broken after 2.8 release

; This will remove a number of pulp packages also. That's ok. Then do: > > $ sudo yum update > $ sudo yum groupinstall pulp-server-qpid > > > On Tue, Mar 22, 2016 at 10:05 PM, Konstantin M. Khankin < > khankin.konstan...@gmail.com> wrote: > >> Hi! >>

[Pulp-list] Dependencies are broken after 2.8 release

Hi! After Pulp 2,8 release dependencies got broken. This is what I see on Pulp server: file /usr/lib/python2.7/site-packages/semantic_version/__init__.py from install of python-semantic_version-2.4.2-1.el7.noarch conflicts with file from package python-semantic-version-2.2.0-3.el7.noarch ...

[Pulp-list] goferd on consumers cannot connect to pulp server's queue after 2.7 -> 2.8 upgrade

Hello! After 2.7->2.8 upgrade all consumers cannot talk to pulp server - goferd returns the next error on any operation: [WARNING][MainThread] pulp.agent.gofer.pulpplugin:107 - validate registration failed: (None, 'tlsv1 alert decrypt error', None) I didn't change any keys or configs. Logs also

Re: [Pulp-list] Updating pulp-consumer command on consumers

Hi Lutchy I ended up mirroring pulp-2-stable repo and adding it to all consumers. My pulp CA cert is broken now, so I cannot show how I did it, but it should not be harder then mirroring any other repo 2016-05-02 17:05 GMT+03:00 Lutchy Horace (Mailing List) <

[Pulp-list] Pulp + FreeIPA = ?

Hi! I'm trying to use FreeIPA PKI for pulp. I successfully installed all certificates/keys on consumers and set up httpd to use correct certificates/keys, but faced a problem - pulp wants to have CA superpowers to sign client certificates, even though config file and documentation both says that

Re: [Pulp-list] Pulp + FreeIPA = ?

reasons pulp is not able to generate a certificate. I've tried to restart all pulp processes and httpd multiple times already. Tried to disable SELinux (and enabled it back since it didn't change anything). Do you have any idea why this error could occur? Thanks! 2016-04-15 22:29 GMT+03:00 Konstantin M.

Re: [Pulp-list] Existing sync schedules do not work after 2.7 -> 2.8 upgrade

.com>: > Did this ever get resolved? If not, would you be willing to file a bug > with reproducer instructions in the bug tracker[0]. > > [0]: https://pulp.plan.io/ > > -Brian > > On 04/02/2016 04:42 PM, Konstantin M. Khankin wrote: > > Hello! > > >

Re: [Pulp-list] external authentication/authorization

You may try to use PAM to hook up authentication to any external source. This is how I connected it to FreeIPA: AuthType Basic AuthBasicProvider PAM AuthPAMService pulp AuthName "Pulp" Require valid-user # cat /etc/pam.d/pulp authrequired pam_sss.so account required

Re: [Pulp-list] issues with pulp 2.9 on centos

st files in /etc/httpd/conf.d/ > > > > Please let me know what you need I’ll be happy to provide. > > > > Thanks > > > > Jeff > > > > *From:* Konstantin M. Khankin [mailto:khankin.konstan...@gmail.com] > *Sent:* Thursday, September 29, 2016 12:12 AM

Re: [Pulp-list] Feedback needed: new user/auth system in 3.0

I use PAM auth, which is in turn authenticates login requests through FreeIPA. I don't create any roles other than admin though 2016-07-15 22:29 GMT+03:00 Michael Hrivnak : > As many of you know, we are switching from mongodb to postgres in Pulp > 3.0. This will come with

Re: [Pulp-list] Pulp CLI feedback

Hi David! My deployment is quite small (10-15 repos, rpm/python, ~20 clients), planning to also begin using puppet which is shipped with pulp-consumer anyway and looking at using Docker registry in future. - What commands or functionality in the CLI do you rely on the most? > rpm sync schedules

Re: [Pulp-list] docker cli 1.13.1 can't parse JSON returned by pulp+crane

Hi Ina, Great, thank you very much :) пн, 13 авг. 2018 г. в 13:16, Ina Panova : > Hi Konstantin, > > after some investigation and collaboration with skopeo project, we managed > to track down the root cause. > The issue is filled [0] and a PR is on its way already. > Fix will go into next

[Pulp-list] docker cli 1.13.1 can't parse JSON returned by pulp+crane

Hi! I'm using docker 1.13.1 on CentOS 7.5 on the server named 'front'. On another server named 'hive' I have docker API compatible registry based on pulp 2.16.3 + crane 3.2.0, running on CentOS 7.5. I created custom pulp-docker repository named 'gsk/centos7', dumped custom image from docker

Re: [Pulp-list] Can't import containers created with Buildah

Thank you, https://pulp.plan.io/issues/4095 filed (why didn't I wait a bit to get 4096...) ср, 24 окт. 2018 г. в 15:35, Austin Macdonald : > The other projects are sometimes hidden. > https://pulp.plan.io/projects/pulp_docker > > On Wed, Oct 24, 2018 at 2:55 AM Konstanti

Re: [Pulp-list] Can't import containers created with Buildah

Dennis, Which project I should use? I don't see a separate project for pulp_docker. Thanks! вт, 23 окт. 2018 г. в 23:58, Dennis Kliban : > Konstantin, > > Could you please file an issue in pulp.plan.io? > > Thanks, > Dennis > > On Sat, Oct 20, 2018 at 5:40

[Pulp-list] Can't import containers created with Buildah

Hi! I tried the tool Buildah ( https://www.projectatomic.io/blog/2017/06/introducing-buildah/) to build containers without having docker binary. Containers are built (not sure if they work), but I can't upload them to the pulp repo: 1) I copy container from "container-storage:" to "dir:", then

Re: [Pulp-list] Can't import containers created with Buildah

sha256:c17d63d23edcbe46b14fbe531e2e9b4411483947669087e90bdba3372eb2684d', 'mediaType': 'application/vnd.docker.container.image.v1+json', 'size': 1217}, 'layers': [{'digest': 'sha256:f972d139738dfcd1519fd2461815651336ee25a8b54c358834c50af094bb262f', 'mediaType': 'appli

[Pulp-list] "Plugin "pulp-profile-update" can't be imported" at 2.20.0

Hi! I've upgraded my clients to 2.20.0 and now each of them reports "Plugin "pulp-profile-update" can't be imported" on any yum operation. I took one client which was not updated and didn't have this issue and ran "yum update": # yum upgrade *Loaded plugins: fastestmirror, pulp-profile-update,

Re: [Pulp-list] "Plugin "pulp-profile-update" can't be imported" at 2.20.0

, +proxy_host=proxy_host, +proxy_port=proxy_port) Bindings.__init__(self, connection) Tried to uncomment proxy_port and proxy_host in the config but it didn't help. I also tried to remove .pyc and .pyo, but no effect. вс, 14 июл. 2019 г. в 23:54, Konstantin M. Khankin

Re: [Pulp-list] "Plugin "pulp-profile-update" can't be imported" at 2.20.0

ulp-server "PULP_VERSION = pkg_resources.require('pulp-server')[0].version" was introduced in https://github.com/pulp/pulp/commit/19a527036d4e1b3ed06037ada70a5de5cd556940 and was released with 2.20.0. I checked 2.19.1 RPM does not include this line. Obviously client side will not have pu

Re: [Pulp-list] "Plugin "pulp-profile-update" can't be imported" at 2.20.0

ues/5126 >> >> On Mon, Jul 15, 2019 at 10:05 AM Dennis Kliban >> wrote: >> >>> Please file an issue at https://pulp.plan.io/issues/new/. This is >>> definitely a regression. >>> >>> On Mon, Jul 15, 2019 at 4:47 AM Konstantin M. Khank

Re: [Pulp-list] Can't import containers created with Buildah

'mediaType': 'application/vnd.docker.image.rootfs.diff.tar.gzip', 'size': 39936}], 'mediaType': 'application/vnd.docker.distribution.manifest.v2+json', 'schemaVersion': 2} ср, 24 окт. 2018 г. в 16:05, Konstantin M. Khankin < khankin.konstan...@gmail.com>: > Thank you, https://pulp.

Re: [Pulp-list] Can't import containers created with Buildah

fix the upload issue > https://github.com/pulp/pulp_docker/pull/418 > > > > Regards, > > Ina Panova > Senior Software Engineer| Pulp| Red Hat Inc. > > "Do not go where the path may lead, > go instead where there is no path and leave a trail." &g

Re: [Pulp-list] [Pulp-dev] Pulp 3 CLI MVP

Is it an option to keep the Pulp 2 CLI syntax as much as possible? чт, 7 мая 2020 г. в 15:28, Dennis Kliban : > On Thu, May 7, 2020 at 7:13 AM Tatiana Tereshchenko > wrote: > >> +1 to `pulp` command. >> >> I think for me as a user, the most logical would be to have a plugin name >> first and

Re: [Pulp-list] Can't get CentOS 7 Updates repo published

> repository will be usable. > > [0] https://pulp.plan.io/issues/2019#note-2 > > On Mon, Aug 31, 2020 at 4:10 PM Konstantin M. Khankin < > khankin.konstan...@gmail.com> wrote: > >> # rpm -qa | grep pulp | sort >> pulp-admin-client-2.21.3-1.el7.noarch >> pulp-a

Re: [Pulp-list] Can't get CentOS 7 Updates repo published

oks exactly like the issue that was reported here[0]. > > What version of pulp are you using? What version of createrepo_c is > installed? > > [0] https://pulp.plan.io/issues/2019 > > On Mon, Aug 31, 2020 at 3:16 PM Konstantin M. Khankin < > khankin.konstan...@gmail.com>

Re: [Pulp-list] Can't get CentOS 7 Updates repo published

Hi! The issue still persists. Could someone take a look please? Thanks! ср, 19 авг. 2020 г., 13:15 Konstantin M. Khankin < khankin.konstan...@gmail.com>: > Hi! > > I found that my pulp2-managed mirror of > http://mirror.yandex.ru/centos/7/updates/x86_64 has not been succes

Re: [Pulp-list] Can't get CentOS 7 Updates repo published

a web browser. I > believe that users are still able to browse the repository without it, but > in that case the HTML listing of directories is generated by the web server > each time a user requests it. > > On Tue, Sep 1, 2020 at 4:53 AM Konstantin M. Khankin < > khankin.konst

[Pulp-list] Can't get CentOS 7 Updates repo published

Hi! I found that my pulp2-managed mirror of http://mirror.yandex.ru/centos/7/updates/x86_64 has not been successfully published since April 30. I ran publish manually and received an error: ''' Generating sqlite files [/] ... failed Error occurred during 'sqliterepo_c' execution: Preparing

Re: [Pulp-list] Can't get CentOS 7 Updates repo published

p_rpm/blob/2-master/plugins/pulp_rpm/plugins/db/models.py#L1064 > > On Fri, Oct 2, 2020 at 3:27 AM Konstantin M. Khankin < > khankin.konstan...@gmail.com> wrote: > >> Sorry for reviving this thread but I think I found something. >> >> Today I tried to install CentOS

Re: [Pulp-list] Can't reinstate a replica from scratch after it was off for 6 months

I'm sorry for spam. It's so hard to choose the right mailing list when it's night already. вс, 9 авг. 2020 г., 01:11 Konstantin M. Khankin < khankin.konstan...@gmail.com>: > Hi! > > I run IPA on CentOS 7. I have two servers (Leader and Replica, though they > changed roles co

[Pulp-list] Can't reinstate a replica from scratch after it was off for 6 months

Hi! I run IPA on CentOS 7. I have two servers (Leader and Replica, though they changed roles couple times because of reinstalls), had ca and domain services on both of them, replication set up and working. I had to switch off Replica for 6 months. When I turned it on recently, I found expired

Re: [Pulp-list] Pulp2 2.21.4-2 [RELEASED]

Looks like there is one more place where client relies on libraries available only in the server package: goferd: [ERROR][worker-0] pulp.agent.lib.container:290 - handler "bind", import failed goferd: [ERROR][worker-0] pulp.agent.lib.container:290 - Traceback (most recent call last):

[Pulp-list] "Plugin "pulp-profile-update" can't be imported" at 2.21.4

Hi! This report is very similar to the one in https://pulp.plan.io/issues/5126 or mail thread https://www.redhat.com/archives/pulp-list/2019-July/msg00021.html, the only difference is I get this error with the latest Pulp update 2.21.4: # rpm -qa | grep pulp

[Pulp-list] Custom list of CA certificates for pulp-cli

Hello! Today I got unpleasantly surprised about the inability to change the list of CA certificates pulp-cli uses to verify SSL connections. Pulp-cli uses the requests library, so I expected to be able to just specify REQUESTS_CA_BUNDLE envvar and be happy. However, this did not work. So I added

Re: [Pulp-list] Custom list of CA certificates for pulp-cli

Yes, it works. Thank you! пт, 26 нояб. 2021 г. в 20:59, Matthias Dellweg : > Can you please verify that this change solves your problem: > https://github.com/pulp/pulp-cli/pull/434 > > Thank you! > > On Fri, Nov 26, 2021 at 6:09 PM Konstantin M. Khankin > wrote: > >

Re: [Pulp-list] Can't build PEX out of pulp-cli because of missing dependency

> > Matthias > > On Wed, Dec 15, 2021 at 11:56 AM Konstantin M. Khankin > wrote: > > > > Validated PEX build fails because of missing dependency with this > workaround: > > > > $ echo setuptools > pulp_cli.req > > $ pex -r pulp_cli.req -v -c pulp

[Pulp-list] Can't build PEX out of pulp-cli because of missing dependency

Hello! I wanted to make pulp-cli portable and build PEX archive out of it but the latest pex (2.1.56) fails to do so: ``` $ pex -v -c pulp 'pulp-cli[pygments]' ... Running PEX file at /tmp/tmpdy35exye with args [] pex: PEX.run invoking /home/hc/pex/bin/python3 -s -E /tmp/tmpdy35exye pex: