86a870cc50
We had two different workflows here using the same variable but expecting it to have a totally different format. The taskmanager dns code was populating that variable with nova api output; the database list code populated it manually with a custom-format structure. This seems to have survived a long time because these are both edge cases: the dns workflow was only traversed with dns integration is switched on (unusual) and the database list only relied on IP addresses when hostnames weren't present. This patch picks a winner (the custom structure used by the database listing code) and modifies the dns workflow to live with that same format. This is spackle over a whole lot of bitrot, but should get both use cases working properly. Story: #2010077 Task: #45568 Change-Id: I5832733dd312db24d2d8047658fdd1af9f4e700a |
||
---|---|---|
.. | ||
__init__.py | ||
api.py | ||
manager.py | ||
models.py | ||
service.py |