Circular dependencies between trove_datastore and trove_datastore_version

Bug #2007961 reported by Takashi Kajinami
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-trove
In Progress
High
Takashi Kajinami

Bug Description

We currently have two resource types in this module.
 - trove_datastore: a wrapper to execute trove-manage datastore_update
 - trove_datastore_version: a wrapper to execute trove-manage datastore_version_update

The current problem is that these two depend on each other.
The trove_datastore resource type executes
 1. trove-manage datastore_update <name> ""
and
 2. trove-manage datastore_update <name> <version>
but the 2nd command requires that trove-manage datastore_version_update is executed BEFORE that.

Changed in puppet-trove:
importance: Undecided → High
assignee: nobody → Takashi Kajinami (kajinamit)
Changed in puppet-trove:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to puppet-trove (master)

Reviewed: https://review.opendev.org/c/openstack/puppet-trove/+/874568
Committed: https://opendev.org/openstack/puppet-trove/commit/ead07878ba361697a10abd7b5b73d4f5c4fbfba2
Submitter: "Zuul (22348)"
Branch: master

commit ead07878ba361697a10abd7b5b73d4f5c4fbfba2
Author: Takashi Kajinami <email address hidden>
Date: Tue Feb 21 21:11:16 2023 +0900

    trove_datastore: Make version optional

    datastore version can't be used until the version is registered but we
    can't register the version before we register datastore before applying
    catalog. This makes version optional to avoid that dependency look.

    Partial-Bug: #2007961
    Change-Id: Ieba9c10b49f41980555e2734bb29415fcf0b585f

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.