Deployment graph is not being stored into particular Nailgun task(transaction) table
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Ilya Kutukov | ||
Mitaka |
Fix Released
|
High
|
Ilya Kutukov |
Bug Description
fuel-nailgun-
Nailgun tasks table scheme does not contain a field for deployment graph. This seems to be a divergence from our spec for custom graph execution where we expect to store the merged pre-serialized graph into particular nailgun task/transaction.
nailgun=# \d tasks;
id | integer | NOT NULL DEFAULT nextval(
cluster_id | integer |
uuid | character varying(36) | NOT NULL
name | task_name | NOT NULL
message | text |
status | task_status | NOT NULL
progress | integer |
cache | text |
result | text |
parent_id | integer |
weight | double precision |
deleted_at | timestamp without time zone |
deployment_info | text |
cluster_settings | text |
network_settings | text |
tags: | added: team-enhancements |
Changed in fuel: | |
status: | Confirmed → In Progress |
tags: | added: dev-to-verify |
no longer affects: | fuel/newton |
tags: | removed: dev-to-verify |
tags: | added: on-verification |
(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:
actual result
version
expected result
steps to reproduce
For more detailed information on the contents of each of the listed sections see https:/ /wiki.openstack .org/wiki/ Fuel/How_ to_contribute# Here_is_ how_you_ file_a_ bug