SOLVED manage.py: [freenasOS.Manifest:364] Signature check failed, exit value 1

[joeschmuck]

I will need to confirm this however I now get these error messages
"manage.py: [freenasOS.Manifest:364] Signature check failed, exit value 1"
since I did a Verify Install. (System, Update, Verify Install) The verification came back fine. I also conducted a scrub on the boot device which came back fine as well. For some reason the hard drive was accessing a lot after the scrub was reported as complete. Maybe it's that, who knows.

Everything appears to be working fine except the messages keep coming.

I plan to build up from scratch again to see if I can confirm this.

If someone knows what this message means, I'd appreciate the input.

 

[joeschmuck]

So this problem has nothing to do with the operations I mentioned above, it just seems to happen. This message showed up on a clean install of the current BETA iso image and even after the update to the current Beta Train version. I'm curious if it has anything to do with my Test Rig hardware. A bug report has been submitted.

 

[kjp4756]

I got the same message yesterday after I did a 9.3-beta update via system update gui and did a verify install. In my case I'm using vmware fusion.

 

[mjws00]

My guess was an error signing an update, just a glitch on rollout or change of procedure in a build? I ignored for now and expect it will magically dissapear and never return.

 

[joeschmuck]

I was just able to recreate it on my VM version when I went to start an update from the BETA Train. So it looks like this is reproducible on more than one platform.

 

[JoelN]

I am also getting the following message on a clean 9.3 install on the BETA train:
"freenas manage.py: [freenasOS.Manifest:354] Signature check failed, exit value 1"

Edit: I just noticed this error occurs after an apparently failed update check. I believe I applied the following update right after my initial 9.3 install. Now when checking for an update it finds the same files and apparently skips the download and update and generates the above error message.

Upgrade: base-os-9.3-BETA-9764f95-22613ac-aee90d2 -> base-os-9.3-BETA-9a10bd8-22613ac-6fe7954
Upgrade: FreeNASUI-9.3-BETA-9764f95-22613ac-f72da61 -> FreeNASUI-9.3-BETA-9a10bd8-22613ac-6fe7954
Upgrade: freenas-pkg-tools-9.3-BETA-9764f95 -> freenas-pkg-tools-9.3-BETA-9a10bd8

 

[indivision]

I'm getting this as well. Sounds like a universal issue...

 

[joeschmuck]

I would appreciate it if other folks having the issue would add some additional comments to the bug report I submitted. It helps show that the problem isn't just me.

 

[jkh]

This problem has been fixed. What happened is that we're turning on "strict signature validation" in preparation for -RELEASE and there was a bug in the first iteration. As I said, that's now fixed. The warning is harmless and will go away after the next update.

 

[joeschmuck]

Jordan,
When you perform updates for the BETA train, do you also release an iso version as well? I ask because I haven't seen it yet but then again I might not be looking in the right location.

Thanks,
Mark

 

[jkh]

When I roll an update for that train, I also roll it as a full release, yes. Due to the historical way I built nightly releases, they all showed up as "nightlies" however, which of course is no longer reasonable since there are two trains: 9.3-Nightlies and 9.3-BETA. I just changed this today and you will now find: http://download.freenas.org/nightlies/9.3-BETA and http://download.freenas.org/nightlies/9.3-Nightlies directories to conform to the new naming (and update) policy. Under those directories you will find the date of the build, just like before.

Anyone having serious problems with the Upgrader (though that's not anticipated) can also still do a Manual Update using the GUI update image or the ISO image (or, of course, do so from a pre-9.3 build since that's the only update option in that case). In other words, you can "hop on the train" using any build of 9.3 and, of course, switch trains from the UI if you wish. HTH!

 

[joeschmuck]

Thanks Jordan, appreciate it.