If no LSP Identifiers TLV is present in PCRpt message updateLsp in DS throws exception

The 'LSP Identifiers TLV' must be included in the LSP object in PCRpt messages for RSVP-signaled LSPs (draft-ietf-pce-stateful-pce-07). However, in case the path is setup using Segment Routing technique (PST=1) the 'LSP Identifiers TLV' might be not present. In this case LspId is not set in the PathBuilder and the updateLsp DS operation throws the following exception:

2015-05-08 11:11:03,783 | WARN | oupCloseable-3-1 | DefaultChannelPipeline | 104 - io.netty.common - 4.0.26.Final | An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
java.lang.IllegalArgumentException: All keys must be specified for class org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.topology.pcep.rev131024.pcep.client.attributes.path.computation.client.reported.lsp.PathKey. Missing key is getLspId. Supplied key is PathKey []

The reported LSP is not written in the DS.