> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/frequently-asked-questions/unable-source-admin-rc-file-after-pmo-5-8-upgrade.md).

# Unable Source admin.rc File After PMO 5.8 Upgrade

## Problem

Sourcing the admin.rc with the main region FQDN mentioned as the OS\_AUTH\_URL, and specifying the sub-region in the

OS\_REGION\_NAME, ends up in the error "admin endpoint for identity service in region not found", which worked earlier in PMO 5.6 and below.

{% tabs %}
{% tab title="admin.rc" %}

```javascript
export OS_AUTH_URL=https://main-region.platform9.keystone/v3
export OS_IDENTITY_API_VERSION=3
export OS_REGION_NAME="sub-region"
export OS_USERNAME=user@domain.com
export OS_PASSWORD=xxxxxxxxxxx
echo "Please Enter Accessing Site: "
read TENANT_ID
export OS_PROJECT_NAME=$TENANT_ID
export OS_PROJECT_DOMAIN_ID=${OS_PROJECT_DOMAIN_ID:-"default"}
export OS_USER_DOMAIN_ID=${OS_USER_DOMAIN_ID:-"default"}
export OS_PROJECT_ID=$(openstack project show -c id -f value $OS_PROJECT_NAME)
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - v5.8.0 and Higher.

## Answer

Since the keystone in the main region needs to handle the authentication requests for other subregions, from PMO 5.8.0. version onwards, Platform9 reduced Keystone token catalog size by limiting to region scope for all service endpoints.

So for each subregions the admin.rc file should have OS\_AUTH\_URL value with the FQDN of the subregion as shown below:

{% tabs %}
{% tab title="Updated admin.rc" %}

```javascript
export OS_AUTH_URL=https://sub-region.platform9.keystone/v3
export OS_IDENTITY_API_VERSION=3
export OS_REGION_NAME="sub-region"
export OS_USERNAME=user@domain.com
export OS_PASSWORD=xxxxxxxxxxx
echo "Please Enter Accessing Site: "
read TENANT_ID
export OS_PROJECT_NAME=$TENANT_ID
export OS_PROJECT_DOMAIN_ID=${OS_PROJECT_DOMAIN_ID:-"default"}
export OS_USER_DOMAIN_ID=${OS_USER_DOMAIN_ID:-"default"}
export OS_PROJECT_ID=$(openstack project show -c id -f value $OS_PROJECT_NAME)
```

{% endtab %}
{% endtabs %}

Additional Information

Release note: <https://platform9.com/docs/v5.8/openstack/release-notes-openstack>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/frequently-asked-questions/unable-source-admin-rc-file-after-pmo-5-8-upgrade.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.