What happens if you use "apt dist-upgrade" instead? On Wed, May 10, 2017 at 5:34 AM, Jesus Cea <[email protected]> wrote:
> On 10/05/17 13:54, Jesus Cea wrote: > > On 09/05/17 16:37, Christopher Horrell wrote: > >> Hi Jesús, > >> > >> On a new debian-8 20170214 (e74a9cd0-f2d0-11e6-8b69-b3acf2ef87f7) > >> instance I was able to run to upgrade without hitting the same issue you > > > > Confirmed. I just reprovisioned the zone (using Ansible, 18 minutes > > downtime, 1.5 GB of downloads) and upgrading Debian packages worked > > fine. Apparently there was an intermediate upgrade that messed things up. > > > > Thanks for your time and effort. > > Errr... problem reproduced. > > Steps: > > 1. Provision a new zone using debian-8 20170214 > (e74a9cd0-f2d0-11e6-8b69-b3acf2ef87f7) image. > > 2. Inside the zone, "apt-get update; apt-get upgrade". > > 3. Ansible requires "aptitude". Install it inside the zone with "apt-get > install aptitude". This will install tons of dependencies. > > 4. An "apt: upgrade=full" in Ansible will bork your installation. My > update playbook is: > > - hosts: debian > tasks: > name: Update repository > apt: update_cache=yes > > - name: Full Upgrade > apt: upgrade=full > > Running this ansible playbook *WILL BREAK* your debian zone. > > 5. Debugging what the playbook is doing, I see this: "aptitude > full-upgrade". > > 6. Running that command manually I see this: > > """ > root@XXX:~# aptitude full-upgrade > The following packages will be upgraded: > libudev1 > 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Need to get 57.8 kB of archives. After unpacking 31.7 kB will be freed. > The following packages have unmet dependencies: > udev : Depends: libudev1 (= 215-17+deb8u6) but 215-17+deb8u7 is to be > installed. > The following actions will resolve these dependencies: > > Remove the following packages: > systemd > systemd-sysv > udev > > Install the following packages: > sysvinit-core [2.88dsf-59 (stable)] > > Accept this solution? [Y/n/q/?] > """ > > Ansible is probably accepting that suggestion, implying udev removal. > > Since ansible is a common tool, I think we need a workaround for this. I > am using version 2.3.0.0, current release. > > Trying several choices offered by "aptitude- full-upgrade", I see > "Upgrade the following packages: > udev [215-17+deb8u6 (now) -> 215-17+deb8u7 (stable)]" but it also > break the debian zone. > > If you do "Keep the following packages at their current version: > libudev1 [215-17+deb8u6 (now)]" > keep installed udev version". You will have the same issue in the next > "aptitude full-upgrade". > > That is, if you are managing Debian updates with Ansible, a popular > choice, you will be messed. > > -- > Jesús Cea Avión _/_/ _/_/_/ _/_/_/ > [email protected] - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ > Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ > jabber / xmpp:[email protected] _/_/ _/_/ _/_/ _/_/ _/_/ > "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ > "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ > "El amor es poner tu felicidad en la felicidad de otro" - Leibniz > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
