[Pulp-list] Pulp 3.20 content server
I am trying to install content only server with pulp_content role and getting
an error
TASK [pulp_content : Get the database fields key from the pulp_database_config
node] *
fatal: [pulp-t14 -> pulp-t14]: FAILED! => {"changed": false, "msg": "file not
found: /etc/pulp/certs/database_fields.symmetric.key"}
Does anyone know how to fix this?
Thanks
___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] webserver authentication
I tried same authentication setting on 3.18.1. It works fine with the postsql db installed on the same host but got a "500 internal Server Error" when connect to an external db. The db is not a issue because if I remove the settings, it works for both local and external db. I didn't find any useful logs. Can someone guide me how to troubleshot this issue? From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/10/22 10:42:23 UTC-5:00To: pulp-list@redhat.com Subject: webserver authentication We are currently use the below setting for webserver authentication. It doesn't work anymore in 3.15. Does anyone know what should be the new setting? REMOTE_USER_ENVIRON_NAME: 'HTTP_REMOTE_USER' AUTHENTICATION_BACKENDS: ['pulpcore.app.authentication.PulpNoCreateRemoteUserBackend'] REST_FRAMEWORK__DEFAULT_AUTHENTICATION_CLASSES: ['rest_framework.authentication.SessionAuthentication', 'pulpcore.app.authentication.PulpRemoteUserAuthentication'] ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] webserver authentication
We are currently use the below setting for webserver authentication. It doesn't work anymore in 3.15. Does anyone know what should be the new setting? REMOTE_USER_ENVIRON_NAME: 'HTTP_REMOTE_USER' AUTHENTICATION_BACKENDS: ['pulpcore.app.authentication.PulpNoCreateRemoteUserBackend'] REST_FRAMEWORK__DEFAULT_AUTHENTICATION_CLASSES: ['rest_framework.authentication.SessionAuthentication', 'pulpcore.app.authentication.PulpRemoteUserAuthentication'] ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] Pulp 3.15 content only server
Thanks, Mike. Two questions: 1) Is the advantage of manual configuration to have a independent slave redis rather than sharing the same redis? 2) Does the example configuration described in https://docs.pulpproject.org/pulp_installer/customizing/#separate-servers-for-each-and-every-service still need additional manual work that your mentioned or this example works in the latest 3.17 release? From: mikedep...@redhat.com At: 02/28/22 13:52:36 UTC-5:00To: danny.sa...@konghq.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com Subject: Re: [Pulp-list] Pulp 3.15 content only server Hi Bin, Using the Pulp3 Ansible Installer, we do not support a read-only server like you want. The installer could be extended to support it, as pulp 3 does support it, but we do not currently support it and overcoming #7 below would be time-consuming. The closest you can do with the current installer (or 3.15's installer) is: 1. Run pulp_content and pulp_webserver against this server. 2. You would configure pulp_webserver to talk only to that pulp_content instance by leaving pulp_content_bind at its default of "127.0.0.1:24816" for this host (or use a unix domain socket). 3. You'd have to point to another pulp_api server (pulp_api_bind) and redis (pulp_settings.redis_host). Additionally, with manual configuration you can accomplish what you want: 4. Manually install & configure the redis instance to be a replica. See our pulp_redis role on how to install it and how to configure it to listen on the network: it is relatively simple to read & understand. You should actually do this before running pulp_content and pulp_webserver. 5. When running the installer against this host, pulp_settings.redis_host defaults to `localhost`, which is what you'd want instead of pointing to another pulp_redis server (contradicts #3). 6. After running the installer, manually adjust the apache/nginx config files (nginx.conf & pulp-vhost.conf) placed by pulp_webserver to not talk to any pulp-api server. pulp_webserver's pulp_content_bind variable defaults to localhost, which makes things easier.) 7. After running the installer, manually adjust the webserver snippets from plugins (e.g., pulp_container.conf) to not talk to any API server. See https://docs.pulpproject.org/pulp_installer/customizing/#separate-servers-for-each-and-every-service for a different example of multiple hosts, each host having a roles lists & variables. -Mike On Sun, Feb 27, 2022 at 4:40 PM Danny Sauer wrote: You can definitely run multiple content servers as long as they all have access to the DB and files are available in the same path. --Danny On Sun, Feb 27, 2022, 12:23 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: Just wondering if there is a documented procedure to configure additional content only server. Will it work if I only run 3 roles below and config redis as slave of the primary server? We share the external db and rsync the /var/lob/pulp/media/artifact. - pulp_content - pulp_redis - pulp_webserver Thanks___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list -- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat IM: mikedep333 GPG: 51745404 ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] check_snippet.py
I noticed this message in 3.15 installation and also previous release. I wonder
what they are and if it is normal to fail.
skipping: [pulp-d2] => (item={'changed': False, 'rc': 1, 'stdout': 'Traceback
(most recent call last):\r\n File
"/home/cloud-user/.ansible/tmp/ansible-tmp-1645984199.9720438-8177-67668749165546/check_snippet.py",
line 16, in \r\nwebserver_snippets =
importlib.import_module(sys.argv[1] + ".app.webserver_snippets")\r\n File
"/opt/python/3.8.8/lib64/python3.8/importlib/__init__.py", line 127, in
import_module\r\nreturn _bootstrap._gcd_import(name[level:], package,
level)\r\n File "", line 1014, in _gcd_import\r\n
File "", line 991, in _find_and_load\r\n File
"", line 973, in
_find_and_load_unlocked\r\nModuleNotFoundError: No module named
\'pulp_file.app.webserver_snippets\'\r\n', 'stdout_lines': ['Traceback (most
recent call last):', ' File
"/home/cloud-user/.ansible/tmp/ansible-tmp-1645984199.9720438-8177-67668749165546/check_snippet.py",
line 16, in ', 'webserver_snippets =
importlib.import_module(sys.argv[1] + ".app.webserver_snippets")', ' File
"/opt/python/3.8.8/lib64/python3.8/importlib/__init__.py", line 127, in
import_module', 'return _bootstrap._gcd_import(name[level:], package,
level)', ' File "", line 1014, in _gcd_import', '
File "", line 991, in _find_and_load', ' File
"", line 973, in _find_and_load_unlocked',
"ModuleNotFoundError: No module named 'pulp_file.app.webserver_snippets'"],
'stderr': 'Shared connection to 10.178.24.121 closed.\r\n', 'stderr_lines':
['Shared connection to 10.178.24.121 closed.'], 'failed': False, 'msg':
'non-zero return code', 'exception': 'NoneType: None\n', 'failed_when_result':
False, '__pulp_webserver_plugin': {'key': 'pulp-file', 'value': {'version':
'1.9.1'}}, 'ansible_loop_var': '__pulp_webserver_plugin'})
module.pulp-install["pulp-d2"].null_resource.pulp-install (local-exec):
skipping: [pulp-d2] => (item={'changed': False, 'rc': 1, 'stdout': 'Traceback
(most recent call last):\r\n File
"/home/cloud-user/.ansible/tmp/ansible-tmp-1645984200.449993-8177-92525154956070/check_snippet.py",
line 16, in \r\nwebserver_snippets =
importlib.import_module(sys.argv[1] + ".app.webserver_snippets")\r\n File
"/opt/python/3.8.8/lib64/python3.8/importlib/__init__.py", line 127, in
import_module\r\nreturn _bootstrap._gcd_import(name[level:], package,
level)\r\n File "", line 1014, in _gcd_import\r\n
File "", line 991, in _find_and_load\r\n File
"", line 973, in
_find_and_load_unlocked\r\nModuleNotFoundError: No module named
\'pulp_rpm.app.webserver_snippets\'\r\n', 'stdout_lines': ['Traceback (most
recent call last):', ' File
"/home/cloud-user/.ansible/tmp/ansible-tmp-1645984200.449993-8177-92525154956070/check_snippet.py",
line 16, in ', 'webserver_snippets =
importlib.import_module(sys.argv[1] + ".app.webserver_snippets")', ' File
"/opt/python/3.8.8/lib64/python3.8/importlib/__init__.py", line 127, in
import_module', 'return _bootstrap._gcd_import(name[level:], package,
level)', ' File "", line 1014, in _gcd_import', '
File "", line 991, in _find_and_load', ' File
"", line 973, in _find_and_load_unlocked',
"ModuleNotFoundError: No module named 'pulp_rpm.app.webserver_snippets'"],
'stderr': 'Shared connection to 10.178.24.121 closed.\r\n', 'stderr_lines':
['Shared connection to 10.178.24.121 closed.'], 'failed': False, 'msg':
'non-zero return code', 'exception': 'NoneType: None\n', 'failed_when_result':
False, '__pulp_webserver_plugin': {'key': 'pulp-rpm', 'value': {'version':
'3.15.0'}}, 'ansible_loop_var': '__pulp_webserver_plugin'})
___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp 3.7.3 sync failure
Is there a workaround such as recreating the repo? It will take some time for us to test and upgrade to newer release. From: ggai...@redhat.com At: 02/11/22 08:51:25 UTC-5:00To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync failure There are a few ways this can happen (all of them fixed in more-recent-than-3.7 versions). See https://pulp.plan.io/issues/8430 https://pulp.plan.io/issues/8452 G On Fri, Feb 11, 2022 at 8:38 AM Bin Li (BLOOMBERG/ 120 PARK) wrote: We got a error from sync of one repo. What could cause this? Could it cause by a mismatch metadata in upstream repo? "traceback": " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line 886, in perform_job\nrv = job.perform()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line 664, in perform\nself._result = self._execute()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line 670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\", line 266, in synchronize\ndv.create()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\", line 148, in create\nloop.run_until_complete(pipeline)\n File \"/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py\", line 584, in run_until_complete\nreturn future.result()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\", line 225, in create_pipeline\nawait asyncio.gather(*futures)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\", line 43, in __call__\nawait self.run()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/content_stages.py\", line 105, in run\nd_content.content.q()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/manager.py\", line 82, in manager_method\nreturn getattr(self.get_queryset(), name)(*args, **kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\", line 408, in get\nself.model._meta.object_name\n", "description": "Package matching query does not exist." Thanks___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list -- Grant Gainey Principal Software Engineer, Red Hat System Management Engineering ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp 3.7.3 sync failure
We got a error from sync of one repo. What could cause this? Could it cause by a mismatch metadata in upstream repo? "traceback": " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line 886, in perform_job\nrv = job.perform()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line 664, in perform\nself._result = self._execute()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line 670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\", line 266, in synchronize\ndv.create()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\", line 148, in create\nloop.run_until_complete(pipeline)\n File \"/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py\", line 584, in run_until_complete\nreturn future.result()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\", line 225, in create_pipeline\nawait asyncio.gather(*futures)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\", line 43, in __call__\nawait self.run()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/content_stages.py\", line 105, in run\nd_content.content.q()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/manager.py\", line 82, in manager_method\nreturn getattr(self.get_queryset(), name)(*args, **kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\", line 408, in get\nself.model._meta.object_name\n", "description": "Package matching query does not exist." Thanks___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] redis sentinel
Just wondering if there is a plan to support external redis sentinel in the future?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] redis on a passive backup server
Thanks Brain and Matthias. It's really helpful to understand how this works. I'd like to know the answer of the same question under two different scenarios. In both scenarios, we will have 2 content servers behind a load balancer and share the same external db. Api server is only run on one of the hosts. 1) Both content servers have the same artifacts in its own filesystems (rsyned) 2) Both content servers shared the S3. We currently use filesystem as the storage and would like to move to S3. Can redis be independent in above two cases? From: mdell...@redhat.com At: 09/21/21 16:50:53 UTC-4:00To: bmbou...@redhat.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com Subject: Re: [Pulp-list] redis on a passive backup server Right i did not read that correctly. It's a failover scenario. It would even be safe to flush redis on failover. I was thinking about multiple independent content app installations each with their own redis server. But that is another challenge. On Tue, Sep 21, 2021 at 7:32 PM Brian Bouterse wrote: > > > > On Mon, Sep 20, 2021 at 5:40 PM Matthias Dellweg wrote: >> >> I am not sure if the cache invalidations will be pushed to all redis >> instances if deployed that way. Maybe there is a little bit of extra >> work needed. > > I imagined the backup Pulp would have its Redis empty because that Pulp wasn't in use. If that were the case cache invalidations not reaching it would be fine because the cache would be empty at failover time. As always though, there could be more needed to handle some specific use cases. > >> >> On Mon, Sep 20, 2021 at 10:31 PM Brian Bouterse wrote: >> > >> > I believe with 3.14+ and new style workers, you can have an independant redis on the backup server. >> > >> > With the new-style tasking system (the default in 3.14) you no longer need Redis for tasking. It's only purpose then is to help speedup the content app which caches info about requests to make answering subsequent content-app requests easier. If those caches miss, e.g. if you had a failover event, Pulp will continue to work fine, just building the Redis cache data as it goes. >> > >> > On Mon, Sep 20, 2021 at 4:22 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: >> >> >> >> We configured a redis slave on a passive backup server which shares the same external database with the primary pulp server. I noticed the task queues are now being tracked in the database. Is it still necessary to configure redis as a slave or we can have an independent instance of redis on the backup server? >> >> >> >> Thanks >> >> ___ >> >> Pulp-list mailing list >> >> Pulp-list@redhat.com >> >> https://listman.redhat.com/mailman/listinfo/pulp-list >> > >> > ___ >> > Pulp-list mailing list >> > Pulp-list@redhat.com >> > https://listman.redhat.com/mailman/listinfo/pulp-list >> ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] content only server
Does anyone know if there is an option to only enable the content server in the pulp_installer? I think I could skip pulp_database and pulp_database_config and disable systemd api, worker, redis service once it is installed. Just wondering if there is a better way to do this. The content only server will share the storage and db with the primary server. We are planning to have multiple servers to distribute the load and achieve high availability.___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] redis on a passive backup server
We configured a redis slave on a passive backup server which shares the same external database with the primary pulp server. I noticed the task queues are now being tracked in the database. Is it still necessary to configure redis as a slave or we can have an independent instance of redis on the backup server? Thanks___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp3 migration directory
Thanks Mike. What you described is what we plan to do. I do see the migration historical files. They are under ../venv/pulp/3.7 in our case. It is a virtual environment used by the pulp_installer. We set the pulp_install_dir to this directory. Since we are upgrading python to 3.8 for pulp 3.15. We set the pulp_install_dir to a new ../venv/pulp/3.8. Because this is a new python install dir, I am not sure how pulp_installer know where to find the historical file under the old ../venv/pulp/3.7. Could this be an issue for the migration? From: mikedep...@redhat.com At: 09/20/21 12:21:22 UTC-4:00To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp3 migration directory Hi Bin, We are trying to understand what you are asking exactly. It sounds like: 1. you have a test environment with a copy of the production database. 2. You upgraded pulp on the test environment. During this, the migrations were ran by pulp_installer against the test database copy. 3. You will run the upgrade pulp on the production environment, which will upgrade the production database. So we have all the possibly needed migration files on disk. They are static, and are part of the pypi packages (and RPM packages too.) This is a change from the pulpcore 3.0 alpha/beta/rc behavior, when we generated the migrations. If you run `find /usr/local/lib/pulp | grep migrations` , you will see all of them. You'll see both compiled .pyc files and the original .py files. When the installer runs, it runs all the needed migrations. This is part of the pulp_database_config role, the task is named "Run database migrations". roles/pulp_database_config/README.md still refers to the pulpcore 3.0 alpha/beta/rc behavior when it says that it "Create and run migrations." It only runs them now. I will fix this doc. Does this answer your questions? -Mike On Thu, Sep 16, 2021 at 4:52 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: The 3.15 release requires python 3.8. We are currently running pulpcore 3.7 with python 3.7 and an external db. When we use the pulp_installer to migrate the older release to 3.15 with new python 3.8 venv,it run successfully in a test environment. I am wondering how the new version knows the the historical migration file. Should I copy the historical migration files from older python 3.7 venv to the new 3.8 venv first?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list -- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat IM: mikedep333 GPG: 51745404 ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp3 migration directory
The 3.15 release requires python 3.8. We are currently running pulpcore 3.7 with python 3.7 and an external db. When we use the pulp_installer to migrate the older release to 3.15 with new python 3.8 venv,it run successfully in a test environment. I am wondering how the new version knows the the historical migration file. Should I copy the historical migration files from older python 3.7 venv to the new 3.8 venv first?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp-rpm-client 3.15.0
It makes sense to make it private. Redhat subscription manager frequent updated the entitlement cert. We don't know if the client_key in pulp is valid until we get the 403 error. We'd like update the key automatically. Is there an alternative way to compare the client key so we always have a valid key? From: davidda...@redhat.com At: 09/09/21 12:56:46 UTC-4:00To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp-rpm-client 3.15.0 The remote fields client_key, username, and password became no longer readable in pulp 3.11. You can still set/update them but we considered exposing them in the API as a security vulnerability. https://docs.pulpproject.org/pulpcore/changes.html#id330 https://pulp.plan.io/issues/8202 David On Thu, Sep 9, 2021 at 12:42 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: We are using pulpcore.client.pulp_rpm to query pulp remote objects to compare the client_key to make sure we always have valid entitlement in pulp. We current running 3.7.3 After we upgraded to 3.15.2 and installed pulp-rpm-client 3.15.0. We got the following error AttributeError: 'RpmRpmRemoteResponse' object has no attribute 'client_key'. Should the 'RpmRpmRemoteResponse' has client_key attribute as previous releases? class RpmRpmRemoteResponse(builtins.object) | RpmRpmRemoteResponse(pulp_href=None, pulp_created=None, name=None, url=None, ca_cert=None, client_cert=None, tls_validation=None, proxy_url=None, pulp_labels=None, pulp_last_updated=None, download_concurrency=None, max_retries=None, policy=None, total_timeout=None, connect_timeout=None, sock_connect_timeout=None, sock_read_timeout=None, headers=None, rate_limit=None, sles_auth_token=None, local_vars_configuration=None) class RpmRpmRemote(builtins.object) | RpmRpmRemote(name=None, url=None, ca_cert=None, client_cert=None, client_key=None, tls_validation=None, proxy_url=None, proxy_username=None, proxy_password=None, username=None, password=None, pulp_labels=None, download_concurrency=None, max_retries=None, policy=None, total_timeout=None, connect_timeout=None, sock_connect_timeout=None, sock_read_timeout=None, headers=None, rate_limit=None, sles_auth_token=None, local_vars_configuration=None) ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp-rpm-client 3.15.0
We are using pulpcore.client.pulp_rpm to query pulp remote objects to compare the client_key to make sure we always have valid entitlement in pulp. We current running 3.7.3 After we upgraded to 3.15.2 and installed pulp-rpm-client 3.15.0. We got the following error AttributeError: 'RpmRpmRemoteResponse' object has no attribute 'client_key'. Should the 'RpmRpmRemoteResponse' has client_key attribute as previous releases? class RpmRpmRemoteResponse(builtins.object) | RpmRpmRemoteResponse(pulp_href=None, pulp_created=None, name=None, url=None, ca_cert=None, client_cert=None, tls_validation=None, proxy_url=None, pulp_labels=None, pulp_last_updated=None, download_concurrency=None, max_retries=None, policy=None, total_timeout=None, connect_timeout=None, sock_connect_timeout=None, sock_read_timeout=None, headers=None, rate_limit=None, sles_auth_token=None, local_vars_configuration=None) class RpmRpmRemote(builtins.object) | RpmRpmRemote(name=None, url=None, ca_cert=None, client_cert=None, client_key=None, tls_validation=None, proxy_url=None, proxy_username=None, proxy_password=None, username=None, password=None, pulp_labels=None, download_concurrency=None, max_retries=None, policy=None, total_timeout=None, connect_timeout=None, sock_connect_timeout=None, sock_read_timeout=None, headers=None, rate_limit=None, sles_auth_token=None, local_vars_configuration=None) ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] New python version
We'd like to use python 3.8 instead of 3.7 during the migration from 3.7 to
3.14 and we got the errors below with pulp_installer.
The current pulp 3.7 is installed in /opt/utils/venv/pulp/3.7.3. If I pip
install pulpcore and all plugins with python 3.8 first before running
python_installer, I don't see this errors. What is the correct way to migrate
an older release to a newer with a new python version?
fatal: [pulp-t3]: FAILED! => {"changed": false, "cmd":
["/opt/utils/venv/pulp/3.8.8/bin/pip-compile", "-P", "pulp-file", "-P",
"pulp-rpm"], "delta": "0:00:03.500102", "end": "2021-09-03 12:11:01.748991",
"failed_when_result": true, "msg": "non-zero return code", "rc": 2, "start":
"2021-09-03 12:10:58.248889", "stderr": "Could not find a version that matches
pulpcore<3.17,==3.14.4,>=3.15.0 (from pulp-file==1.9.1)\nTried: 3.0.0, 3.0.0,
3.0.1, 3.0.1, 3.1.0, 3.1.0, 3.1.1, 3.1.1, 3.2.0, 3.2.0, 3.2.1, 3.2.1, 3.3.0,
3.3.0, 3.3.1, 3.3.1, 3.4.0, 3.4.0, 3.4.1, 3.4.1, 3.5.0, 3.5.0, 3.6.0, 3.6.0,
3.6.1, 3.6.1, 3.6.2, 3.6.2, 3.6.3, 3.6.3, 3.6.4, 3.6.4, 3.6.5.post1,
3.6.5.post1, 3.6.5.post2, 3.6.5.post2, 3.7.0, 3.7.0, 3.7.1, 3.7.1, 3.7.2,
3.7.2, 3.7.3, 3.7.3, 3.7.4, 3.7.4, 3.7.5, 3.7.5, 3.7.5.post0, 3.7.5.post0,
3.7.6, 3.7.6, 3.7.7, 3.7.7, 3.7.8, 3.7.8, 3.8.0, 3.8.0, 3.8.1, 3.8.1, 3.9.0,
3.9.0, 3.9.1, 3.9.1, 3.10.0, 3.10.0, 3.11.0, 3.11.0, 3.11.0.post0,
3.11.0.post0, 3.11.1, 3.11.1, 3.11.2, 3.11.2, 3.12.0, 3.12.0, 3.12.1, 3.12.1,
3.12.2, 3.12.2, 3.13.0, 3.13.0, 3.14.0, 3.14.0, 3.14.1, 3.14.1, 3.14.2, 3.14.2,
3.14.3, 3.14.3, 3.14.4, 3.14.4, 3.14.5, 3.14.5, 3.14.6, 3.14.6, 3.15.0, 3.15.0,
3.15.1, 3.15.1, 3.15.2, 3.15.2\nSkipped pre-versions: 3.0.0b1, 3.0.0b1,
3.0.0b2, 3.0.0b2, 3.0.0b3, 3.0.0b3, 3.0.0b4, 3.0.0b4, 3.0.0b5, 3.0.0b5,
3.0.0b6, 3.0.0b6, 3.0.0b7, 3.0.0b7, 3.0.0b8, 3.0.0b8, 3.0.0b9, 3.0.0b9,
3.0.0b10, 3.0.0b10, 3.0.0b11, 3.0.0b11, 3.0.0b12, 3.0.0b12, 3.0.0b13, 3.0.0b13,
3.0.0b14, 3.0.0b14, 3.0.0b15, 3.0.0b15, 3.0.0b16, 3.0.0b16, 3.0.0b17, 3.0.0b18,
3.0.0b18, 3.0.0b19, 3.0.0b19, 3.0.0b20, 3.0.0b20, 3.0.0b21, 3.0.0b21, 3.0.0b22,
3.0.0b22, 3.0.0b23, 3.0.0b23, 3.0.0rc1, 3.0.0rc1, 3.0.0rc2, 3.0.0rc2, 3.0.0rc3,
3.0.0rc3, 3.0.0rc4, 3.0.0rc4, 3.0.0rc5, 3.0.0rc5, 3.0.0rc6, 3.0.0rc6, 3.0.0rc7,
3.0.0rc7, 3.0.0rc8, 3.0.0rc8, 3.0.0rc9, 3.0.0rc9\nThere are incompatible
versions in the resolved dependencies:\n pulpcore==3.14.4 (from -r
requirements.in (line 1))\n pulpcore<3.17,>=3.15.0 (from pulp-file==1.9.1)\n
pulpcore<3.17,>=3.15.0 (from pulp-rpm==3.15.0)", "stderr_lines": ["Could not
find a version that matches pulpcore<3.17,==3.14.4,>=3.15.0 (from
pulp-file==1.9.1)", "Tried: 3.0.0, 3.0.0, 3.0.1, 3.0.1, 3.1.0, 3.1.0, 3.1.1,
3.1.1, 3.2.0, 3.2.0, 3.2.1, 3.2.1, 3.3.0, 3.3.0, 3.3.1, 3.3.1, 3.4.0, 3.4.0,
3.4.1, 3.4.1, 3.5.0, 3.5.0, 3.6.0, 3.6.0, 3.6.1, 3.6.1, 3.6.2, 3.6.2, 3.6.3,
3.6.3, 3.6.4, 3.6.4, 3.6.5.post1, 3.6.5.post1, 3.6.5.post2, 3.6.5.post2, 3.7.0,
3.7.0, 3.7.1, 3.7.1, 3.7.2, 3.7.2, 3.7.3, 3.7.3, 3.7.4, 3.7.4, 3.7.5, 3.7.5,
3.7.5.post0, 3.7.5.post0, 3.7.6, 3.7.6, 3.7.7, 3.7.7, 3.7.8, 3.7.8, 3.8.0,
3.8.0, 3.8.1, 3.8.1, 3.9.0, 3.9.0, 3.9.1, 3.9.1, 3.10.0, 3.10.0, 3.11.0,
3.11.0, 3.11.0.post0, 3.11.0.post0, 3.11.1, 3.11.1, 3.11.2, 3.11.2, 3.12.0,
3.12.0, 3.12.1, 3.12.1, 3.12.2, 3.12.2, 3.13.0, 3.13.0, 3.14.0, 3.14.0, 3.14.1,
3.14.1, 3.14.2, 3.14.2, 3.14.3, 3.14.3, 3.14.4, 3.14.4, 3.14.5, 3.14.5, 3.14.6,
3.14.6, 3.15.0, 3.15.0, 3.15.1, 3.15.1, 3.15.2, 3.15.2", "Skipped pre-versions:
3.0.0b1, 3.0.0b1, 3.0.0b2, 3.0.0b2, 3.0.0b3, 3.0.0b3, 3.0.0b4, 3.0.0b4,
3.0.0b5, 3.0.0b5, 3.0.0b6, 3.0.0b6, 3.0.0b7, 3.0.0b7, 3.0.0b8, 3.0.0b8,
3.0.0b9, 3.0.0b9, 3.0.0b10, 3.0.0b10, 3.0.0b11, 3.0.0b11, 3.0.0b12, 3.0.0b12,
3.0.0b13, 3.0.0b13, 3.0.0b14, 3.0.0b14, 3.0.0b15, 3.0.0b15, 3.0.0b16, 3.0.0b16,
3.0.0b17, 3.0.0b18, 3.0.0b18, 3.0.0b19, 3.0.0b19, 3.0.0b20, 3.0.0b20, 3.0.0b21,
3.0.0b21, 3.0.0b22, 3.0.0b22, 3.0.0b23, 3.0.0b23, 3.0.0rc1, 3.0.0rc1, 3.0.0rc2,
3.0.0rc2, 3.0.0rc3, 3.0.0rc3, 3.0.0rc4, 3.0.0rc4, 3.0.0rc5, 3.0.0rc5, 3.0.0rc6,
3.0.0rc6, 3.0.0rc7, 3.0.0rc7, 3.0.0rc8, 3.0.0rc8, 3.0.0rc9, 3.0.0rc9", "There
are incompatible versions in the resolved dependencies:", " pulpcore==3.14.4
(from -r requirements.in (line 1))", " pulpcore<3.17,>=3.15.0 (from
pulp-file==1.9.1)", " pulpcore<3.17,>=3.15.0 (from pulp-rpm==3.15.0)"],
"stdout": "", "stdout_lines": []}
___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] Pulp-list Digest, Vol 141, Issue 4
sions": [
{
"component": "core",
"version": "3.14.4"
},
{
"component": "rpm",
"version": "3.14.1"
},
{
"component": "file",
"version": "1.8.2"
}
# pip list |grep pulp
pulp-file 1.8.2
pulp-rpm3.14.1
pulp-rpm-client 3.14.1
pulpcore3.14.4
pulpcore-client 3.14.4
From: pulp-list@redhat.com At: 08/06/21 02:44:17 UTC-4:00To:
pulp-list@redhat.com
Subject: Pulp-list Digest, Vol 141, Issue 4
Send Pulp-list mailing list submissions to
pulp-list@redhat.com
To subscribe or unsubscribe via the World Wide Web, visit
https://listman.redhat.com/mailman/listinfo/pulp-list
or, via email, send a message with subject or body 'help' to
pulp-list-requ...@redhat.com
You can reach the person managing the list at
pulp-list-ow...@redhat.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Pulp-list digest..."
Today's Topics:
1. Re: pulp 3.14 migration (Daniel Alley)
--
Message: 1
Date: Thu, 5 Aug 2021 17:38:56 -0400
From: Daniel Alley
To: Fabricio Aguiar
Cc: pulp-list , Bin Li
Subject: Re: [Pulp-list] pulp 3.14 migration
Message-ID:
Content-Type: text/plain; charset="utf-8"
Here's a hypothesis for what happened.
* System is at pulpcore 3.7, it has artifacts saved with checksums that are
disabled on later versions of Pulp
* 3.14 is installed, migration to 3.14 database schema fails due to the
disallowed checksums (IIRC we have a special case to avoid this happening,
but maybe we missed a scenario. There is a question mark here.)
* Bin attempts to run "handle-artifact-checksums" but is unable to do so
because of the incompleted migrations
I think the correct workaround is to update the settings file to allow all
checksum types prior to the upgrade. And presumably if you're still
managing content with such checksums, you want to keep them enabled, anyway.
@Bin Li, On your test system please edit /etc/pulp/settings.py to include
the following line
ALLOWED_CONTENT_CHECKSUMS = ["md5", "sha1", "sha224", "sha256", "sha384",
> "sha512"]
>
And then restart the upgrade process / database migrations.
On Thu, Aug 5, 2021 at 5:26 PM Daniel Alley wrote:
> Bin is using Katello's RPM builds, I'm not sure if Katello has RPMs built
> for 3.10.
>
> On Thu, Aug 5, 2021 at 4:22 PM Fabricio Aguiar
> wrote:
>
>> I tried but I couldn't reproduce the error,
>> I know pulpcore 3.11 introduced some breaking changes [1]
>> I would try to migrate from 3.7 to 3.10, and then from 3.10 to 3.14
>>
>> [1] https://docs.pulpproject.org/pulpcore/changes.html#id198
>>
>> Best regards,
>> Fabricio Aguiar
>> Software Engineer, Pulp Project
>> Red Hat Brazil - Latam <https://www.redhat.com/>
>> +55 22 999000595
>>
>>
>>
>> On Thu, Jul 29, 2021 at 1:17 PM Bin Li (BLOOMBERG/ 120 PARK) <
>> bli...@bloomberg.net> wrote:
>>
>>> Thanks Faguiard. We are using pulp_installer. The error originally from
>>> pulpcore 3.14 and pulp_rpm 3.13.
>>>
>>> I just tried the latest pulp_installer. I still see the same errors.
>>> pulp-file 1.8.2
>>> pulp-rpm 3.14.0
>>> pulpcore 3.14.3
>>>
>>> I noticed a interesting thing. The migration from 3.7.3 works fine if I
>>> migrate a fresh installed 3.7.3 to 3.14.3. The error only happened after I
>>> syncd a few repos to the 3.7.3 instance and then migrate to 3.14.3.
>>>
>>>
>>> From: fagui...@redhat.com At: 07/27/21 10:37:36 UTC-4:00
>>> To: Bin Li (BLOOMBERG/ 120 PARK )
>>> Cc: pulp-list@redhat.com
>>> Subject: Re: [Pulp-list] pulp 3.14 migration
>>>
>>> Hi Bin,
>>>
>>> We currently test migrating from 3.11 to 3.14, so probably something is
>>> happening from 3.7 to 3.11
>>> I'll be trying to reproduce the error. Are you using pulp_installer? If
>>> so, which version? Which plugins do you use?
>>>
>>> Best regards,
>>> Fabricio Aguiar
>>> Software Engineer, Pulp Project
>>> Red Hat Brazil - Latam <https://www.redhat.com/>
>>> +55 22 999000595
>>>
>>>
>>>
>>> On Fri, Jul 23, 2021 at 11:29 AM Bin Li (BLOOMBERG/ 120 PARK) <
>>> bli...@bloomberg.net> wrote:
>>>
>>>> The installation didn't pass the health che
Re: [Pulp-list] pulp 3.14 migration
Thanks Faguiard. We are using pulp_installer. The error originally from
pulpcore 3.14 and pulp_rpm 3.13.
I just tried the latest pulp_installer. I still see the same errors.
pulp-file 1.8.2
pulp-rpm3.14.0
pulpcore3.14.3
I noticed a interesting thing. The migration from 3.7.3 works fine if I migrate
a fresh installed 3.7.3 to 3.14.3. The error only happened after I syncd a few
repos to the 3.7.3 instance and then migrate to 3.14.3.
From: fagui...@redhat.com At: 07/27/21 10:37:36 UTC-4:00To: Bin Li (BLOOMBERG/
120 PARK )
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.14 migration
Hi Bin,
We currently test migrating from 3.11 to 3.14, so probably something is
happening from 3.7 to 3.11
I'll be trying to reproduce the error. Are you using pulp_installer? If so,
which version? Which plugins do you use?
Best regards,
Fabricio Aguiar
Software Engineer, Pulp Project
Red Hat Brazil - Latam
+55 22 999000595
On Fri, Jul 23, 2021 at 11:29 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
The installation didn't pass the health check because the following errors:
pulpcore-worker: django.core.exceptions.ImproperlyConfigured: There have been
identified artifacts with forbidden checksum 'sha1'. Run 'pulpcore-manager
handle-artifact-checksums' first to unset forbidden checksums.
Tried to run pulpcore-manager. It also failed. This is a migration from
existing 3.7.2 to 3.14. Please advise.
$ pulpcore-manager handle-artifact-checksums
System check identified some issues:
WARNINGS:
?: (guardian.W001) Guardian authentication backend is not hooked. You can add
this in settings as eg: `AUTHENTICATION_BACKENDS =
('django.contrib.auth.backends.ModelBackend',
'guardian.backends.ObjectPermissionBackend')`.
Traceback (most recent call last):
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/backends/utils.py",
line 84, in _execute
return self.cursor.execute(sql, params)
psycopg2.errors.UndefinedColumn: column core_artifact.timestamp_of_interest
does not exist
LINE 1: ...ore_artifact"."sha384", "core_artifact"."sha512", "core_arti...
^
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/models/sql/compiler.py",
line 1142, in execute_sql
cursor.execute(sql, params)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/backends/utils.py",
line 67, in execute
return self._execute_with_wrappers(sql, params, many=False,
executor=self._execute)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/backends/utils.py",
line 76, in _execute_with_wrappers
return executor(sql, params, many, context)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/backends/utils.py",
line 84, in _execute
return self.cursor.execute(sql, params)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/utils.py",
line 89, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/backends/utils.py",
line 84, in _execute
return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: column core_artifact.timestamp_of_interest
does not exist
LINE 1: ...ore_artifact"."sha384", "core_artifact"."sha512", "core_arti...
^
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/utils/venv/pulp/3.8.8/bin/pulpcore-manager", line 8, in
sys.exit(manage())
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/pulpcore/app/manage.py",
line 11, in manage
execute_from_command_line(sys.argv)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/core/management/__init__.py",
line 381, in execute_from_command_line
utility.execute()
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/core/management/__init__.py",
line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/core/management/base.py",
line 323, in run_from_argv
self.execute(*args, **cmd_options)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/core/management/base.py",
line 364, in execute
output = self.handle(*args, **options)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/pulpcore/app/management/commands/handle-artifact-checksums.py"
Re: [Pulp-list] pulp 3.7.2 api 499 error
"configure resources" is to create and update repos, remote, pub, and distribution. We compare them with a predefined input file and update pulp accordingly. I will try increasing the worker to 10 to see how it goes. From: mdell...@redhat.com At: 07/23/21 10:22:56 UTC-4:00To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.2 api 499 error It will sure help availability. It will not so much help with the syncs (as those are between the workers and the database). I am unsure about what "configure resources" means, but if you are also querying the status of the sync tasks regularly, more api-workers should help, too. On Fri, Jul 23, 2021 at 4:15 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: > > Our monitoring service watches the /pulp/api/v3/status to alert in case server(3.7.2) is down. We have recently experienced 499 error when the server is busy to configure resources and sync a few hundreds upstream repos. I noticed the pulpcore-api only has 1 worker by default. Will increasing the pulpcore-api workers help in this case? > ___ > Pulp-list mailing list > Pulp-list@redhat.com > https://listman.redhat.com/mailman/listinfo/pulp-list ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp 3.14 migration
The installation didn't pass the health check because the following errors:
pulpcore-worker: django.core.exceptions.ImproperlyConfigured: There have been
identified artifacts with forbidden checksum 'sha1'. Run 'pulpcore-manager
handle-artifact-checksums' first to unset forbidden checksums.
Tried to run pulpcore-manager. It also failed. This is a migration from
existing 3.7.2 to 3.14. Please advise.
$ pulpcore-manager handle-artifact-checksums
System check identified some issues:
WARNINGS:
?: (guardian.W001) Guardian authentication backend is not hooked. You can add
this in settings as eg: `AUTHENTICATION_BACKENDS =
('django.contrib.auth.backends.ModelBackend',
'guardian.backends.ObjectPermissionBackend')`.
Traceback (most recent call last):
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/backends/utils.py",
line 84, in _execute
return self.cursor.execute(sql, params)
psycopg2.errors.UndefinedColumn: column core_artifact.timestamp_of_interest
does not exist
LINE 1: ...ore_artifact"."sha384", "core_artifact"."sha512", "core_arti...
^
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/models/sql/compiler.py",
line 1142, in execute_sql
cursor.execute(sql, params)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/backends/utils.py",
line 67, in execute
return self._execute_with_wrappers(sql, params, many=False,
executor=self._execute)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/backends/utils.py",
line 76, in _execute_with_wrappers
return executor(sql, params, many, context)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/backends/utils.py",
line 84, in _execute
return self.cursor.execute(sql, params)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/utils.py",
line 89, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/backends/utils.py",
line 84, in _execute
return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: column core_artifact.timestamp_of_interest
does not exist
LINE 1: ...ore_artifact"."sha384", "core_artifact"."sha512", "core_arti...
^
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/utils/venv/pulp/3.8.8/bin/pulpcore-manager", line 8, in
sys.exit(manage())
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/pulpcore/app/manage.py",
line 11, in manage
execute_from_command_line(sys.argv)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/core/management/__init__.py",
line 381, in execute_from_command_line
utility.execute()
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/core/management/__init__.py",
line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/core/management/base.py",
line 323, in run_from_argv
self.execute(*args, **cmd_options)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/core/management/base.py",
line 364, in execute
output = self.handle(*args, **options)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/pulpcore/app/management/commands/handle-artifact-checksums.py",
line 177, in handle
for a in artifacts_qs.iterator():
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/models/query.py",
line 341, in _iterator
yield from self._iterable_class(self, chunked_fetch=use_chunked_fetch,
chunk_size=chunk_size)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/models/query.py",
line 55, in __iter__
results = compiler.execute_sql(chunked_fetch=self.chunked_fetch,
chunk_size=self.chunk_size)
File
"/opt/utils/venv/pulp/3.8.8/lib64/python3.8/site-packages/django/db/models/sql/compiler.py",
line 1145, in execute_sql
cursor.close()
psycopg2.errors.InvalidCursorName: cursor "_django_curs_139896608020288_1" does
not exist
___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp 3.7.2 api 499 error
Our monitoring service watches the /pulp/api/v3/status to alert in case server(3.7.2) is down. We have recently experienced 499 error when the server is busy to configure resources and sync a few hundreds upstream repos. I noticed the pulpcore-api only has 1 worker by default. Will increasing the pulpcore-api workers help in this case?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp_rpm version
We are able to install the older version of pulp_rpm. Just wondering if this is supported or we should wait for the pulp_rpm 3.14 (pulp) bash-5.1$ pip list | grep pulp pulp-container 2.7.1 pulp-deb2.14.0 pulp-file 1.8.2 pulp-rpm3.13.3 pulpcore3.14.2 From: Bin Li (BLOOMBERG/ 120 PARK) At: 07/22/21 10:44:22 UTC-4:00To: pulp-list@redhat.com Subject: pulp_rpm version We used to have to install the same major version of pulp_rpm as the the pulpcore. Is this still the case or the older version of pulp_rpm works with the latest version of pulpcore?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp_rpm version
We used to have to install the same major version of pulp_rpm as the the pulpcore. Is this still the case or the older version of pulp_rpm works with the latest version of pulpcore?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] Installer error
Here is the version:click 8.0.1
rq 1.3.0
Tried to upgrade rq and got the following errors:
ERROR: pip's dependency resolver does not currently take into account all the
packages that are installed. This behaviour is the source of the following
dependency conflicts.
pulpcore 3.7.3 requires rq<1.6,>=1.1, but you have rq 1.9.0 which is
incompatible.
On our production server, I have click 7.1.2 and rq 1.3. Should I pin the
versions?
From: ggai...@redhat.com At: 07/06/21 16:30:23 UTC-4:00To: Bin Li (BLOOMBERG/
120 PARK )
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] Installer error
This looks like it's exactly the problem we had with pulp3, click-8, and rq:
https://pulp.plan.io/issues/8765
We are currently running 3.7.3 and would like to migrate to latest 3.14. I
tried to reinstall older version 3.7.3 so we can test the migration process.
Somehow the installation no longer works and gives the following errors.
RUNNING HANDLER [pulp_common : Collect static content]
***
fatal: [127.
What versions are you running for click and for rq, please?
G
On Tue, Jul 6, 2021 at 3:56 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
0.0.1]: FAILED! => {"changed": true, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/pulpcore-manager", "collectstatic",
"--noinput", "--link"], "delta": "0:00:02.861992", "end": "2021-07-06
15:19:20.270329", "msg": "non-zero return code", "rc": 1, "start": "2021-07-06
15:19:17.408337", "stderr": "Traceback (most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/bin/pulpcore-manager\", line 8, in \n
sys.exit(manage())\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/manage.py\",
line 11, in manage\nexecute_from_command_line(sys.argv)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
line 381, in execute_from_command_line\nutility.execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
line 357, in execute\ndjango.setup()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/__init__.py\",
line 24, in setup\napps.populate(settings.INSTALLED_APPS)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/apps/registry.py\",
line 122, in populate\napp_config.ready()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/apps.py\",
line 81, in ready\nself.import_viewsets()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/apps.py\",
line 110, in import_viewsets\nfrom pulpcore.app.viewsets import
NamedModelViewSet\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/viewsets/__init__.py\",
line 1, in \nfrom .base import ( # noqa\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/viewsets/base.py\",
line 17, in \nfrom pulpcore.app import tasks\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/tasks/__init__.py\",
line 5, in \nfrom .importer import pulp_import # noqa\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/tasks/importer.py\",
line 33, in \nfrom pulpcore.tasking.tasks import
enqueue_with_reservation\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/tasking/tasks.py\",
line 20, in \nfrom pulpcore.tasking import connection, util\n
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/tasking/connection.py\",
line 1, in \nfrom rq.cli.helpers import get_redis_from_config\n
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/cli/__init__.py\",
line 2, in \nfrom .cli import main\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/cli/cli.py\",
line 93, in \n@pass_cli_config\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/cli/cli.py\",
line 72, in pass_cli_config\nfunc = option(func)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/decorators.py\",
line 247, in decorator\n_param_memo(f, OptionClass(param_decls,
**option_attrs))\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 2482, in __init__\nsuper().__init__(param_decls, type=type,
multiple=multiple, **attrs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\&
Re: [Pulp-list] Content server Performance
We will look into upgrade 3.7.3 to 3.14.
For now, I have updated number of worker a few times. We are having 50 workers
running. I no longer see the timed out messages but the TIME_WAIT is still
around 5k.
# netstat -an | grep -i TIME_WAIT |grep 24816 | wc -l
5473
Also notice the database connection is over 60.
=> select count(*) from pg_stat_activity where usename = 'pulp';
count
---
63
(1 row)
Should I keep adding workers until the queue comes down? We still have plenty
of cpu and memory on the host.
From: bmbou...@redhat.com At: 06/22/21 12:01:30 UTC-4:00To:
danny.sa...@konghq.com
Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com
Subject: Re: [Pulp-list] Content server Performance
On Tue, Jun 22, 2021 at 11:56 AM Danny Sauer wrote:
You can certainly run multiple instances of the content server. It just needs
a connection to the database and access to the storage.
Agreed, you could deploy additional content servers and have your nginx/apache
load balance them.
Have you tuned the number of worker processes in Gunicorn? It defaults to 1,
but should almost certainly be increased for any sort of volume.
https://docs.gunicorn.org/en/stable/settings.html#worker-processes
Pulp changed the default gunicorn worker processes to 8 maybe a release or two
ago. See the `pulp_content_workers` variable in the installer here
https://pulp-installer.readthedocs.io/en/latest/roles/pulp_content/#role-variables
There are several moving pieces, but that's really all I had to touch here.
--Danny
With pulpcore==3.14 there is a significant performance improvement being
reviewed now https://pulp.plan.io/issues/8805 . In addition to resolving it
with methods like ^, when 3.14 comes out (scheduled for June 29th) it would be
great if you could report on if the improvements helped you.
On Tue, Jun 22, 2021 at 10:34 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
We recently add more clients to use the pulp content server. The processes run
out the file descriptor first. We then increased both nginx and pulp-content by
creating a override.conf
/etc/systemd/system/pulpcore-content.service.d # cat override.conf
[Service]
LimitNOFILE=65536
and updated nginx.conf
# Gunicorn docs suggest this value.
worker_processes 1;
events {
worker_connections 1; # increase if you have lots of clients
accept_mutex off; # set to 'on' if nginx worker_processes > 1
}
worker_rlimit_nofile2;
Now we are keep getting this error.
2021/06/22 11:26:36 [error] 78373#0: *112823 upstream timed out (110:
Connection timed out) while connecting to upstream, client:
It looks like pulp-content server cannot keep up with requests. Is there
anything we could do to increase the performance of the content
server?___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] Content server Performance
We added api workers but not the gunicorn worker. I noticed
ExecStart=/opt/utils/venv/pulp/3.7.3/bin/gunicorn pulpcore.content:server \
--bind '127.0.0.1:24816' \
--worker-class 'aiohttp.GunicornWebWorker' \
-w 2 \
--access-logfile -
I will update -w to 10 to see if it helps.
From: danny.sa...@konghq.com At: 06/22/21 11:55:53 UTC-4:00To: Bin Li
(BLOOMBERG/ 120 PARK )
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] Content server Performance
You can certainly run multiple instances of the content server. It just needs
a connection to the database and access to the storage.
Have you tuned the number of worker processes in Gunicorn? It defaults to 1,
but should almost certainly be increased for any sort of volume.
https://docs.gunicorn.org/en/stable/settings.html#worker-processes
There are several moving pieces, but that's really all I had to touch here.
--Danny
On Tue, Jun 22, 2021 at 10:34 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
We recently add more clients to use the pulp content server. The processes run
out the file descriptor first. We then increased both nginx and pulp-content by
creating a override.conf
/etc/systemd/system/pulpcore-content.service.d # cat override.conf
[Service]
LimitNOFILE=65536
and updated nginx.conf
# Gunicorn docs suggest this value.
worker_processes 1;
events {
worker_connections 1; # increase if you have lots of clients
accept_mutex off; # set to 'on' if nginx worker_processes > 1
}
worker_rlimit_nofile2;
Now we are keep getting this error.
2021/06/22 11:26:36 [error] 78373#0: *112823 upstream timed out (110:
Connection timed out) while connecting to upstream, client:
It looks like pulp-content server cannot keep up with requests. Is there
anything we could do to increase the performance of the content
server?___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] Content server Performance
We recently add more clients to use the pulp content server. The processes run
out the file descriptor first. We then increased both nginx and pulp-content by
creating a override.conf
/etc/systemd/system/pulpcore-content.service.d # cat override.conf
[Service]
LimitNOFILE=65536
and updated nginx.conf
# Gunicorn docs suggest this value.
worker_processes 1;
events {
worker_connections 1; # increase if you have lots of clients
accept_mutex off; # set to 'on' if nginx worker_processes > 1
}
worker_rlimit_nofile2;
Now we are keep getting this error.
2021/06/22 11:26:36 [error] 78373#0: *112823 upstream timed out (110:
Connection timed out) while connecting to upstream, client:
It looks like pulp-content server cannot keep up with requests. Is there
anything we could do to increase the performance of the content server?___
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp 3.7.3 aarch64 repo
zing.py", line 266, in synchronize Jun 18 14:47:28 pulpserver rq: dv.create() Jun 18 14:47:28 pulpserver rq: File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py", line 148, in create Jun 18 14:47:28 pulpserver rq: loop.run_until_complete(pipeline) Jun 18 14:47:28 pulpserver rq: File "/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py", line 584, in run_until_complete Jun 18 14:47:28 pulpserver rq: return future.result() Jun 18 14:47:28 pulpserver rq: File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py", line 225, in create_pipeline Jun 18 14:47:28 pulpserver rq: await asyncio.gather(*futures) Jun 18 14:47:28 pulpserver rq: File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py", line 43, in __call__ Jun 18 14:47:28 pulpserver rq: await self.run() Jun 18 14:47:28 pulpserver rq: File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/artifact_stages.py", line 152, in run Jun 18 14:47:28 pulpserver rq: pb.done += task.result() # download_count Jun 18 14:47:28 pulpserver rq: File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/artifact_stages.py", line 178, in _handle_content_unit Jun 18 14:47:28 pulpserver rq: await asyncio.gather(*downloaders_for_content) Jun 18 14:47:28 pulpserver rq: File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/models.py", line 88, in download Jun 18 14:47:28 pulpserver rq: download_result = await downloader.run(extra_data=self.extra_data) Jun 18 14:47:28 pulpserver rq: File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/download/base.py", line 227, in run Jun 18 14:47:28 pulpserver rq: return await self._run(extra_data=extra_data) Jun 18 14:47:28 pulpserver rq: File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/downloaders.py", line 87, in _run Jun 18 14:47:28 pulpserver rq: async with self.session.get(url, proxy=self.proxy, auth=self.auth) as response: Jun 18 14:47:28 pulpserver rq: File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/client.py", line 1012, in __aenter__ Jun 18 14:47:28 pulpserver rq: self._resp = await self._coro Jun 18 14:47:28 pulpserver rq: File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/client.py", line 504, in _request Jun 18 14:47:28 pulpserver rq: await resp.start(conn) Jun 18 14:47:28 pulpserver rq: File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/client_reqrep.py", line 847, in start Jun 18 14:47:28 pulpserver rq: message, payload = await self._protocol.read() # type: ignore # noqa Jun 18 14:47:28 pulpserver rq: File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/streams.py", line 591, in read Jun 18 14:47:28 pulpserver rq: await self._waiter Jun 18 14:47:28 pulpserver rq: aiohttp.client_exceptions.ServerDisconnectedError The aarch64 baseos repo completed successfully. From: dal...@redhat.com At: 06/18/21 10:55:56 UTC-4:00To: dkli...@redhat.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 aarch64 repo replace "but only with the errors" with "but only with the normal types of errors" On Fri, Jun 18, 2021 at 10:52 AM Daniel Alley wrote: @Bin Li Could you post the error that was logged? I think this traceback is missing some of the relevant details. I can tell you what I expect that problem *might* be, because we've been hearing about it a lot recently. Again, this is just a guess, without more information. We have found that some content delivery networks (including the Red Hat one) start returning seemingly irrelevant error messages when they get 'angry' about too much traffic coming from one source. Rather than returning HTTP 429 or some other standard response, sometimes it will just terminate the connection, or give you SSL errors, or return an incomplete payload. This might be some type of DDoS prevention / flood control mechanism, I'm not entirely sure. The mitigation is to either reduce the "download_concurrency" on your remote from 10 to 5, or using "on_demand" syncs rather than "immediate". Both of those are just to lessen the load on the CDN and make it less likely to start dropping connections. But the "proper" fix is being worked on for pulpcore 3.14. We want to automatically retry downloads that fail using a backoff algorithm to prevent the entire sync from failing. We were already doing this, but only with the errors, rather than the weird ones that seem to come up in practice. And we're making the number of retry attempts configurable. On Fri, Jun 18, 2021 at 9:04 AM D
[Pulp-list] pulp 3.7.3 aarch64 repo
Tried to download aarch64 repo and got the errors below: "description": "", "traceback": " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line 886, in perform_job\nrv = job.perform()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line 664, in perform\nself._result = self._execute()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line 670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\", line 266, in synchronize\ndv.create()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\", line 148, in create\nloop.run_until_complete(pipeline)\n File \"/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py\", line 584, in run_until_complete\nreturn future.result()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\", line 225, in create_pipeline\nawait asyncio.gather(*futures)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\", line 43, in __call__\nawait self.run()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/artifact_stages.py\", line 152, in run\npb.done += task.result() # download_count\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/artifact_stages.py\", line 178, in _handle_content_unit\nawait asyncio.gather(*downloaders_for_content)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/models.py\", line 88, in download\ndownload_result = await downloader.run(extra_data=self.extra_data)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/download/base.py\", line 227, in run\nreturn await self._run(extra_data=extra_data)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/downloaders.py\", line 87, in _run\nasync with self.session.get(url, proxy=self.proxy, auth=self.auth) as response:\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/client.py\", line 1012, in __aenter__\nself._resp = await self._coro\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/client.py\", line 504, in _request\nawait resp.start(conn)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/client_reqrep.py\", line 847, in start\nmessage, payload = await self._protocol.read() # type: ignore # noqa\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/streams.py\", line 591, in read\nawait self._waiter\n The same error happened on both remote https://cdn.redhat.com/content/dist/rhel8/8.4/aarch64/baseos/os and https://cdn.redhat.com/content/dist/rhel8/8.4/aarch64/appstream/os Please advise. Thanks___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp3 remote mirrorlist
Does the pulp support a mirrorlist as the remote url? If not, will this feature be added in the future?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] httpie query pulp 3 api
Thanks David. It worked perfectly. From: davidda...@redhat.com At: 05/20/21 16:29:21To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] httpie query pulp 3 api What about something like this? http :/pulp/api/v3/tasks/ state==failed started_at__gte=="2021-05-15T0:0:0.0Z" started_at__lte=="2021-05-20T0:0:0.0Z" This would find the failed tasks that started between 2021-05-15 and 2021-05-20. David On Thu, May 20, 2021 at 4:00 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: Just wondering if anyone knows how to use httpie to filter the result from the api. This query to get failed job works http GET localhost/pulp/api/v3/tasks/?limit=2 state==failed But I could not find a way to get failed jobs in a date range. The below query doesn't give me the correct result. http GET localhost/pulp/api/v3/tasks/ state==failed%20AND%20started_at%20%3E%3D%20"2021-05-15T0:0:0.0Z" Can I use httpie to filter or I have to pipe to jq?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] httpie query pulp 3 api
Just wondering if anyone knows how to use httpie to filter the result from the api. This query to get failed job works http GET localhost/pulp/api/v3/tasks/?limit=2 state==failed But I could not find a way to get failed jobs in a date range. The below query doesn't give me the correct result. http GET localhost/pulp/api/v3/tasks/ state==failed%20AND%20started_at%20%3E%3D%20"2021-05-15T0:0:0.0Z" Can I use httpie to filter or I have to pipe to jq?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
q: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django_lifecycle/mixins.py",
line 129, in save
Mar 22 17:01:51 pulp-dev1 rq: save(*args, **kwargs)
Mar 22 17:01:51 pulp-dev1 rq: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/base.py",
line 744, in save
Mar 22 17:01:51 pulp-dev1 rq: force_update=force_update,
update_fields=update_fields)
Mar 22 17:01:51 pulp-dev1 rq: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/base.py",
line 782, in save_base
Mar 22 17:01:51 pulp-dev1 rq: force_update, using, update_fields,
Mar 22 17:01:51 pulp-dev1 rq: result = self._do_insert(cls._base_manager,
using, fields, update_pk, raw)
Mar 22 17:01:51 pulp-dev1 rq: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/base.py",
line 911, in _do_insert
Mar 22 17:01:51 pulp-dev1 rq: using=using, raw=raw)
Mar 22 17:01:51 pulp-dev1 rq: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/manager.py",
line 82, in manager_method
Mar 22 17:01:51 pulp-dev1 rq: return getattr(self.get_queryset(), name)(*args,
**kwargs)
Mar 22 17:01:51 pulp-dev1 rq: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py",
line 1186, in _insert
Mar 22 17:01:51 pulp-dev1 rq: return
query.get_compiler(using=using).execute_sql(return_id)
Mar 22 17:01:51 pulp-dev1 rq: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py",
line 1377, in execute_sql
Mar 22 17:01:51 pulp-dev1 rq: cursor.execute(sql, params)
Mar 22 17:01:51 pulp-dev1 rq: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 67, in execute
Mar 22 17:01:51 pulp-dev1 rq: return self._execute_with_wrappers(sql, params,
many=False, executor=self._execute)
Mar 22 17:01:51 pulp-dev1 rq: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 76, in _execute_with_wrappers
Mar 22 17:01:51 pulp-dev1 rq: return executor(sql, params, many, context)
Mar 22 17:01:51 pulp-dev1 rq: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 85, in _execute
Mar 22 17:01:51 pulp-dev1 rq: return self.cursor.execute(sql, params)
Mar 22 17:01:51 pulp-dev1 rq: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py",
line 89, in __exit__
Mar 22 17:01:51 pulp-dev1 rq: raise dj_exc_value.with_traceback(traceback) from
exc_value
Mar 22 17:01:51 pulp-dev1 rq: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 85, in _execute
Mar 22 17:01:51 pulp-dev1 rq: return self.cursor.execute(sql, params)
Mar 22 17:01:51 pulp-dev1 rq: django.db.utils.IntegrityError: duplicate key
value violates unique constraint "rpm_package_pkgId_key"
Mar 22 17:01:51 pulp-dev1 rq: DETAIL: Key
("pkgId")=(6c6abbab55502947f3139e42b4ba32bebf87eb99) already exists.
Mar 22 17:01:51 pulp-dev1 rq: pulp: rq.worker:INFO:
51...@pulp-dev1.bloomberg.com: e8c66486-94ec-431f-9c7e-42b0120078d4
Mar 22 17:01:52 pulp-dev1 rq: pulp: rq.worker:INFO:
51...@pulp-dev1.bloomberg.com: Job OK (e8c66486-94ec-431f-9c7e-42b0120078d4)
From: davidda...@redhat.com At: 03/19/21 16:27:19To: Bin Li (BLOOMBERG/ 120
PARK )
Cc: dal...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
I'd be curious about the data that's causing this issue. Can you try applying
this patch and rerunning sync? It should give you more info about the existing
package that's causing the conflict.
https://gist.github.com/daviddavis/3716ff3a988be8a5d797da136c7b90bf
David
On Fri, Mar 19, 2021 at 3:27 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
The core_taskreservedresource is actually empty after restoring the database. I
found 2 tasks in waiting state from 10 month ago. I got a 409 conflict error
when try to delete them with api. I then deleted both tasks from core_task
table. The sync job was able to run but got the same "Package matching query
does not exist". It looks like the issue existed before we tried to sync a week
ago. I am not sure what else we can do except a reset of the database from
scratch. We don't add any packages locally. All packages are synced from the
upstream. The only concern is how to keep distributions with the same content.
Some of our distributions point to older version of repo. Is there a way to
make these distribution to have the same content after reset database?
From: dal...@redhat.com At: 03/19/21 11:08:32To: Bin Li (BLOOMBERG/ 120 PARK )
Cc: davidda...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
I believe the correct procedure is to stop the workers, delete all of the ite
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
The core_taskreservedresource is actually empty after restoring the database. I found 2 tasks in waiting state from 10 month ago. I got a 409 conflict error when try to delete them with api. I then deleted both tasks from core_task table. The sync job was able to run but got the same "Package matching query does not exist". It looks like the issue existed before we tried to sync a week ago. I am not sure what else we can do except a reset of the database from scratch. We don't add any packages locally. All packages are synced from the upstream. The only concern is how to keep distributions with the same content. Some of our distributions point to older version of repo. Is there a way to make these distribution to have the same content after reset database? From: dal...@redhat.com At: 03/19/21 11:08:32To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: davidda...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error I believe the correct procedure is to stop the workers, delete all of the items in the "reserved_resources" table, and restart the workers. You are still using Pulpcore 3.7, correct? Once this is sorted, I would recommend trying to upgrade... which I'm sure doesn't sound appealing right now... but a lot of work was done in the 3.9 - 3.10 timeframe to prevent tasking system deadlocks like this, as well as some improvements around being able to check for corrupted artifacts. https://yum.theforeman.org/pulpcore/3.9/ On Fri, Mar 19, 2021 at 9:25 AM Bin Li (BLOOMBERG/ 120 PARK) wrote: I tried to restore the database on a dev instance. I was able to recreate repo and remote with the restored database but the sync stucked on waiting. No other jobs was running. The dev instance has a different hostname. How do we find out why the sync job is in the waiting state? From: davidda...@redhat.com At: 03/18/21 15:30:29To: dal...@redhat.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error I'm guessing there's a package that got saved with a bad pkgId. I think what dalley recommends should work. I'd also make a backup of your current database in case rolling back causes bigger problems. David On Thu, Mar 18, 2021 at 2:32 PM Daniel Alley wrote: Restoring postgresql from tape should fix your database, yes. I'm not 100% sure what happens if the artifact store has untracked files, or missing files that the database expects to be there. In newer versions of pulpcore we have a "repair" feature to help deal with such issues, but 3.7 predates it. I would say, take a backup of your /var/lib/pulp directory and then try the database restore. On Thu, Mar 18, 2021 at 10:23 AM Bin Li (BLOOMBERG/ 120 PARK) wrote: We still need to restore our instance to the previous state before this happened. We already get the postgresql dump from tape. Will restoring database work in this case? From: dal...@redhat.com At: 03/17/21 14:45:15To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: bmbou...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Thanks! On Wed, Mar 17, 2021 at 11:34 AM Bin Li (BLOOMBERG/ 120 PARK) wrote: FYI, I filed a new issue https://pulp.plan.io/issues/8411 to track this. From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/16/21 15:31:14To: dal...@redhat.com, bmbou...@redhat.com Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error I checked the metadate from primary.xml. The sha1sum matches with actual file. http://linux.duke.edu/metadata/common; xmlns:rpm="http://linux.duke.edu/metadata/rpm;> flume noarch b8b257c32135daf51e703d439594f1a676871d7d # sha1sum flume-1.9.0-1.noarch.rpm b8b257c32135daf51e703d439594f1a676871d7d flume-1.9.0-1.noarch.rpm From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/16/21 15:06:43To: bmbou...@redhat.com, dal...@redhat.com Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error I downloaded the package and I didn't find the check_sum in rpm_checksum. # sha256sum flume-1.9.0-1.noarch.rpm c7fcec6d3385c079af6ed83cb272f52cbe2cb30ca93ed91732b1c8698b2ad76b flume-1.9.0-1.noarch.rpm => select checksum from rpm_checksum where checksum like '%a93ed91732b1c8698b2ad76b'; checksum -- (0 rows) Also,there is no result from core_contentartifact => select * from core_contentartifact where relative_path like '%flume%'; pulp_id | pulp_created | pulp_last_updated | relative_path | artifact_id | content_id -+--+---+---+-+ (0 rows) The upstream repo was fixed. I had no issues when I syncd from a fresh empty pulp instance. From: dal...@redhat.com At: 03/16/21 14:37:29To: bmbou...@redhat.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
We still need to restore our instance to the previous state before this happened. We already get the postgresql dump from tape. Will restoring database work in this case? From: dal...@redhat.com At: 03/17/21 14:45:15To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: bmbou...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Thanks! On Wed, Mar 17, 2021 at 11:34 AM Bin Li (BLOOMBERG/ 120 PARK) wrote: FYI, I filed a new issue https://pulp.plan.io/issues/8411 to track this. From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/16/21 15:31:14To: dal...@redhat.com, bmbou...@redhat.com Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error I checked the metadate from primary.xml. The sha1sum matches with actual file. http://linux.duke.edu/metadata/common; xmlns:rpm="http://linux.duke.edu/metadata/rpm;> flume noarch b8b257c32135daf51e703d439594f1a676871d7d # sha1sum flume-1.9.0-1.noarch.rpm b8b257c32135daf51e703d439594f1a676871d7d flume-1.9.0-1.noarch.rpm From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/16/21 15:06:43To: bmbou...@redhat.com, dal...@redhat.com Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error I downloaded the package and I didn't find the check_sum in rpm_checksum. # sha256sum flume-1.9.0-1.noarch.rpm c7fcec6d3385c079af6ed83cb272f52cbe2cb30ca93ed91732b1c8698b2ad76b flume-1.9.0-1.noarch.rpm => select checksum from rpm_checksum where checksum like '%a93ed91732b1c8698b2ad76b'; checksum -- (0 rows) Also,there is no result from core_contentartifact => select * from core_contentartifact where relative_path like '%flume%'; pulp_id | pulp_created | pulp_last_updated | relative_path | artifact_id | content_id -+--+---+---+-+ (0 rows) The upstream repo was fixed. I had no issues when I syncd from a fresh empty pulp instance. From: dal...@redhat.com At: 03/16/21 14:37:29To: bmbou...@redhat.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Also, the checksum of the package is stored as "pkgId" rather than as "checksum". Simply because that's what the RPM tools call it. There's no field actually named "checksum". pulp=> select * from rpm_package; content_ptr_id | name | epoch | version | release | arch | pkgId | checksum_type | summary | description | url | changelogs | files | requires | provides | conflicts | obsoletes | suggests | enhances | recommends | supplements | location _base | location_href | rpm_buildhost | rpm_group | rpm_license | rpm_packager | rpm_sourcerpm | rpm_vendor | rpm_header_start | rpm_header_end | is_modular | size_archive | size_installed | size_package | time_build | time_file | evr +--+---+-+-+--+---+---+-+-+-++---+--+--+---+---+--+--++-+- --+---+---+---+-+--+---++--+++--++--++---+- (0 rows) Going back to the original error though, this almost sounds like the file being downloaded doesn't match the checksum it's supposed to have. Received checksum b8b257c32135daf51e703d439594f1a676871d7d for http://something/something/flume-1.9.0-1.noarch.rpm but expected c281a94a354178c42800d47b63479c2621772351 Is there any chance you could manually download that file and verify its checksum, to make sure it's not corrupted at the source? On Tue, Mar 16, 2021 at 2:24 PM Daniel Alley wrote: I tried to read content from v3/content/. There is too much content to be listed. Not sure if I can specify a regex so I use select from db directly You can use query parameters when making HTTP calls against Pulp, like so: POST .../pulp/api/v3/content/packages/ name=flume There's a bunch of options available, they are documented here:https://pulp-rpm.readthedocs.io/en/latest/restapi.html#operation/content_rpm_packages_list On Tue, Mar 16, 2021 at 12:44 PM Brian Bouterse wrote: This doesn't help you today, but I think this type of use case is what motivates an API call like this one that is being discussed: https://pulp.plan.io/issues/8372 On Tue, Mar 16, 2021 at 12:30 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: I tried to read content from v3/content/. There is too much content to be listed. Not sure if I can specify a regex so I use select from db directly to see if I can find the package which causes the issue originally. The query returns 0 rows. It looks like it was cleaned out unless another content causes this
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
FYI, I filed a new issue https://pulp.plan.io/issues/8411 to track this. From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/16/21 15:31:14To: dal...@redhat.com, bmbou...@redhat.com Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error I checked the metadate from primary.xml. The sha1sum matches with actual file. http://linux.duke.edu/metadata/common; xmlns:rpm="http://linux.duke.edu/metadata/rpm;> flume noarch b8b257c32135daf51e703d439594f1a676871d7d # sha1sum flume-1.9.0-1.noarch.rpm b8b257c32135daf51e703d439594f1a676871d7d flume-1.9.0-1.noarch.rpm From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/16/21 15:06:43To: bmbou...@redhat.com, dal...@redhat.com Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error I downloaded the package and I didn't find the check_sum in rpm_checksum. # sha256sum flume-1.9.0-1.noarch.rpm c7fcec6d3385c079af6ed83cb272f52cbe2cb30ca93ed91732b1c8698b2ad76b flume-1.9.0-1.noarch.rpm => select checksum from rpm_checksum where checksum like '%a93ed91732b1c8698b2ad76b'; checksum -- (0 rows) Also,there is no result from core_contentartifact => select * from core_contentartifact where relative_path like '%flume%'; pulp_id | pulp_created | pulp_last_updated | relative_path | artifact_id | content_id -+--+---+---+-+ (0 rows) The upstream repo was fixed. I had no issues when I syncd from a fresh empty pulp instance. From: dal...@redhat.com At: 03/16/21 14:37:29To: bmbou...@redhat.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Also, the checksum of the package is stored as "pkgId" rather than as "checksum". Simply because that's what the RPM tools call it. There's no field actually named "checksum". pulp=> select * from rpm_package; content_ptr_id | name | epoch | version | release | arch | pkgId | checksum_type | summary | description | url | changelogs | files | requires | provides | conflicts | obsoletes | suggests | enhances | recommends | supplements | location _base | location_href | rpm_buildhost | rpm_group | rpm_license | rpm_packager | rpm_sourcerpm | rpm_vendor | rpm_header_start | rpm_header_end | is_modular | size_archive | size_installed | size_package | time_build | time_file | evr +--+---+-+-+--+---+---+-+-+-++---+--+--+---+---+--+--++-+- --+---+---+---+-+--+---++--+++--++--++---+- (0 rows) Going back to the original error though, this almost sounds like the file being downloaded doesn't match the checksum it's supposed to have. Received checksum b8b257c32135daf51e703d439594f1a676871d7d for http://something/something/flume-1.9.0-1.noarch.rpm but expected c281a94a354178c42800d47b63479c2621772351 Is there any chance you could manually download that file and verify its checksum, to make sure it's not corrupted at the source? On Tue, Mar 16, 2021 at 2:24 PM Daniel Alley wrote: I tried to read content from v3/content/. There is too much content to be listed. Not sure if I can specify a regex so I use select from db directly You can use query parameters when making HTTP calls against Pulp, like so: POST .../pulp/api/v3/content/packages/ name=flume There's a bunch of options available, they are documented here:https://pulp-rpm.readthedocs.io/en/latest/restapi.html#operation/content_rpm_packages_list On Tue, Mar 16, 2021 at 12:44 PM Brian Bouterse wrote: This doesn't help you today, but I think this type of use case is what motivates an API call like this one that is being discussed: https://pulp.plan.io/issues/8372 On Tue, Mar 16, 2021 at 12:30 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: I tried to read content from v3/content/. There is too much content to be listed. Not sure if I can specify a regex so I use select from db directly to see if I can find the package which causes the issue originally. The query returns 0 rows. It looks like it was cleaned out unless another content causes this issue. Let me know if there is anything else I can try. Below is what I have tried. The original error: Received checksum b8b257c32135daf51e703d439594f1a676871d7d for http://something/something/flume-1.9.0-1.noarch.rpm but expected c281a94a354178c42800d47b63479c2621772351 => select name from rpm_package where name like 'flume%' limit 100; name -- (0 rows) => select checksum from rpm_checksum where checksum like '%594f1a676871
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
I checked the metadate from primary.xml. The sha1sum matches with actual file. http://linux.duke.edu/metadata/common; xmlns:rpm="http://linux.duke.edu/metadata/rpm;> flume noarch b8b257c32135daf51e703d439594f1a676871d7d # sha1sum flume-1.9.0-1.noarch.rpm b8b257c32135daf51e703d439594f1a676871d7d flume-1.9.0-1.noarch.rpm From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/16/21 15:06:43To: bmbou...@redhat.com, dal...@redhat.com Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error I downloaded the package and I didn't find the check_sum in rpm_checksum. # sha256sum flume-1.9.0-1.noarch.rpm c7fcec6d3385c079af6ed83cb272f52cbe2cb30ca93ed91732b1c8698b2ad76b flume-1.9.0-1.noarch.rpm => select checksum from rpm_checksum where checksum like '%a93ed91732b1c8698b2ad76b'; checksum -- (0 rows) Also,there is no result from core_contentartifact => select * from core_contentartifact where relative_path like '%flume%'; pulp_id | pulp_created | pulp_last_updated | relative_path | artifact_id | content_id -+--+---+---+-+ (0 rows) The upstream repo was fixed. I had no issues when I syncd from a fresh empty pulp instance. From: dal...@redhat.com At: 03/16/21 14:37:29To: bmbou...@redhat.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Also, the checksum of the package is stored as "pkgId" rather than as "checksum". Simply because that's what the RPM tools call it. There's no field actually named "checksum". pulp=> select * from rpm_package; content_ptr_id | name | epoch | version | release | arch | pkgId | checksum_type | summary | description | url | changelogs | files | requires | provides | conflicts | obsoletes | suggests | enhances | recommends | supplements | location _base | location_href | rpm_buildhost | rpm_group | rpm_license | rpm_packager | rpm_sourcerpm | rpm_vendor | rpm_header_start | rpm_header_end | is_modular | size_archive | size_installed | size_package | time_build | time_file | evr +--+---+-+-+--+---+---+-+-+-++---+--+--+---+---+--+--++-+- --+---+---+---+-+--+---++--+++--++--++---+- (0 rows) Going back to the original error though, this almost sounds like the file being downloaded doesn't match the checksum it's supposed to have. Received checksum b8b257c32135daf51e703d439594f1a676871d7d for http://something/something/flume-1.9.0-1.noarch.rpm but expected c281a94a354178c42800d47b63479c2621772351 Is there any chance you could manually download that file and verify its checksum, to make sure it's not corrupted at the source? On Tue, Mar 16, 2021 at 2:24 PM Daniel Alley wrote: I tried to read content from v3/content/. There is too much content to be listed. Not sure if I can specify a regex so I use select from db directly You can use query parameters when making HTTP calls against Pulp, like so: POST .../pulp/api/v3/content/packages/ name=flume There's a bunch of options available, they are documented here:https://pulp-rpm.readthedocs.io/en/latest/restapi.html#operation/content_rpm_packages_list On Tue, Mar 16, 2021 at 12:44 PM Brian Bouterse wrote: This doesn't help you today, but I think this type of use case is what motivates an API call like this one that is being discussed: https://pulp.plan.io/issues/8372 On Tue, Mar 16, 2021 at 12:30 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: I tried to read content from v3/content/. There is too much content to be listed. Not sure if I can specify a regex so I use select from db directly to see if I can find the package which causes the issue originally. The query returns 0 rows. It looks like it was cleaned out unless another content causes this issue. Let me know if there is anything else I can try. Below is what I have tried. The original error: Received checksum b8b257c32135daf51e703d439594f1a676871d7d for http://something/something/flume-1.9.0-1.noarch.rpm but expected c281a94a354178c42800d47b63479c2621772351 => select name from rpm_package where name like 'flume%' limit 100; name -- (0 rows) => select checksum from rpm_checksum where checksum like '%594f1a676871d7d' OR checksum like '%63479c2621772351'; checksum -- (0 rows) From: dal...@redhat.com At: 03/15/21 11:03:48To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: davidda...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum e
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
I downloaded the package and I didn't find the check_sum in rpm_checksum. # sha256sum flume-1.9.0-1.noarch.rpm c7fcec6d3385c079af6ed83cb272f52cbe2cb30ca93ed91732b1c8698b2ad76b flume-1.9.0-1.noarch.rpm => select checksum from rpm_checksum where checksum like '%a93ed91732b1c8698b2ad76b'; checksum -- (0 rows) Also,there is no result from core_contentartifact => select * from core_contentartifact where relative_path like '%flume%'; pulp_id | pulp_created | pulp_last_updated | relative_path | artifact_id | content_id -+--+---+---+-+ (0 rows) The upstream repo was fixed. I had no issues when I syncd from a fresh empty pulp instance. From: dal...@redhat.com At: 03/16/21 14:37:29To: bmbou...@redhat.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Also, the checksum of the package is stored as "pkgId" rather than as "checksum". Simply because that's what the RPM tools call it. There's no field actually named "checksum". pulp=> select * from rpm_package; content_ptr_id | name | epoch | version | release | arch | pkgId | checksum_type | summary | description | url | changelogs | files | requires | provides | conflicts | obsoletes | suggests | enhances | recommends | supplements | location _base | location_href | rpm_buildhost | rpm_group | rpm_license | rpm_packager | rpm_sourcerpm | rpm_vendor | rpm_header_start | rpm_header_end | is_modular | size_archive | size_installed | size_package | time_build | time_file | evr +--+---+-+-+--+---+---+-+-+-++---+--+--+---+---+--+--++-+- --+---+---+---+-+--+---++--+++--++--++---+- (0 rows) Going back to the original error though, this almost sounds like the file being downloaded doesn't match the checksum it's supposed to have. Received checksum b8b257c32135daf51e703d439594f1a676871d7d for http://something/something/flume-1.9.0-1.noarch.rpm but expected c281a94a354178c42800d47b63479c2621772351 Is there any chance you could manually download that file and verify its checksum, to make sure it's not corrupted at the source? On Tue, Mar 16, 2021 at 2:24 PM Daniel Alley wrote: I tried to read content from v3/content/. There is too much content to be listed. Not sure if I can specify a regex so I use select from db directly You can use query parameters when making HTTP calls against Pulp, like so: POST .../pulp/api/v3/content/packages/ name=flume There's a bunch of options available, they are documented here:https://pulp-rpm.readthedocs.io/en/latest/restapi.html#operation/content_rpm_packages_list On Tue, Mar 16, 2021 at 12:44 PM Brian Bouterse wrote: This doesn't help you today, but I think this type of use case is what motivates an API call like this one that is being discussed: https://pulp.plan.io/issues/8372 On Tue, Mar 16, 2021 at 12:30 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: I tried to read content from v3/content/. There is too much content to be listed. Not sure if I can specify a regex so I use select from db directly to see if I can find the package which causes the issue originally. The query returns 0 rows. It looks like it was cleaned out unless another content causes this issue. Let me know if there is anything else I can try. Below is what I have tried. The original error: Received checksum b8b257c32135daf51e703d439594f1a676871d7d for http://something/something/flume-1.9.0-1.noarch.rpm but expected c281a94a354178c42800d47b63479c2621772351 => select name from rpm_package where name like 'flume%' limit 100; name -- (0 rows) => select checksum from rpm_checksum where checksum like '%594f1a676871d7d' OR checksum like '%63479c2621772351'; checksum -- (0 rows) From: dal...@redhat.com At: 03/15/21 11:03:48To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: davidda...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Do you know if that package could possibly have been present in any other repositories also? If you know which content unit it is, try accessing it via the content API after having done the orphan cleanup. If it still exists, it wasn't cleaned up for some reason, which may mean it's used by some other repository. This is... interesting. Pulp seems to be attempting to save the package, hitting an IntegrityError because it already exists (expected), and then trying to retrieve the package, and not being able to find it.
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
I tried to read content from v3/content/. There is too much content to be
listed. Not sure if I can specify a regex so I use select from db directly to
see if I can find the package which causes the issue originally. The query
returns 0 rows. It looks like it was cleaned out unless another content causes
this issue. Let me know if there is anything else I can try.
Below is what I have tried.
The original error:
Received checksum b8b257c32135daf51e703d439594f1a676871d7d for
http://something/something/flume-1.9.0-1.noarch.rpm but expected
c281a94a354178c42800d47b63479c2621772351
=> select name from rpm_package where name like 'flume%' limit 100;
name
--
(0 rows)
=> select checksum from rpm_checksum where checksum like '%594f1a676871d7d' OR
checksum like '%63479c2621772351';
checksum
--
(0 rows)
From: dal...@redhat.com At: 03/15/21 11:03:48To: Bin Li (BLOOMBERG/ 120 PARK )
Cc: davidda...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
Do you know if that package could possibly have been present in any other
repositories also? If you know which content unit it is, try accessing it via
the content API after having done the orphan cleanup. If it still exists, it
wasn't cleaned up for some reason, which may mean it's used by some other
repository.
This is... interesting. Pulp seems to be attempting to save the package,
hitting an IntegrityError because it already exists (expected), and then trying
to retrieve the package, and not being able to find it.
Please file an issue with all the information you've posted so far, we will
look into how this could be happening.
On Mon, Mar 15, 2021 at 9:37 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
I deleted the repo which failed sync and run "delete
localhost/pulp/api/v3/orphans/" but I am still getting the same messages.
From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/12/21 12:18:44To: dal...@redhat.com
Cc: davidda...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
Hi Dan,
Here is the traceback?
"error": {
"description": "Package matching query does not exist.",
"traceback": " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line
886, in perform_job\nrv = job.perform()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
664, in perform\nself._result = self._execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
line 266, in synchronize\ndv.create()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\",
line 148, in create\nloop.run_until_complete(pipeline)\n File
\"/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py\", line 584, in
run_until_complete\nreturn future.result()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\",
line 225, in create_pipeline\nawait asyncio.gather(*futures)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\",
line 43, in __call__\nawait self.run()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/content_stages.py\",
line 105, in run\nd_content.content.q()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/manager.py\",
line 82, in manager_method\nreturn getattr(self.get_queryset(),
name)(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\",
line 408, in get\n self.model._meta.object_name\n"
I will try removing the repo first and deleting orphans.
From: dal...@redhat.com At: 03/12/21 11:19:17To: Bin Li (BLOOMBERG/ 120 PARK )
Cc: davidda...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
Hi Bin,
It's difficult to understand what exactly this error is. Is it an error
message being printed out nicely, or part of a Python exception bubbling up?
And if it's the latter, do you have the rest of the traceback?
You can't manually delete specific content units but you can delete "orphan"
content units that aren't part of any repository. So if you know the content
unit in question, you can delete it from your repositories, and then run orphan
cleanup.
On Thu, Mar 11, 2021 at 11:27 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
If inconsistent repo data can cause Pulp to become unrecoverable, this is very
difficult to preven
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
I deleted the repo which failed sync and run "delete
localhost/pulp/api/v3/orphans/" but I am still getting the same messages.
From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/12/21 12:18:44To: dal...@redhat.com
Cc: davidda...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
Hi Dan,
Here is the traceback?
"error": {
"description": "Package matching query does not exist.",
"traceback": " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line
886, in perform_job\nrv = job.perform()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
664, in perform\nself._result = self._execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
line 266, in synchronize\ndv.create()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\",
line 148, in create\nloop.run_until_complete(pipeline)\n File
\"/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py\", line 584, in
run_until_complete\nreturn future.result()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\",
line 225, in create_pipeline\nawait asyncio.gather(*futures)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\",
line 43, in __call__\nawait self.run()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/content_stages.py\",
line 105, in run\nd_content.content.q()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/manager.py\",
line 82, in manager_method\nreturn getattr(self.get_queryset(),
name)(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\",
line 408, in get\n self.model._meta.object_name\n"
I will try removing the repo first and deleting orphans.
From: dal...@redhat.com At: 03/12/21 11:19:17To: Bin Li (BLOOMBERG/ 120 PARK )
Cc: davidda...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
Hi Bin,
It's difficult to understand what exactly this error is. Is it an error
message being printed out nicely, or part of a Python exception bubbling up?
And if it's the latter, do you have the rest of the traceback?
You can't manually delete specific content units but you can delete "orphan"
content units that aren't part of any repository. So if you know the content
unit in question, you can delete it from your repositories, and then run orphan
cleanup.
On Thu, Mar 11, 2021 at 11:27 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
If inconsistent repo data can cause Pulp to become unrecoverable, this is very
difficult to prevent. Any inconsistent updates from upstream could potentially
cause this to happen. At this point, we are thinking to restore the database
from the backup before this sync issue happened, will this approach work?
From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/10/21 14:41:38To:
davidda...@redhat.com
Cc: bmbou...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
We know the rpm name which has different check sum with repodata and caused the
sync failure earlier. I am guessing the current issue is caused by this rpm. Is
there any way we can remove it from database?
From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/09/21 17:47:17To:
davidda...@redhat.com
Cc: bmbou...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
Please ignore the last message. It is irrelevant.
We actually able to sync the upstream repo successfully after we reset the
database. The question is how to we recover from previous failure? We keep
getting "Package matching query does not exist." without reset the database.
Recreating the repo didn't help either.
From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/09/21 17:06:53To:
davidda...@redhat.com
Cc: bmbou...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
It looks like the last error caused failed sync process. I reset the db on a
dev host and try to sync the same upstream repo and got
""An error occurred (QuotaExceeded) when calling the PutObject operation:
Unknown"
Any idea how to fix this?
"traceback": " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line
886, in perform_job\nrv =
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
Hi Dan,
Here is the traceback?
"error": {
"description": "Package matching query does not exist.",
"traceback": " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line
886, in perform_job\nrv = job.perform()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
664, in perform\nself._result = self._execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
line 266, in synchronize\ndv.create()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\",
line 148, in create\nloop.run_until_complete(pipeline)\n File
\"/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py\", line 584, in
run_until_complete\nreturn future.result()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\",
line 225, in create_pipeline\nawait asyncio.gather(*futures)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\",
line 43, in __call__\nawait self.run()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/content_stages.py\",
line 105, in run\nd_content.content.q()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/manager.py\",
line 82, in manager_method\nreturn getattr(self.get_queryset(),
name)(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\",
line 408, in get\nself.model._meta.object_name\n"
I will try removing the repo first and deleting orphans.
From: dal...@redhat.com At: 03/12/21 11:19:17To: Bin Li (BLOOMBERG/ 120 PARK )
Cc: davidda...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
Hi Bin,
It's difficult to understand what exactly this error is. Is it an error
message being printed out nicely, or part of a Python exception bubbling up?
And if it's the latter, do you have the rest of the traceback?
You can't manually delete specific content units but you can delete "orphan"
content units that aren't part of any repository. So if you know the content
unit in question, you can delete it from your repositories, and then run orphan
cleanup.
On Thu, Mar 11, 2021 at 11:27 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
If inconsistent repo data can cause Pulp to become unrecoverable, this is very
difficult to prevent. Any inconsistent updates from upstream could potentially
cause this to happen. At this point, we are thinking to restore the database
from the backup before this sync issue happened, will this approach work?
From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/10/21 14:41:38To:
davidda...@redhat.com
Cc: bmbou...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
We know the rpm name which has different check sum with repodata and caused the
sync failure earlier. I am guessing the current issue is caused by this rpm. Is
there any way we can remove it from database?
From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/09/21 17:47:17To:
davidda...@redhat.com
Cc: bmbou...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
Please ignore the last message. It is irrelevant.
We actually able to sync the upstream repo successfully after we reset the
database. The question is how to we recover from previous failure? We keep
getting "Package matching query does not exist." without reset the database.
Recreating the repo didn't help either.
From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/09/21 17:06:53To:
davidda...@redhat.com
Cc: bmbou...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error
It looks like the last error caused failed sync process. I reset the db on a
dev host and try to sync the same upstream repo and got
""An error occurred (QuotaExceeded) when calling the PutObject operation:
Unknown"
Any idea how to fix this?
"traceback": " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line
886, in perform_job\nrv = job.perform()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
664, in perform\nself._result = self._execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
670, in _execute\nreturn self.func(*self.args, **self.kwargs)\
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
If inconsistent repo data can cause Pulp to become unrecoverable, this is very difficult to prevent. Any inconsistent updates from upstream could potentially cause this to happen. At this point, we are thinking to restore the database from the backup before this sync issue happened, will this approach work? From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/10/21 14:41:38To: davidda...@redhat.com Cc: bmbou...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error We know the rpm name which has different check sum with repodata and caused the sync failure earlier. I am guessing the current issue is caused by this rpm. Is there any way we can remove it from database? From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/09/21 17:47:17To: davidda...@redhat.com Cc: bmbou...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Please ignore the last message. It is irrelevant. We actually able to sync the upstream repo successfully after we reset the database. The question is how to we recover from previous failure? We keep getting "Package matching query does not exist." without reset the database. Recreating the repo didn't help either. From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/09/21 17:06:53To: davidda...@redhat.com Cc: bmbou...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error It looks like the last error caused failed sync process. I reset the db on a dev host and try to sync the same upstream repo and got ""An error occurred (QuotaExceeded) when calling the PutObject operation: Unknown" Any idea how to fix this? "traceback": " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line 886, in perform_job\nrv = job.perform()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line 664, in perform\nself._result = self._execute()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line 670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\", line 266, in synchronize\ndv.create()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\", line 148, in create\nloop.run_until_complete(pipeline)\n File \"/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py\", line 584, in run_until_complete\nreturn future.result()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\", line 225, in create_pipeline\nawait asyncio.gather(*futures)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\", line 43, in __call__\nawait self.run()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/artifact_stages.py\", line 219, in run\nd_artifact.artifact for d_artifact in da_to_save\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/models/content.py\", line 87, in bulk_get_or_create\nreturn super().bulk_create(objs, batch_size=batch_size)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/manager.py\", line 82, in manager_method\nreturn getattr(self.get_queryset(), name)(*args, **kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\", line 468, in bulk_create\nself._batched_insert(objs_with_pk, fields, batch_size, ignore_conflicts=ignore_conflicts)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\", line 1204, in _batched_insert\nignore_conflicts=ignore_conflicts,\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\", line 1186, in _insert\nreturn query.get_compiler(using=using).execute_sql(return_id)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1376, in execute_sql\nfor sql, params in self.as_sql():\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django_readonly_field/compiler.py\", line 31, in as_sql\nreturn super(ReadonlySQLCompilerMixin, self).as_sql()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1320, in as_sql\nfor obj in self.query.objs\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1320, in \nfor obj in self.query.objs\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
We know the rpm name which has different check sum with repodata and caused the sync failure earlier. I am guessing the current issue is caused by this rpm. Is there any way we can remove it from database? From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/09/21 17:47:17To: davidda...@redhat.com Cc: bmbou...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Please ignore the last message. It is irrelevant. We actually able to sync the upstream repo successfully after we reset the database. The question is how to we recover from previous failure? We keep getting "Package matching query does not exist." without reset the database. Recreating the repo didn't help either. From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/09/21 17:06:53To: davidda...@redhat.com Cc: bmbou...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error It looks like the last error caused failed sync process. I reset the db on a dev host and try to sync the same upstream repo and got ""An error occurred (QuotaExceeded) when calling the PutObject operation: Unknown" Any idea how to fix this? "traceback": " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line 886, in perform_job\nrv = job.perform()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line 664, in perform\nself._result = self._execute()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line 670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\", line 266, in synchronize\ndv.create()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\", line 148, in create\nloop.run_until_complete(pipeline)\n File \"/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py\", line 584, in run_until_complete\nreturn future.result()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\", line 225, in create_pipeline\nawait asyncio.gather(*futures)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\", line 43, in __call__\nawait self.run()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/artifact_stages.py\", line 219, in run\nd_artifact.artifact for d_artifact in da_to_save\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/models/content.py\", line 87, in bulk_get_or_create\nreturn super().bulk_create(objs, batch_size=batch_size)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/manager.py\", line 82, in manager_method\nreturn getattr(self.get_queryset(), name)(*args, **kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\", line 468, in bulk_create\nself._batched_insert(objs_with_pk, fields, batch_size, ignore_conflicts=ignore_conflicts)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\", line 1204, in _batched_insert\nignore_conflicts=ignore_conflicts,\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\", line 1186, in _insert\nreturn query.get_compiler(using=using).execute_sql(return_id)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1376, in execute_sql\nfor sql, params in self.as_sql():\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django_readonly_field/compiler.py\", line 31, in as_sql\nreturn super(ReadonlySQLCompilerMixin, self).as_sql()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1320, in as_sql\nfor obj in self.query.objs\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1320, in \nfor obj in self.query.objs\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1319, in \n[self.prepare_value(field, self.pre_save_val(field, obj)) for field in fields]\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1270, in pre_save_val\nreturn field.pre_save(obj, add=True)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/models/fields.py\", line 68, in pre_save\nreturn super().pre_save(model_instance, add)\
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
Please ignore the last message. It is irrelevant. We actually able to sync the upstream repo successfully after we reset the database. The question is how to we recover from previous failure? We keep getting "Package matching query does not exist." without reset the database. Recreating the repo didn't help either. From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/09/21 17:06:53To: davidda...@redhat.com Cc: bmbou...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error It looks like the last error caused failed sync process. I reset the db on a dev host and try to sync the same upstream repo and got ""An error occurred (QuotaExceeded) when calling the PutObject operation: Unknown" Any idea how to fix this? "traceback": " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line 886, in perform_job\nrv = job.perform()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line 664, in perform\nself._result = self._execute()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line 670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\", line 266, in synchronize\ndv.create()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\", line 148, in create\nloop.run_until_complete(pipeline)\n File \"/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py\", line 584, in run_until_complete\nreturn future.result()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\", line 225, in create_pipeline\nawait asyncio.gather(*futures)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\", line 43, in __call__\nawait self.run()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/artifact_stages.py\", line 219, in run\nd_artifact.artifact for d_artifact in da_to_save\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/models/content.py\", line 87, in bulk_get_or_create\nreturn super().bulk_create(objs, batch_size=batch_size)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/manager.py\", line 82, in manager_method\nreturn getattr(self.get_queryset(), name)(*args, **kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\", line 468, in bulk_create\nself._batched_insert(objs_with_pk, fields, batch_size, ignore_conflicts=ignore_conflicts)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\", line 1204, in _batched_insert\nignore_conflicts=ignore_conflicts,\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\", line 1186, in _insert\nreturn query.get_compiler(using=using).execute_sql(return_id)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1376, in execute_sql\nfor sql, params in self.as_sql():\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django_readonly_field/compiler.py\", line 31, in as_sql\nreturn super(ReadonlySQLCompilerMixin, self).as_sql()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1320, in as_sql\nfor obj in self.query.objs\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1320, in \nfor obj in self.query.objs\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1319, in \n[self.prepare_value(field, self.pre_save_val(field, obj)) for field in fields]\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\", line 1270, in pre_save_val\nreturn field.pre_save(obj, add=True)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/models/fields.py\", line 68, in pre_save\nreturn super().pre_save(model_instance, add)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/fields/files.py\", line 288, in pre_save\nfile.save(file.name, file.file, save=False)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/fields/files.py\", line 87, in save\nself.name = self.storage.save(name, content, max_length=self.field.max_len
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
ck=Callback, Config=Config)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/boto3/s3/inject.py\", line 539, in upload_fileobj\nreturn future.result()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/s3transfer/futures.py\", line 106, in result\nreturn self._coordinator.result()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/s3transfer/futures.py\", line 265, in result\nraise self._exception\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/s3transfer/tasks.py\", line 126, in __call__\nreturn self._execute_main(kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/s3transfer/tasks.py\", line 150, in _execute_main\nreturn_value = self._main(**kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/s3transfer/upload.py\", line 692, in _main\nclient.put_object(Bucket=bucket, Key=key, Body=body, **extra_args)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/botocore/client.py\", line 357, in _api_call\nreturn self._make_api_call(operation_name, kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/botocore/client.py\", line 676, in _make_api_call\nraise error_class(parsed_response, operation_name)\n" From: Bin Li (BLOOMBERG/ 120 PARK) At: 03/09/21 11:34:57To: davidda...@redhat.com Cc: bmbou...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Got a new errors "Package matching query does not exist.". Is this also related to upstream repo? Can we have more details when this happens? From: davidda...@redhat.com At: 03/05/21 15:06:40To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: bmbou...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Great, thanks for the update. David On Fri, Mar 5, 2021 at 2:47 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: Thanks Dave. Got the filename which has the inconsistent checksum after patching. We will ask upstream remote to update the repodata. From: davidda...@redhat.com At: 03/05/21 12:42:56To: bmbou...@redhat.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Regarding the error message, I've observed the problem myself. and have filed an issue: https://pulp.plan.io/issues/8357 In the meantime, if you can patch the code, this should tell you give you more info: https://gist.github.com/daviddavis/2e6ab1872d97230d144a6cd1f9d05e31 David On Fri, Mar 5, 2021 at 12:35 PM Brian Bouterse wrote: Did this happen inside a task? Did you see a traceback for it also? On Fri, Mar 5, 2021 at 12:00 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: The sync process gave an error "A file failed validation due to checksum". Is this error caused by remote repo? Is there a way to find out which file cause the issue?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
Got a new errors "Package matching query does not exist.". Is this also related to upstream repo? Can we have more details when this happens? From: davidda...@redhat.com At: 03/05/21 15:06:40To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: bmbou...@redhat.com, pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Great, thanks for the update. David On Fri, Mar 5, 2021 at 2:47 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: Thanks Dave. Got the filename which has the inconsistent checksum after patching. We will ask upstream remote to update the repodata. From: davidda...@redhat.com At: 03/05/21 12:42:56To: bmbou...@redhat.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Regarding the error message, I've observed the problem myself. and have filed an issue: https://pulp.plan.io/issues/8357 In the meantime, if you can patch the code, this should tell you give you more info: https://gist.github.com/daviddavis/2e6ab1872d97230d144a6cd1f9d05e31 David On Fri, Mar 5, 2021 at 12:35 PM Brian Bouterse wrote: Did this happen inside a task? Did you see a traceback for it also? On Fri, Mar 5, 2021 at 12:00 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: The sync process gave an error "A file failed validation due to checksum". Is this error caused by remote repo? Is there a way to find out which file cause the issue?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp 3.7.3 sync with checksum error
Thanks Dave. Got the filename which has the inconsistent checksum after patching. We will ask upstream remote to update the repodata. From: davidda...@redhat.com At: 03/05/21 12:42:56To: bmbou...@redhat.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.3 sync with checksum error Regarding the error message, I've observed the problem myself. and have filed an issue: https://pulp.plan.io/issues/8357 In the meantime, if you can patch the code, this should tell you give you more info: https://gist.github.com/daviddavis/2e6ab1872d97230d144a6cd1f9d05e31 David On Fri, Mar 5, 2021 at 12:35 PM Brian Bouterse wrote: Did this happen inside a task? Did you see a traceback for it also? On Fri, Mar 5, 2021 at 12:00 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: The sync process gave an error "A file failed validation due to checksum". Is this error caused by remote repo? Is there a way to find out which file cause the issue?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp 3.7.3 sync with checksum error
The sync process gave an error "A file failed validation due to checksum". Is this error caused by remote repo? Is there a way to find out which file cause the issue?___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] mirrored sync in 3.7.3
I noticed the repomd.xml on artifactory is a little different (see below). This is why pulp doesn't sync when optimize is true. Is the revision optional field in repomd.xml? http://linux.duke.edu/metadata/repo; xmlns:rpm="http://linux.duke.edu/metadata/rpm;> deddaac9159b0dd137637e3f054699ed835c2188 55565 1610569598 440b3887bd333a9f198daf8d11d883c39b9cfa6b 163364 2ab424ed2e5cb27ded110002678a64efe61fdc6c 722 1610569598 7b21b424589b3d0fcbfb5e78b5eb21441a739dd5 3064 18af240dc9319adc1fc746da197f195d35d3fca6 1724 1610569599 49ad32d347e2bde51dd070085cbe145b0146faf4 9708 From: dkli...@redhat.com At: 01/13/21 14:36:27To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] mirrored sync in 3.7.3 The sync task examines the repomd.xml and the revision number in it. All the logic for optimizing the sync is here[0]. [0] https://github.com/pulp/pulp_rpm/blob/3.7/pulp_rpm/app/tasks/synchronizing.py#L169-L175 On Wed, Jan 13, 2021 at 1:45 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: Happy new year. I run a mirrored sync with upstream. The sync didn't pick up new rpms in upstream repo. I rerun sync with optimize=false and it synced all rpms. I do see the file names from new rpms are in the filelists.xml.gz of the upstream repodata. Just wondering which repo data does pulp check before starting a optimized mirror sync and why the optimized sync didn't work?___ 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] mirrored sync in 3.7.3
Happy new year. I run a mirrored sync with upstream. The sync didn't pick up new rpms in upstream repo. I rerun sync with optimize=false and it synced all rpms. I do see the file names from new rpms are in the filelists.xml.gz of the upstream repodata. Just wondering which repo data does pulp check before starting a optimized mirror sync and why the optimized sync didn't work?___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] Database migration from 3.3 to 3.7
We are running rhel7.6. The installer was stuck on database migration for almost 2 hours. It eventually went through. Not sure why it took such a long time. I was wondering if I should send a break. I saved pg_stat_activity output from postgresql. My question is if I can tell the progress of the database migration from any logs or postgresql so I know if the process is really got stuck or just very slow? From: bmbou...@redhat.com At: 12/05/20 10:46:19To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] Database migration from 3.3 to 3.7 Maybe it's selinux labeling related. What step is it stuck on in the installer's output? What OS are you using? On Sat, Dec 5, 2020 at 9:48 AM Bin Li (BLOOMBERG/ 120 PARK) wrote: We are upgrading pulp from 3.3 to 3.7. Ansible stuck on database migration for more that 50 mins. We have 1.5T of artifact in file system. The database size is about 25G. Is this normal? Is there a way we can check the progress log? ___ 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] Database migration from 3.3 to 3.7
We are upgrading pulp from 3.3 to 3.7. Ansible stuck on database migration for more that 50 mins. We have 1.5T of artifact in file system. The database size is about 25G. Is this normal? Is there a way we can check the progress log? ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] sync issue on 3.7.3
Thanks. Here is the info On Test Server with 3.7.3# pip freeze aiodns==2.0.0 aiofiles==0.6.0 aiohttp==3.7.2 ansible==2.10.1 ansible-base==2.10.2 async-timeout==3.0.1 attrs==20.2.0 backoff==1.10.0 certifi==2020.6.20 cffi==1.14.3 chardet==3.0.4 click==7.1.2 coreapi==2.3.3 coreschema==0.0.4 createrepo-c==0.16.0.post1 cryptography==3.2.1 defusedxml==0.6.0 diff-match-patch==20200713 distro==1.5.0 Django==2.2.16 django-currentuser==0.5.1 django-extensions==3.0.9 django-filter==2.3.0 django-guardian==2.3.0 django-import-export==2.3.0 django-lifecycle==0.8.0 django-readonly-field==1.0.5 djangorestframework==3.11.2 djangorestframework-queryfields==1.0.0 drf-access-policy==0.7.0 drf-nested-routers==0.91 drf-spectacular==0.9.13 drf-yasg==1.17.1 dynaconf==3.1.2 et-xmlfile==1.0.1 gunicorn==20.0.4 idna==2.10 importlib-metadata==2.0.0 inflection==0.5.1 itypes==1.2.0 jdcal==1.4.1 Jinja2==2.11.2 jsonschema==3.2.0 libcomps==0.1.15.post1 MarkupPy==1.14 MarkupSafe==1.1.1 modulemd==1.3.3 multidict==5.0.0 nose==1.3.7 odfpy==1.4.1 openpyxl==3.0.5 packaging==20.4 pip-tools==5.3.1 productmd==1.28 psycopg2==2.8.6 pulp-file==1.3.0 pulp-file-client==1.3.0 pulp-rpm==3.7.0 pulp-rpm-client==3.7.0 pulpcore==3.7.3 pulpcore-client==3.7.3 pyasn1==0.4.8 pyasn1-modules==0.2.8 pycairo==1.20.0 pycares==3.1.1 pycparser==2.20 PyGObject==3.38.0 pygtrie==2.3.3 pyparsing==2.4.7 pyrsistent==0.17.3 python-box==5.2.0 python-dateutil==2.8.1 python-dotenv==0.15.0 python-gnupg==0.4.6 python-ldap==3.3.1 pytz==2020.1 PyYAML==5.3.1 redis==3.5.3 requests==2.24.0 rq==1.3.0 ruamel.yaml==0.16.12 ruamel.yaml.clib==0.2.2 scikit-build==0.11.1 six==1.15.0 solv==0.7.14 sqlparse==0.4.1 tablib==2.0.0 toml==0.10.1 typing-extensions==3.7.4.3 uritemplate==3.0.1 urllib3==1.25.11 urlman==1.3.0 whitenoise==5.0.1 xlrd==1.2.0 xlwt==1.3.0 yarl==1.6.2 zipp==3.4.0 On Prod server running 3.3 aiodns==2.0.0 aiofiles==0.5.0 aiohttp==3.6.2 ansible==2.9.9 async-timeout==3.0.1 attrs==19.3.0 autopep8==1.5.3 backoff==1.10.0 certifi==2020.4.5.1 cffi==1.14.0 chardet==3.0.4 click==7.1.2 coreapi==2.3.3 coreschema==0.0.4 createrepo-c==0.15.10 cryptography==2.9.2 defusedxml==0.6.0 diff-match-patch==2018 distro==1.5.0 Django==2.2.12 django-filter==2.2.0 django-import-export==2.0.2 djangorestframework==3.10.3 djangorestframework-queryfields==1.0.0 drf-nested-routers==0.91 drf-yasg==1.17.1 dynaconf==3.0.0rc1 et-xmlfile==1.0.1 gunicorn==20.0.4 idna==2.9 importlib-metadata==1.6.0 inflection==0.4.0 itypes==1.2.0 jdcal==1.4.1 Jinja2==2.11.2 jsonschema==3.2.0 libcomps==0.1.14.post1 MarkupPy==1.14 MarkupSafe==1.1.1 modulemd==1.3.3 multidict==4.7.6 nose==1.3.7 odfpy==1.4.1 openpyxl==3.0.3 packaging==20.4 pip-tools==5.2.0 productmd==1.26 psycopg2==2.8.5 pulp-file==0.3.0 pulp-file-client==0.3.0 pulp-rpm==3.3.2 pulp-rpm-client==3.3.2 pulpcore==3.3.1 pulpcore-client==3.3.1 pyasn1==0.4.8 pyasn1-modules==0.2.8 pycairo==1.19.1 pycares==3.1.1 pycodestyle==2.6.0 pycparser==2.20 PyGObject==3.36.1 pygtrie==2.3.3 pyparsing==2.4.7 pyrsistent==0.16.0 python-box==4.2.3 python-dateutil==2.8.1 python-dotenv==0.13.0 python-gnupg==0.4.6 python-ldap==3.2.0 pytz==2020.1 PyYAML==5.3.1 redis==3.5.2 requests==2.23.0 rq==1.3.0 ruamel.yaml==0.16.10 ruamel.yaml.clib==0.2.0 scikit-build==0.11.1 six==1.15.0 solv==0.7.11 sqlparse==0.3.1 tablib==2.0.0 toml==0.10.1 uritemplate==3.0.1 urllib3==1.25.9 whitenoise==5.0.1 xlrd==1.2.0 xlwt==1.3.0 yarl==1.4.2 zipp==3.1.0 They are on different proxy host. I am asking network team to check proxy also. From: dkli...@redhat.com At: 11/02/20 14:10:53To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] sync issue on 3.7.3 Are both systems downloading via the same proxy? Could you share the output of 'pip freeze' from your 3.7.3 install and one from your 3.3 install? On Mon, Nov 2, 2020 at 11:13 AM Bin Li (BLOOMBERG/ 120 PARK) wrote: We have been seeing a few sync issues during test of 3.7.3. Below is a list of summary of repo name and errors. We were able to resolve some issues by rerun the sync but most of errors seems to be consistent. The test was done on a 4cpu 64GB host with 2 workers configured. We are running 3.3 in our production without any of these issue. Just wondering if anyone experienced something similar and how we troubleshoot. rhel-7-server-optional-rpms Response payload is not completed = rhel-7-server-rpms Cannot connect to host cdn.redhat.com:443 ssl:default [Connection reset by peer] = rhel-7-server-debug-rpms Cannot connect to host cdn.redhat.com:443 ssl:default [None] = rhel-7-server-source-rpms [Errno 104] Connection reset by peer = rhel-server-rhscl-7-rpms Response payload is not completed = rhel-7-server-optional-debug-rpms Response payload is not completed ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list ___ Pulp-list mailing list Pulp
[Pulp-list] sync issue on 3.7.3
We have been seeing a few sync issues during test of 3.7.3. Below is a list of summary of repo name and errors. We were able to resolve some issues by rerun the sync but most of errors seems to be consistent. The test was done on a 4cpu 64GB host with 2 workers configured. We are running 3.3 in our production without any of these issue. Just wondering if anyone experienced something similar and how we troubleshoot. rhel-7-server-optional-rpms Response payload is not completed = rhel-7-server-rpms Cannot connect to host cdn.redhat.com:443 ssl:default [Connection reset by peer] = rhel-7-server-debug-rpms Cannot connect to host cdn.redhat.com:443 ssl:default [None] = rhel-7-server-source-rpms [Errno 104] Connection reset by peer = rhel-server-rhscl-7-rpms Response payload is not completed = rhel-7-server-optional-debug-rpms Response payload is not completed ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] 3.7.3 errors when reset external postgres db
Unfortunately, in our case the pulp user is not the owner of the database. It is the schema owner. reset_db requires the db owner to recreate database. We can only drop what we own. From: dal...@redhat.com At: 10/31/20 15:01:14To: ggai...@redhat.com Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com Subject: Re: [Pulp-list] 3.7.3 errors when reset external postgres db If you want to make it easier in the future -- you can install the "django-extensions" package which enables the "resetdb" command, which will drop everything properly, whereas the django builtin one does trip up sometimes. On Fri, Oct 30, 2020 at 9:00 PM Grant Gainey wrote: On Fri, Oct 30, 2020 at 8:31 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: Hi, I am testing 3.7.3 release with external postgres db. I want to reset the database first. After I drop all database tables and got the following errors when I run "django-admin migrate --noinput" Please advice. File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py", line 82, in _execute return self.cursor.execute(sql) psycopg2.errors.DuplicateObject: type "pulp_evr_array_item" already exists pulp_evr_array_item is a database type, installed/created by pulp_rpm/app/migrations/0013_RAW_rpm_evr_extension.py. If you're dropping all the tables and running the migrations, you'll also want to DROP TYPE pulp_evr_array_item; DROP TYPE pulp_evr_t; See if that helps! G The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/utils/venv/pulp/3.7.3/bin/django-admin", line 8, in sys.exit(execute_from_command_line()) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv self.execute(*args, **cmd_options) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py", line 364, in execute output = self.handle(*args, **options) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py", line 83, in wrapped res = handle_func(*args, **kwargs) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py", line 234, in handle fake_initial=fake_initial, File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py", line 117, in migrate state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py", line 245, in apply_migration state = migration.apply(state, schema_editor) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py", line 124, in apply operation.database_forwards(self.app_label, schema_editor, old_state, project_state) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/special.py", line 105, in database_forwards self._run_sql(schema_editor, self.sql) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/special.py", line 130, in _run_sql schema_editor.execute(statement, params=None) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py", line 137, in execute cursor.execute(sql, params) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from ex
Re: [Pulp-list] 3.7.3 errors when reset external postgres db
Thanks. Now I am getting a different errors. Applying rpm.0010_revision_null_redo... OK Applying rpm.0011_rpmremote_sles_auth_token... OK Applying rpm.0012_remove_pkg_group_env_cat_related_pkgs... OK Applying rpm.0013_RAW_rpm_evr_extension...Traceback (most recent call last): File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py", line 82, in _execute return self.cursor.execute(sql) psycopg2.errors.DuplicateFunction: function "pulp_evr_trigger" already exists with same argument types The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/utils/venv/pulp/3.7.3/bin/django-admin", line 8, in sys.exit(execute_from_command_line()) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line From: ggai...@redhat.com At: 10/30/20 21:00:04To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] 3.7.3 errors when reset external postgres db On Fri, Oct 30, 2020 at 8:31 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: Hi, I am testing 3.7.3 release with external postgres db. I want to reset the database first. After I drop all database tables and got the following errors when I run "django-admin migrate --noinput" Please advice. File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py", line 82, in _execute return self.cursor.execute(sql) psycopg2.errors.DuplicateObject: type "pulp_evr_array_item" already exists pulp_evr_array_item is a database type, installed/created by pulp_rpm/app/migrations/0013_RAW_rpm_evr_extension.py. If you're dropping all the tables and running the migrations, you'll also want to DROP TYPE pulp_evr_array_item; DROP TYPE pulp_evr_t; See if that helps! G The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/utils/venv/pulp/3.7.3/bin/django-admin", line 8, in sys.exit(execute_from_command_line()) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv self.execute(*args, **cmd_options) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py", line 364, in execute output = self.handle(*args, **options) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py", line 83, in wrapped res = handle_func(*args, **kwargs) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py", line 234, in handle fake_initial=fake_initial, File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py", line 117, in migrate state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py", line 245, in apply_migration state = migration.apply(state, schema_editor) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py", line 124, in apply operation.database_forwards(self.app_label, schema_editor, old_state, project_state) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/special.py", line 105, in database_forwards self._run_sql(schema_editor, self.sql) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/special.py", line 130, in _run_sql schema_editor.execute(statement, params=None) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py", line 137, in execute cursor.execute(sql, params) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backend
[Pulp-list] 3.7.3 errors when reset external postgres db
Hi,
I am testing 3.7.3 release with external postgres db. I want to reset the
database first. After I drop all database tables and got the following errors
when I run "django-admin migrate --noinput"
Please advice.
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 82, in _execute
return self.cursor.execute(sql)
psycopg2.errors.DuplicateObject: type "pulp_evr_array_item" already exists
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/utils/venv/pulp/3.7.3/bin/django-admin", line 8, in
sys.exit(execute_from_command_line())
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py",
line 381, in execute_from_command_line
utility.execute()
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py",
line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py",
line 323, in run_from_argv
self.execute(*args, **cmd_options)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py",
line 364, in execute
output = self.handle(*args, **options)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py",
line 83, in wrapped
res = handle_func(*args, **kwargs)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py",
line 234, in handle
fake_initial=fake_initial,
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py",
line 117, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake,
fake_initial=fake_initial)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py",
line 147, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake,
fake_initial=fake_initial)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py",
line 245, in apply_migration
state = migration.apply(state, schema_editor)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py",
line 124, in apply
operation.database_forwards(self.app_label, schema_editor, old_state,
project_state)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/special.py",
line 105, in database_forwards
self._run_sql(schema_editor, self.sql)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/special.py",
line 130, in _run_sql
schema_editor.execute(statement, params=None)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py",
line 137, in execute
cursor.execute(sql, params)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 67, in execute
return self._execute_with_wrappers(sql, params, many=False,
executor=self._execute)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 76, in _execute_with_wrappers
return executor(sql, params, many, context)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 84, in _execute
return self.cursor.execute(sql, params)
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py",
line 89, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 82, in _execute
return self.cursor.execute(sql)
django.db.utils.ProgrammingError: type "pulp_evr_array_item" already exists
I am running
{
"versions": [
{
"component": "pulpcore",
"version": "3.7.3"
},
{
"component": "pulp_rpm",
"version": "3.7.0"
},
{
"component": "pulp_file",
"version": "1.3.0"
}
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] Pulp 3.3 sync issue from artifactory
Yes, we have 'mirror' = True. The remote repository has not changed. This should not delete all packages from repo after sync. Version 2 repo in pulp shows all packages are deleted while remote repo has not changed from version 1. From: dkli...@redhat.com At: 08/31/20 15:35:06To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] Pulp 3.3 sync issue from artifactory I suspect that you have 'mirror' = True in your 'sync' request[0]. With this option set to True, the sync creates an exact copy of the remote repository. If no packages are found, a new version is created without any packages. When a subsequent sync occurs, no changes are detected, so a new version is not created. [0] https://pulp-rpm.readthedocs.io/en/latest/restapi.html#operation/repositories_rpm_rpm_sync On Mon, Aug 31, 2020 at 3:12 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: We created a rpm repos on artifactory and sync the repo to pulp 3.3. All packages are synced to pulp as version 1. If we run sync again, pulp could not find any packages and remove all previous packages in version 2. Subsequent sync also could not find any packages and the repo version stay as version 2. So far we only experience the issue when syncing from artifactory. Please advise. Thanks___ 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] Pulp 3.3 sync issue from artifactory
We created a rpm repos on artifactory and sync the repo to pulp 3.3. All packages are synced to pulp as version 1. If we run sync again, pulp could not find any packages and remove all previous packages in version 2. Subsequent sync also could not find any packages and the repo version stay as version 2. So far we only experience the issue when syncing from artifactory. Please advise. Thanks___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp_rpm 3.6.1 not able to connect through proxy
After we upgraded to latest pulp version from 3.3, we got the following errors
to sync repos through proxy. This works fine before the upgrade. I tried the
upgrade on multiple hosts and got the same errors. This error only happens when
sync external repos which requires proxy. Please advise
"description": "Cannot connect to host cdn.redhat.com:443 ssl:default
[Connect call failed ('173.222.100.251', 443)]",
"traceback": " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line
884, in perform_job\nrv = job.perform()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
664, in perform\nself._result = self._execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
line 211, in synchronize\nremote_url = fetch_remote_url(remote)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
line 136, in fetch_remote_url\ndownloader.fetch()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/download/base.py\",
line 160, in fetch\nreturn done.pop().result()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/download/base.py\",
line 227, in run\nreturn await self._run(extra_data=extra_data)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/downloaders.py\",
line 87, in _run\nasync with self.session.get(url) as response:\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/client.py\",
line 1012, in __aenter__\nself._resp = await self._coro\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/client.py\",
line 483, in _request\ntimeout=real_timeout\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/connector.py\",
line 523, in connect\nproto = await self._create_connection(req, traces,
timeout)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/connector.py\",
line 859, in _create_connection\nreq, traces, timeout)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/connector.py\",
line 1004, in _create_direct_connection\nraise last_exc\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/connector.py\",
line 986, in _create_direct_connection\nreq=req,
client_error=client_error)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/aiohttp/connector.py\",
line 943, in _wrap_create_connection\nraise
client_error(req.connection_key, exc) from exc\n"
The pulp version we are running:
"versions": [
{
"component": "pulpcore",
"version": "3.6.0"
},
{
"component": "pulp_rpm",
"version": "3.6.1"
},
{
"component": "pulp_file",
"version": "1.2.0"
}
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp 3.6.1 from 3.3
Thanks Mike, This works very well. It updated database without installing a new one. From: mikedep...@redhat.com At: 08/27/20 11:01:13To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.6.1 from 3.3 Hi Bin, It sounds like you are using external postgres but included redis and webserver, correct? You could do that. However, we recommend you use the following roles list instead on 3.6. It utilizes the smaller meta role `pulp_services`: - pulp_redis - pulp_services - pulp_health_check - pulp_webserver `pulp_services` includes the 4 services themselves, as well as the `pulp_database_config` role. https://pulp-installer.readthedocs.io/en/latest/meta_roles/pulp_services/ - Mike On Wed, Aug 26, 2020 at 5:20 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: We are upgrading from 3.3 with an external database. In our playbook, we used to include individual roles with "pulp_install_db: false". The pulp_all_services roles seems to install a new local database. Are we better off listing all roles in the playbook? Thanks___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list -- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat IM: mikedep333 GPG: 51745404 ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp 3.6.1 from 3.3
We are upgrading from 3.3 with an external database. In our playbook, we used to include individual roles with "pulp_install_db: false". The pulp_all_services roles seems to install a new local database. Are we better off listing all roles in the playbook? Thanks___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] Pulp 3 distribution trees
Hi, I am trying to understand how to create a distribution tree. I was able to create a repo and sync a kickstart tree to this repo. Should I create a publication and a distribution, then use the distribution base_url to access the the tree just as a regular repo? Is there anything else we need add to distribution tree? Can we create a distribution tree from a iso or local directory? Thanks Bin___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] Pulp-rpm 3.3.2 sync issues
Have you tried syncing this repo rhel-8.1-for-x86_64-appstream-rpms
No declared artifact with relative path
"repodata/ccbdfec4-421c-4cfe-86aa-887da978e8ac" for content ""
I am still getting the error today on 3.3.2 release.
Thanks
From: ppi...@redhat.com At: 06/17/20 08:51:53To: Bin Li (BLOOMBERG/ 120 PARK )
Cc: pulp-list@redhat.com, ggai...@redhat.com
Subject: Re: [Pulp-list] Pulp-rpm 3.3.2 sync issues
Hello,
'integer out of range' has been addressed in the issue you mentioned above
(#6717) and is merged in master now.
For issues 'No declared artifact with relative path' there was
https://pulp.plan.io/issues/6944 created.
As commented in the issue too, tested it with 3.2 and 3.3 and can't reproduce.
Then I tried to update pulp to the latest (version 3.4) to re-sync the already
existing pulp repository and sync to a new pulp repo without any issue too.
So I believe it is not reproducible.
On Fri, May 29, 2020 at 2:09 PM Grant Gainey wrote:
The libitm-debuginfo 404s look like a problem at cdn.redhat.com. Logging into
my redhat.com account and trying to download it directly fails with "Sorry, we
can’t find that content."
Go here
https://access.redhat.com/downloads/content/libitm-debuginfo/8.3.1-4.5.el8/x86_64/fd431d51/package
and hit download to reproduce.
Please open a support-case with Red Hat to report this.
G
On Fri, May 29, 2020 at 7:51 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
Below are the errors we found when sync with upstream redhat repos.
The "integer out of range" issue is already tracked in
https://pulp.plan.io/issues/6717
Let me know if I need open a new issues for any of the following issues.
rhel-server-rhscl-7.7-eus-rpms
No declared artifact with relative path "repodata/productid" for content
""
=
rhel-8.2-for-x86_64-baseos-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.2/x86_64/baseos/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
rhel-8.2-for-x86_64-appstream-source-rpms
integer out of range\n
=
rhel-8.2-for-x86_64-appstream-rpms
No declared artifact with relative path
"repodata/a22b89e3-765e-45bf-97f0-60e53435f3e5" for content ""
=
rhel-8.2-for-x86_64-appstream-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.2/x86_64/appstream/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
rhel-8.1-for-x86_64-baseos-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.1/x86_64/baseos/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.i686.rpm')
=
rhel-8.1-for-x86_64-appstream-source-rpms
integer out of range\n
=
rhel-8.1-for-x86_64-appstream-rpms
No declared artifact with relative path
"repodata/ccbdfec4-421c-4cfe-86aa-887da978e8ac" for content ""
=
rhel-8.1-for-x86_64-appstream-debug-rpms
Response payload is not completed
=
codeready-builder-for-rhel-8.2-x86_64-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.2/x86_64/codeready-builder/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
codeready-builder-for-rhel-8.1-x86_64-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.1/x86_64/codeready-builder/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
rhel-server-rhscl-7.7-eus-rpms
No declared artifact with relative path "repodata/productid" for content
""
=
rhel-8.2-for-x86_64-baseos-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.2/x86_64/baseos/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
rhel-8.2-for-x86_64-appstream-source-rpms
integer out of range\n
=
rhel-8.2-for-x86_64-appstream-rpms
No declared artifact with relative path
"repodata/a22b89e3-765e-45bf-97f0-60e53435f3e5" for content ""
=
rhel-8.2-for-x86_64-appstream-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.2/x86_64/appstream/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
rhel-8.1-for-x86_64-baseos-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.1/x86_64/baseos/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.i686.rpm')
=
rhel-8.1-for-x86_64-appstream-source-rpms
integer out of range\n
=
rhel-8.1-for-x86_64-appstream-rpms
No declared artifact with relative path
"repodata/ccbdfec4-421c-4cfe-86aa-887da978e8ac" for content ""
=
rhel-8.1-for-x86_64-appstream-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.1/x86_64/appstream/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
codeready-builder-for-rhel-8.2-x86_64-debug-rpms
4
Re: [Pulp-list] Pulp 3.3 error on listing publications
Hi Fabricio, Below is the version of all pulp modules we are using. pulp-file 0.3.0 pulp-file-client0.3.0 pulp-rpm3.3.2 pulp-rpm-client 3.3.1 pulpcore3.3.1 pulpcore-client 3.3.1 From: fabricio.agu...@redhat.com At: 06/15/20 09:26:19To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] Pulp 3.3 error on listing publications Hi Bin Li, Could you share what's the version of your pulp-rpm-client ? Best regards, Fabricio Aguiar Software Engineer, Pulp Project Red Hat Brazil - Latam +55 11 999652368 On Wed, Jun 10, 2020 at 7:33 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: Hi All Listing publications gives the following error when any publication is being created. I don't recall see this issue before 3.3. Can this be fixed? Traceback (most recent call last): File "./listpub.py", line 15, in PublicationsRpmApi(rpm_client).list().results File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api/publications_rpm_api.py", line 289, in list return self.list_with_http_info(**kwargs) # noqa: E501 File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api/publications_rpm_api.py", line 401, in list_with_http_info collection_formats=collection_formats) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 353, in call_api _preload_content, _request_timeout, _host) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 192, in __call_api return_data = self.deserialize(response_data, response_type) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 264, in deserialize return self.__deserialize(data, response_type) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 303, in __deserialize return self.__deserialize_model(data, klass) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 639, in __deserialize_model kwargs[attr] = self.__deserialize(value, attr_type) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 281, in __deserialize for sub_data in data] File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 281, in for sub_data in data] File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 303, in __deserialize return self.__deserialize_model(data, klass) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 641, in __deserialize_model instance = klass(**kwargs) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/models/rpm_rpm_publication.py", line 76, in __init__ self.metadata_checksum_type = metadata_checksum_type File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/models/rpm_rpm_publication.py", line 192, in metadata_checksum_type .format(metadata_checksum_type, allowed_values) ValueError: Invalid value for `metadata_checksum_type` (), must be one of ['unknown', 'md5', 'sha1', 'sha224', 'sha256', 'sha384', 'sha512'] To reproduce the issue. run the below program when a creating publication task is running. #!/usr/bin/env python from pulpcore.client import pulpcore from pulpcore.client import pulp_rpm from pulpcore.client.pulp_rpm import PublicationsRpmApi # Configure HTTP basic authorization: basic configuration = pulpcore.Configuration() configuration.host = 'http://pulpserver' configuration.username = 'admin' configuration.password = 'admin' configuration.safe_chars_for_path_param = '/' rpm_client = pulp_rpm.ApiClient(configuration) PublicationsRpmApi(rpm_client).list().results ___ 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] Pulp 3.3 error on listing publications
Hi All Listing publications gives the following error when any publication is being created. I don't recall see this issue before 3.3. Can this be fixed? Traceback (most recent call last): File "./listpub.py", line 15, in PublicationsRpmApi(rpm_client).list().results File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api/publications_rpm_api.py", line 289, in list return self.list_with_http_info(**kwargs) # noqa: E501 File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api/publications_rpm_api.py", line 401, in list_with_http_info collection_formats=collection_formats) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 353, in call_api _preload_content, _request_timeout, _host) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 192, in __call_api return_data = self.deserialize(response_data, response_type) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 264, in deserialize return self.__deserialize(data, response_type) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 303, in __deserialize return self.__deserialize_model(data, klass) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 639, in __deserialize_model kwargs[attr] = self.__deserialize(value, attr_type) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 281, in __deserialize for sub_data in data] File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 281, in for sub_data in data] File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 303, in __deserialize return self.__deserialize_model(data, klass) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/api_client.py", line 641, in __deserialize_model instance = klass(**kwargs) File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/models/rpm_rpm_publication.py", line 76, in __init__ self.metadata_checksum_type = metadata_checksum_type File "/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/client/pulp_rpm/models/rpm_rpm_publication.py", line 192, in metadata_checksum_type .format(metadata_checksum_type, allowed_values) ValueError: Invalid value for `metadata_checksum_type` (), must be one of ['unknown', 'md5', 'sha1', 'sha224', 'sha256', 'sha384', 'sha512'] To reproduce the issue. run the below program when a creating publication task is running. #!/usr/bin/env python from pulpcore.client import pulpcore from pulpcore.client import pulp_rpm from pulpcore.client.pulp_rpm import PublicationsRpmApi # Configure HTTP basic authorization: basic configuration = pulpcore.Configuration() configuration.host = 'http://pulpserver' configuration.username = 'admin' configuration.password = 'admin' configuration.safe_chars_for_path_param = '/' rpm_client = pulp_rpm.ApiClient(configuration) PublicationsRpmApi(rpm_client).list().results ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp 3 contingency server
Hi, We are creating the pulp contingency server in case the primary fails. The postgres is on external db, rq is replication to primary on local machine. We use rsync to copy the artifact from primary to contingency. Is /var/lib/pulp/artifact the only directory need to be synced from primary to make sure contingency has the same data?___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp 3.2 to 3.3.1 pip-compile error
Thanks Mike, This works. On a another host, I had to remove the current installation dir and install from scratch and it works. The new installation also has pip-tools 5.2. Is it possible to have prerequisite in pulp_installer so it is always upgraded first? From: mikedep...@redhat.com At: 05/29/20 17:24:29To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.2 to 3.3.1 pip-compile error Hmm, your pip-tools is much older: pip-tools 5.2.0 It looks like we need to modify the task that installs pip-tools to ensure it is new enough. The changelog says that pip-tools 5.0 is about pip 20.0 support. In the meantime, an easy workaround is: $ source /usr/local/lib/pulp/bin/activate $ pip install --upgrade pip-tools Then re-run the installer. -Mike On Fri, May 29, 2020 at 5:17 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: Thanks Mike. Here is the output. # more /opt/utils/venv/osupgrade/3.7.3/pyvenv.cfg home = /opt/python/3.7.3/bin include-system-site-packages = false version = 3.7.3 Package Version --- aiodns 2.0.0 aiofiles0.4.0 aiohttp 3.6.2 ansible 2.9.6 async-timeout 3.0.1 attrs 19.3.0 backoff 1.10.0 certifi 2019.11.28 cffi1.14.0 chardet 3.0.4 Click 7.0 coreapi 2.3.3 coreschema 0.0.4 createrepo-c0.15.7 cryptography2.8 Django 2.2.11 django-filter 2.2.0 djangorestframework 3.10.3 djangorestframework-queryfields 1.0.0 drf-nested-routers 0.91 drf-yasg1.17.1 dynaconf3.0.0rc1 gunicorn20.0.4 idna2.9 importlib-metadata 1.5.0 inflection 0.3.1 itypes 1.1.0 Jinja2 2.11.1 jsonschema 3.2.0 libcomps0.1.14.post1 MarkupSafe 1.1.1 modulemd1.3.3 multidict 4.7.5 nose1.3.7 packaging 20.3 pip 20.1.1 pip-tools 4.5.1 productmd 1.24 psycopg22.8.4 pulp-file 0.2.0 pulp-file-client0.2.0 pulp-rpm3.2.0 pulp-rpm-client 3.2.0 pulpcore3.2.0 pulpcore-client 3.2.0 pycairo 1.19.1 pycares 3.1.1 pycparser 2.20 PyGObject 3.34.0 pygtrie 2.3.2 pyparsing 2.4.6 pyrsistent 0.15.7 python-box 3.4.6 python-dateutil 2.8.1 python-dotenv 0.12.0 python-gnupg0.4.5 pytz2019.3 PyYAML 5.3 redis 3.4.1 requests2.23.0 rq 1.2.2 ruamel.yaml 0.16.10 ruamel.yaml.clib0.2.0 scikit-build0.10.0 setuptools 40.8.0 six 1.14.0 sqlparse0.3.1 toml0.10.0 uritemplate 3.0.1 urllib3 1.25.8 wheel 0.34.2 whitenoise 5.0.1 yarl1.4.2 zipp3.1.0 From: mikedep...@redhat.com At: 05/29/20 17:08:46To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.2 to 3.3.1 pip-compile error 1. I ran a test install against CentOS 7.6. Now we do not support CentOS 7.6 and earlier anymore, 7.7 & 7.8 work. RHEL is in the same situation. I disabled the check CentOS version task, and newer packages from the CentOS 7.8 repos were installed (like those for python3 and for libmodulem2), so it actually succeeded. I did not get the error like we would expect on the old distro (due to the newer packages on top), and I did not get your error either: https://pastebin.com/uBtQ9UTv 2. My apologies, I mistyped it. It is pyvenv.cfg , with a v: [vagrant@pulp3-sandbox-centos7 ~]$ cat /usr/local/lib/pulp/pyvenv.cfg home = /usr/bin include-system-site-packages = false version = 3.6.8 Please run that. 3. I'm going to have to think about any other steps we can take to reproduce your problem. Can you run the follo
Re: [Pulp-list] pulp 3.3 migration error
Thanks Daniel. We will soon start testing on 3.4.
From: dal...@redhat.com At: 05/29/20 17:18:41To: Bin Li (BLOOMBERG/ 120 PARK )
Cc: dkli...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3 migration error
Hello Bin,
Unfortunately it looks like when we fixed the migration from 3.3.0 -> 3.3.1, we
accidentally broke the migration from 3.2.z -> 3.3.z. This is my fault since I
tested the various migration paths for that patch - including migrating from
3.2.0 - but I must have missed something when doing so.
On Monday we will be releasing Pulp RPM 3.4.0 which should fix the migration
issues permanently. We're also considering entirely removing the 3.3.z releases
of the RPM plugin from PyPI to avoid anyone else experiencing this issue going
forwards, and investigating automated upgrade testing to catch this kind of
problem earlier.
I apologize for the headache this has probably been, but we really appreciate
the effort you've put into reporting these issues, it is of tremendous value to
the project!
Thank you,
Daniel
On Thu, May 28, 2020 at 11:26 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
Yes, we are trying to upgrade to 3.3.2.
From: dkli...@redhat.com At: 05/28/20 17:13:05To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3 migration error
Are you upgrading to pulp-rpm 3.3.2?
On Thu, May 28, 2020 at 5:08 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
Hi All,Getting a new error when migrate from 3.2 to 3.3. Please advise if this
can be fixed manually.
TASK [pulp_database : Run database migrations]
fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"],
"delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg":
"non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333",
"stderr": "Traceback (most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _execute\nreturn self.cursor.execute(sql,
params)\npsycopg2.errors.NotNullViolation: column \"last_sync_revision_number\"
contains null values\n\n\nThe above exception was the direct cause of the
following exception:\n\nTraceback (most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in \n
sys.exit(execute_from_command_line())\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
line 381, in execute_from_command_line\nutility.execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
line 375, in execute\n
self.fetch_command(subcommand).run_from_argv(self.argv)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
line 323, in run_from_argv\nself.execute(*args, **cmd_options)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
line 364, in execute\noutput = self.handle(*args, **options)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
line 83, in wrapped\nres = handle_func(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
line 234, in handle\nfake_initial=fake_initial,\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
line 117, in migrate\nstate = self._migrate_all_forwards(state, plan,
full_plan, fake=fake, fake_initial=fake_initial)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
line 147, in _migrate_all_forwards\nstate = self.apply_migration(state,
migration, fake=fake, fake_initial=fake_initial)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
line 245, in apply_migration\nstate = migration.apply(state,
schema_editor)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py\",
line 124, in apply\noperation.database_forwards(self.app_label,
schema_editor, old_state, project_state)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/fields.py\",
line 112, in database_forwards\nfield,\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\&quo
Re: [Pulp-list] pulp 3.2 to 3.3.1 pip-compile error
Thanks Mike. Here is the output. # more /opt/utils/venv/osupgrade/3.7.3/pyvenv.cfg home = /opt/python/3.7.3/bin include-system-site-packages = false version = 3.7.3 Package Version --- aiodns 2.0.0 aiofiles0.4.0 aiohttp 3.6.2 ansible 2.9.6 async-timeout 3.0.1 attrs 19.3.0 backoff 1.10.0 certifi 2019.11.28 cffi1.14.0 chardet 3.0.4 Click 7.0 coreapi 2.3.3 coreschema 0.0.4 createrepo-c0.15.7 cryptography2.8 Django 2.2.11 django-filter 2.2.0 djangorestframework 3.10.3 djangorestframework-queryfields 1.0.0 drf-nested-routers 0.91 drf-yasg1.17.1 dynaconf3.0.0rc1 gunicorn20.0.4 idna2.9 importlib-metadata 1.5.0 inflection 0.3.1 itypes 1.1.0 Jinja2 2.11.1 jsonschema 3.2.0 libcomps0.1.14.post1 MarkupSafe 1.1.1 modulemd1.3.3 multidict 4.7.5 nose1.3.7 packaging 20.3 pip 20.1.1 pip-tools 4.5.1 productmd 1.24 psycopg22.8.4 pulp-file 0.2.0 pulp-file-client0.2.0 pulp-rpm3.2.0 pulp-rpm-client 3.2.0 pulpcore3.2.0 pulpcore-client 3.2.0 pycairo 1.19.1 pycares 3.1.1 pycparser 2.20 PyGObject 3.34.0 pygtrie 2.3.2 pyparsing 2.4.6 pyrsistent 0.15.7 python-box 3.4.6 python-dateutil 2.8.1 python-dotenv 0.12.0 python-gnupg0.4.5 pytz2019.3 PyYAML 5.3 redis 3.4.1 requests2.23.0 rq 1.2.2 ruamel.yaml 0.16.10 ruamel.yaml.clib0.2.0 scikit-build0.10.0 setuptools 40.8.0 six 1.14.0 sqlparse0.3.1 toml0.10.0 uritemplate 3.0.1 urllib3 1.25.8 wheel 0.34.2 whitenoise 5.0.1 yarl1.4.2 zipp3.1.0 From: mikedep...@redhat.com At: 05/29/20 17:08:46To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.2 to 3.3.1 pip-compile error 1. I ran a test install against CentOS 7.6. Now we do not support CentOS 7.6 and earlier anymore, 7.7 & 7.8 work. RHEL is in the same situation. I disabled the check CentOS version task, and newer packages from the CentOS 7.8 repos were installed (like those for python3 and for libmodulem2), so it actually succeeded. I did not get the error like we would expect on the old distro (due to the newer packages on top), and I did not get your error either: https://pastebin.com/uBtQ9UTv 2. My apologies, I mistyped it. It is pyvenv.cfg , with a v: [vagrant@pulp3-sandbox-centos7 ~]$ cat /usr/local/lib/pulp/pyvenv.cfg home = /usr/bin include-system-site-packages = false version = 3.6.8 Please run that. 3. I'm going to have to think about any other steps we can take to reproduce your problem. Can you run the following? $ source /usr/local/lib/pulp/bin/activate (pulp) $ pip list On Fri, May 29, 2020 at 4:17 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: Mike,1. The pulp server is on rhel7.6 2. pulp_use_system_wide_pkgs is not defined. I run a find to grep pulp_use_system_wide_pkgs and didn't see it defined in ansible roles I don't find this file /usr/local/lib/pulp/pyenv.cfg either. I also run a find and didn't have a file named pyenv.cfg. From: mikedep...@redhat.com At: 05/29/20 15:09:42To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.2 to 3.3.1 pip-compile error Your pulp_instal_plugins looks correct for Pulp 3.3.1. Interesting error, I will try to reproduce. 2 questions: 1. What distro are you installing Pulp on? 2. pulp_use_system_wide_pkgs is undefined or set to false, correct? If true, it causes all sorts of problems with our pip-compile c
Re: [Pulp-list] pulp 3.2 to 3.3.1 pip-compile error
Mike,1. The pulp server is on rhel7.6
2. pulp_use_system_wide_pkgs is not defined. I run a find to grep
pulp_use_system_wide_pkgs and didn't see it defined in ansible roles
I don't find this file /usr/local/lib/pulp/pyenv.cfg either. I also run a find
and didn't have a file named pyenv.cfg.
From: mikedep...@redhat.com At: 05/29/20 15:09:42To: Bin Li (BLOOMBERG/ 120
PARK )
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.2 to 3.3.1 pip-compile error
Your pulp_instal_plugins looks correct for Pulp 3.3.1.
Interesting error, I will try to reproduce.
2 questions:
1. What distro are you installing Pulp on?
2. pulp_use_system_wide_pkgs is undefined or set to false, correct? If true, it
causes all sorts of problems with our pip-compile check, is no longer needed
for pulp-rpm to install, and we are about to remove it.
If you previously set it to true, and are upgrading a system, it would still
be effectively true as well. In fact, until 3.3.0, we were setting it to true
in the pulp_rpm_prerequisites role, even if you didn't set it. So that would be
another reason for it to be effectively true. You can check by viewing the file
/usr/local/lib/pulp/pyenv.cfg .
-Mike
On Fri, May 29, 2020 at 11:52 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
I have both pulp-file and pulp-rpm pined to compatible version.
pulp_install_plugins:
pulp-file:
version: '0.3.0'
pulp-rpm:
version: '3.3.2'
Still got an error as below. Please advise
TASK [pulp : Run pip-compile to check pulpcore/plugin compatibility]
[WARNING]: conditional statements should not include jinja2 templating
delimiters such as {{ }} or {% %}. Found: {{ failed_condition
| default("compatibility.rc != 0") }}
fatal: [myhost]: FAILED! => {"changed": false, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/pip-compile"], "delta": "0:00:00.393598",
"end": "2020-05-29 11:46:09.917436", "failed_when_result": true, "msg":
"non-zero return code", "rc": 1, "start": "2020-05-29 11:46:09.523838",
"stderr": "Traceback (most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/bin/pip-compile\", line 8, in \n
sys.exit(cli())\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 764, in __call__\nreturn self.main(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 717, in main\nrv = self.invoke(ctx)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 956, in invoke\nreturn ctx.invoke(self.callback, **ctx.params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 555, in invoke\nreturn callback(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/decorators.py\",
line 17, in new_func\nreturn f(get_current_context(), *args, **kwargs)\n
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/piptools/scripts/compile.py\",
line 304, in cli\nfor ireq in filter(is_pinned_requirement, ireqs):\n
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/piptools/utils.py\",
line 122, in is_pinned_requirement\nif ireq.editable:\nAttributeError:
'ParsedRequirement' object has no attribute 'editable'", "stderr_lines":
["Traceback (most recent call last):", " File
\"/opt/utils/venv/pulp/3.7.3/bin/pip-compile\", line 8, in ", "
sys.exit(cli())", " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 764, in __call__", "return self.main(*args, **kwargs)", " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 717, in main", "rv = self.invoke(ctx)", " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 956, in invoke", "return ctx.invoke(self.callback, **ctx.params)", "
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 555, in invoke", "return callback(*args, **kwargs)", " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/decorators.py\",
line 17, in new_func", "return f(get_current_context(), *args, **kwargs)",
" File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/piptools/scripts/compile.py\",
line 304, in cli", "for ireq in filter(is_pinned_requirement, ireqs):", "
File
\"/opt/utils/venv/pul
[Pulp-list] pulp 3.2 to 3.3.1 pip-compile error
I have both pulp-file and pulp-rpm pined to compatible version.
pulp_install_plugins:
pulp-file:
version: '0.3.0'
pulp-rpm:
version: '3.3.2'
Still got an error as below. Please advise
TASK [pulp : Run pip-compile to check pulpcore/plugin compatibility]
[WARNING]: conditional statements should not include jinja2 templating
delimiters such as {{ }} or {% %}. Found: {{ failed_condition
| default("compatibility.rc != 0") }}
fatal: [myhost]: FAILED! => {"changed": false, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/pip-compile"], "delta": "0:00:00.393598",
"end": "2020-05-29 11:46:09.917436", "failed_when_result": true, "msg":
"non-zero return code", "rc": 1, "start": "2020-05-29 11:46:09.523838",
"stderr": "Traceback (most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/bin/pip-compile\", line 8, in \n
sys.exit(cli())\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 764, in __call__\nreturn self.main(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 717, in main\nrv = self.invoke(ctx)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 956, in invoke\nreturn ctx.invoke(self.callback, **ctx.params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 555, in invoke\nreturn callback(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/decorators.py\",
line 17, in new_func\nreturn f(get_current_context(), *args, **kwargs)\n
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/piptools/scripts/compile.py\",
line 304, in cli\nfor ireq in filter(is_pinned_requirement, ireqs):\n
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/piptools/utils.py\",
line 122, in is_pinned_requirement\nif ireq.editable:\nAttributeError:
'ParsedRequirement' object has no attribute 'editable'", "stderr_lines":
["Traceback (most recent call last):", " File
\"/opt/utils/venv/pulp/3.7.3/bin/pip-compile\", line 8, in ", "
sys.exit(cli())", " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 764, in __call__", "return self.main(*args, **kwargs)", " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 717, in main", "rv = self.invoke(ctx)", " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 956, in invoke", "return ctx.invoke(self.callback, **ctx.params)", "
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 555, in invoke", "return callback(*args, **kwargs)", " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/decorators.py\",
line 17, in new_func", "return f(get_current_context(), *args, **kwargs)",
" File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/piptools/scripts/compile.py\",
line 304, in cli", "for ireq in filter(is_pinned_requirement, ireqs):", "
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/piptools/utils.py\",
line 122, in is_pinned_requirement", "if ireq.editable:", "AttributeError:
'ParsedRequirement' object has no attribute 'editable'"], "stdout": "",
"stdout_lines": []}
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] Pulp-rpm 3.3.2 sync issues
Below are the errors we found when sync with upstream redhat repos.
The "integer out of range" issue is already tracked in
https://pulp.plan.io/issues/6717
Let me know if I need open a new issues for any of the following issues.
rhel-server-rhscl-7.7-eus-rpms
No declared artifact with relative path "repodata/productid" for content
""
=
rhel-8.2-for-x86_64-baseos-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.2/x86_64/baseos/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
rhel-8.2-for-x86_64-appstream-source-rpms
integer out of range\n
=
rhel-8.2-for-x86_64-appstream-rpms
No declared artifact with relative path
"repodata/a22b89e3-765e-45bf-97f0-60e53435f3e5" for content ""
=
rhel-8.2-for-x86_64-appstream-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.2/x86_64/appstream/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
rhel-8.1-for-x86_64-baseos-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.1/x86_64/baseos/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.i686.rpm')
=
rhel-8.1-for-x86_64-appstream-source-rpms
integer out of range\n
=
rhel-8.1-for-x86_64-appstream-rpms
No declared artifact with relative path
"repodata/ccbdfec4-421c-4cfe-86aa-887da978e8ac" for content ""
=
rhel-8.1-for-x86_64-appstream-debug-rpms
Response payload is not completed
=
codeready-builder-for-rhel-8.2-x86_64-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.2/x86_64/codeready-builder/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
codeready-builder-for-rhel-8.1-x86_64-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.1/x86_64/codeready-builder/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
rhel-server-rhscl-7.7-eus-rpms
No declared artifact with relative path "repodata/productid" for content
""
=
rhel-8.2-for-x86_64-baseos-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.2/x86_64/baseos/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
rhel-8.2-for-x86_64-appstream-source-rpms
integer out of range\n
=
rhel-8.2-for-x86_64-appstream-rpms
No declared artifact with relative path
"repodata/a22b89e3-765e-45bf-97f0-60e53435f3e5" for content ""
=
rhel-8.2-for-x86_64-appstream-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.2/x86_64/appstream/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
rhel-8.1-for-x86_64-baseos-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.1/x86_64/baseos/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.i686.rpm')
=
rhel-8.1-for-x86_64-appstream-source-rpms
integer out of range\n
=
rhel-8.1-for-x86_64-appstream-rpms
No declared artifact with relative path
"repodata/ccbdfec4-421c-4cfe-86aa-887da978e8ac" for content ""
=
rhel-8.1-for-x86_64-appstream-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.1/x86_64/appstream/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
codeready-builder-for-rhel-8.2-x86_64-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.2/x86_64/codeready-builder/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
codeready-builder-for-rhel-8.1-x86_64-debug-rpms
404, message='Not Found',
url=URL('https://cdn.redhat.com/content/dist/rhel8/8.1/x86_64/codeready-builder/debug/Packages/l/libitm-debuginfo-8.3.1-4.5.el8.x86_64.rpm')
=
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp 3.3 content server not able to retrieve pkg.
Thanks Tatiana and Ina. This works just as you described. We found a few more
issues of syncing repos. I will add to a different thread.
From: ipan...@redhat.com At: 05/29/20 04:31:15To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3 content server not able to retrieve pkg.
Hi, the publish layout has changed [0]
You will be able to find your package under sorted and alphabetical order.
$ http HEAD
http://localhost:24816/pulp/content/pub/centos/7/os/x86_64/Packages/z/zenity-3.28.1-1.el7.x86_64.rpm
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Length: 4184192
Content-Type: application/x-rpm
Date: Fri, 29 May 2020 08:26:47 GMT
Etag: "1303868120"
Last-Modified: Mon, 12 Nov 2018 14:49:52 GMT
Server: lighttpd/1.4.47
(pulp) [vagrant@pulp2-nightly-pulp3-source-centos7 ~]$ http HEAD
http://localhost:24816/pulp/content/pub/centos/7/os/x86_64/zenity-3.28.1-1.el7.x86_64.rpm
HTTP/1.1 404 Not Found
Content-Length: 14
Content-Type: text/plain; charset=utf-8
Date: Fri, 29 May 2020 08:26:59 GMT
Server: Python/3.6 aiohttp/3.6.2
[0] https://pulp.plan.io/issues/4445
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."
On Fri, May 29, 2020 at 5:37 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
We did a fresh install of 3.3. After sysing repos from remote, got 404 error
when try to retrieve the packages from repo.
# wget
http://localhost:24816/pulp/content/system3rdparty/7.3/admin-python-36-3.6.5-2.el7.x86_64.rpm
--2020-05-28 23:31:05--
http://localhost:24816/pulp/content/system3rdparty/7.3/admin-python-36-3.6.5-2.el7.x86_64.rpm
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:24816... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-05-28 23:31:06 ERROR 404: Not Found.
We are able to see the rpm though api but not able to wget
Here are the info of the distribution, publication, and repo.
{'base_path': 'system3rdparty/7.3',
'base_url':
'http://ip-1-76-158-244.drr1.bcpc.bloomberg.com/pulp/content/system3rdparty/7.3',
'content_guard': None,
'name': 'systems_third_party_rhel7.3',
'publication':
'/pulp/api/v3/publications/rpm/rpm/78ed2012-feb1-452c-bf0f-20c877afc3a0/',
'pulp_created': datetime.datetime(2020, 5, 9, 5, 11, 47, 639184,
tzinfo=tzutc()),
'pulp_href':
'/pulp/api/v3/distributions/rpm/rpm/7134856d-de97-4ef1-a425-241a9f425c63/'}
{'metadata_checksum_type': 'sha256',
'package_checksum_type': 'sha256',
'pulp_created': datetime.datetime(2020, 5, 28, 20, 33, 36, 140455,
tzinfo=tzutc()),
'pulp_href':
'/pulp/api/v3/publications/rpm/rpm/78ed2012-feb1-452c-bf0f-20c877afc3a0/',
'repository':
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/',
'repository_version':
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/versions/7/'}
{'description': 'system party 7.3',
'latest_version_href':
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/versions/7/',
'metadata_signing_service': None,
'name': 'systems_third_party_rhel7.3',
'pulp_created': datetime.datetime(2020, 5, 9, 5, 6, 8, 781604, tzinfo=tzutc()),
'pulp_href':
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/',
'versions_href':
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/versions/'}
# ./sget status
{
"versions": [
{
"component": "pulpcore",
"version": "3.3.1"
},
{
"component": "pulp_rpm",
"version": "3.3.2"
},
{
"component": "pulp_file",
"version": "0.3.0"
}
],
"online_workers": [
{
"pulp_href":
"/pulp/api/v3/workers/86605b78-6d6b-4ad4-bb8f-cf9885c5f90d/",
"pulp_created": "2020-05-09T05:05:55.272910Z",
"name": "resource-manager",
"last_heartbeat": "2020-05-29T03:35:29.913501Z"
},
{
"pulp_href":
"/pulp/api/v3/workers/b373a038-e8bc-4207-aba3-eefc816cadb3/",
"pulp_created": "2020-05-29T02:58:28.912571Z",
"name": "116...@ip-1-76-158-244.drr1.bcpc.bloomberg.com",
"last_heartbeat": "2020-05-29T03:35:32.817973Z"
},
{
"pulp_href":
"/pulp/api/v3/workers/e9b7b7c2-c86d-4d2d-b887-17b48d16dc41/",
"pulp_created": "2020-05-29T02:58:29.248424Z",
"name": "116...@ip-1-76-158-244.drr1.bcpc.bloomberg.com",
&qu
Re: [Pulp-list] Pulp-list Digest, Vol 126, Issue 47
Below is output of querying the package through api
{
"pulp_href":
"/pulp/api/v3/content/rpm/packages/ed31233e-2745-406b-8e5d-17e616725040/",
"name": "admin-python-36",
"version": "3.6.5",
"release": "2.el7",
"location_href": "packages/admin-python-36-3.6.5-2.el7.x86_64.rpm"
},
From: pulp-list@redhat.com At: 05/28/20 23:26:41To: pulp-list@redhat.com
Subject: Pulp-list Digest, Vol 126, Issue 47
Send Pulp-list mailing list submissions to
pulp-list@redhat.com
To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/pulp-list
or, via email, send a message with subject or body 'help' to
pulp-list-requ...@redhat.com
You can reach the person managing the list at
pulp-list-ow...@redhat.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Pulp-list digest..."
Today's Topics:
1. Re: pulp 3.3 migration error (Dennis Kliban)
2. Re: pulp 3.3 migration error (Bin Li (BLOOMBERG/ 120 PARK))
--
Message: 1
Date: Thu, 28 May 2020 17:12:40 -0400
From: Dennis Kliban
To: Bin Li
Cc: pulp-list
Subject: Re: [Pulp-list] pulp 3.3 migration error
Message-ID:
Content-Type: text/plain; charset="utf-8"
Are you upgrading to pulp-rpm 3.3.2?
On Thu, May 28, 2020 at 5:08 PM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:
> Hi All,
> Getting a new error when migrate from 3.2 to 3.3. Please advise if this
> can be fixed manually.
>
> TASK [pulp_database : Run database migrations]
>
> fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd":
> ["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"],
> "delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg":
> "non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333",
> "stderr": "Traceback (most recent call last):\n File
>
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 84, in _execute\n return self.cursor.execute(sql,
> params)\npsycopg2.errors.NotNullViolation: column
> \"last_sync_revision_number\" contains null values\n\n\nThe above exception
> was the direct cause of the following exception:\n\nTraceback (most recent
> call last):\n File \"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8,
> in \n sys.exit(execute_from_command_line())\n File
>
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
> line 381, in execute_from_command_line\n utility.execute()\n File
>
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
> line 375, in execute\n
> self.fetch_command(subcommand).run_from_argv(self.argv)\n File
>
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
> line 323, in run_from_argv\n self.execute(*args, **cmd_options)\n File
>
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
> line 364, in execute\n output = self.handle(*args, **options)\n File
>
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
> line 83, in wrapped\n res = handle_func(*args, **kwargs)\n File
>
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
> line 234, in handle\n fake_initial=fake_initial,\n File
>
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
> line 117, in migrate\n state = self._migrate_all_forwards(state, plan,
> full_plan, fake=fake, fake_initial=fake_initial)\n File
>
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
> line 147, in _migrate_all_forwards\n state = self.apply_migration(state,
> migration, fake=fake, fake_initial=fake_initial)\n File
>
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
> line 245, in apply_migration\n state = migration.apply(state,
> schema_editor)\n File
>
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py\",
> line 124, in apply\n operation.database_forwards(self.app_label,
> schema_editor, o
[Pulp-list] pulp 3.3 content server not able to retrieve pkg.
We did a fresh install of 3.3. After sysing repos from remote, got 404 error
when try to retrieve the packages from repo.
# wget
http://localhost:24816/pulp/content/system3rdparty/7.3/admin-python-36-3.6.5-2.el7.x86_64.rpm
--2020-05-28 23:31:05--
http://localhost:24816/pulp/content/system3rdparty/7.3/admin-python-36-3.6.5-2.el7.x86_64.rpm
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:24816... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-05-28 23:31:06 ERROR 404: Not Found.
We are able to see the rpm though api but not able to wget
Here are the info of the distribution, publication, and repo.
{'base_path': 'system3rdparty/7.3',
'base_url':
'http://ip-1-76-158-244.drr1.bcpc.bloomberg.com/pulp/content/system3rdparty/7.3',
'content_guard': None,
'name': 'systems_third_party_rhel7.3',
'publication':
'/pulp/api/v3/publications/rpm/rpm/78ed2012-feb1-452c-bf0f-20c877afc3a0/',
'pulp_created': datetime.datetime(2020, 5, 9, 5, 11, 47, 639184,
tzinfo=tzutc()),
'pulp_href':
'/pulp/api/v3/distributions/rpm/rpm/7134856d-de97-4ef1-a425-241a9f425c63/'}
{'metadata_checksum_type': 'sha256',
'package_checksum_type': 'sha256',
'pulp_created': datetime.datetime(2020, 5, 28, 20, 33, 36, 140455,
tzinfo=tzutc()),
'pulp_href':
'/pulp/api/v3/publications/rpm/rpm/78ed2012-feb1-452c-bf0f-20c877afc3a0/',
'repository':
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/',
'repository_version':
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/versions/7/'}
{'description': 'system party 7.3',
'latest_version_href':
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/versions/7/',
'metadata_signing_service': None,
'name': 'systems_third_party_rhel7.3',
'pulp_created': datetime.datetime(2020, 5, 9, 5, 6, 8, 781604, tzinfo=tzutc()),
'pulp_href':
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/',
'versions_href':
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/versions/'}
# ./sget status
{
"versions": [
{
"component": "pulpcore",
"version": "3.3.1"
},
{
"component": "pulp_rpm",
"version": "3.3.2"
},
{
"component": "pulp_file",
"version": "0.3.0"
}
],
"online_workers": [
{
"pulp_href":
"/pulp/api/v3/workers/86605b78-6d6b-4ad4-bb8f-cf9885c5f90d/",
"pulp_created": "2020-05-09T05:05:55.272910Z",
"name": "resource-manager",
"last_heartbeat": "2020-05-29T03:35:29.913501Z"
},
{
"pulp_href":
"/pulp/api/v3/workers/b373a038-e8bc-4207-aba3-eefc816cadb3/",
"pulp_created": "2020-05-29T02:58:28.912571Z",
"name": "116...@ip-1-76-158-244.drr1.bcpc.bloomberg.com",
"last_heartbeat": "2020-05-29T03:35:32.817973Z"
},
{
"pulp_href":
"/pulp/api/v3/workers/e9b7b7c2-c86d-4d2d-b887-17b48d16dc41/",
"pulp_created": "2020-05-29T02:58:29.248424Z",
"name": "116...@ip-1-76-158-244.drr1.bcpc.bloomberg.com",
"last_heartbeat": "2020-05-29T03:35:33.419618Z"
}
],
"online_content_apps": [
{
"name": "116...@ip-1-76-158-244.drr1.bcpc.bloomberg.com",
"last_heartbeat": "2020-05-29T03:35:28.815660Z"
},
{
"name": "116...@ip-1-76-158-244.drr1.bcpc.bloomberg.com",
"last_heartbeat": "2020-05-29T03:35:28.818255Z"
}
],
"database_connection": {
"connected": true
},
"redis_connection": {
"connected": true
},
"storage": {
"total": 21463281664,
"used": 18353487872,
"free": 3109793792
}
}
We never had issues with this in all previous pulp 3 release. Please help.___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp 3.3 migration error
Yes, we are trying to upgrade to 3.3.2.
From: dkli...@redhat.com At: 05/28/20 17:13:05To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3 migration error
Are you upgrading to pulp-rpm 3.3.2?
On Thu, May 28, 2020 at 5:08 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
Hi All,Getting a new error when migrate from 3.2 to 3.3. Please advise if this
can be fixed manually.
TASK [pulp_database : Run database migrations]
fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"],
"delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg":
"non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333",
"stderr": "Traceback (most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _execute\nreturn self.cursor.execute(sql,
params)\npsycopg2.errors.NotNullViolation: column \"last_sync_revision_number\"
contains null values\n\n\nThe above exception was the direct cause of the
following exception:\n\nTraceback (most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in \n
sys.exit(execute_from_command_line())\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
line 381, in execute_from_command_line\nutility.execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
line 375, in execute\n
self.fetch_command(subcommand).run_from_argv(self.argv)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
line 323, in run_from_argv\nself.execute(*args, **cmd_options)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
line 364, in execute\noutput = self.handle(*args, **options)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
line 83, in wrapped\nres = handle_func(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
line 234, in handle\nfake_initial=fake_initial,\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
line 117, in migrate\nstate = self._migrate_all_forwards(state, plan,
full_plan, fake=fake, fake_initial=fake_initial)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
line 147, in _migrate_all_forwards\nstate = self.apply_migration(state,
migration, fake=fake, fake_initial=fake_initial)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
line 245, in apply_migration\nstate = migration.apply(state,
schema_editor)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py\",
line 124, in apply\noperation.database_forwards(self.app_label,
schema_editor, old_state, project_state)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/fields.py\",
line 112, in database_forwards\nfield,\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
line 447, in add_field\nself.execute(sql, params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
line 137, in execute\ncursor.execute(sql, params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 67, in execute\nreturn self._execute_with_wrappers(sql, params,
many=False, executor=self._execute)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 76, in _execute_with_wrappers\nreturn executor(sql, params, many,
context)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _execute\nreturn self.cursor.execute(sql, params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py\",
line 89, in __exit__\nraise dj_exc_value.with_traceback(traceback) from
exc_value\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _ex
[Pulp-list] pulp 3.3 migration error
Hi All,Getting a new error when migrate from 3.2 to 3.3. Please advise if this
can be fixed manually.
TASK [pulp_database : Run database migrations]
fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"],
"delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg":
"non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333",
"stderr": "Traceback (most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _execute\nreturn self.cursor.execute(sql,
params)\npsycopg2.errors.NotNullViolation: column \"last_sync_revision_number\"
contains null values\n\n\nThe above exception was the direct cause of the
following exception:\n\nTraceback (most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in \n
sys.exit(execute_from_command_line())\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
line 381, in execute_from_command_line\nutility.execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
line 375, in execute\n
self.fetch_command(subcommand).run_from_argv(self.argv)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
line 323, in run_from_argv\nself.execute(*args, **cmd_options)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
line 364, in execute\noutput = self.handle(*args, **options)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
line 83, in wrapped\nres = handle_func(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
line 234, in handle\nfake_initial=fake_initial,\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
line 117, in migrate\nstate = self._migrate_all_forwards(state, plan,
full_plan, fake=fake, fake_initial=fake_initial)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
line 147, in _migrate_all_forwards\nstate = self.apply_migration(state,
migration, fake=fake, fake_initial=fake_initial)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
line 245, in apply_migration\nstate = migration.apply(state,
schema_editor)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py\",
line 124, in apply\noperation.database_forwards(self.app_label,
schema_editor, old_state, project_state)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/fields.py\",
line 112, in database_forwards\nfield,\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
line 447, in add_field\nself.execute(sql, params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
line 137, in execute\ncursor.execute(sql, params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 67, in execute\nreturn self._execute_with_wrappers(sql, params,
many=False, executor=self._execute)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 76, in _execute_with_wrappers\nreturn executor(sql, params, many,
context)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _execute\nreturn self.cursor.execute(sql, params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py\",
line 89, in __exit__\nraise dj_exc_value.with_traceback(traceback) from
exc_value\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _execute\nreturn self.cursor.execute(sql,
params)\ndjango.db.utils.IntegrityError: column \"last_sync_revision_number\"
contains null values", "stderr_lines": ["Traceback (most recent call last):", "
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _execute", "return self.cursor.execute(sql, params)",
"psycopg2.errors.NotNullViolation: column \"last_sync_revision_number\"
contains null values", "", "", "The above exception was the direct cause of the
following exception:", "", "Traceback (most recent call last):", " File
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in ", "
Re: [Pulp-list] Pulp-list Digest, Vol 126, Issue 44
I figured it out the issue. The 3.3 installer works after I pin plugins. pulp_install_plugins: pulp-file: #upgrade: true version: '0.3.0' pulp-rpm: #upgrade: true version: '3.3.2' From: pulp-list@redhat.com At: 05/28/20 12:02:36To: pulp-list@redhat.com Subject: Pulp-list Digest, Vol 126, Issue 44 Send Pulp-list mailing list submissions to pulp-list@redhat.com To subscribe or unsubscribe via the World Wide Web, visit https://www.redhat.com/mailman/listinfo/pulp-list or, via email, send a message with subject or body 'help' to pulp-list-requ...@redhat.com You can reach the person managing the list at pulp-list-ow...@redhat.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Pulp-list digest..." Today's Topics: 1. Pin pulp 3.3.1 (Bin Li (BLOOMBERG/ 120 PARK)) -- Message: 1 Date: Thu, 28 May 2020 15:52:04 -0000 From: "Bin Li (BLOOMBERG/ 120 PARK)" To: pulp-list@redhat.com Subject: [Pulp-list] Pin pulp 3.3.1 Message-ID: <5ECFDE2400FF035A00390603_0_54956@msllnjpmsgsv06> Content-Type: text/plain; charset="utf-8" We got an error when rerun pulp_installer 3.3 after 3.4 is released. " pulpcore==3.3.1 (from -r requirements.in (line 1))", " pulpcore<3.4,>=3.3 (from pulp-rpm==3.3.2)", " pulpcore<3.5,>=3.4 (from pulp-file==1.0.0)" How do we pin the pulpcore to 3.3 for now since we haven't test 3.4 yet in our dev environment? Thanks -- next part -- An HTML attachment was scrubbed... URL: <https://www.redhat.com/archives/pulp-list/attachments/20200528/a2d4d334/atta chment.html> -- ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list End of Pulp-list Digest, Vol 126, Issue 44 ** ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] Pin pulp 3.3.1
We got an error when rerun pulp_installer 3.3 after 3.4 is released. " pulpcore==3.3.1 (from -r requirements.in (line 1))", " pulpcore<3.4,>=3.3 (from pulp-rpm==3.3.2)", " pulpcore<3.5,>=3.4 (from pulp-file==1.0.0)" How do we pin the pulpcore to 3.3 for now since we haven't test 3.4 yet in our dev environment? Thanks ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] Pulp rpm copy
Hi, Can someone provide the "config" json schema for copying content?https://pulp-rpm.readthedocs.io/en/latest/restapi.html#tag/rpm:-copy Thanks___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp 3 live-live setup
Is it true that both host should have it's own rq in this case? Is it true we don't need add cert on both pulp hosts if we'd like enable ssl and install cert on load balancer which will forward traffic from 443 to pulp port 80? From: dkli...@redhat.com At: 05/13/20 12:28:30To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3 live-live setup On Wed, May 13, 2020 at 12:21 PM Bin Li (BLOOMBERG/ 120 PARK) wrote: Hi All, If we share s3 and external postgres between two pulp host, is it possible to have both up for read only purpose behind a load balancer? Yes, you just want to make sure that the CONTENT_ORIGIN setting reflects the hostname of the load balancer. ___ 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] pulp 3 live-live setup
Hi All, If we share s3 and external postgres between two pulp host, is it possible to have both up for read only purpose behind a load balancer? ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp 3.3.1 server error
Here is what I have
# django-admin showmigrations
admin
[X] 0001_initial
[X] 0002_logentry_remove_auto_add
[X] 0003_logentry_add_action_flag_choices
auth
[X] 0001_initial
[X] 0002_alter_permission_name_max_length
[X] 0003_alter_user_email_max_length
[X] 0004_alter_user_username_opts
[X] 0005_alter_user_last_login_null
[X] 0006_require_contenttypes_0002
[X] 0007_alter_validators_add_error_messages
[X] 0008_alter_user_username_max_length
[X] 0009_alter_user_last_name_max_length
[X] 0010_alter_group_name_max_length
[X] 0011_update_proxy_permissions
contenttypes
[X] 0001_initial
[X] 0002_remove_content_type_name
core
[X] 0001_initial
[X] 0002_increase_artifact_size_field
[X] 0003_remove_upload_completed
[X] 0004_add_duplicated_reserved_resources
[X] 0005_progressreport_code
[X] 0006_repository_plugin_managed
[X] 0007_delete_progress_proxies
[X] 0008_published_metadata_as_content
[X] 0009_remove_task_non_fatal_errors
[X] 0010_pulp_fields
[X] 0011_relative_path
[X] 0012_auto_20191104_2000
[X] 0013_repository_pulp_type
[X] 0014_remove_repository_plugin_managed
[X] 0015_auto_20191112_1426
[X] 0016_charfield_to_textfield
[X] 0017_remove_task_parent
[X] 0018_auto_20191127_2350
[X] 0019_add_signing_service_model
[X] 0020_change_publishedartifact_constraints
[X] 0021_add_signing_service_foreign_key
[X] 0022_rename_last_version
[X] 0023_change_exporter_models
[X] 0024_use_local_storage_for_uploads
[X] 0025_task_parent_task
[X] 0026_task_group
[X] 0027_export_backend
[X] 0028_import_importer_pulpimporter_pulpimporterrepository
file
[X] 0001_initial
[X] 0002_file_related_names
[X] 0003_auto_20191014_1721
[X] 0004_filefilesystemexporter
[X] 0005_filerepository
[X] 0006_delete_filefilesystemexporter
[X] 0007_filefilesystemexporter
rpm
[X] 0001_initial
[X] 0002_updaterecord_reboot_suggested
[X] 0003_DATA_incorrect_json
[X] 0004_add_metadata_signing_service_fk
[X] 0005_optimize_sync
[X] 0006_opensuse_support
[X] 0007_checksum_types
[X] 0008_advisory_pkg_sumtype_as_int
[X] 0009_revision_null
sessions
[X] 0001_initial
From: ipan...@redhat.com At: 05/13/20 11:41:13To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: ttere...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3.1 server error
Can you confirm that migration 0009_revision_null was applied?
You can see the migrations with this command 'django-admin showmigrations'
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."
On Wed, May 13, 2020 at 4:09 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
Hi Ina,
The error was not from migration. I see the error when I try to create a new
repo. My pulp_installer is on the latest version. Rerun the installer doesn't
solve the issue. What should I do to fix this? We cannot reset database from
scratch since we already have a lot data.
From: ipan...@redhat.com At: 05/13/20 09:43:45To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: ttere...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3.1 server error
This issue was fixed in the 3.3.1 release [0][1]
[0] https://pulp-rpm.readthedocs.io/en/latest/changes.html#bugfixes
[1] https://pulp.plan.io/issues/6662
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."
On Tue, May 12, 2020 at 11:30 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
I removed the 0009_auto.. and rerun the installer. The upgrade was successful.
Below is error log.
May 12 17:25:05 myhost gunicorn[55426]: pulp: django.request:ERROR: Internal
Server Error: /pulp/api/v3/repositories/rpm/rpm/
May 12 17:25:05 myhost gunicorn[55426]: Traceback (most recent call last):
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 84, in _execute
May 12 17:25:05 myhost gunicorn[55426]: return self.cursor.execute(sql, params)
May 12 17:25:05 myhost gunicorn[55426]: psycopg2.errors.NotNullViolation: null
value in column "last_sync_revision_number" violates not-null constraint
May 12 17:25:05 myhost gunicorn[55426]: DETAIL: Failing row contains
(0053634d-d0ca-46de-81d4-b8acf19d592e, f, null, null, 0, null, {}).
May 12 17:25:05 myhost gunicorn[55426]: The above exception was the direct
cause of the following exception:
May 12 17:25:05 myhost gunicorn[55426]: Traceback (most recent call last):
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/handlers/exception.py",
line 34, in inner
May 12 17:25:05 myhost gunicorn[55426]: response = get_response(request)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/handlers/base.py",
line 115, in _g
Re: [Pulp-list] pulp 3.3.1 server error
Hi Ina,
The error was not from migration. I see the error when I try to create a new
repo. My pulp_installer is on the latest version. Rerun the installer doesn't
solve the issue. What should I do to fix this? We cannot reset database from
scratch since we already have a lot data.
From: ipan...@redhat.com At: 05/13/20 09:43:45To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: ttere...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3.1 server error
This issue was fixed in the 3.3.1 release [0][1]
[0] https://pulp-rpm.readthedocs.io/en/latest/changes.html#bugfixes
[1] https://pulp.plan.io/issues/6662
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."
On Tue, May 12, 2020 at 11:30 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
I removed the 0009_auto.. and rerun the installer. The upgrade was successful.
Below is error log.
May 12 17:25:05 myhost gunicorn[55426]: pulp: django.request:ERROR: Internal
Server Error: /pulp/api/v3/repositories/rpm/rpm/
May 12 17:25:05 myhost gunicorn[55426]: Traceback (most recent call last):
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 84, in _execute
May 12 17:25:05 myhost gunicorn[55426]: return self.cursor.execute(sql, params)
May 12 17:25:05 myhost gunicorn[55426]: psycopg2.errors.NotNullViolation: null
value in column "last_sync_revision_number" violates not-null constraint
May 12 17:25:05 myhost gunicorn[55426]: DETAIL: Failing row contains
(0053634d-d0ca-46de-81d4-b8acf19d592e, f, null, null, 0, null, {}).
May 12 17:25:05 myhost gunicorn[55426]: The above exception was the direct
cause of the following exception:
May 12 17:25:05 myhost gunicorn[55426]: Traceback (most recent call last):
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/handlers/exception.py",
line 34, in inner
May 12 17:25:05 myhost gunicorn[55426]: response = get_response(request)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/handlers/base.py",
line 115, in _get_response
May 12 17:25:05 myhost gunicorn[55426]: response =
self.process_exception_by_middleware(e, request)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/handlers/base.py",
line 113, in _get_response
May 12 17:25:05 myhost gunicorn[55426]: response = wrapped_callback(request,
*callback_args, **callback_kwargs)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/views/decorators/csrf.py",
line 54, in wrapped_view
May 12 17:25:05 myhost gunicorn[55426]: return view_func(*args, **kwargs)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rest_framework/viewsets.py",
line 114, in view
May 12 17:25:05 myhost gunicorn[55426]: return self.dispatch(request, *args,
**kwargs)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rest_framework/views.py",
line 505, in dispatch
May 12 17:25:05 myhost gunicorn[55426]: response = self.handle_exception(exc)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rest_framework/views.py",
line 465, in handle_exception
May 12 17:25:05 myhost gunicorn[55426]: self.raise_uncaught_exception(exc)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rest_framework/views.py",
line 476, in raise_uncaught_exception
May 12 17:25:05 myhost gunicorn[55426]: raise exc
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rest_framework/views.py",
line 502, in dispatch
May 12 17:25:05 myhost gunicorn[55426]: response = handler(request, *args,
**kwargs)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rest_framework/mixins.py",
line 19, in create
May 12 17:25:05 myhost gunicorn[55426]: self.perform_create(serializer)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rest_framework/mixins.py",
line 24, in perform_create
May 12 17:25:05 myhost gunicorn[55426]: serializer.save()
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rest_framework/serializers.py",
line 213, in save
May 12 17:25:05 myhost gunicorn[55426]: self.instance =
self.create(validated_data)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/r
Re: [Pulp-list] pulp 3.3.1 server error
rn[55426]: super().save(*args, **kwargs)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/models/base.py",
line 107, in save
May 12 17:25:05 myhost gunicorn[55426]: return super().save(*args, **kwargs)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/base.py",
line 741, in save
May 12 17:25:05 myhost gunicorn[55426]: force_update=force_update,
update_fields=update_fields)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/base.py",
line 779, in save_base
May 12 17:25:05 myhost gunicorn[55426]: force_update, using, update_fields,
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/base.py",
line 870, in _save_table
May 12 17:25:05 myhost gunicorn[55426]: result =
self._do_insert(cls._base_manager, using, fields, update_pk, raw)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/base.py",
line 908, in _do_insert
May 12 17:25:05 myhost gunicorn[55426]: using=using, raw=raw)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/manager.py",
line 82, in manager_method
May 12 17:25:05 myhost gunicorn[55426]: return getattr(self.get_queryset(),
name)(*args, **kwargs)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py",
line 1186, in _insert
May 12 17:25:05 myhost gunicorn[55426]: return
query.get_compiler(using=using).execute_sql(return_id)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py",
line 1368, in execute_sql
May 12 17:25:05 myhost gunicorn[55426]: cursor.execute(sql, params)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 67, in execute
May 12 17:25:05 myhost gunicorn[55426]: return self._execute_with_wrappers(sql,
params, many=False, executor=self._execute)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 76, in _execute_with_wrappers
May 12 17:25:05 myhost gunicorn[55426]: return executor(sql, params, many,
context)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 84, in _execute
May 12 17:25:05 myhost gunicorn[55426]: return self.cursor.execute(sql, params)
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py",
line 89, in __exit__
May 12 17:25:05 myhost gunicorn[55426]: raise
dj_exc_value.with_traceback(traceback) from exc_value
May 12 17:25:05 myhost gunicorn[55426]: File
"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py",
line 84, in _execute
May 12 17:25:05 myhost gunicorn[55426]: return self.cursor.execute(sql, params)
May 12 17:25:05 myhost gunicorn[55426]: django.db.utils.IntegrityError: null
value in column "last_sync_revision_number" violates not-null constraint
May 12 17:25:05 myhost gunicorn[55426]: DETAIL: Failing row contains
(0053634d-d0ca-46de-81d4-b8acf19d592e, f, null, null, 0, null, {}).
May 12 17:25:05 myhost gunicorn[55426]: 127.0.0.1 - admin [12/May/2020:21:25:05
+] "POST /pulp/api/v3/repositories/rpm/rpm/ HTTP/1.1" 500 27 "-"
"HTTPie/0.9.4"
From: ttere...@redhat.com At: 05/12/20 16:19:31To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3.1 server error
Was the upgrade successful after you removed the 0009_auto...? Did you run the
installer again?
If no, please do so.
If yes, could you share logs? There will be some traceback showing why 500
error happened.
Thank you,
Tanya
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulp 3.3.1 server error
I got a error "Server Error (500)" when creating a repo. This error only happened on a test host I upgraded from previous release. The db migration was fixed by removing 0009_auto_... Creating a remote is fine and I don't see any errors in the log. Two other 3.3.1 hosts that we installed from the scratch work fine. As we are planning to migrate another 3.2 with over 500 repos, I'd like to find out what cause this and if it can be fixed so we don't run into the same issue when migrate production. Thanks___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulp 3.2 rel 8 repo sync
Hi Tanya,
I created a new issue https://pulp.plan.io/issues/6717. I didn't have the 2nd
issue on 3.3.1.
Thanks
From: ttere...@redhat.com At: 05/12/20 06:15:55To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.2 rel 8 repo sync
Hi Bin,
Both look like Pulp issues to me, or at least it's worth investigating if Pulp
handles everything correctly.
With pulp_rpm 3.3.1, I was able to reproduce #1 but not #2. Could you file a
bug for #1?
If you are using pulp 3.2, consider upgrading to 3.3.1 and let us know if you
still encounter the issue #2.
There are many improvements and fixes in 3.3, including handling of relative
paths, so it's possible that you'll see it in 3.2 only.
Thank you,
Tanya
On Tue, May 12, 2020 at 3:30 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
Got two errors below to sync rel 8 repo that I haven't seen before. Are they
related to upstream repo or it could be a pulp issue?
1.
rhel-8.2-for-x86_64-appstream-source-rpms{
"created_resources": [],
"error": {
"description": "integer out of range\n",
"traceback": " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line
884, in perform_job\nrv = job.perform()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
664, in perform\nself._result = self._execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
line 152, in synchronize\ndv.create()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\",
line 149, in create\nloop.run_until_complete(pipeline)\n File
\"/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py\", line 584, in
run_until_complete\nreturn future.result()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\",
line 228, in create_pipeline\nawait asyncio.gather(*futures)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\",
line 43, in __call__\nawait self.run()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/artifact_stages.py\",
line 219, in run\n
RemoteArtifact.objects.bulk_get_or_create(self._needed_remote_artifacts(batch))\n
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/models/content.py\",
line 48, in bulk_get_or_create\nreturn super().bulk_create(objs,
batch_size=batch_size)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/manager.py\",
line 82, in manager_method\nreturn getattr(self.get_queryset(),
name)(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\",
line 468, in bulk_create\nself._batched_insert(objs_with_pk, fields,
batch_size, ignore_conflicts=ignore_conflicts)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\",
line 1204, in _batched_insert\nignore_conflicts=ignore_conflicts,\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\",
line 1186, in _insert\nreturn
query.get_compiler(using=using).execute_sql(return_id)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\",
line 1375, in execute_sql\ncursor.execute(sql, params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 67, in execute\nreturn self._execute_with_wrappers(sql, params,
many=False, executor=self._execute)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 76, in _execute_with_wrappers\nreturn executor(sql, params, many,
context)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _execute\nreturn self.cursor.execute(sql, params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py\",
line 89, in __exit__\nraise dj_exc_value.with_traceback(traceback) from
exc_value\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _execute\nreturn self.cursor.execute(sql, params)\n"
},
2.
rhel-8.2-for-x86_64-baseos-rpms
"error": {
"description": "No declared artifact with relative path
\"repodata/ad
[Pulp-list] pulp 3.2 rel 8 repo sync
Got two errors below to sync rel 8 repo that I haven't seen before. Are they
related to upstream repo or it could be a pulp issue?
1.
rhel-8.2-for-x86_64-appstream-source-rpms{
"created_resources": [],
"error": {
"description": "integer out of range\n",
"traceback": " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line
884, in perform_job\nrv = job.perform()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
664, in perform\nself._result = self._execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
line 152, in synchronize\ndv.create()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\",
line 149, in create\nloop.run_until_complete(pipeline)\n File
\"/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py\", line 584, in
run_until_complete\nreturn future.result()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\",
line 228, in create_pipeline\nawait asyncio.gather(*futures)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\",
line 43, in __call__\nawait self.run()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/artifact_stages.py\",
line 219, in run\n
RemoteArtifact.objects.bulk_get_or_create(self._needed_remote_artifacts(batch))\n
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/models/content.py\",
line 48, in bulk_get_or_create\nreturn super().bulk_create(objs,
batch_size=batch_size)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/manager.py\",
line 82, in manager_method\nreturn getattr(self.get_queryset(),
name)(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\",
line 468, in bulk_create\nself._batched_insert(objs_with_pk, fields,
batch_size, ignore_conflicts=ignore_conflicts)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\",
line 1204, in _batched_insert\nignore_conflicts=ignore_conflicts,\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/query.py\",
line 1186, in _insert\nreturn
query.get_compiler(using=using).execute_sql(return_id)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/models/sql/compiler.py\",
line 1375, in execute_sql\ncursor.execute(sql, params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 67, in execute\nreturn self._execute_with_wrappers(sql, params,
many=False, executor=self._execute)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 76, in _execute_with_wrappers\nreturn executor(sql, params, many,
context)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _execute\nreturn self.cursor.execute(sql, params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py\",
line 89, in __exit__\nraise dj_exc_value.with_traceback(traceback) from
exc_value\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _execute\nreturn self.cursor.execute(sql, params)\n"
},
2.
rhel-8.2-for-x86_64-baseos-rpms
"error": {
"description": "No declared artifact with relative path
\"repodata/adff8e65-8c3c-4ffb-bb72-5d4116fab7c9\" for content
\"\"",
"traceback": " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line
884, in perform_job\nrv = job.perform()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
664, in perform\nself._result = self._execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
line 152, in synchronize\ndv.create()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\",
line 149, in create\nloop.run_until_complete(pipeline)\n File
\"/opt/python/3.7.3/lib64/python3.7/asyncio/base_events.py\", line 584, in
run_until_complete\nreturn future.result()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/api.py\",
line 228, in create_pipeline\nawait
Re: [Pulp-list] pulp 3.2.0 error: advisories have the same id
Hi, Tanya
Sync which mirror=True works. No more error. Thanks for your help.
From: ttere...@redhat.com At: 05/11/20 05:13:16To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.2.0 error: advisories have the same id
Hi Bin,
This error is always tricky, it can be valid and it can be a bug,so we need to
know some details of what happened to a repo before.
The issue [0] you are referencing is for a mirror mode. Do you sync with
mirror=True?
Have there been any modifications (uploaded, copied content, sync from
different remote) to a repository or was it the following scenario:
- created a repo and synced EPEL7
- resynced it again into the same repo using the same remote and got the
AdvisoryConflict error?
Thank you,
Tanya
[0] https://pulp.plan.io/issues/5924
On Sat, May 9, 2020 at 2:56 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
This issue https://pulp.plan.io/issues/5924 was fixed and closed for 3.2.
However we got the the similar errors when sync epel7. Is this a new issue?
"description": "Incoming and existing advisories have the same id and
timestamp but different and intersecting package lists. At least one of them is
wrong. Advisory id: FEDORA-EPEL-2020-1dafb95591",
"traceback": " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line
884, in perform_job\nrv = job.perform()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
664, in perform\nself._result = self._execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
line 152, in synchronize\ndv.create()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\",
line 149, in create\nloop.run_until_complete(pipeline)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/models/repository.py\",
line 782, in __exit__\nrepository.finalize_new_version(self)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/models/repository.py\",
line 120, in finalize_new_version\nresolve_advisories(new_version,
previous_version)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/advisory.py\",
line 65, in resolve_advisories\nprevious_advisory, added_advisory\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/advisory.py\",
line 138, in resolve_advisory_conflict\nraise AdvisoryConflict(_('Incoming
and existing advisories have the same id and '\n"
___
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] pulp 3.2.0 error: advisories have the same id
This issue https://pulp.plan.io/issues/5924 was fixed and closed for 3.2.
However we got the the similar errors when sync epel7. Is this a new issue?
"description": "Incoming and existing advisories have the same id and
timestamp but different and intersecting package lists. At least one of them is
wrong. Advisory id: FEDORA-EPEL-2020-1dafb95591",
"traceback": " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line
884, in perform_job\nrv = job.perform()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
664, in perform\nself._result = self._execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
670, in _execute\nreturn self.func(*self.args, **self.kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
line 152, in synchronize\ndv.create()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\",
line 149, in create\nloop.run_until_complete(pipeline)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/models/repository.py\",
line 782, in __exit__\nrepository.finalize_new_version(self)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/models/repository.py\",
line 120, in finalize_new_version\nresolve_advisories(new_version,
previous_version)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/advisory.py\",
line 65, in resolve_advisories\nprevious_advisory, added_advisory\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/advisory.py\",
line 138, in resolve_advisory_conflict\nraise AdvisoryConflict(_('Incoming
and existing advisories have the same id and '\n"
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] 3.3.1 migration error
Got a different error when try upgrade from another host. I am sure it will be
fine if I remove entire pulp install directory. It is interesting to see that I
got different error by following the same process on different host. For this
host, I install last version 3.3 from scratch instead the manual workaround.
TASK [pulp : Run pip-compile to check pulpcore/plugin compatibility]
**
[WARNING]: conditional statements should not include jinja2 templating
delimiters such as {{ }} or {% %}. Found: {{ failed_condition |
default("compatibility.rc != 0") }}
fatal: [pulp3-1]: FAILED! => {"changed": false, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/pip-compile"], "delta": "0:00:00.500886",
"end": "2020-05-08 18:32:04.309943", "failed_when_result": true, "msg":
"non-zero return code", "rc": 1, "start": "2020-05-08 18:32:03.809057",
"stderr": "Traceback (most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/bin/pip-compile\", line 8, in \n
sys.exit(cli())\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 764, in __call__\nreturn self.main(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 717, in main\nrv = self.invoke(ctx)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 956, in invoke\nreturn ctx.invoke(self.callback, **ctx.params)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 555, in invoke\nreturn callback(*args, **kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/decorators.py\",
line 17, in new_func\nreturn f(get_current_context(), *args, **kwargs)\n
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/piptools/scripts/compile.py\",
line 304, in cli\nfor ireq in filter(is_pinned_requirement, ireqs):\n
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/piptools/utils.py\",
line 122, in is_pinned_requirement\nif ireq.editable:\nAttributeError:
'ParsedRequirement' object has no attribute 'editable'", "stderr_lines":
["Traceback (most recent call last):", " File
\"/opt/utils/venv/pulp/3.7.3/bin/pip-compile\", line 8, in ", "
sys.exit(cli())", " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 764, in __call__", "return self.main(*args, **kwargs)", " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 717, in main", "rv = self.invoke(ctx)", " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 956, in invoke", "return ctx.invoke(self.callback, **ctx.params)", "
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/core.py\",
line 555, in invoke", "return callback(*args, **kwargs)", " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/click/decorators.py\",
line 17, in new_func", "return f(get_current_context(), *args, **kwargs)",
" File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/piptools/scripts/compile.py\",
line 304, in cli", "for ireq in filter(is_pinned_requirement, ireqs):", "
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/piptools/utils.py\",
line 122, in is_pinned_requirement", "if ireq.editable:", "AttributeError:
'ParsedRequirement' object has no attribute 'editable'"], "stdout": "",
"stdout_lines": []}
From: dkli...@redhat.com At: 05/08/20 17:56:41To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: ggai...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] 3.3.1 migration error
I filed the issue about the requirements.in file[0]. In the meantime you could
manually install pulp_rpm using pip. Then run 'pulpcore-manager migrate'.
[0] https://pulp.plan.io/issues/6697
On Fri, May 8, 2020 at 5:48 PM Dennis Kliban wrote:
This looks like a bug in pulp_installer. There is supposed to be a newline
between pulp-rpm-client and pulp-file-client. I'll file the issue and we'll try
to get a fix out on Monday.
On Fri, May 8, 2020 at 5:35 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
After remove entire pulp installation directory. Now I am getting an error
fatal: [pulp3-2]: FAILED! => {"changed": false, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/pip-compile"],
Re: [Pulp-list] 3.3.1 migration error
After remove entire pulp installation directory. Now I am getting an error
fatal: [pulp3-2]: FAILED! => {"changed": false, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/pip-compile"], "delta": "0:00:00.778728",
"end": "2020-05-08 17:26:32.680701", "failed_when_result": true, "msg":
"non-zero return code", "rc": 2, "start": "2020-05-08 17:26:31.901973",
"stderr": "Could not find a version that matches
pulp-rpm-clientpulp-file-client (from -r requirements.in (line 6))\nNo versions
found\nWas
https://artifactory.inf.bloomberg.com/artifactory/api/pypi/bloomberg-pypi-ose/simple
reachable?", "stderr_lines": ["Could not find a version that matches
pulp-rpm-clientpulp-file-client (from -r requirements.in (line 6))", "No
versions found", "Was
https://artifactory.inf.bloomberg.com/artifactory/api/pypi/bloomberg-pypi-ose/simple
reachable?"], "stdout": "", "stdout_lines": []}
It looks like this file is wrong
# more /opt/utils/venv/pulp/3.7.3/requirements.in
pulpcore==3.3.1
pulp-file==0.3.0
pulp-rpm==3.3.1
# Any plugins listed below were already installed but not specified in
# pulp_install_plugins
pulp-rpm-clientpulp-file-client
From: Bin Li (BLOOMBERG/ 120 PARK) At: 05/08/20 17:15:02To: ggai...@redhat.com
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] 3.3.1 migration error
No idea where it came from. The timestamp is from 4/25. I run pip uninstall
pulp-rpm and it didn't remove it.
# ls -ld
/opt/utils/venv/pulp/3.7.3/lib/python3.7/site-packages/pulp_rpm/app/migrations/0009_auto_20200425_1932.py
-rw-rw-r-- 1 pulp mse-python 492 Apr 25 15:32
/opt/utils/venv/pulp/3.7.3/lib/python3.7/site-packages/pulp_rpm/app/migrations/0009_auto_20200425_1932.py
# more
/opt/utils/venv/pulp/3.7.3/lib/python3.7/site-packages/pulp_rpm/app/migrations/0009_auto_20200425_1932.py
# Generated by Django 2.2.12 on 2020-04-25 19:32
from django.db import migrations, models
class Migration(migrations.Migration):
dependencies = [
('rpm', '0008_advisory_pkg_sumtype_as_int'),
]
operations = [
migrations.AlterField(
model_name='updatecollectionpackage',
name='sum_type',
field=models.PositiveIntegerField(choices=[(0, 0), (1, 1), (2, 2),
(3, 3), (4, 4), (5, 5), (6, 6), (7, 7)], null=True),
),
From: ggai...@redhat.com At: 05/08/20 16:21:45To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] 3.3.1 migration error
Hey there!
On Fri, May 8, 2020 at 3:53 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
Hi All,
Getting an error to upgrade from 3.3. run 'python manage.py makemigrations
--merge' gave more errors. Anyidea how this can be fixed?
TASK [pulp-database : Run database auth migrations]
**
fatal: [pulp3-2]: FAILED! => {"changed": true, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "auth",
"--no-input"], "delta": "0:00:03.534845", "end": "2020-05-08 15:44:20.362670",
"msg": "non-zero return code", "rc": 1, "start": "2020-05-08 15:44:16.827825",
"stderr": "CommandError: Conflicting migrations detected; multiple leaf nodes
in the migration graph: (0009_revision_null, 0009_auto_20200425_1932 in
rpm).\nTo fix them run 'python manage.py makemigrations --merge'",
"stderr_lines": ["CommandError: Conflicting migrations detected; multiple leaf
nodes in the migration graph: (0009_revision_null, 0009_auto_20200425_1932 in
rpm).", "To fix them run 'python manage.py makemigrations --merge'"], "stdout":
"", "stdout_lines": []}
Where did migration "0009_auto_20200425_1932" come from? Looks like it's
conflicting with the delivered 0009_revision_null and causing your problem.
G--
Grant Gainey
Principal Software Engineer, Red Hat System Management Engineering
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] 3.3.1 migration error
No idea where it came from. The timestamp is from 4/25. I run pip uninstall
pulp-rpm and it didn't remove it.
# ls -ld
/opt/utils/venv/pulp/3.7.3/lib/python3.7/site-packages/pulp_rpm/app/migrations/0009_auto_20200425_1932.py
-rw-rw-r-- 1 pulp mse-python 492 Apr 25 15:32
/opt/utils/venv/pulp/3.7.3/lib/python3.7/site-packages/pulp_rpm/app/migrations/0009_auto_20200425_1932.py
# more
/opt/utils/venv/pulp/3.7.3/lib/python3.7/site-packages/pulp_rpm/app/migrations/0009_auto_20200425_1932.py
# Generated by Django 2.2.12 on 2020-04-25 19:32
from django.db import migrations, models
class Migration(migrations.Migration):
dependencies = [
('rpm', '0008_advisory_pkg_sumtype_as_int'),
]
operations = [
migrations.AlterField(
model_name='updatecollectionpackage',
name='sum_type',
field=models.PositiveIntegerField(choices=[(0, 0), (1, 1), (2, 2),
(3, 3), (4, 4), (5, 5), (6, 6), (7, 7)], null=True),
),
From: ggai...@redhat.com At: 05/08/20 16:21:45To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] 3.3.1 migration error
Hey there!
On Fri, May 8, 2020 at 3:53 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
Hi All,
Getting an error to upgrade from 3.3. run 'python manage.py makemigrations
--merge' gave more errors. Anyidea how this can be fixed?
TASK [pulp-database : Run database auth migrations]
**
fatal: [pulp3-2]: FAILED! => {"changed": true, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "auth",
"--no-input"], "delta": "0:00:03.534845", "end": "2020-05-08 15:44:20.362670",
"msg": "non-zero return code", "rc": 1, "start": "2020-05-08 15:44:16.827825",
"stderr": "CommandError: Conflicting migrations detected; multiple leaf nodes
in the migration graph: (0009_revision_null, 0009_auto_20200425_1932 in
rpm).\nTo fix them run 'python manage.py makemigrations --merge'",
"stderr_lines": ["CommandError: Conflicting migrations detected; multiple leaf
nodes in the migration graph: (0009_revision_null, 0009_auto_20200425_1932 in
rpm).", "To fix them run 'python manage.py makemigrations --merge'"], "stdout":
"", "stdout_lines": []}
Where did migration "0009_auto_20200425_1932" come from? Looks like it's
conflicting with the delivered 0009_revision_null and causing your problem.
G--
Grant Gainey
Principal Software Engineer, Red Hat System Management Engineering
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] upgrade to 3.3
Yes, the database role worked with pulp_install_db set to false. Thanks Mike
From: mikedep...@redhat.com At: 05/08/20 16:30:45To: Bin Li (BLOOMBERG/ 120
PARK )
Cc: bmbou...@redhat.com, pulp-list@redhat.com, fabricio.agu...@redhat.com
Subject: Re: [Pulp-list] upgrade to 3.3
Also, I'd like to know if the database role worked for you or not with
pulp_install_db set.
(We want to make sure our docs on the role are good enough, and that we can
support any reasonable use case.)
On Fri, May 8, 2020 at 4:19 PM Mike DePaulo wrote:
FYI, we wrote up the issue mentioned in our last 2 emails, and plan to address
it soon. We'll probably ignore `upgrade: true` whenever `version` is set.
https://pulp.plan.io/issues/6669
On Thu, Apr 30, 2020 at 6:58 PM Mike DePaulo wrote:
You have to set either "version" or "upgrade" for each plugin.
That is a known issue I intend to address.
-Mike
On Thu, Apr 30, 2020 at 6:39 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
Thanks Brian and Mike for looking into this.
I tried to set the version in the pulp_install_plugins below but got the errors
pulp_install_plugins:
pulp-file:
upgrade: true
version: '0.3.0'
pulp-rpm:
upgrade: true
version: '3.3.0'
---
TASK [pulp : Install Pulp plugins via PyPI]
***
failed: [pulp3] (item={'value': {u'upgrade': True, u'version': u'0.3.0'},
'key': u'pulp-file'}) => {"ansible_loop_var": "item", "changed": false, "item":
{"key": "pulp-file", "value": {"upgrade": true, "version": "0.3.0"}}, "msg":
"version is incompatible with state=latest"}
failed: [pulp3] (item={'value': {u'upgrade': True, u'version': u'3.3.0'},
'key': u'pulp-rpm'}) => {"ansible_loop_var": "item", "changed": false, "item":
{"key": "pulp-rpm", "value": {"upgrade": true, "version": "3.3.0"}}, "msg":
"version is incompatible with state=latest"}
From: bmbou...@redhat.com At: 04/30/20 12:20:58To: mikedep...@redhat.com
Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com,
fabricio.agu...@redhat.com
Subject: Re: [Pulp-list] upgrade to 3.3
Hi Bin,
Another user reported a similar error to you, and I've filed this issue
https://pulp.plan.io/issues/6623 The "pre-flight" check is designed to verify
that the pulpcore version being installed/upgraded to is compatible with all
plugins that will be installed prior to any bits installing and stop the user
from continuing if there is a conflict. In your case the conflict is occuring
after all the installation has occurred, yet it can't finish due to the
conflict. I believe the pre-flight test does not work correctly in all cases.
I'm going to advocate for us to fix this bug soon.
Thanks,
Brian
On Wed, Apr 29, 2020 at 3:47 PM Mike DePaulo wrote:
Hi Bin,
Usually whenever you upgrade pulpcore (X.Y release), you need to upgrade the
plugins.
If you run it right after pulpcore release, your updated plugins may not be
available yet on PyPI.
You can upgrade plugins by specifying one of these 2 sub-variables under
`pulp_install_plugins.plugin-name`[1]:
`upgrade: true`
`version: "3.3.0"`
Where "3.3.0" is an actual released version of the plugin.[2]
The latter is safer (but more work) since `upgrade` tries the latest version no
matter what, pulpcore compatible or not.
We are also wondering why this task didn't fail. It should fail as a
precaution; so as to stop the installer early on & not break your install:
`pulp: Run pip-compile to check pulpcore/plugin compatibility`
Do you have any output from that task?
As for the external postgresql database, It shouldn't affect pip installs. But
there are the django migrations to run within the role. Without the migrations,
the pip install would work, but Pulp would not function. You should include the
role, but set `pulp_install_db` to false.[3]
-Mike
[1] https://github.com/pulp/pulp_installer/tree/master/roles/pulp#role-variables
[2] https://pypi.org/search/?q=pulp=
[3]
https://github.com/pulp/pulp_installer/tree/master/roles/pulp-database#pulp-database
On Wed, Apr 29, 2020 at 1:33 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
We are using the latest version of installer. It upgraded the pulpcore but not
plugins.# grep 3.3 README.md
This version of the installer, 3.3.0, installs Pulp 3.3.0 specifically.
If run against an older version of Pulp 3, it will upgrade it to 3.3.0.
We are using external postrgresql database so we exclude the pulp-database role
from playbook. Could this cause the issue?
From: dkli...@redhat.com At: 04/29/20 11:00:14To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: fabricio.agu...@redhat.com, pulp-list@redhat.com
Subject: Re:
[Pulp-list] 3.3.1 migration error
Hi All,
Getting an error to upgrade from 3.3. run 'python manage.py makemigrations
--merge' gave more errors. Anyidea how this can be fixed?
TASK [pulp-database : Run database auth migrations]
**
fatal: [pulp3-2]: FAILED! => {"changed": true, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "auth",
"--no-input"], "delta": "0:00:03.534845", "end": "2020-05-08 15:44:20.362670",
"msg": "non-zero return code", "rc": 1, "start": "2020-05-08 15:44:16.827825",
"stderr": "CommandError: Conflicting migrations detected; multiple leaf nodes
in the migration graph: (0009_revision_null, 0009_auto_20200425_1932 in
rpm).\nTo fix them run 'python manage.py makemigrations --merge'",
"stderr_lines": ["CommandError: Conflicting migrations detected; multiple leaf
nodes in the migration graph: (0009_revision_null, 0009_auto_20200425_1932 in
rpm).", "To fix them run 'python manage.py makemigrations --merge'"], "stdout":
"", "stdout_lines": []}
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
I wonder if we could set the below in /etc/pulp/settings.py. The doc use a
tuple. I replaced with a list since I couldn't figure out how to set a tuple in
ansible pulp_installer. It seems to work.
REST_FRAMEWORK__DEFAULT_AUTHENTICATION_CLASSES =
["rest_framework.authentication.SessionAuthentication", "pulpcore.app.authentica
tion.PulpRemoteUserAuthentication"]
Thanks.
From: Bin Li (BLOOMBERG/ 120 PARK) At: 04/24/20 22:40:15To: dkli...@redhat.com
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
Thanks Dennis. It works now by setting proxy_set_header REMOTE_USER 'admin' in
nginx.conf. It was set to $remote_user.
From: dkli...@redhat.com At: 04/23/20 08:11:20To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulpcore-client 3.2 ldap authentication
All the settings look correct to me. It seems like nginx is not setting
HTTP_REMOTE_USER header on the request it passes to guincorn. The value of this
header needs to always be 'admin' since that is the only user in the system
right now.
On Wed, Apr 22, 2020 at 9:43 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
Django app detected
Working in development environment
BASE_DIR
'/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app'
DEBUG False
ALLOWED_HOSTS ['*']
MEDIA_ROOT '/var/lib/pulp/'
STATIC_ROOT '/var/lib/pulp/assets/'
DEFAULT_FILE_STORAGE 'pulpcore.app.models.storage.FileSystem'
FILE_UPLOAD_TEMP_DIR '/var/lib/pulp/tmp/'
WORKING_DIRECTORY '/var/lib/pulp/tmp/'
FILE_UPLOAD_HANDLERS ['pulpcore.app.files.HashingFileUploadHandler']
SECRET_KEY '3e$d+861lqv8x6y39p%^0!3(=%jzw6()g!u44%(=u@1_5p42g!'
INSTALLED_APPS ['django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'django_filters',
'drf_yasg',
'rest_framework',
'pulpcore.app',
'pulp_rpm.app.PulpRpmPluginAppConfig',
'pulp_file.app.PulpFilePluginAppConfig']
INSTALLED_PULP_PLUGINS ['pulp_rpm', 'pulp_file']
OPTIONAL_APPS ['crispy_forms', 'django_extensions', 'storages']
MIDDLEWARE ['django.middleware.security.SecurityMiddleware',
'whitenoise.middleware.WhiteNoiseMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware']
AUTHENTICATION_BACKENDS
['pulpcore.app.authentication.PulpNoCreateRemoteUserBackend']
ROOT_URLCONF 'pulpcore.app.urls'
TEMPLATES [{'APP_DIRS': True,
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS':
['/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/templates'],
'OPTIONS': {'context_processors': ['django.template.context_processors.debug',
'django.template.context_processors.request',
'django.contrib.auth.context_processors.auth',
'django.contrib.messages.context_processors.messages']}}]
WSGI_APPLICATION 'pulpcore.app.wsgi.application'
REST_FRAMEWORK {'DEFAULT_AUTHENTICATION_CLASSES':
['rest_framework.authentication.SessionAuthentication',
'pulpcore.app.authentication.PulpRemoteUserAuthentication'],
'DEFAULT_FILTER_BACKENDS':
['django_filters.rest_framework.DjangoFilterBackend'],
'DEFAULT_PAGINATION_CLASS': 'rest_framework.pagination.LimitOffsetPagination',
'DEFAULT_PERMISSION_CLASSES': ['rest_framework.permissions.IsAuthenticated'],
'DEFAULT_VERSIONING_CLASS': 'rest_framework.versioning.URLPathVersioning',
'PAGE_SIZE': 100,
'UPLOADED_FILES_USE_URL': False,
'URL_FIELD_NAME': 'pulp_href'}
AUTH_PASSWORD_VALIDATORS [{'NAME':
'django.contrib.auth.password_validation.UserAttributeSimilarityValidator'},
{'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator'},
{'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator'},
{'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator'}]
LANGUAGE_CODE 'en-us'
TIME_ZONE 'UTC'
USE_I18N ['USE_I18N', True]
USE_L10N True
USE_TZ True
STATIC_URL '/static/'
DATABASES {'default': {'ENGINE': 'django.db.backends.postgresql_psycopg2',
'HOST': 'localhost',
'NAME': 'pulp',
'PASSWORD': 'pulp',
'PORT': 5432,
'USER': 'pulp'}}
LOGGING {'disable_existing_loggers': False,
'formatters': {'simple': {'format': 'pulp: %(name)s:%(levelname)s: '
'%(message)s'}},
'handlers': {'console': {'class': 'logging.StreamHandler',
'formatter': 'simple'}},
'loggers': {'': {'handlers': ['console'], 'level': 'INFO'}},
'version': 1}
CONTENT_PATH_PREFIX '/pulp/content/'
CONTENT_APP_TTL 120
REMO
Re: [Pulp-list] pulp 3.3 db migration
Is there a workaround or I cannot upgrade before this is fixed?
Thanks
From: dkli...@redhat.com At: 05/04/20 15:52:16To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3 db migration
Please file a bug.
This is a problem with a migration that adds the ability to track when an RPM
repository can skip syncing from the remote repository because the metadata is
the same as it was during the previous sync. The migration is failing to
provide a default value for databases that are being upgraded.
On Mon, May 4, 2020 at 3:09 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
Hi,
Keep getting this error from ansible_install to upgrade from 3.2 to 3.3. What
could cause this and how can we fix it?
Thanks
TASK [pulp-database : Run database migrations]
**
fatal: [pulp3-1]: FAILED! => {"changed": true, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/django -admin",
"migrate", "--no-input"], "delta": "0:00:03.879347", "end": "2020-05-04
14:54:18.580 273", "msg": "non-zero return code", "rc":
1, "start": "2020-05-04 14:54:14.700926", "stderr" :
"Traceback (most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/si
te-packages/django/db/backends/utils.py\", line 84, in _execute\nreturn
self.cursor.execu te(sql,
params)\npsycopg2.errors.NotNullViolation: column \"last_sync_revision_number\"
conta ins null values\n\n\nThe above exception was the
direct cause of the following exception:\n\n Traceback
(most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", l ine 8,
in \nsys.exit(execute_from_command_line())\n File
\"/opt/utils/venv/pulp/
3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\", line
381, in execut e_from_command_line\n
utility.execute()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3
.7/site-packages/django/core/management/__init__.py\", line 375, in
execute\nself.fetch_c
ommand(subcommand).run_from_argv(self.argv)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python
3.7/site-packages/django/core/management/base.py\", line 323, in
run_from_argv\nself.exec ute(*args, **cmd_options)\n
File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/
django/core/management/base.py\", line 364, in execute\noutput =
self.handle(*args, **opt ions)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/manageme
nt/base.py\", line 83, in wrapped\nres =
handle_func(*args, **kwargs)\n File \"/opt/util
s/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
line 234, in handle\nfake_initial=fake_initial,\n
File \"/opt/utils/venv/pulp/3.7.3/lib
64/python3.7/site-packages/django/db/migrations/executor.py\", line 117, in
migrate\nstat e = self._migrate_all_forwards(state,
plan, full_plan, fake=fake, fake_initial=fake_initial)\ n
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/execu
tor.py\", line 147, in _migrate_all_forwards\nstate
= self.apply_migration(state, migrati on, fake=fake,
fake_initial=fake_initial)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.
7/site-packages/django/db/migrations/executor.py\", line
245, in apply_migration\nstate =
migration.apply(state, schema_editor)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/s
ite-packages/django/db/migrations/migration.py\", line 124, in apply\n
operation.database_ forwards(self.app_label,
schema_editor, old_state, project_state)\n File \"/opt/utils/venv/p
ulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/fields.py\",
line 112 , in database_forwards\nfield,\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-
packages/django/db/backends/base/schema.py\", line 447, in add_field\n
self.execute(sql, p arams)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/
[Pulp-list] pulp 3.3 db migration
Hi,
Keep getting this error from ansible_install to upgrade from 3.2 to 3.3. What
could cause this and how can we fix it?
Thanks
TASK [pulp-database : Run database migrations]
**
fatal: [pulp3-1]: FAILED! => {"changed": true, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/django -admin",
"migrate", "--no-input"], "delta": "0:00:03.879347", "end": "2020-05-04
14:54:18.580 273", "msg": "non-zero return code", "rc":
1, "start": "2020-05-04 14:54:14.700926", "stderr" :
"Traceback (most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/si
te-packages/django/db/backends/utils.py\", line 84, in _execute\nreturn
self.cursor.execu te(sql,
params)\npsycopg2.errors.NotNullViolation: column \"last_sync_revision_number\"
conta ins null values\n\n\nThe above exception was the
direct cause of the following exception:\n\n Traceback
(most recent call last):\n File
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", l ine 8,
in \nsys.exit(execute_from_command_line())\n File
\"/opt/utils/venv/pulp/
3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\", line
381, in execut e_from_command_line\n
utility.execute()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3
.7/site-packages/django/core/management/__init__.py\", line 375, in
execute\nself.fetch_c
ommand(subcommand).run_from_argv(self.argv)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python
3.7/site-packages/django/core/management/base.py\", line 323, in
run_from_argv\nself.exec ute(*args, **cmd_options)\n
File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/
django/core/management/base.py\", line 364, in execute\noutput =
self.handle(*args, **opt ions)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/manageme
nt/base.py\", line 83, in wrapped\nres =
handle_func(*args, **kwargs)\n File \"/opt/util
s/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
line 234, in handle\nfake_initial=fake_initial,\n
File \"/opt/utils/venv/pulp/3.7.3/lib
64/python3.7/site-packages/django/db/migrations/executor.py\", line 117, in
migrate\nstat e = self._migrate_all_forwards(state,
plan, full_plan, fake=fake, fake_initial=fake_initial)\ n
File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/execu
tor.py\", line 147, in _migrate_all_forwards\nstate
= self.apply_migration(state, migrati on, fake=fake,
fake_initial=fake_initial)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.
7/site-packages/django/db/migrations/executor.py\", line
245, in apply_migration\nstate =
migration.apply(state, schema_editor)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/s
ite-packages/django/db/migrations/migration.py\", line 124, in apply\n
operation.database_ forwards(self.app_label,
schema_editor, old_state, project_state)\n File \"/opt/utils/venv/p
ulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/fields.py\",
line 112 , in database_forwards\nfield,\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-
packages/django/db/backends/base/schema.py\", line 447, in add_field\n
self.execute(sql, p arams)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/
base/schema.py\", line 137, in execute\n
cursor.execute(sql, params)\n File \"/opt/utils/
venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 67, in exec ute\nreturn
self._execute_with_wrappers(sql, params, many=False, executor=self._execute)\
n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.p
y\", line 76, in _execute_with_wrappers\nreturn
executor(sql, params, many, context)\n F ile
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
line 84, in _execute\nreturn
self.cursor.execute(sql, params)\n File \"/opt/utils/venv/
pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py\", line
Re: [Pulp-list] upgrade to 3.3
Thanks Brian and Mike for looking into this.
I tried to set the version in the pulp_install_plugins below but got the errors
pulp_install_plugins:
pulp-file:
upgrade: true
version: '0.3.0'
pulp-rpm:
upgrade: true
version: '3.3.0'
---
TASK [pulp : Install Pulp plugins via PyPI]
***
failed: [pulp3] (item={'value': {u'upgrade': True, u'version': u'0.3.0'},
'key': u'pulp-file'}) => {"ansible_loop_var": "item", "changed": false, "item":
{"key": "pulp-file", "value": {"upgrade": true, "version": "0.3.0"}}, "msg":
"version is incompatible with state=latest"}
failed: [pulp3] (item={'value': {u'upgrade': True, u'version': u'3.3.0'},
'key': u'pulp-rpm'}) => {"ansible_loop_var": "item", "changed": false, "item":
{"key": "pulp-rpm", "value": {"upgrade": true, "version": "3.3.0"}}, "msg":
"version is incompatible with state=latest"}
From: bmbou...@redhat.com At: 04/30/20 12:20:58To: mikedep...@redhat.com
Cc: Bin Li (BLOOMBERG/ 120 PARK ) , pulp-list@redhat.com,
fabricio.agu...@redhat.com
Subject: Re: [Pulp-list] upgrade to 3.3
Hi Bin,
Another user reported a similar error to you, and I've filed this issue
https://pulp.plan.io/issues/6623 The "pre-flight" check is designed to verify
that the pulpcore version being installed/upgraded to is compatible with all
plugins that will be installed prior to any bits installing and stop the user
from continuing if there is a conflict. In your case the conflict is occuring
after all the installation has occurred, yet it can't finish due to the
conflict. I believe the pre-flight test does not work correctly in all cases.
I'm going to advocate for us to fix this bug soon.
Thanks,
Brian
On Wed, Apr 29, 2020 at 3:47 PM Mike DePaulo wrote:
Hi Bin,
Usually whenever you upgrade pulpcore (X.Y release), you need to upgrade the
plugins.
If you run it right after pulpcore release, your updated plugins may not be
available yet on PyPI.
You can upgrade plugins by specifying one of these 2 sub-variables under
`pulp_install_plugins.plugin-name`[1]:
`upgrade: true`
`version: "3.3.0"`
Where "3.3.0" is an actual released version of the plugin.[2]
The latter is safer (but more work) since `upgrade` tries the latest version no
matter what, pulpcore compatible or not.
We are also wondering why this task didn't fail. It should fail as a
precaution; so as to stop the installer early on & not break your install:
`pulp: Run pip-compile to check pulpcore/plugin compatibility`
Do you have any output from that task?
As for the external postgresql database, It shouldn't affect pip installs. But
there are the django migrations to run within the role. Without the migrations,
the pip install would work, but Pulp would not function. You should include the
role, but set `pulp_install_db` to false.[3]
-Mike
[1] https://github.com/pulp/pulp_installer/tree/master/roles/pulp#role-variables
[2] https://pypi.org/search/?q=pulp=
[3]
https://github.com/pulp/pulp_installer/tree/master/roles/pulp-database#pulp-database
On Wed, Apr 29, 2020 at 1:33 PM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
We are using the latest version of installer. It upgraded the pulpcore but not
plugins.# grep 3.3 README.md
This version of the installer, 3.3.0, installs Pulp 3.3.0 specifically.
If run against an older version of Pulp 3, it will upgrade it to 3.3.0.
We are using external postrgresql database so we exclude the pulp-database role
from playbook. Could this cause the issue?
From: dkli...@redhat.com At: 04/29/20 11:00:14To: Bin Li (BLOOMBERG/ 120 PARK
)
Cc: fabricio.agu...@redhat.com, pulp-list@redhat.com
Subject: Re: [Pulp-list] upgrade to 3.3
It seems like you are using a very old version of pulp_installer (formerly
known as ansible-pulp). What commit are you at?
You should be using pulp_installer 3.3.0 to do the install[0].
[0] https://github.com/pulp/pulp_installer/releases/tag/3.3.0
On Wed, Apr 29, 2020 at 8:12 AM Bin Li (BLOOMBERG/ 120 PARK)
wrote:
Hi Fabricio,
I got the errors below. It looks it only update pulpcore but not the plugins.
RUNNING HANDLER [pulp : Collect static content]
fatal: [pulp3]: FAILED! => {"changed": true, "cmd":
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "collectstatic", "--noinput",
"--link"], "delta": "0:00:00.250852", "end": "2020-04-29 08:08:45.007362",
"msg": "non-zero return code", "rc": 1, "start": "2020-04-29 08:08:44.756510",
"s
