Skip to content
This repository has been archived by the owner on Dec 7, 2022. It is now read-only.

Update release notes about migration caveat #2878

Merged
merged 1 commit into from Dec 6, 2016
Merged

Update release notes about migration caveat #2878

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 10 additions & 1 deletion docs/user-guide/release-notes/2.11.x.rst
View file
Open in desktop
Expand Up @@ -24,9 +24,18 @@ New Features
* For RPM content, a full sync will be forced if the sync configuration has been changed or content
has been removed since the last sync.

* When pulp-manage-db is run, prompt the user to continue if there are Pulp services still running.
* When ``pulp-manage-db`` is run, prompt the user to continue if there are Pulp services still running.

* Memory improvements! Worker process recycling can be enabled to release unused memory back to
the system after tasks complete. This feature is disabled by default. See the
:ref:`process recycling documentation<process_recycling>` for more info. Thank you to Jan-Otto
Kröpke for contributing this feature.

Known Issue
-----------

When upgrading to Pulp 2.11, it's possible that the new feature to ensure all workers are stopped
before migrating the database will erroneously report that the workers are still running. During a
manual upgrade, this is simple to bypass, but if you are using a configuration management tools like
Ansible or Puppet your automation may stall on this. See the :ref:`troubleshooting guide
<ignore-running-workers>` for updating your automation to bypass this check.
11 changes: 7 additions & 4 deletions docs/user-guide/troubleshooting.rst
View file
Open in desktop
Expand Up @@ -287,10 +287,13 @@ Workers not releasing memory
See the :ref:`process recycling documentation<process_recycling>` for more information on how to
have your Pulp workers return memory back to the system.

.. _ignore-running-workers:

pulp-manage-db prompts for running workers when running automated upgrade
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

While running an automated upgrade to Pulp 2.11.x Pulp will prompt you that you have running
workers even though all workers are stopped. When this happens please call `pulp-manage-db` with
the `--ignore-running-workers` flag. This flag should only be used in automation, and the
automation is responsible for ensuring all pulp processes are stopped before the upgrade proceeds.
While running an automated upgrade from a version of Pulp older than 2.11, ``pulp-manage-db`` may
prompt you that you have running workers even though all workers are stopped. If this happens,
call ``pulp-manage-db`` with the ``--ignore-running-workers`` flag. This flag is intended to be used
in automation, and the automation is responsible for ensuring all pulp processes are stopped before
the upgrade can proceed.