client can't register in v1
Bug #2032895 reported by
suzhengwei
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Backup/Restore and DR (Freezer) |
In Progress
|
Undecided
|
suzhengwei | ||
Bug Description
when 'enable_v1_api' is set 'True', it can't register to freezer-api when I start freezer-scheduler in no-daemon mode.
When 'enable_v1_api' is set 'False', freezer-scheduler registers to freezer-api successfully.
Opt 'enable_v1_api' in freezer-api and freezer-scheduler has the same value. And it already has 'os_auth_url' and others auth opts in the scheduler config file.
'freezer-scheduler --config-
OS_AUTH_URL should be provides.
| Changed in freezer: | |
| assignee: | nobody → suzhengwei (suzhengwei) |
| description: | updated |
Revision history for this message
| suzhengwei (suzhengwei) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to python-freezerclient (master) | #2 |
| description: | updated |
| Changed in freezer: | |
| status: | New → In Progress |
To post a comment you must log in.
The cause of this problem seems simple.
It gets apiclient in v1 and v2 in the same way.
https:/
But in v1 client it doesn't handle 'opts' parameter.
https:/