View Issue Details

IDProjectCategoryView StatusLast Update
1507RackTablesVMs/containerspublic2015-08-26 23:29
Reporterdmnmitsupu Assigned Toadoom42  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version0.20.10 
Target Version0.20.11Fixed in Version0.20.11 
Summary1507: Parent Child relationship bug
DescriptionDiscovered a bug - if a child has multiple parents i.e. server to server chassis and same server to vm cluster, the ID of the object is used for the order of operations so if a child is created after a parent the ordering is affected.

The parent and child relationships are being derived on the basis of IDs. Therefore if you create the objects in the wrong order the relationship is affected.

((child entities in this example are the first blade in 3 different chassis that are all in the same VM Cluster thus 2 parents))

Example:
SELECT * FROM `EntityLink` where `child_entity_id` in (1095, 950, 981)
ORDER BY `EntityLink`.`child_entity_id` ASC

Result:
id parent_entity_type parent_entity_id child_entity_type
child_entity_id
1026 object 1073 object 950
1027 object 872 object 950
596 object 977 object 981
783 object 1073 object 981
1029 object 1457 object 1095
1046 object 1073 object 1095

872, 977, and 1457 are Server Chassis.
1073 is the VM Cluster.
In this case object 1457 displays incorrectly in graphwiz, and the order on the properties page is reversed.
Recreating the VM Cluster new id is 1460 - Everything works perfect.

Isn't it common to create the "top level" parent entity first?
TagsNo tags attached.

Activities

adoom42

adoom42

2015-08-26 21:13

administrator   ~0002945

I fixed container ordering on the Object -> View & Properties pages.

As for the graphviz issue, that is a 3rd-party plugin. Contact the developer for support.
dmnmitsupu

dmnmitsupu

2015-08-26 22:57

reporter   ~0002947

Graphwiz was an example of how this bug affects the outcome. Because the secondary parent was created after the 1st parent is is taking priority in ordering.
adoom42

adoom42

2015-08-26 23:29

administrator   ~0002949

As I already said, the ordering issue has been fixed. It's in commit af8916e901.

Don't re-open this unless you can prove that the commit doesn't really fix it.

Issue History

Date Modified Username Field Change
2015-08-26 17:45 dmnmitsupu New Issue
2015-08-26 17:45 dmnmitsupu Status new => assigned
2015-08-26 17:45 dmnmitsupu Assigned To => adoom42
2015-08-26 21:13 adoom42 Note Added: 0002945
2015-08-26 21:13 adoom42 Status assigned => closed
2015-08-26 21:13 adoom42 Resolution open => fixed
2015-08-26 21:13 adoom42 Fixed in Version => 0.20.11
2015-08-26 21:13 adoom42 Target Version => 0.20.11
2015-08-26 22:57 dmnmitsupu Note Added: 0002947
2015-08-26 22:57 dmnmitsupu Status closed => feedback
2015-08-26 22:57 dmnmitsupu Resolution fixed => reopened
2015-08-26 23:29 adoom42 Note Added: 0002949
2015-08-26 23:29 adoom42 Status feedback => closed
2015-08-26 23:29 adoom42 Resolution reopened => fixed