[Pulp-list] Pulp - Upgrade Centos 7.7 to 8

[Sathasivam, Pradeep]

Hi All,

Is there any way by which I can upgrade from CentOS version 7.7 to 8 using pulp?

Regards.
Pradeep. S

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

Re: [Pulp-list] Content Signing for Pulp 3.y -- Use Cases

[Dennis Kliban]

Thank you everyone who participated in the discussion earlier today. I have
moved the content to a google doc[0]. You can find the summary of today's
discussion below the use cases. The full log of the discussion is here[1].

I would like to continue the discussion at 9 AM EST (in your time zone
)
on Thursday, December 5, 2019 in #pulp-meeting on IRC. Your

[0]
https://docs.google.com/document/d/1HSrRduFYuidhbc8ISjUnkb3IXk6FnJ2iXEqa4vDC-pA/edit#
[1]
https://pulpadmin.fedorapeople.org/triage/pulp-dev/2019/pulp-dev.2019-11-26-14.30.log.html

On Thu, Nov 21, 2019 at 8:27 AM Dennis Kliban  wrote:

> On Thu, Nov 21, 2019 at 7:59 AM Dennis Kliban  wrote:
>
>> I will be hosting a chat meeting to discuss use cases for signing in Pulp
>> 3.y.
>> The meeting details and agenda link are below. Both users and plugin
>> developers are invited. Please join if you're interested!
>>
>> When: Wednesday, November 26 9:30 – 10:30am EST or in your time zone
>> 
>> .
>>
>
> Correction: this will take place on Tuesday. The link is correct.
>
>
>> Where: #pulp-dev on freenode
>> Agenda: https://etherpad.net/p/Pulp_-_Signing_Use_Cases
>>
>> Questions and feedback are also welcome ahead of time.
>>
>> Thanks!
>>
>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] pulp3 rc8 ssl_client_key

[Dennis Kliban]

You are right. We fixed this issue in the source code[0]. The fix will be
available in RC 9 that will ship next week.


[0] https://pulp.plan.io/issues/5770

On Tue, Nov 26, 2019 at 1:20 PM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:

> It looks rc8 is still looking from ssl_client_key attribute to sync the
> remote.
>
> I got the following error:
>
> "description": "'RpmRemote' object has no attribute 'ssl_client_key'",
> "traceback": " File
> \"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/rq/worker.py\",
> line 822, in perform_job\n rv = job.perform()\n File
> \"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/rq/job.py\",
> line 605, in perform\n self._result = self._execute()\n File
> \"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/rq/job.py\",
> line 611, in _execute\n return self.func(*self.args, **self.kwargs)\n File
> \"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
> line 122, in synchronize\n treeinfo = get_treeinfo_data(remote)\n File
> \"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/pulp_rpm/app/kickstart/treeinfo.py\",
> line 19, in get_treeinfo_data\n downloader =
> remote.get_downloader(url=urljoin(remote_url, namespace))\n File
> \"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/pulpcore/app/models/repository.py\",
> line 261, in get_downloader\n return self.download_factory.build(url,
> **kwargs)\n File
> \"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/pulpcore/app/models/repository.py\",
> line 219, in download_factory\n self._download_factory =
> DownloaderFactory(self)\n File
> \"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/pulpcore/download/factory.py\",
> line 68, in __init__\n self._session =
> self._make_aiohttp_session_from_remote()\n File
> \"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/pulpcore/download/factory.py\",
> line 90, in _make_aiohttp_session_from_remote\n
> key_file.write(bytes(self._remote.ssl_client_key, 'utf-8'))\n"
> },
>
> The remote already have the updated attribute client_key:
> {
> "ca_cert":
> "b8bd944ff40f1756c08743800453b724f133029725dc762ed9ce6504a828a5ec",
> "client_cert":
> "3f54707a201ac8a03484c7db9d8e804983bb7aa3a5864a30b946efae325002b0",
> "client_key":
> "5df5b2961f6c6ceca347eb25e645bb2e5702324f4c6e31fcfc6b36281e5e3e32",
> "download_concurrency": 5,
> "name": "rhel-x86_64-server-7",
> "policy": "immediate",
> "proxy_url": "http://proxy/";,
> "pulp_created": "2019-11-26T17:41:55.986500Z",
> "pulp_href":
> "/pulp/api/v3/remotes/rpm/rpm/3dbbd2f9-65d6-4d40-bd3a-64ace3071a01/",
> "pulp_last_updated": "2019-11-26T17:41:55.986524Z",
> "tls_validation": true,
> "url": "
> https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/";
> }
>
> Version that I am running is:
> "versions": [
> {
> "component": "pulpcore",
> "version": "3.0.0rc8"
> },
> {
> "component": "pulp_rpm",
> "version": "3.0.0rc1"
> },
> {
> "component": "pulp_file",
> "version": "0.1.0rc1"
> }
>
>
>
> ___
> 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] pulp3 rc8 ssl_client_key

[Bin Li (BLOOMBERG/ 120 PARK)]

It looks rc8 is still looking from ssl_client_key attribute to sync the remote. 

I got the following error:

"description": "'RpmRemote' object has no attribute 'ssl_client_key'", 
"traceback": "  File 
\"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/rq/worker.py\", line 
822, in perform_job\nrv = job.perform()\n  File 
\"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/rq/job.py\", line 
605, in perform\nself._result = self._execute()\n  File 
\"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/rq/job.py\", line 
611, in _execute\nreturn self.func(*self.args, **self.kwargs)\n  File 
\"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
 line 122, in synchronize\ntreeinfo = get_treeinfo_data(remote)\n  File 
\"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/pulp_rpm/app/kickstart/treeinfo.py\",
 line 19, in get_treeinfo_data\ndownloader = 
remote.get_downloader(url=urljoin(remote_url, namespace))\n  File 
\"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/pulpcore/app/models/repository.py\",
 line 261, in get_downloader\nreturn self.download_factory.build(url, 
**kwargs)\n  File 
\"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/pulpcore/app/models/repository.py\",
 line 219, in download_factory\nself._download_factory = 
DownloaderFactory(self)\n  File 
\"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/pulpcore/download/factory.py\",
 line 68, in __init__\nself._session = 
self._make_aiohttp_session_from_remote()\n  File 
\"/opt/utils/venv/pulp/3.6.5/lib64/python3.6/site-packages/pulpcore/download/factory.py\",
 line 90, in _make_aiohttp_session_from_remote\n
key_file.write(bytes(self._remote.ssl_client_key, 'utf-8'))\n"
}, 

The remote already have the updated attribute client_key:
{
"ca_cert": 
"b8bd944ff40f1756c08743800453b724f133029725dc762ed9ce6504a828a5ec", 
"client_cert": 
"3f54707a201ac8a03484c7db9d8e804983bb7aa3a5864a30b946efae325002b0", 
"client_key": 
"5df5b2961f6c6ceca347eb25e645bb2e5702324f4c6e31fcfc6b36281e5e3e32", 
"download_concurrency": 5, 
"name": "rhel-x86_64-server-7", 
"policy": "immediate", 
"proxy_url": "http://proxy/";, 
"pulp_created": "2019-11-26T17:41:55.986500Z", 
"pulp_href": 
"/pulp/api/v3/remotes/rpm/rpm/3dbbd2f9-65d6-4d40-bd3a-64ace3071a01/", 
"pulp_last_updated": "2019-11-26T17:41:55.986524Z", 
"tls_validation": true, 
"url": 
"https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/";
}

Version that I am running is:
"versions": [
{
"component": "pulpcore", 
"version": "3.0.0rc8"
}, 
{
"component": "pulp_rpm", 
"version": "3.0.0rc1"
}, 
{
"component": "pulp_file", 
"version": "0.1.0rc1"
}


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

Re: [Pulp-list] Pulp 3.0.0 Release Date, December 12

[Brian Bouterse]

title correction: Dec 12th

On Tue, Nov 26, 2019 at 11:08 AM Brian Bouterse  wrote:

> We're planning one final release candidate 3.0.0rc9 for Dec 3rd, and a
> generally available release with improved documentation on Dec 12th. This
> will include pulp_rpm, pulp_container, and pulp_file as well. This is a
> delay from the initial GA release date of Dec 3rd.
>
> Read the blog post for more details on the schedule change.
> https://pulpproject.org/2019/11/25/pulp-3-GA-update/
>
> Any questions or concerns are welcome! Please share.
>
> -Brian
>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 3.0.0 Release Date, December 13

[Brian Bouterse]

We're planning one final release candidate 3.0.0rc9 for Dec 3rd, and a
generally available release with improved documentation on Dec 12th. This
will include pulp_rpm, pulp_container, and pulp_file as well. This is a
delay from the initial GA release date of Dec 3rd.

Read the blog post for more details on the schedule change.
https://pulpproject.org/2019/11/25/pulp-3-GA-update/

Any questions or concerns are welcome! Please share.

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

Re: [Pulp-list] Pulp rpm install query

[Tatiana Tereshchenko]

Hi Pradeep,

The only option that I'm aware of is to explicitly specify multiple
packages by name.
With pulp-admin it will be `pulp-admin rpm consumer package install run -n
name1 -n name2 ...`
It might be more convenient if you use REST API
https://docs.pulpproject.org/dev-guide/integration/rest-api/consumer/content.html#install-content-on-a-consumer
.
E.g. You can write a script to generate a list  of `units` to install.

Tanya


On Mon, Nov 25, 2019 at 10:38 AM Sathasivam, Pradeep <
pradeep.sathasi...@hpe.com> wrote:

> Hi All,
>
>
>
> I have a pulp server and a consumer configured. I have a repository setup
> in the server and I am able to sync and also install packages from the repo
> on to the consumer. Currently I am using the 'pulp-admin rpm install'
> command.  Is there a command to install all the packages in the repo from
> the server to the consumer?
>
>
>
> Regards.
>
> Pradeep. S
>
>
> ___
> 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] RHEL8 and no modules

[Tatiana Tereshchenko]

Hi Stefan,

Do you still have the issue? Or have you already figured out where the
problem is?

I tested with pulp 2.21 and it works for me.
I synced and published RHEL 8.1 Appstream, configured it in
/etc/yum.repos.d and I can see all the modules available with `dnf module
list`.

Can you see RPM content from RHEL8 repo? Is it only modules which are not
available?
I'd suggest to check if the correct URL is configured for rhel8_appstream
(naive and obvious :) but worth checking).
Look at the pulp repo with your browser, can you see modules.yaml file in
repodata directory?
https://pulphost.example.com/pulp/repos/your_repo_relative_url/repodata
If it's not there, then we'd need to dig deeper into why it was not
published by pulp or if it has ever been synced into pulp in the first
place.

Tanya






On Thu, Nov 21, 2019 at 3:08 PM Stefan Wiederoder <
stefanwiedero...@googlemail.com> wrote:

> Hello pulp-list,
>
> I'm using pulp v2.21 to sync RHEL8 repos, problem is that I can't list any
> modules at all:
>
> [root@myhost ~]# dnf module list
> Updating Subscription Management repositories.
> Unable to read consumer identity
> This system is not registered to Red Hat Subscription Management. You can
> use subscription-manager to register.
> Last metadata expiration check: 0:00:09 ago on Thu 21 Nov 2019 01:07:34 PM
> UTC.
> [root@myhost ~]# dnf repolist
> Updating Subscription Management repositories.
> Unable to read consumer identity
> This system is not registered to Red Hat Subscription Management. You can
> use subscription-manager to register.
> Last metadata expiration check: 0:00:16 ago on Thu 21 Nov 2019 01:22:26 PM
> UTC.
> repo id   repo name
>   status
> rhel8_appstream   rhel8_appstream
>   8,995
> rhel8_baseos  rhel8_baseos
>  3,314
>
> looks like this issuehttps://community.oracle.com/thread/4281741
>
> I found one article which says that you need to add the option
>  --setopt=repo_id.module_hotfixes=1 to reposync,
> which results in
> repodata/6ebbfad195ec992ac04423670bc8e58ce09a7430d22e2db9f02c5e267cdf7028-modules.yaml.gz
>
> do I need to add a similar option to my pulp repo as well?
>
> I've tried to upload that file (either yaml or yaml.gz) to my repo (like I
> do with the comps-Server xml file), but that fails.
>
> thanks
> ,
> Stefan
> ___
> 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