Swift backup driver fails to initialize unless backup_swift_url is set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Alan Bishop |
Bug Description
Unless backup_swift_url is configured, the swift backup driver fails during service startup:
2019-04-23 07:20:49.511 35 ERROR oslo.service.
2019-04-23 07:20:49.511 35 ERROR oslo.service.
2019-04-23 07:20:49.511 35 ERROR oslo.service.
2019-04-23 07:20:49.511 35 ERROR oslo.service.
2019-04-23 07:20:49.511 35 ERROR oslo.service.
2019-04-23 07:20:49.511 35 ERROR oslo.service.
2019-04-23 07:20:49.511 35 ERROR oslo.service.
2019-04-23 07:20:49.511 35 ERROR oslo.service.
2019-04-23 07:20:49.511 35 ERROR oslo.service.
2019-04-23 07:20:49.511 35 ERROR oslo.service.
2019-04-23 07:20:49.511 35 ERROR oslo.service.
2019-04-23 07:20:49.511 35 ERROR oslo.service.
This happens because the driver is trying to use the service catalog in the associated context, but on startup the catalog is empty. Traditionally, the swift driver takes care of this situation in its get_backup_driver [1]. However, with [1] that function is no longer called.
[1] https:/
[2] https:/
The problem can be fixed by putting the same logic in the swift driver's constructor.
Changed in cinder: | |
assignee: | nobody → Alan Bishop (alan-bishop) |
Fix proposed to branch: master /review. opendev. org/655765
Review: https:/