1- Site version was 8.7.9
2- Listed updatable modules at /admin/reports/updates/update
3- Updated 3 modules using the UI
4- Ran database update => modules showed as "Up to date" at /admin/reports/updates
5- Updated Drupal core to 8.8.3
6- Ran database update => Drupal core showed as "Up to date" at /admin/reports/updates
But all Modules and Themes show "No available releases found" as apposed to "Up to date"

Apache, PHP 7.1.14, MySQL 5.6.41

Issue fork drupal-3120168

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

AlenaSystems created an issue. See original summary.

Anonymous’s picture

Apparently if you run "Check for updates manually", next time the statuses are displayed properly.

dww’s picture

Category: Bug report » Support request
Status: Active » Closed (works as designed)

8.8.3 probably should have shipped with a post_update function to reset the Update manager's cache of fetched data and ensure that sites automatically try to re-fetch available updates. The URL changed where Update manager is fetching info. See #3074993: Use "current" in update URLs instead of CORE_COMPATIBILITY to retrieve all future updates. But the post_update didn't happen, and it's going to be weeks before another 8.8.x release that can help any of this, so there's not much more to do here. If you have trouble, click 'Check manually'. /shrug

Sorry,
-Derek

tedbow’s picture

Very unlikely since @AlenaSystems didn't mention it but it could also happen if you were running an alternative update server and the format was update to match changes in #3074993: Use "current" in update URLs instead of CORE_COMPATIBILITY to retrieve all future updates

jdleonard’s picture

Version: 8.8.3 » 8.8.x-dev
Status: Closed (works as designed) » Active

I ran into this as well and still having this problem on 8.9.1. I am not using an alternative update server. "Check for updates manually" does not help. Cache rebuild does not help. I haven't been able to figure out how to get the module working again.

Releases ARE shown for:

  • pantheon_advanced_page_cache
  • google_tag
  • datalayer
  • config_split
  • config_readonly
  • config_ignore_readonly

No releases are shown for core or for these modules:

  • admin_toolbar
  • adminimal_admin_toolbar
  • autocomplete_deluxe
  • classy_paragraphs
  • config_filter
  • config_ignore
  • config_update
  • csv_serialization
  • ctools
  • devel
  • dropzonejs
  • empty_fields
  • entity
  • entity_browser
  • entity_browser_enhanced
  • entity_reference_revisions
  • field_group
  • field_permissions
  • flag
  • honeypot
  • inline_entity_form
  • linkit
  • markup
  • metatag
  • paragraphs
  • pathauto
  • redirect
  • redis
  • scheduler
  • shariff
  • simple_sitemap
  • smart_trim
  • social_media_links
  • svg_image
  • token
  • viewsreference
  • webform
  • adminimal_theme

I don't see any pattern to which modules have releases shown.

seismicmike’s picture

+1 for this issue. I'm having the same problem, and finding this was a relief because I thought I was going insane.

If it wasn't for the fact that some of the projects are able to successfully fetch update information, I'd suspect this to be a network issue... like the web server can't reach d.o or something. But Since some projects are fetching updates, I'm less sure of that.

junaidpv’s picture

We got similar experience as @jdleonard.

It got worked after I deleted some entries from "key_value" table with this query:

DELETE
FROM `key_value`
WHERE `collection` = 'update_fetch_task'
dww’s picture

Category: Support request » Bug report
Status: Active » Closed (duplicate)
Issue tags: +Bug Smash Initiative
Parent issue: » #2920285: Update module can get 'stuck' with 'no releases available'

Given #7, this is almost certainly duplicate with #2920285: Update module can get 'stuck' with 'no releases available'. Let's continue over there.

Thanks,
-Derek

marcvangend’s picture

I had the same symptoms, but for me the workaround in #7 did not help. In my case it turned out to be a config problem. I noticed that on the settings page (/admin/reports/updates/settings) all form fields were empty. After selecting some settings (I chose "Weekly" and "Only security updates", but I guess it doesn't matter what you pick) and saving the form, things started to work as expected.

The cause of my broken config may be syncing of databases between environments - I'm not sure. I don't even think this qualifies as a bug, but I wanted to leave my solution here as a tip for anyone with similar problems.

vm’s picture

ran into this today on a locally hosted site not installed with composer and can confirm that the advice in #7 corrected the issue.

mizage@gmail.com’s picture

#7 worked like a charm!

seppe beelprez’s picture

#7 did it for me except for checking updates for Drupal Core. As in #9, there weren't any settings enabled on the /admin/reports/updates/settings page. So selecting a few options there made the available updates checking again for Drupal Core updates.

joshuautley’s picture

#7 - Thank you!!!

PeterE’s picture

#7 worked for me - thanks!

William Santoso made their first commit to this issue’s fork.

dydave’s picture

Confirming #7 worked in my case as well.

Executed the following code in command line with drush php:

$res = \Drupal::keyValue('update_fetch_task');
$res->deleteAll();

Thanks again for the help!

amir jamshidi’s picture

#7 worked :) thanks

boinkster’s picture

#9 worked for me on several sites. - Thanks!

winkflo’s picture

#7 worked for me (after hours of searching) - THANKS!!!!

adevms’s picture

#7 worked for me as well. Thanks

argiepiano’s picture

#9 worked well in a couple Drupal 9 sites

aswathyajish’s picture

#7 worked for me. Thanks a lot.

jamesfk’s picture

Ditto - #7 worked for me on a few sites - this issue keeps reoccurring for me. Many thanks :)

jimconte’s picture

#9 worked in my situation

liquidcms’s picture

With 9.2.11

Yes, hours searching for fix for this.. for me, it was working on server but not on my local (with same db). #7 on my local fixed the issue.

On server it was also busted but different solution. In Settings, neither daily or weekly was selected. Once one of these was selected - it worked (didnt work on my local).

Certainly bugs in the update module.

anybody’s picture

On Drupal 9 (after Drupal 8 to 9 Upgrade) #7 only fixed it for some hours for us, I now tried re-installing the "Update Manager" module, let's see, if it fixes things permanently.

bigboy’s picture

Drupal 9.3.15, #7 worked for me as well. Thank you!

suryaden’s picture

Thank you #7, worked for me Drupal 9.3.10

junaidpv’s picture

Again, #7 helped me today!

stevenx’s picture

#9 worked for me, thanks.
/admin/reports/updates/settings

ivnish’s picture

#7 works for me!

darrell_ulm’s picture

#7 still working for me