Actions
Issue #792
closedupgrade for 2.5->2.6 does not specify that you need to run pulp-manage-db
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
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
Upgrade from 2.5->2.6 does not mention running pulp-manage-db
Updated by dkliban@redhat.com almost 10 years ago
- Assignee set to dkliban@redhat.com
Updated by dkliban@redhat.com almost 10 years ago
- Status changed from NEW to ASSIGNED
Updated by dkliban@redhat.com almost 10 years ago
- Status changed from ASSIGNED to POST
Updated by dkliban@redhat.com almost 10 years ago
- Triaged changed from No to Yes
Updated by bmbouter almost 10 years ago
- Category deleted (
1) - Tags Documentation added
Documentation is now a Tag not a Category.
Updated by igulina@redhat.com almost 10 years ago
- Status changed from 5 to 6
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.
Updated by rbarlow over 9 years ago
- Status changed from 6 to CLOSED - CURRENTRELEASE
Actions