No actions for designate v2 but v1 were removed in Queens release

Bug #1824803 reported by ITD27M01
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mistral
Triaged
Medium
Unassigned

Bug Description

Hello

The Mistral does not have the Designate V2 actions. Designate V1 API and Domain and Record resources were removed in Queens release.

https://github.com/openstack/designate/commit/c318106c01b2b3976049f2c3ba0c8502a874242b

amix (amix307)
description: updated
description: updated
Changed in mistral:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Eyal B (eyalb1) wrote :
Revision history for this message
ITD27M01 (igortiunov) wrote :

Hi, the change https://review.opendev.org/#/c/682785/ broke designate actions at all:

2020-05-03 15:07:42.637 10210 ERROR mistral.actions.openstack.action_generator.base [-] Failed to create action: designate.diagnostics_ping: ValueError: A session instance is required
2020-05-03 15:07:42.637 10210 ERROR mistral.actions.openstack.action_generator.base File "/usr/lib/python3.6/site-packages/designateclient/v2/client.py", line 112, in __init__
2020-05-03 15:07:42.637 10210 ERROR mistral.actions.openstack.action_generator.base raise ValueError("A session instance is required")
2020-05-03 15:07:42.637 10210 ERROR mistral.actions.openstack.action_generator.base ValueError: A session instance is required
2020-05-03 15:07:42.637 10210 ERROR mistral.actions.openstack.action_generator.base ESC[00m

Revision history for this message
ITD27M01 (igortiunov) wrote :

I want to suggest to replace old vocabulary like "domain" and "records" to new "zone" and "recordset":

https://github.com/ITD27M01/mistral-designate-actions

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.