An attempt to upgrade failed, logging the following entries:
dnf[910]: Failed to synchronize cache for repo 'my', disabling.
Followed by a bunch of:
"Unable to match package <name>"
and
"Error: Unable to match some of packages"
The "my" repo contains locally-built packages. The repo is on the server being upgraded here. Normally, apache starts and provides access to the repo over http. Nothing exotic.
system-upgrade downloaded all the packages from the "my" report without any problems, but "system-upgrade reboot" apparently rebooted the server, and the reboot apparently tried to sync again with the repo, but, of course, since the repo is down it failed.
So, how can I proceed with the upgrade, with this situation? Copy the "my" repo to another server, and point to it? That seems awkward. Why is "system upgrade" reboot trying to resync everything, that should've been "download"'s job, I would think.
On Thu, Nov 16, 2017 at 6:32 AM, Sam Varshavchik mrsam@courier-mta.com wrote:
The "my" repo contains locally-built packages. The repo is on the server being upgraded here. Normally, apache starts and provides access to the repo over http. Nothing exotic.
system-upgrade downloaded all the packages from the "my" report without any problems, but "system-upgrade reboot" apparently rebooted the server, and the reboot apparently tried to sync again with the repo, but, of course, since the repo is down it failed.
I'll bet this is because the system-upgrade reboot does not start apache. I have a similar setup except that I use a "file:" designation for my local repo rather than relying on a web server. This seems to work, and in fact I have local rsync'ed copies of the entire fedora and fedora-updates repos on a local machine, and I never have any trouble upgrading it that is due to having local repos (getting asterisk/dahdi to work after an upgrade is another thing entirely, but unrelated to local repos, more related to the fact that the dahdi driver is not free software by Fedora's criteria and therefore not included in the Fedora repos).
--Greg
Greg Woods writes:
system-upgrade downloaded all the packages from the "my" report without any problems, but "system-upgrade reboot" apparently rebooted the server, and the reboot apparently tried to sync again with the repo, but, of course, since the repo is down it failed.
I'll bet this is because the system-upgrade reboot does not start apache. I
Of course it doesn't.
have a similar setup except that I use a "file:" designation for my local repo rather than relying on a web server. This seems to work, and in fact I
Yes, it does. But "system-upgrade reboot" should not be doing that. You should be able to complete the reboot being completely off-line. Prior versions of Fedora had no issues doing everything, download-wise, during "system-upgrade download".
I can work around my local LAN issues. But there seems to be plenty of folks who, for one reason or another, will not have full network connectivity during a "system-upgrade reboot" (nor should they be required to). They are completely hosed, and will not be able to upgrade to F27, unless this bug gets fixed.
-
Greg Woods -
Sam Varshavchik