Yes, the database role worked with pulp_install_db set to false. Thanks Mike
From: [email protected] At: 05/08/20 16:30:45To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: [email protected], [email protected], [email protected] 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 <[email protected]> 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 <[email protected]> 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) <[email protected]> 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: [email protected] At: 04/30/20 12:20:58To: [email protected] Cc: Bin Li (BLOOMBERG/ 120 PARK ) , [email protected], [email protected] 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 <[email protected]> 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&o= [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) <[email protected]> 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: [email protected] At: 04/29/20 11:00:14To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: [email protected], [email protected] 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) <[email protected]> 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", "stderr": "Traceback (most recent call last):\n File \"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in <module>\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 325, in execute\n settings.INSTALLED_APPS\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/conf/__init__.py\", line 79, in __getattr__\n self._setup(name)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/conf/__init__.py\", line 66, in _setup\n self._wrapped = Settings(settings_module)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/conf/__init__.py\", line 157, in __init__\n mod = importlib.import_module(self.SETTINGS_MODULE)\n File \"/opt/python/3.7.3/lib64/python3.7/importlib/__init__.py\", line 127, in import_module\n return _bootstrap._gcd_import(name[level:], package, level)\n File \"<frozen importlib._bootstrap>\", line 1006, in _gcd_import\n File \"<frozen importlib._bootstrap>\", line 983, in _find_and_load\n File \"<frozen importlib._bootstrap>\", line 967, in _find_and_load_unlocked\n File \"<frozen importlib._bootstrap>\", line 677, in _load_unlocked\n File \"<frozen importlib._bootstrap_external>\", line 728, in exec_module\n File \"<frozen importlib._bootstrap>\", line 219, in _call_with_frames_removed\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/settings.py\", line 73, in <module>\n plugin_app_config = entry_point.load()\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pkg_resources/__init__.py\", line 2410, in load\n self.require(*args, **kwargs)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pkg_resources/__init__.py\", line 2433, in require\n items = working_set.resolve(reqs, env, installer, extras=self.extras)\n File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pkg_resources/__init__.py\", line 791, in resolve\n raise VersionConflict(dist, req).with_context(dependent_req)\npkg_resources.VersionConflict: (pulpcore 3.3.0 (/opt/utils/venv/pulp/3.7.3/lib/python3.7/site-packages), Requirement.parse('pulpcore<3.2,>=3.1'))", "stderr_lines": ["Traceback (most recent call last):", " File \"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in <module>", " 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 325, in execute", " settings.INSTALLED_APPS", " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/conf/__init__.py\", line 79, in __getattr__", " self._setup(name)", " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/conf/__init__.py\", line 66, in _setup", " self._wrapped = Settings(settings_module)", " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/conf/__init__.py\", line 157, in __init__", " mod = importlib.import_module(self.SETTINGS_MODULE)", " File \"/opt/python/3.7.3/lib64/python3.7/importlib/__init__.py\", line 127, in import_module", " return _bootstrap._gcd_import(name[level:], package, level)", " File \"<frozen importlib._bootstrap>\", line 1006, in _gcd_import", " File \"<frozen importlib._bootstrap>\", line 983, in _find_and_load", " File \"<frozen importlib._bootstrap>\", line 967, in _find_and_load_unlocked", " File \"<frozen importlib._bootstrap>\", line 677, in _load_unlocked", " File \"<frozen importlib._bootstrap_external>\", line 728, in exec_module", " File \"<frozen importlib._bootstrap>\", line 219, in _call_with_frames_removed", " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/settings.py\", line 73, in <module>", " plugin_app_config = entry_point.load()", " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pkg_resources/__init__.py\", line 2410, in load", " self.require(*args, **kwargs)", " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pkg_resources/__init__.py\", line 2433, in require", " items = working_set.resolve(reqs, env, installer, extras=self.extras)", " File \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pkg_resources/__init__.py\", line 791, in resolve", " raise VersionConflict(dist, req).with_context(dependent_req)", "pkg_resources.VersionConflict: (pulpcore 3.3.0 (/opt/utils/venv/pulp/3.7.3/lib/python3.7/site-packages), Requirement.parse('pulpcore<3.2,>=3.1'))"], "stdout": "", "stdout_lines": []} # pip list |grep pulp pulp-file 0.1.1 pulp-file-client 0.1.1 pulp-rpm 3.1.0 pulp-rpm-client 3.1.0 pulpcore 3.3.0 pulpcore-client 3.1.0 From: [email protected] At: 04/27/20 10:45:29To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: [email protected] Subject: Re: [Pulp-list] upgrade to 3.3 Could you share what was the failure? Best regards, Fabricio Aguiar Software Engineer, Pulp Project Red Hat Brazil - Latam +55 11 999652368 On Fri, Apr 24, 2020 at 11:44 PM Bin Li (BLOOMBERG/ 120 PARK) <[email protected]> wrote: Simple run the pulp_installer failed. It worked after I removed the pulp installation directory. What is the best practice to upgrade pulp to 3.3 from 3.2? Thanks_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list _______________________________________________ Pulp-list mailing list [email protected] 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 [email protected] https://www.redhat.com/mailman/listinfo/pulp-list -- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat IM: mikedep333 GPG: 51745404 -- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat IM: mikedep333 GPG: 51745404 -- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat IM: mikedep333 GPG: 51745404
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
