Bug 1227351 - Repository 'Main Update Repository' metadata expired since 2024-07-03 03:46:10 CDT
Summary: Repository 'Main Update Repository' metadata expired since 2024-07-03 03:46:1...
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Maintenance (show other bugs)
Version: Leap 15.5
Hardware: 64bit Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Mr Maintenance
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-03 15:30 UTC by Nick Dordea
Modified: 2024-07-04 15:02 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Dordea 2024-07-03 15:30:08 UTC
Hello, 
Trying to install some maintenance I noticed the messages ..
Building repository 'Main Update Repository' cache ...........................................................................[done]
Loading repository data...
Warning: Repository 'Main Update Repository' metadata expired since 2024-07-03 03:46:10 CDT.

    Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise
    manually refresh the repository (zypper ref). If this does not solve the issue, it could be that
    you are using a broken mirror or the server has actually discontinued to support the repository 

I followed the above procedures but the issue was not solved . 

What's wrong with that repository ?
Thanks ,
ND

Please find below what I've done .....

A)     
  zypper lr -d -r 61
Alias          : repo-update
Name           : Main Update Repository
URI            : https://download.opensuse.org/update/leap/15.5/oss
Enabled        : Yes
GPG Check      : (r ) Yes
Priority       : 99 (default priority)
Autorefresh    : On
Keep Packages  : Off
Type           : rpm-md
GPG Key URI    : 
Path Prefix    : /
Parent Service : 
Keywords       : update
Repo Info Path : /etc/zypp/repos.d/repo-update.repo
MD Cache Path  : /var/cache/zypp/raw/repo-update

B)
 sudo zypper cc -r 61
Specified repositories have been cleaned up.

C)
 sudo zypper ref -f -r 61
Forcing raw metadata refresh
Retrieving repository 'Main Update Repository' metadata ..................................................................................................[done]
Forcing building of repository cache
Building repository 'Main Update Repository' cache .......................................................................................................[done]
Specified repositories have been refreshed.

D)
sudo ZYPP_MULTICURL=0 zypper up -l --details --no-allow-vendor-change
Loading repository data...
Warning: Repository 'Main Update Repository' metadata expired since 2024-07-03 03:46:10 CDT.

    Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise
    manually refresh the repository (zypper ref). If this does not solve the issue, it could be that
    you are using a broken mirror or the server has actually discontinued to support the repository.
   
 E)   
sudo ZYPP_MULTICURL=1 zypper up -l --details --no-allow-vendor-change
Loading repository data...
Warning: Repository 'Main Update Repository' metadata expired since 2024-07-03 03:46:10 CDT.

    Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise
    manually refresh the repository (zypper ref). If this does not solve the issue, it could be that
    you are using a broken mirror or the server has actually discontinued to support the repository.
  
F)  
 sudo zypper up -l --details --no-allow-vendor-change
Loading repository data...
Warning: Repository 'Main Update Repository' metadata expired since 2024-07-03 03:46:10 CDT.

    Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise
    manually refresh the repository (zypper ref). If this does not solve the issue, it could be that
    you are using a broken mirror or the server has actually discontinued to support the repository.
Comment 1 Marcus Meissner 2024-07-03 15:56:00 UTC
it does not get updates often enough.

I will release a dummy update to refresh it.
Comment 2 Nick Dordea 2024-07-04 15:02:46 UTC
The issue is solved ...

sudo ZYPP_MULTICURL=0 zypper up -l --details --no-allow-vendor-change
...
Retrieving repository 'Main Update Repository' metadata ...........................................................[done]
Building repository 'Main Update Repository' cache ...........................................................[done]
Loading repository data...
Reading installed packages...
.....
Thank you for the quick resolution .

ND