Description

 This article describes the annotation issue, which is caused by inheriting the configuration, before upgrading.

Symptoms

When a database cannot be patched with a new configuration, it will notice a error reminder; but not be found with commit check . The following excerpt is an example of the error message, as it appears in the syslog output: 

[edit]
root@re0-router# commit check
re0:
commit complete

root@re0-router# commit full
[edit firewall family inet filter LOOPBACK-OUTBOUND term allow-ipv6 then]
'accept'
    outgoing comment does not match patch:

Solution

Possible causes :

The annotation had a change after the 10.1 release to notice the valid annotation command, after the final level of any hierarchy level.

Confirm causes :

The following sample outputs can be examined to determine the cause of this message: 
[edit]
root@re0-router# show | compare
[edit firewall family inet filter LOOPBACK-OUTBOUND term allow-ipv6 then]
+ /* Don't process the packet here; it's IPv6, not IPv4.
+ * Accept it and have it be processed by the IPv6 ACL. */
accept;
The annotation is configured, if it is present under the last hierarchy level.

Delete the annotation configuration from the present annotate, which is inherited, if the No valid completions is indicated in the query display: 

[edit firewall family inet filter LOOPBACK-OUTBOUND term allow-ipv6 then]
root@router-re0# annotate ?
No valid completions