Traffic Ops Topology with Secondary Parent returns error

[rob05c]

I attempted to create the following Topology in Traffic Portal:

{
  "name": "Foo",
  "description": "bar",
  "nodes": [
    {
      "cachegroup": "mid-west",
      "parent": "",
      "secParent": "",
      "parents": []
    },
    {
      "cachegroup": "sacramento-ca-usa",
      "parent": "mid-west",
      "secParent": "mid-east",
      "parents": [
        0,
        2
      ]
    },
    {
      "cachegroup": "mid-east",
      "parent": "",
      "secParent": "",
      "parents": []
    },
    {
      "cachegroup": "albany-ny-usa",
      "parent": "mid-east",
      "secParent": "mid-west",
      "parents": [
        2,
        0
      ]
    },
    {
      "cachegroup": "tallahassee-fl-usa",
      "parent": "mid-east",
      "secParent": "mid-west",
      "parents": [
        2,
        0
      ]
    }
  ]
}

And Traffic Ops returned the error message

parent 'sacramento-ca-usa' edge type' cachegroup sacramento-ca-usa's type is EDGE_LOC; it cannot be a parent of sacramento-ca-usa

Note in the JSON, sacramento-ca-usa is not a parent of itself. I also sometimes get error messages for the other edges, thinking other edges are parented to edges, when they're not.

It seems to fail with any Secondary CacheGroup assignment. When I remove the secondaries, it succeeds.

I'm submitting a ...

• bug report

Traffic Control components affected ...

• Traffic Ops
• Traffic Portal

Current behavior:

Cannot create Topology with Secondary Parents. See above.

Expected / new behavior:

Ability to create Topology with Secondary Parents.

Minimal reproduction of the problem with instructions:

In Traffic Portal, attempt to create a topology with multiple Mids and multiple Edges, where the edges' secondary is a different Mid.

Anything else: