Re: [Pulp-list] [Pulp-dev] Pulp 3 CLI PoC Feedback

2020-10-05 Thread David Davis
Good question. I think the short/easy answer is to edit this line of code
and set default=False:

https://github.com/pulp/pulp-cli/blob/e913ca808e324f1dbfd51907450394dab4a935cc/pulpcore/cli/common.py#L54

Alternatively, the CLI uses requests and per the requests docs[0] I think
you can specify which trusted CA bundle to use:

*This list of trusted CAs can also be specified through the
REQUESTS_CA_BUNDLE environment variable. If REQUESTS_CA_BUNDLE is not set,
CURL_CA_BUNDLE will be used as fallback.*

I think we'll need to figure how to handle this so I filed an issue[1].

[0]
https://requests.readthedocs.io/en/master/user/advanced/#ssl-cert-verification
[1] https://pulp.plan.io/issues/7652

David


On Mon, Oct 5, 2020 at 9:18 AM Brian Bouterse  wrote:

> I'm excited to use this. I went to try it, but the CLI's requests wouldn't
> trust the server which uses self-signed certificates. When running `pulp
> status` I get this error:
>
> requests.exceptions.SSLError: HTTPSConnectionPool(host='localhost',
> port=443): Max retries exceeded with url: /pulp/api/v3/docs/api.json
> (Caused by SSLError(SSLCertVerificationError(1, '[SSL:
> CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local
> issuer certificate (_ssl.c:1123)'))
>
> Let me know if I should file this somewhere more specifically.
>
> On Mon, Oct 5, 2020 at 5:08 AM Melanie Corr  wrote:
>
>> Hi all,
>>
>> An initial Pulp 3 CLI PoC is now available. We are hoping to gather as
>> much feedback as possible from the Pulp community so that future
>> development can progress with your opinions and requirements in mind.
>>
>> The following blog post has instructions on how to download and install
>> the Pulp 3 CLI PoC, as well as a demo and a feedback link. Please test out
>> the Pulp 3 CLI PoC and let us know your thoughts. We will have some SWAG
>> for participants :)
>>
>> https://pulpproject.org/2020/09/28/pulp-3-cli-poc-call-for-feedback/
>>
>> If you've any questions or comments, feel free to ask.
>>
>> Melanie
>>
>> --
>>
>> Melanie Corr, RHCE
>>
>> Community Manager
>>
>> Red Hat 
>>
>> Remote, Ireland
>>
>> mc...@redhat.com
>> M: +353857774436 IM: mcorr
>> 
>>
>> ___
>> Pulp-dev mailing list
>> pulp-...@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
> ___
> 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

[Pulp-list] Dropping fedora builds of Pulp2

2020-10-05 Thread Ina Panova
Hi Folks,

Pulp 2.19 was the last release having Fedora 28 packages.
Our release machinery kept building packages even after Fedora 28 went EOL-
this is confusing that's why we want to remove 2.20 and 2.21 Fedora 28
repositories [0].

We will continue building Pulp2 packages for RHEL7.

Please, provide feedback by October 12. Repositories are going to be
removed on that day, if no concerns are raised.

Thanks!

[0] https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.21/
https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.20/

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."
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] [Pulp-dev] Pulp 3 CLI PoC Feedback

2020-10-05 Thread Brian Bouterse
I'm excited to use this. I went to try it, but the CLI's requests wouldn't
trust the server which uses self-signed certificates. When running `pulp
status` I get this error:

requests.exceptions.SSLError: HTTPSConnectionPool(host='localhost',
port=443): Max retries exceeded with url: /pulp/api/v3/docs/api.json
(Caused by SSLError(SSLCertVerificationError(1, '[SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local
issuer certificate (_ssl.c:1123)'))

Let me know if I should file this somewhere more specifically.

On Mon, Oct 5, 2020 at 5:08 AM Melanie Corr  wrote:

> Hi all,
>
> An initial Pulp 3 CLI PoC is now available. We are hoping to gather as
> much feedback as possible from the Pulp community so that future
> development can progress with your opinions and requirements in mind.
>
> The following blog post has instructions on how to download and install
> the Pulp 3 CLI PoC, as well as a demo and a feedback link. Please test out
> the Pulp 3 CLI PoC and let us know your thoughts. We will have some SWAG
> for participants :)
>
> https://pulpproject.org/2020/09/28/pulp-3-cli-poc-call-for-feedback/
>
> If you've any questions or comments, feel free to ask.
>
> Melanie
>
> --
>
> Melanie Corr, RHCE
>
> Community Manager
>
> Red Hat 
>
> Remote, Ireland
>
> mc...@redhat.com
> M: +353857774436 IM: mcorr
> 
>
> ___
> Pulp-dev mailing list
> pulp-...@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 3 CLI PoC Feedback

2020-10-05 Thread Melanie Corr
Hi all,

An initial Pulp 3 CLI PoC is now available. We are hoping to gather as much
feedback as possible from the Pulp community so that future development can
progress with your opinions and requirements in mind.

The following blog post has instructions on how to download and install the
Pulp 3 CLI PoC, as well as a demo and a feedback link. Please test out the
Pulp 3 CLI PoC and let us know your thoughts. We will have some SWAG for
participants :)

https://pulpproject.org/2020/09/28/pulp-3-cli-poc-call-for-feedback/

If you've any questions or comments, feel free to ask.

Melanie

-- 

Melanie Corr, RHCE

Community Manager

Red Hat 

Remote, Ireland

mc...@redhat.com
M: +353857774436 IM: mcorr

___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

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

2020-10-05 Thread Tatiana Tereshchenko
Hi Konstantin,

Do you know if it's one or many RPMs which are affected?
If it's one or few, I think you need to identify which repositories they
are in and remove them from those repositories.
The goal is to make those RPMs an orphan content.
Then you can run orphan cleanup which will remove those RPMs from pulp
entirely. Then sync (with --force-full) all the affected repositories, it
should bring those RPMs back. If in some repositories those RPMs were
copied, you'd need to copy them again.

It's very error-prone and not straightforward to try to fix it directly in
the db, I'd discourage doing that.

Tanya


On Sat, Oct 3, 2020 at 7:57 AM Konstantin M. Khankin <
khankin.konstan...@gmail.com> wrote:

> Thanks for the info Dennis!
>
> I tried 'rpm repo sync sun --force-full' but it didn't help to clear the
> corrupted entry. How can I drop this on the server side? Should I just
> directly edit an entry in mongodb?
>
> пт, 2 окт. 2020 г. в 14:39, Dennis Kliban :
>
>> Filelists are stored in the database in a compressed form[0]. During
>> publishing of metadata, each fillist is decompressed before being written
>> to a file[1]. It's hard to speculate when data corruption occurred. It's
>> possible that the data was corrupted in the remote repository the first
>> time that this RPM was downloaded. That metadata could have been fixed
>> since then, but Pulp thinks it already has the information and is not
>> trying to re-download.
>>
>> [0]
>> https://github.com/pulp/pulp_rpm/blob/2-master/plugins/pulp_rpm/plugins/db/models.py#L1051
>> [1]
>> https://github.com/pulp/pulp_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 7 and got an error:
>>> "TypeError: Parsing filelists.xml error: expected '>'"
>>>
>>> So I did this:
>>>
>>> >>> import xml.etree.ElementTree as ET
>>> >>> tree =
>>> ET.parse('/mnt/sysimage/var/tmp/yum.cache/centos_updates/gen/filelists.xml')
>>> ...
>>>   File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1506, in
>>> _raiseerror
>>> raise err
>>> xml.etree.ElementTree.ParseError: not well-formed (invalid token): line
>>> 1884123, column 136
>>>
>>> I opened filelists.xml and found that line 1884123 is indeed corrupt and
>>> looks like this:
>>>
>>> /usr/share/javadoc/java-1.8.0-openjdk-1.8.0.111-1.b15.el7_2-debug/api/javax/sql/rowset/serial/compact3-package-frame.html>>   !,^@ 0
>>> 480!share/javadoc/java-1.8.0-openjdk-1.8.0.111-1.b15.el7_2-debug/api/javax/sql/rowset/serial/compact3-package-summary.html
>>>
>>> I verified another consumer has exactly the same issue with this file.
>>>
>>> Do I understand correctly Pulp generates filelists.xml? If so, can it be
>>> because of a bug in Pulp or should I look for a silent data corruption
>>> issue on my pulp server?
>>>
>>> Thanks!
>>>
>>>
>>> вт, 1 сент. 2020 г. в 17:14, Dennis Kliban :
>>>
 The repoview feature requires the sqlite db to be generated. This
 feature generates HTML pages for browsing the repository in 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.konstan...@gmail.com> wrote:

> Thank you, that obviously helped. Still would be useful to know the
> root cause.
>
> OTOH, if sqlite creation functionality is not that critical - why
> would we ever enable something which only consumes time during sync for no
> benefit?
>
> вт, 1 сент. 2020 г. в 00:26, Dennis Kliban :
>
>> Looks like everything is up to date. I have no idea what the root
>> cause is, but according to this comment[0], you can work around the 
>> problem
>> by disabling the generation of sqlite db. I am not sure what the exact
>> effect of this will be for the clients that are consuming this content, 
>> but
>> the 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-agent-2.21.3-1.el7.noarch
>>> pulp-consumer-client-2.21.3-1.el7.noarch
>>> pulp-deb-admin-extensions-1.10.1-1.el7.noarch
>>> pulp-deb-plugins-1.10.1-1.el7.noarch
>>> pulp-docker-admin-extensions-3.2.6-1.el7.noarch
>>> pulp-docker-plugins-3.2.6-1.el7.noarch
>>> pulp-puppet-consumer-extensions-2.21.3-1.el7.noarch
>>> pulp-puppet-handlers-2.21.3-1.el7.noarch
>>> pulp-python-admin-extensions-2.0.4-1.el7.noarch
>>> pulp-python-plugins-2.0.4-1.el7.noarch
>>> pulp-rpm-admin-extensions-2.