Fixture is not executing __call__
Bug #1645868 reported by
Lubosz Kosnik
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.config |
Won't Fix
|
Low
|
Unassigned |
Bug Description
oslo config Fixture is not running __call__ on cfg.CONF in other sitatuation than in load_raw_values method.
Based on this using fixture and testing oslo policy code results with exception NotInitializedE
Must be executed probably in __init__ or setup method.
To post a comment you must log in.
The timing for this is a little tricky. After ConfigOpts is initialized, it's not possible to add more command line options. Depending on how the fixture is going to be used, that may cause a problem with the test.
We could add a flag to the fixture's constructor telling it whether to initialize the ConfigOpts instance, but we would need to default to False for now.