Project

Profile

Help

Issue #792

closed

upgrade for 2.5->2.6 does not specify that you need to run pulp-manage-db

Added by pthomas@redhat.com over 9 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
2.6.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation, Pulp 2
Sprint:
Quarter:

Description

Actions #1

Updated by dkliban@redhat.com over 9 years ago

  • Assignee set to dkliban@redhat.com
Actions #2

Updated by dkliban@redhat.com over 9 years ago

  • Status changed from NEW to ASSIGNED
Actions #3

Updated by dkliban@redhat.com over 9 years ago

  • Status changed from ASSIGNED to POST
Actions #4

Updated by dkliban@redhat.com over 9 years ago

  • Status changed from POST to 5
Actions #5

Updated by dkliban@redhat.com over 9 years ago

  • Platform Release set to 2.6.0
Actions #6

Updated by dkliban@redhat.com over 9 years ago

  • Triaged changed from No to Yes
Actions #7

Updated by bmbouter over 9 years ago

  • Category deleted (1)
  • Tags Documentation added

Documentation is now a Tag not a Category.

Actions #8

Updated by igulina@redhat.com over 9 years ago

  • Status changed from 5 to 6

Here http://pulp.readthedocs.org/en/latest/user-guide/release-notes/2.6.x.html#upgrade-instructions-for-2-5-x-2-6-0

there was added:

After yum completes you should migrate the database using:

sudo -u apache pulp-manage-db

After the database migrations finish, restart httpd, pulp_workers, pulp_celerybeat, and pulp_resource_manager.

Actions #9

Updated by rbarlow about 9 years ago

  • Status changed from 6 to CLOSED - CURRENTRELEASE
Actions #11

Updated by bmbouter about 5 years ago

  • Severity set to 2. Medium
Actions #12

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF