Endpoint for object-store not found - have you specified a region?

Bug #1806163 reported by alpha23
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Backup/Restore and DR (Freezer)
New
Undecided
Unassigned

Bug Description

After wasting a significant amount of time on 'freezer-agent' authentication issues, I'm left with the following error:
Critical Error: Endpoint for object-store not found - have you specified a region?

OS_REGION_NAME is specified per https://wiki.openstack.org/wiki/Freezer-docs.

Please advise on any solution and Freezer even works with Queens as explained below and further convoluted by contradictory documentation.

The reason for the wasted time is that no one seems to have the decency to update the documentation so that users are not spending hours guessing on the correct settings. Besides the fact that there are just aspects of the documentation that no one has even bothered to document, the authentication issue stems from the fact that the documentation is either not updated or is categorically false. In https://docs.openstack.org/freezer/latest/user/installation.html, which per the url is the "latest", it clearly states;

# API version v2.0 is very important
# freezer does not work with API version 3"

yet in the aforementioned https://wiki.openstack.org/wiki/Freezer-docs it clearly shows api v3 specified. Which is it? v2 is supported or v2 is not supported?

If the latest is meant for Rocky, then there is clearly a disconnect with the Freezer team because as of Queens, v2 was removed. https://docs.openstack.org/keystone/queens/contributor/http-api.html. Is Freezer supported as of Queens or is Freezer limited to Pike. Or is the whole Freezer documentation just a mess? Given the number of OS projects and the voluminous documentation, projects are unusable when project leads flat out ignore the need for adequate and correct documentation.

Revision history for this message
Deepa (dpaclt) wrote :

any update on this bug ?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.