On 06/19/11 18:48, Mike Gerdts wrote:
During zone attach, I ran into:-----------%<----------- Updating non-global zone: Linking to image /. pkg attach-linked: A 'sync-linked' operation failed for child 'zone:p2vtest-11764' with an unexpected return value of 1 and the following error message: Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: Invalid content: manifest hash failure: fmri: pkg://userland/library/[email protected],5.11-0.169:20110616T214549Z expected: b0774f5937d1ad1edbe4428411f057ae9b0f2754 computed: 5f31b413cb45688fecd3cb33098e3ac6fb9fb8a9. (happened 4 times) -----------%<----------- The odd thing is that it is only sync-linked that complains about this. Neither 'pkg verify libxml2' nor 'pkg update libxml2' complains. Is there some other way that I could know that I will get bit during sync-linked? I believe the problem was introduced by the userland consolidation being updated. When I switched the userland publisher in the image over to a mirror that I created, the problem went away. Perhaps this indicates that a more specific error message should have been displayed.
If manifests changed for an existing package (which should generally not happen ignoring the pkgsign case), I'm uncertain how gracefully the zone proxy will handle that (whether it will keep returning the old cached version).
This error is only raised during transport operations, which is why you probably didn't see it during verify libxml2 or update libxml2 (since they likely used an already cached copy).
But during a sync-linked, that would typically involve transport operations in a zone.
Transport (at the point of manifest retrieval) will verify that the digest of the manifest specified in the catalog matches that of the manifest retrieved.
So either your catalog or your manifest was in the "wrong state". -Shawn _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
