As this bug still unresolved (surprised to see its from 2016), I have to post another night night headache bug #1899075. I should agree with this bug author. Release upgrade script should not block due any package upgrade error. Any fail in a package upgrade should be just an warning, to be handled after full distro upgrade. Or you can at least leave grub correctly installed even with packages upgrade errors, to avoid servers stucks at boot screen. Most servers today are remote and virtualized, and most people will not know how to handle with this situation. Luckly MS Azure has an vm repair extension to be used in azure console, but its still hidden for people which only uses Web UI.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612517 Title: Server fails to start after upgrade because of customized config and obsolete/renamed directives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1612517/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
