The endpoint you set using the env variable OS_AUTH_URL is the keystone endpoint to use for authentication by any service. So glance service will talk to that url (whatever you have set it to - internal/public/admin) every time it needs to. So when you set glance's endpoint to use internalURL, it means glance is talking to other services including keystone with its internal url.
glance-cache-manage would be picking up keystone's internal url to talk to as you have set it as your env variable. (By default, glance-cache-manage will talk to whatever is given for OS_AUTH_URL)
So if your glance-cache-manage command does not go through you need to check if your glance's endpoint that you have set as intenralURL (GLANCE_ENDPOINT_TYPE=internalURL) has it registered with keystone. Your other Glance commands might have worked because it was picking up the publicURL of glance to talk to keytsone's internalURL.
Hello Sasikiran,
The endpoint you set using the env variable OS_AUTH_URL is the keystone endpoint to use for authentication by any service. So glance service will talk to that url (whatever you have set it to - internal/ public/ admin) every time it needs to. So when you set glance's endpoint to use internalURL, it means glance is talking to other services including keystone with its internal url. ENDPOINT_ TYPE=internalUR L) has it registered with keystone. Your other Glance commands might have worked because it was picking up the publicURL of glance to talk to keytsone's internalURL.
glance-cache-manage would be picking up keystone's internal url to talk to as you have set it as your env variable. (By default, glance-cache-manage will talk to whatever is given for OS_AUTH_URL)
So if your glance-cache-manage command does not go through you need to check if your glance's endpoint that you have set as intenralURL (GLANCE_