HC does not inform that DC changed configuration and reload/restart is required when `--cached-dc` is used.

This issue was created based on discussion at https://issues.jboss.org/browse/EAP7-496.

HC starts with `--cached-dc` and DC is down. If DC contains changed attribute and is started HC receives configuration updates that was changed in comparison to existing
"domain.cached-remote.xml". The change seems to be propagated to HC but it's not "activated" (it's not part of model at HC) neither information that reload/restart of HC is needed is provided.

This could be checked with following steps

1. start DC and HC with --cached-dc parameter

    cd $JBOSS_HOME
    ./bin/domain.sh --host-config=host-master.xml
    ./bin/domain.sh  --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=9899 -Djboss.host.name=slave --cached-dc
    

2. stop HC
3. configure logging at DC

    cd $JBOSS_HOME
    ./bin/jboss-cli.sh -c
    /profile=full/subsystem=logging/logger=my.test:add(category=my.test, level=FINE)
    

4. stop DC
5. start HC

    ./bin/domain.sh  --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=9899 -Djboss.host.name=slave --cached-dc
    

6. check that logging is not configured

    ./bin/jboss-cli.sh -c --controller=remoting://localhost:9899
    /host=slave/server=server-one/subsystem=logging:read-children-resources(child-type=logger)
    

7. start DC and wait a while when HC is connected to it

    INFO  [org.jboss.as.host.controller] (Host Controller Service Threads - 33) WFLYHC0150: Trying to reconnect to master host controller.
    INFO  [org.jboss.as.host.controller] (Host Controller Service Threads - 33) WFLYHC0148: Connected to master host controller at remote://127.0.0.1:9999
    

8. check what DC says about server-one

    ./bin/jboss-cli.sh -c
    /host=slave/server=server-one/subsystem=logging:read-children-resources(child-type=logger)
    

The result is that the new logger my.test is not part of the configuration of server-one. There is no warning about such fact in server log what I can see.
True is that here behaves differently against my testing before that after printing resources of the subsystem logging node there is information reload-required.
From your point of view - is this correct behavior? If so I think some warning message in server log at least that content of domain.cached-remote.xml is not in sync with servers' model should be promoted.