Fabric config push fails because security group name being too long
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
Won't Fix
|
High
|
Atul Moghe | |||
Trunk |
New
|
High
|
Ankur Tandon |
Bug Description
Fabric config push fails because the security group name is too long. The security group gets created but does not get applied because the corresponding filter name is very long. This way not all the security groups created will get applied.
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failure loading the configuraton: ConfigLoadError
11/02/2018 17:41:38.879 [ansible] pid=30200 [WARNING]: TASK [commit_
11/02/2018 17:41:38.950 [ansible] pid=30200 [WARNING]: included: /opt/contrail/
11/02/2018 17:41:38.968 [ansible] pid=30200 [WARNING]: TASK [commit_
11/02/2018 17:41:39.028 [ansible] pid=30200 [WARNING]: ok: [localhost]
11/02/2018 17:41:39.044 [ansible] pid=30200 [WARNING]: TASK [commit_
11/02/2018 17:41:39.081 [ansible] pid=30200 [WARNING]: skipping: [localhost]
11/02/2018 17:41:39.097 [ansible] pid=30200 [WARNING]: TASK [commit_
11/02/2018 17:41:40.457 FabricAnsible [INFO]: SANDESH: CONNECT TO COLLECTOR: True
11/02/2018 17:41:40.522 FabricAnsible [INFO]: SANDESH: Logging: LEVEL: [SYS_INFO] -> [SYS_NOTICE]
11/02/2018 17:41:40.524 FabricAnsible [ERROR]: SANDESH: [DROP: WrongClientSMState] SandeshModuleCl
11/02/2018 17:41:45.021 [ansible] pid=30200 [WARNING]: ok: [localhost]
11/02/2018 17:41:45.038 [ansible] pid=30200 [WARNING]: TASK [commit_
11/02/2018 17:41:45.074 [ansible] pid=30200 [WARNING]: skipping: [localhost]
11/02/2018 17:41:45.094 [ansible] pid=30200 [WARNING]: PLAY RECAP *******
11/02/2018 17:41:45.094 [ansible] pid=30200 [WARNING]: localhost : ok=127 changed=12 unreachable=0 failed=1
11/02/2018 17:41:45.095 [ansible] pid=30200 [WARNING]: localhost : ok=127 changed=12 unreachable=0 failed=1
sg-filter- test_tcp_ sec_group_ ctest-random- 05297852- 11113553- ba79-4f07- 87a2-ce3958d182 a2 is an example filter name they have generated. out of which they have appended sg-filter- -ba79-4f07- 87a2-ce3958d182 a2(38 chars long) string. which would leave us with 26 chars. So any security group created with a name more 26 chars long will not get applied.