But the fix is a bit complicated. I can think of a few option.
1. expose a global configurable option in oslo.versionedobjects to set the tzinfo_aware option.
https://github.com/openstack/oslo.versionedobjects/blob/master/oslo_versionedobjects/fields.py#L453
It shouldn't be per class as a given DB is either timezone-aware or not.
2. expose the option at the service level (i.e. in Nova config) and pass in the tzinfo_aware parameter when we instantiate the DateTimeField.
3. expose a global option in oslo.db and do the conversion there.
But the fix is a bit complicated. I can think of a few option.
1. expose a global configurable option in oslo.versionedo bjects to set the tzinfo_aware option.
https:/ /github. com/openstack/ oslo.versionedo bjects/ blob/master/ oslo_versionedo bjects/ fields. py#L453
It shouldn't be per class as a given DB is either timezone-aware or not.
2. expose the option at the service level (i.e. in Nova config) and pass in the tzinfo_aware parameter when we instantiate the DateTimeField.
3. expose a global option in oslo.db and do the conversion there.