-
Notifications
You must be signed in to change notification settings - Fork 687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[xenial] Investigate noninteractive do-release-upgrade #3968
Comments
See @zenmonkeykstop’s suggestion here: #3204 (comment) |
The above error can be an one time thing. I just wanted that to be documented. |
Any idea why this error would be happening? |
The error is due to my ISP it seems :( |
I was trying the command mentioned in that playbook (pointed by @zenmonkeykstop ), it still asked for user input and later gave this error.
|
Gave me the following error (after user input).
I was trying to identify ways to fully unattended upgrade to xenial. |
The required Even if Python3.4 and related minimal package is installed on |
Note: |
Once we have addressed all blocking issues for the Xenial migration, we should perform a timeboxed investigation to determine whether it is feasible to perform a noninteractive upgrade.
It is unlikely that we would force the upgrade, but even for a manual upgrade (initiated, for example, via
securedrop-admin
), it would be ideal to minimize manual steps, which are error-prone and could result in inconsistent system configurations if users make choices different from the documented ones.This would also unblock automated Trusty->Xenial upgrade testing.
Part of #3204.
The text was updated successfully, but these errors were encountered: