#9239 Mirrormanager is giving bad repos for fedora 33
Closed: Fixed 3 years ago by adrian. Opened 3 years ago by ausil.

Describe what you would like us to do:


fedora-33 in mirrormanager is giving rawhide repos, https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-33&arch=x86_64 gives a list pointing to rawhide, the gpg keys pointing at the wrong ones prevent someone getting bad content installed but it will prevent any type of updating. mirrormanager needs to be configured correctly post branching

When do you need this to be done by? (YYYY/MM/DD)


2020/08/15


The repository redirects from 33 to rawhide were still active. I removed them from 33 to rawhide and added them from 34 to rawhide.

Please re-open if it still does not work in a few hours.

Metadata Update from @adrian:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

@adrian Is this something that I can do? I can add it to the branching doc so that this wont happen again.

@mohanboddu Great idea. For F33 I did the following:

mirrormanager2=> delete from repository_redirect where from_repo like '%33%';

and

insert into repository_redirect (from_repo , to_repo) values ('fedora-34','rawhide');               
insert into repository_redirect (from_repo , to_repo) values ('fedora-source-34','rawhide-source');
insert into repository_redirect (from_repo , to_repo) values ('updates-released-f34','rawhide');
insert into repository_redirect (from_repo , to_repo) values ('updates-released-debug-f34','rawhide-debug');
insert into repository_redirect (from_repo , to_repo) values ('updates-released-source-f34','rawhide-source');
insert into repository_redirect (from_repo , to_repo) values ('updates-testing-f34','rawhide');
insert into repository_redirect (from_repo , to_repo) values ('updates-testing-debug-f34','rawhide-debug');
insert into repository_redirect (from_repo , to_repo) values ('updates-testing-source-f34','rawhide-source');
insert into repository_redirect (from_repo , to_repo) values ('fedora-modular-34','rawhide-modular');
insert into repository_redirect (from_repo , to_repo) values ('fedora-modular-debug-34','rawhide-modular-debug');
insert into repository_redirect (from_repo , to_repo) values ('fedora-modular-source-34','rawhide-modular-source');
insert into repository_redirect (from_repo , to_repo) values ('updates-released-modular-f34','rawhide-modular');
insert into repository_redirect (from_repo , to_repo) values ('updates-testing-modular-f34','rawhide-modular');
insert into repository_redirect (from_repo , to_repo) values ('updates-released-modular-debug-f34','rawhide-modular-debug');
insert into repository_redirect (from_repo , to_repo) values ('updates-testing-modular-debug-f34','rawhide-modular-debug');
insert into repository_redirect (from_repo , to_repo) values ('updates-testing-modular-source-f34','rawhide-modular-source');
insert into repository_redirect (from_repo , to_repo) values ('updates-released-modular-source-f34','rawhide-modular-source');
insert into repository_redirect (from_repo , to_repo) values ('fedora-debug-34','rawhide-debug');

Right now it is all manual, but should be simple to put into a script.

Thanks @adrian I will update the doc with your comment above. This is very helpful, thanks.

Log in to comment on this ticket.

Metadata