client can't register in v1

[suzhengwei]

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-file=/etc/freezer/scheduler.conf start' just exit with simple log:
OS_AUTH_URL should be provides.

[suzhengwei (suzhengwei)]

The cause of this problem seems simple.
It gets apiclient in v1 and v2 in the same way.
https://opendev.org/openstack/freezer/src/branch/master/freezer/scheduler/freezer_scheduler.py L214 L217
But in v1 client it doesn't handle 'opts' parameter.
https://opendev.org/openstack/python-freezerclient/src/branch/master/freezerclient/utils.py L183

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/python-freezerclient/+/892647