Failed to get available update data

composer show drupal/sticky

@cilfen,

I get...

$ composer show drupal/sticky
name     : drupal/sticky
descrip. : Sticky is a module that gives you the ability to make any element on your website to always stay visible.
keywords :
versions : * 2.1.1
type     : drupal-module
license  : GNU General Public License v2.0 or later (GPL-2.0-or-later) (OSI approved) https://spdx.org/licenses/GPL-2.0-or-later.html#licenseText
homepage : https://www.drupal.org/project/sticky
source   : [git] https://git.drupalcode.org/project/sticky.git 2.1.1
dist     : [zip] https://ftp.drupal.org/files/projects/sticky-2.1.1.zip 2.1.1
path     : C:\Users\nick\Sites\bit-by-bit.org\public_html\modules\contrib\sticky
names    : drupal/sticky

support
source : https://git.drupalcode.org/project/sticky

requires
drupal/core ^9 || ^10

That seems ok. What are the contents of the module's info.yml file in that site's codebase?

See also #2741853: Failed to get available update data. Drupal 8 → , #2741853: Failed to get available update data. Drupal 8 → . Absent more information I can't distinguish this from those issues.

Also #3117775: Updater falsely generates "Failed to get available update data" →

Am unable to replicate the issue attached screenshot for reference. It may be some random issue on accessing the project info on Curl.

It's good to close from my side.

@arunkumark, sure go ahead and close, Stiky seems OK now anyway after the recent update but VBO still dodgy but I can live with that ;-)

I have been struggling with the same problem since a few days . When running /admin/reports/updates I get the message “Failed to get available update data” with Drupal Core and with all modules. Image on postimg
Here there is no connection with module Sticky as it is not used. When I restart the update after some time, the error messages disappear at Drupal Core and at a few modules. After another new update, in alphabetical order, again some modules are added to the list labeled “Up to date”.

The following changes were made: update Drupal 10.3.1 to 10.3.2 and updates to modules admin_toolbar, asset_injector, ckeditor5_plugin_pack, crop, colorbox, focal_point, metatag, pathauto and token (drupal11 compatible updates).

In /reports/dblog, I find the (known issue) error "Field layout_builder__layout is unknown. in DrupalCoreEntityContentEntityBase" and a whole bunch of warnings “Trying to run cron again while it's already running.”

Thanks for your opinion on this

I can confirm I am experiencing this issue. Updated from 10.3.1 to 10.3.2.

🐛 No release history was found for the requested project (Drupal). Fixed