cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

Who Me Too'd this topic

Prime Infrastructure 3.1 upgrade: MR 3.1.7 refuses to install on a vanilla CPI 3.1.0 server, Device Pack 16 .ubf file not signed

jakubjakubiak
Level 1
Level 1

Hi,

I was unable to install Maintenance Release 3.1.7 on a fresh CPI 3.1.0 server - the error message was that I need to install an earlier MR first to be able to install 3.1.7, however the earlier MR files are deleted from the downloads page. I've had some older ones, but it turned out that after failed 3.1.7 installation attempt the CPI server refused to install other MRs as well - the error message was something along the lines 'please install MR 3.1.6 first to be able to install this patch' (while trying to push 3.1.5 or 3.1.6).

Also the Device Pack 16 ubf has problems - the file isn't signed. The DP16 download is a zip file, inside it the ubf file and a small txt file with signature (.sig), CPI server refuses to install that as well, the following error is displayed:

The update file Device-Pack-16-PI3.1-133.ubf appears to be unsigned, which may come from an untrusted source. Unsigned updates are not allowed because of security requirements.

 

ncs stop/start didn't help, neither rebooting the VM. 

 

The fix to get 3.1.7 to work: I first pushed an older DP file (DP11), this unlocked the CPI server to be able to accept MR 3.1.6, and only after this succeeded it was possible to install MR 3.1.7. I've had no problems pushing MR3.1.7 onto CPIs with various MRs already in place, but doing it on vanilla 3.1 is a bit of a bummer... anyone else tested this yet, similar or different experiences?

 

Cheers,

 

 

Who Me Too'd this topic