Can't receive any new notifications from confd after do in-service upgrade

[buddha87]

Thanks for the detailed example.

1.For the stream subscribed, there is no specific stream, just subscribe to all streams.
2.In confd,conf, just enable the notification

  <notification>
    <enabled>true</enabled>
    <!--
        Enable this to make the agent handle RPCs while sending
        notifications.
    -->
    <interleave>
      <enabled>false</enabled>
    </interleave>
  </notification>

There is one important point I forgot to mentioned. After the in-service upgrade, I have to close all existed sessions otherwise the service will keep getting the “capabilities changed error” from confd.
See this topic I posted before:

Why I keep getting "capabilities-changed" error from confd?

In my design, there are some new fxs files and I do in service upgrade. After the upgrade completed (succeeded), I can see the expected schema shown using confd_cli. When I try to lock the confd candidate datastore, I keep getting the error response: <rpc-error> <error-type>application <error-tag>resource-denied <error-severity>error <error-app-tag>capabilities-changed </rpc-error> There is NO changes in confd.conf about before and after upgrade. The only changes in confd.conf is addin…

So I do is close all ssh sessions to the confd and reopen, then re subscribe. But even like this, after subscribe again, the application should be able to receive the notification, correct ?