This article explains what to do when upgrade of an EX device fails from Routing Director with the Software Validation Failed error messages.

On trying to upgrade an EX device from Routing Director, the following error is seen:

"Software Validation failed"

On performing the upgrade from the device CLI, the following error is seen:

request system software validate /var/tmp/jinstall-ex-4300-21.4Rxxxx-signed.tgz

...

Event processing process: <source-daemon>eventd</source-daemon>

Event processing process: <message>Cannot open configuration file: &amp;#230;&amp;#xe00f;{&amp;#247;-k*n{y&amp;#166;&amp;#237;&amp;#166;&amp;#201;)&amp;#212;&amp;#xe014;&amp;#210;h&amp;#248;&amp;#242;?V&amp;#217;&amp;#246;O&amp;#128;)&amp;#134;&amp;#xe002;I&amp;#135;D&amp;#235;&amp;#214;&amp;#251;*&amp;#156;\&amp;#157;8&amp;#143;~}&amp;#239;&amp;#148;e&amp;#242;j &amp;#230;g

..

mgd: error: configuration check-out failed

Validation failed

ERROR: Current configuration not compatible with /var/tmp/jinstall-ex-4300-21.4Rxxxx-signed.tgz

WARNING: Current configuration not compatible with /var/tmp/jinstall-ex-4300-21.4Rxxxx-signed.tgz

Running the command "deactivate groups jcloud-script" will allow the upgrade to go through.

You can check the following in such cases:

• Device is compatible with RD. Please refer to this link to confirm the same.
• If the device is compatible, then check if you are able to upgrade the device from the CLI with the no-validate option.

In case the error at the device level is the same as the KB: KB82770 [juniper.net].

This is not an RD issue but a JUNOS side issue.

You can run the following work-arounds to resolve the issue:

• Manually copy the etcroot file as that is the root cause of the issue at the EX side. PR for the same is with the EX Team.

cp -p /var/etcroot/*pwd.db /var/v/c/var/etcroot" file.

• Removing “group jcloud-script" configuration hierarchy manually before upgrade will also work. This config needs to be configured once the upgrade is done.