Bluetooth: Mesh: Fix incorrect write conn_count

[LingaoM]

When Device use pb-gatt bearer provisioning, and first
provisioning failed due to some reasons(invalid oob etc..).

Which cause proxy:gatt_disconnectd incorrected write conn_count

Cause this var euqals -1.

Signed-off-by: Lingao Meng [email protected]

[trond-snekvik]

How can I trigger this issue? By connecting to a mesh node without using mesh proxy?

[LingaoM]

How can I trigger this issue? By connecting to a mesh node without using mesh proxy?

While i’m use mesh_shell:

• mesh init
• mesh pb-gatt on
• use nRF Mesh App Provision use Invalid OOB.
• provision failed
• mesh pb-gatt on
• use nRF Mesh App Provision use Valid OOB.

This problem will be occur.

[cfriedt]

Is this also a bug that exists in LTS @jhedberg ? If so, we should add the backport label and create an issue.

[jhedberg]

Is this also a bug that exists in LTS @jhedberg ? If so, we should add the backport label and create an issue.

@cfriedt agreed.

@trond-snekvik @LingaoM if this issue also exists in LTS, could you take the appropriate action as outlined by @cfriedt ?

[LingaoM]

Is this also a bug that exists in LTS @jhedberg ? If so, we should add the backport label and create an issue.

@cfriedt agreed.

@trond-snekvik @LingaoM if this issue also exists in LTS, could you take the appropriate action as outlined by @cfriedt ?

While i'm deep in to 2.7 branch https://github.com/zephyrproject-rtos/zephyr/blob/v2.7-branch/subsys/bluetooth/mesh/gatt_services.c#L912

There is no need to back port for this, since this issue has been involved by #36871