If graceful Routing Engine switchover (GRES), nonstop active routing (NSR), or nonstop bridging (NSB) is enabled when a Junos OS software installation is initiated, the software installation is abandoned.

This article indicates the error that is thrown in this scenario and the solution for ensuring that the software installation is completed.

The following errors may be observed if a Junos OS software installation is initiated without disabling GRES, NSR, or NSB.

Hardware Database regeneration succeeded
Validating against /config/juniper.conf.gz
Chassis control process: <xnm:error xmlns="<a href="http://xml.juniper.net/xnm/1.1/xnm">http://xml.juniper.net/xnm/1.1/xnm" xmlns:xnm="http://xml.juniper.net/xnm/1.1/xnm">
Chassis control process: <source-daemon>chassisd
Chassis control process: <edit-path>[edit chassis redundancy]
Chassis control process: <statement>graceful-switchover
Chassis control process: <message>Graceful switchover not enabled! 
Chassis control process: 
mgd: error: configuration check-out failed
Validation failed
ERROR: Current configuration not compatible with /var/tmp/jinstall-xxx-signed.tgz
​

This issue occurs because GRES, NSR, or NSB is enabled. These configurations are required only if a unified in-service software upgrade (ISSU) is performed as described in Example: Performing a Unified ISSU .

To complete the software installation properly, delete or deactivate the GRES configuration from the [edit chassis] hierarchy, and delete or deactivate the NSR/NSB configuration.

As described in Preparing the Device for Installation , disabling GRES, NSR, or NSB by using the specified steps is a prerequisite to ensure that the software installs properly.