Hi Anda,
It will be very helpful if you add this info directly to the bug.
Regards,
Andrey Pavlov.
On Wed, Jul 12, 2017 at 7:09 PM, Anda Nicolae wrote:
> Hi all,
>
>
>
> Thanks a lot for your responses.
>
>
>
> Contrail version I was using when I encountered this bug was 3.2.3.0.
>
> I have checked contrail-schema process status from contrail-status output
> and it is active.
>
> I have also browsed through contrail-schema log, but I did not find
> anything relevant.
>
>
>
> Now I have installed Contrail version 3.2.4.0 and the bug is not
> reproducible.
>
>
>
> *If you know the commit that fixed this, please let me know. I have tried
> to find the functions/modules where the routing logic happens, but without
> any notable results.*
>
>
>
> I have checked route-target link from Contrail 3.2.4.0 and below is the
> output. Virtual networks names are anda_lenovoA and anda_lenovoB and
> logical router name is router1. I can see “routing_instance_back_refs” and
> “routing-instance” so the route targets are exported.
>
>
>
> {"route-target": {"display_name": "target:64512:803", "uuid":
> "6da5401e-52c6-457d-ab72-3cf3dac49dfa", "href":"https:// IP>:8143/proxy?proxyURL=http://:8082/route-target/
> 6da5401e-52c6-457d-ab72-3cf3dac49dfa", "routing_instance_back_refs":
> [{"to": ["default-domain", "admin", "anda_lenovoA", "anda_lenovoA"],
> "href":"https://:8143/proxy?proxyURL=http:// mgmt IP>:8082/routing-instance/0b09292b-e4b7-47e6-8329-ce461d89137d",
> "attr": {"import_export": null}, "uuid":
> "0b09292b-e4b7-47e6-8329-ce461d89137d"},
> {"to": ["default-domain", "admin", "anda_lenovoB", "anda_lenovoB"],
> "href":"https://:8143/proxy?proxyURL=http:// mgmt IP>:8082/routing-instance/8b756a10-52bc-4c14-a5f4-7a9261ea1003",
> "attr": {"import_export": null}, "uuid":
> "8b756a10-52bc-4c14-a5f4-7a9261ea1003"}],
> "perms2": {"owner": "5792015c404a4bd4a0ff775de5c38bf4", "owner_access":
> 7, "global_access": 0, "share": []}, "id_perms": {"enable": true, "uuid":
> {"uuid_mslong": 7900791620273325437, "uuid_lslong": 12354003745875729914},
> "created": "2017-07-12T14:02:42.656006", "description": null, "creator":
> null, "user_visible": true, "last_modified": "2017-07-12T14:02:42.656006",
> "permissions": {"owner": "cloud-admin", "owner_access": 7, "other_access":
> 7, "group": "cloud-admin-group", "group_access": 7}},
> "logical_router_back_refs": [{"to": ["default-domain", "admin", "router1"],
> "href":"https://:8143/proxy?proxyURL=http:// mgmt IP>:8082/logical-router/98c6dabf-b7c0-46f4-b106-4587c3ce242e",
> "attr": null, "uuid": "98c6dabf-b7c0-46f4-b106-4587c3ce242e"}],
> "fq_name": ["target:64512:803"], "name": "target:64512:803"}}
>
>
>
> Thanks,
>
> Anda
>
>
>
> *From:* Sachin Bansal [mailto:sban...@juniper.net]
> *Sent:* Wednesday, July 12, 2017 6:08 PM
> *To:* Anda Nicolae
> *Cc:* Vedamurthy Ananth Joshi; dev@lists.opencontrail.org
>
> *Subject:* Re: [opencontrail-dev] Contrail GUI Virtual Router IP address
>
>
>
> Anda,
>
>
>
> As Vedu explained earlier, the IP address of the logical router interface
> is completely inconsequential and is not used in any forwarding at all. You
> can rest assured that with .100 addresses, the connectivity is expected to
> work. Also, gateway of a network cannot be changed.
>
>
>
> The way it works is, we allocate a route target for the logical router and
> attach it to each of the VNs so that the VRFs for each of those VNs can
> import each other’s routes. Now
>
>
>
> From the output you sent, it seems the route target is only connected to
> the logical router, not the two virtual networks. Could you please make
> sure contrail-schema is running and active? If it is, please check its logs
> for any errors.
>
>
>
> Sachin
>
>
>
>
>
>
>
> On Jul 12, 2017, at 2:51 AM, Anda Nicolae wrote:
>
>
>
> I have errors in contrail-api.log such as: *Error while accessing
> route_target uuid 408155ef-22d0-46e8-b0c2-07f3fec44dae*
>
> The a
