Bug 1651218 - [docs][UPGRADES] document ceph-ansible fetch directory GET/POST URL expiration (13 > 14)
Summary: [docs][UPGRADES] document ceph-ansible fetch directory GET/POST URL expiratio...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-19 13:09 UTC by John Fulton
Modified: 2020-10-11 15:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-07 17:55:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description John Fulton 2018-11-19 13:09:40 UTC
During upgrades from 13 to 14 there is a prepare step and then an external upgrade step. If you used director to deploy Ceph, then these two steps must be run within 24 hours of each other. This is because the prepare step generates a pair of GET/POST URLs to store the ceph-ansible fetch directory but those URLs expire after 24 hours. Both URLs must not have expired during Ceph upgrade. If 24 hours passes, then you may re-run the prepare step to generate fresh URLs.

Please add a note to the documentation covering upgrades from 13 to 14 explaining the above. The prepare step command looks like this:

$ openstack overcloud upgrade prepare \
    --templates \
    -e /home/stack/templates/overcloud_images.yaml \
    -e <ENVIRONMENT FILE>

The external upgrade step for Ceph looks like this:

$ `openstack overcloud external-upgrade run --tags ceph ...` 

If more than 24 hours have passed after running the first command and before running the second command, then the first command must be re-run so that the second command may succeed. Otherwise during upgrade you will see an error like: `Received HTTP: 401 when attempting to GET from ...`


Note You need to log in before you can comment on or make changes to this bug.