Comments on the 16.04.1 to 18.04.1 upgrade Experience [on hold]
Clash Royale CLAN TAG#URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
0
down vote
favorite
I have 4 different Ubuntu 16.04.1 systems to upgrade to 18.04.1: gateway, mail, web (facing the internet) and an internal file server. Running "do-release-upgrade -d" on the gateway worked perfectly, however the web and file server machines both experienced what I can only call a "successful failure" of the do-release-update procedure. By that I mean that the process reported a failure and said it was rolling things back, but after rebooting I the system reported it was running Ubuntu 18.04.1 and there were over 600 packages to be updated. So, whatever passes for the "version numbered core" of Ubuntu WAS updated even though the process failed. Seems a bit strange to me, but whatever.
So, I found some commands (by searching here and elsewhere) that could possibly help and here's where I have a suggestion/request... The first several commands I tried (A) told me that they could not do their job until I ran (B) the name of a specific command, including parameters. It makes me wonder, in this day and age, why it was too difficult for these developers to offer to execute the correct command for me instead of requiring me to retype what they just showed me? (FWIW, after doing "dpkg --configure -c", "apt-get -f install", and "apt-get dist-upgrade" my 18.04.1 systems seem to be fine and up-to-date, but I'm not completely comfortable after the "successful failures" on both -- is there a "verify-release-upgrade" command?)
My other pet peeve is all of the questions about configuration files that I may have modified locally. Why does the upgrade (or update) process not record a list of these for later review? Instead I need to keep an actual pen and paper next to my server to record things like this, which can be especially tedious with the super long paths that some of these files have. I'm sure there may be a log (or logs) where this info is buried, but not everyone has an eidetic memory for rarely used regular expressions to find these things. It seems like this information is a perfect candidate for a post-upgrade report that should be easily available after the process is completed. Or is there one of those already that is just not mentioned to the user at the end (or beginning) of the upgrade process?
If any folks who work on the upgrade procedures see this, maybe these ideas will have some value. Perhaps in a different form, but anything that improves the overall upgrade experience, IMHO, is a good thing.
apt server upgrade updates 18.04
asked 4 hours ago
Steve Valliere
259415
put on hold as unclear what you're asking by DK Bose, N0rbert, mikewhatever, chili555, Terrance 2 hours ago
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
up vote
0
down vote
favorite
I have 4 different Ubuntu 16.04.1 systems to upgrade to 18.04.1: gateway, mail, web (facing the internet) and an internal file server. Running "do-release-upgrade -d" on the gateway worked perfectly, however the web and file server machines both experienced what I can only call a "successful failure" of the do-release-update procedure. By that I mean that the process reported a failure and said it was rolling things back, but after rebooting I the system reported it was running Ubuntu 18.04.1 and there were over 600 packages to be updated. So, whatever passes for the "version numbered core" of Ubuntu WAS updated even though the process failed. Seems a bit strange to me, but whatever.
So, I found some commands (by searching here and elsewhere) that could possibly help and here's where I have a suggestion/request... The first several commands I tried (A) told me that they could not do their job until I ran (B) the name of a specific command, including parameters. It makes me wonder, in this day and age, why it was too difficult for these developers to offer to execute the correct command for me instead of requiring me to retype what they just showed me? (FWIW, after doing "dpkg --configure -c", "apt-get -f install", and "apt-get dist-upgrade" my 18.04.1 systems seem to be fine and up-to-date, but I'm not completely comfortable after the "successful failures" on both -- is there a "verify-release-upgrade" command?)
My other pet peeve is all of the questions about configuration files that I may have modified locally. Why does the upgrade (or update) process not record a list of these for later review? Instead I need to keep an actual pen and paper next to my server to record things like this, which can be especially tedious with the super long paths that some of these files have. I'm sure there may be a log (or logs) where this info is buried, but not everyone has an eidetic memory for rarely used regular expressions to find these things. It seems like this information is a perfect candidate for a post-upgrade report that should be easily available after the process is completed. Or is there one of those already that is just not mentioned to the user at the end (or beginning) of the upgrade process?
If any folks who work on the upgrade procedures see this, maybe these ideas will have some value. Perhaps in a different form, but anything that improves the overall upgrade experience, IMHO, is a good thing.
apt server upgrade updates 18.04
asked 4 hours ago
Steve Valliere
259415
put on hold as unclear what you're asking by DK Bose, N0rbert, mikewhatever, chili555, Terrance 2 hours ago
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have 4 different Ubuntu 16.04.1 systems to upgrade to 18.04.1: gateway, mail, web (facing the internet) and an internal file server. Running "do-release-upgrade -d" on the gateway worked perfectly, however the web and file server machines both experienced what I can only call a "successful failure" of the do-release-update procedure. By that I mean that the process reported a failure and said it was rolling things back, but after rebooting I the system reported it was running Ubuntu 18.04.1 and there were over 600 packages to be updated. So, whatever passes for the "version numbered core" of Ubuntu WAS updated even though the process failed. Seems a bit strange to me, but whatever.
So, I found some commands (by searching here and elsewhere) that could possibly help and here's where I have a suggestion/request... The first several commands I tried (A) told me that they could not do their job until I ran (B) the name of a specific command, including parameters. It makes me wonder, in this day and age, why it was too difficult for these developers to offer to execute the correct command for me instead of requiring me to retype what they just showed me? (FWIW, after doing "dpkg --configure -c", "apt-get -f install", and "apt-get dist-upgrade" my 18.04.1 systems seem to be fine and up-to-date, but I'm not completely comfortable after the "successful failures" on both -- is there a "verify-release-upgrade" command?)
My other pet peeve is all of the questions about configuration files that I may have modified locally. Why does the upgrade (or update) process not record a list of these for later review? Instead I need to keep an actual pen and paper next to my server to record things like this, which can be especially tedious with the super long paths that some of these files have. I'm sure there may be a log (or logs) where this info is buried, but not everyone has an eidetic memory for rarely used regular expressions to find these things. It seems like this information is a perfect candidate for a post-upgrade report that should be easily available after the process is completed. Or is there one of those already that is just not mentioned to the user at the end (or beginning) of the upgrade process?
If any folks who work on the upgrade procedures see this, maybe these ideas will have some value. Perhaps in a different form, but anything that improves the overall upgrade experience, IMHO, is a good thing.
apt server upgrade updates 18.04
asked 4 hours ago
Steve Valliere
259415
I have 4 different Ubuntu 16.04.1 systems to upgrade to 18.04.1: gateway, mail, web (facing the internet) and an internal file server. Running "do-release-upgrade -d" on the gateway worked perfectly, however the web and file server machines both experienced what I can only call a "successful failure" of the do-release-update procedure. By that I mean that the process reported a failure and said it was rolling things back, but after rebooting I the system reported it was running Ubuntu 18.04.1 and there were over 600 packages to be updated. So, whatever passes for the "version numbered core" of Ubuntu WAS updated even though the process failed. Seems a bit strange to me, but whatever.
So, I found some commands (by searching here and elsewhere) that could possibly help and here's where I have a suggestion/request... The first several commands I tried (A) told me that they could not do their job until I ran (B) the name of a specific command, including parameters. It makes me wonder, in this day and age, why it was too difficult for these developers to offer to execute the correct command for me instead of requiring me to retype what they just showed me? (FWIW, after doing "dpkg --configure -c", "apt-get -f install", and "apt-get dist-upgrade" my 18.04.1 systems seem to be fine and up-to-date, but I'm not completely comfortable after the "successful failures" on both -- is there a "verify-release-upgrade" command?)
My other pet peeve is all of the questions about configuration files that I may have modified locally. Why does the upgrade (or update) process not record a list of these for later review? Instead I need to keep an actual pen and paper next to my server to record things like this, which can be especially tedious with the super long paths that some of these files have. I'm sure there may be a log (or logs) where this info is buried, but not everyone has an eidetic memory for rarely used regular expressions to find these things. It seems like this information is a perfect candidate for a post-upgrade report that should be easily available after the process is completed. Or is there one of those already that is just not mentioned to the user at the end (or beginning) of the upgrade process?
If any folks who work on the upgrade procedures see this, maybe these ideas will have some value. Perhaps in a different form, but anything that improves the overall upgrade experience, IMHO, is a good thing.
apt server upgrade updates 18.04
asked 4 hours ago
Steve Valliere
259415
asked 4 hours ago
Steve Valliere
259415
asked 4 hours ago
Steve Valliere
259415
asked 4 hours ago
Steve Valliere
259415
259415
put on hold as unclear what you're asking by DK Bose, N0rbert, mikewhatever, chili555, Terrance 2 hours ago
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as unclear what you're asking by DK Bose, N0rbert, mikewhatever, chili555, Terrance 2 hours ago
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes