Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Select time outed/canceled repos
2. Run sync (web/cli)
I have problem with Fedora 20 repos
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
To better understand the source of the problem, please provide any additional details such as more precise steps to reproduce. Attaching the output of foreman-debug to this BZ will also be necessary. Thanks!
Created attachment 920494 [details]
I repodiscovered url "http://mirrors.nic.cz/fedora/linux/updates/20/" and added "http://mirrors.nic.cz/fedora/linux/updates/20/i386/" and "http://mirrors.nic.cz/fedora/linux/updates/20/x86_64/" and added it to product Fedora. There were 2 more previously synchronized repos from fodora os (i386 and x86_64). Both successfully. After that I went to Contetnt -> Sync Status, select newly created Fedora updates repo and clicked on Synchronize Now.
Than I go home.
Next day, there was empty progress bar, so I canceled it and than tried to synchronize them again. Since than nothing has happened.
It always happened with all repositories. If I cancel them it is not possible to sync them again.
I still have stucked fedora synchronization. Server restart did not help. I can synchronize all other repositories. Even if I reschedule stucked repos sync it will not help.
The repositories you have listed in your previous comment, when I browse them through the Web UI, do not appear to be valid repository links (e.g. I am not seeing a repomd.xml anywhere). Are you able to check what the error output or what stage the error occurred at during the repository sync?
Jakub, if you are still using Satellite 6 can you re-attempt this with our latest version?
I was able to discover and create repositories with this url just fine:
I'm going to close this as WORKSFORMME but feel free to re-open if you are still seeing this with the latest 6.0.8 or 6.1 Beta versions.
I can confirm, that synchronization works for me.