Release date: June xx7, 2017
We are proud to announce the release of Fedora 4.7.3.
Table of Contents | ||
---|---|---|
|
Warning |
---|
If you are running a 4.7.1 or 4.7.2 instance of Fedora that had been upgraded from a previous version (4.7.0 or earlier), and you do not believe it has ever been shut down since upgrading to 4.7.1 or 4.7.2, you MUST make a backup via fcr:backup immediately. To recover from this bug, take a backup (which will be corrupted in a particular way), fix the backup, and restore into an instance of 4.7.3. All users should take a backup of their Fedora instance before upgrading to 4.7.3 just to be safe. |
Resources
Team
Release Manager
- Nick Ruest - York University
- Andrew Woods - DuraSpace
Developers
- Andrew Woods - DuraSpace
- Aaron Birkland - Johns Hopkins University
Issue Reporters
Summary
The Fedora 4.7.3 release is a backwards compatible refinement of the previous release, which fixes a namespace-corrupting bug that has the effect of Fedora being unable to successfully start after having been shut down.
Notewarning |
---|
If you are running a 4.7.1 or 4.7.2 instance of Fedora that had been upgraded from a previous version (4.7.0 or earlier), and you do not believe it has ever been shut down eversince upgrading to 4.7.1 or 4.7.2, you mustMUST make a backup via fcr:backup immediately. To recover from this bug, take a backup (which will be corrupted in a particular way), fix the backup, and restore into an instance of 4.7.3. All users should take a backup of their Fedora instance before upgrading to 4.7.3 just to be safe. If your repository is too large to perform a backup of both objects and binaries, a backup utility is available for generating a "object-only" backup. |
Detailed Bug Remediation Notes
...
Take a backup
Try simply upgrading 4.7.3 over the existing repository. If it starts up successfully, you are not affected by the issue, and are done!
If Fedora 4.7.3 fails to start, then you need to fix the backup manually, and restore into an empty repository
Detailed instructions
Expand | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
The dump contains a json object whose primary type is “mode:namespaces”. Nested within it is a “children” array that enumerates the namespaces known to modeshape. It appears that Modeshape chooses a single random prefix on all internal identifiers. Acknowledging that prefix, the modeshape namespaces enumeration follows a simple and obvious pattern. When Fedora encounters a novel rdf namespace and prefix, it adds it to the map. In many cases, the prefix is auto-generated, e.g. “ns001”. So if Fedora encountered a SKOS term, at any point, it may contain a namespace entry like:
In Fedora 4.7.1 and 4.7.2, a new set of hard-coded namespaces were published in the internal .cnd file used by modeshape. When started, any pre-existing namespaces that match the hard-coded namespaces, yet differ by prefix, are overwritten. So the namespaces table may now contain an entry:
This overwriting of the namespaces table is problematic. Objects that existed before the repository had been upgraded to 4.7.1 or 4.7.2 will still contain their _old_ namespace references, such as:
This inconsistency is at the root of the problem. 3. For each dangling namespace, add a new entry to the mode:namespaces node, for example:
4. After the namespaces node has been fixed, gzip the file so that it retains its original name 5. Restore the backup via fcr:restore |
Alternate instructions
Expand | ||
---|---|---|
In the case that you have upgraded to either 4.7.1 or 4.7.2 and have stopped your server and are not able to restart your server with an error in your logs like the following:
..this fedora-tech mailing list thread provides guidance for remediation. |
Changes
Complete Listing of Resolved Tickets
...