...
(SO does not update ipv4-oam-address in AAI)Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-3432 - Konrad Bańka , could you please add more details here?
- Sure, so briefly (ticket description has more in-depth status) we have custom automated test running simple VNF (1 vf-module, 1 vserver) LCM using Macro flow and some runtime verification of VM behavior. This VNF is tested on a daily basis on Frankfurt OOM and till today works correctly. It, however, doesn't work on Guilin OOM-deployed ONAP. In that case, our instantiation succeeds, but during it, VNF's IP address is no longer visible in AAI after instantiation. VNF's CSAR didn't change between those two branches and in both cases Heat Template contains relevant "output" section to provide relevant VNF's IP. As far as I remember BPMN logs in Frankfurt scenario logged two AAI requests about generic-vnf - POST (or PUT?) and PATCH, however in Guilin case, only first of these two is present. If you need any further description please take a look into ticket or ask there so we can provide any input that can be valuable for reproducing/fixing this. We will attach BPMN/Openstack Adapter logs today/tomorrow as said during the call. I think this issue should impact every SO-managed VNF that utilizes IP retrieval after vf-module instantiation, so it should be fixed in Guilin Maintenance release
(Socket Timeout (Read Timeout) issue in DoCreateResourcesV3 for E2E flow in 1.7.10)Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-3468 - Xin Miao brought up this issue off-line. Seshu Kumar Mudiganti , could you please take a look at this and advise?
H release:
Project Status in Honolulu Release
...