update_narf

Squish those pesky "No available releases found" issues.

The update manager sometimes ends up with "No available release found" (NARF!) for all, or just a couple of the modules in a site. This is an irritation and potential security issue as an admin will not be able to see if there is a new security release available for a module, and it does not fix itself.

There are a number of attempts to fix this issue but none seem to be a permanent fix that works for everyone. Some of the details are available in issue #2920285: Update module can get 'stuck' with 'no releases available'.

This module just steps in and deletes the extraneous update_fetch_task semaphore just prior to the update module checking for and creating them again.

It will be deprecated for newer versions of Drupal Core once the bug is squashed.

Post-Installation

On installation, the "No available releases found" tasks will have been removed, allowing update information to be downloaded.

They are also removed just prior to Update Manager running it's check via update_cron(), and when an admin clicks "Check manually" from the Available updates page.

In normal operation, they are removed after being present in the keyvalue store after 2 hours (configurable, done via cron). This allows a stuck fetch task to update its information prior to the next main updates fetch.

The 2 hour expiry can be configured by navigating to the Available updates page and clicking the NARF! tab.

Advanced data expunging & rebuild

In the event the normal function of this module still results in NARFs, visit the Advanced Data Expunging form linked from the NARF Settings where an admin can review the behind the scenes data used by the Update module, purge it all, or rebuild it all including checking for updates using an alternate batch method.