As mentioned in https://groups.io/g/onap-bbs/message/566

If PRH receives a PNF re-registration event and the service-orchestration status of the BBS service-instance is “created” (not “active”), then PRH ignores the message (not passing re-registration criteria). No PNF_UPDATE event is sent which is correct behavior.

However, it stills creates a new logical-link and relates it to the PNF which is not correct. PNF ends up with multiple logical-links bringing further errors down the components processing pipeline.

Of course this flow is not the expected one, as the PNF re-registration should come after a CPE authentication but still we need to make sure nothing changes in A&AI if event is discarded.