Comment 4 for bug 1766401

Thanks for getting back to me.

Hope this can help in some way:

1) Do you have the previous contents of 50-cloud-init.cfg?

Once the apt-upgrade was run, the contents were wiped. The only contents
that were left were

auto lo
iface lo inet loopback

2) Did you make modifications to the file, and they were "reverted"?

No mods were made. The VSI was running as installed from SoftLayer's
provisioning ISO. Whereas SEVERAL apt-upgrades (and reboots) were performed
previous to this issue, I can only assume that this is related to a newer
patch. The VSI has been up for a couple of months. I need to be clear, this
happened to 4 other VSI's I'm running, so this isn't a single user issue.
The other VSI's are configured the same way. I have 6 others that I haven't
updated as I am awaiting a bug fix. (Yes, I have already backed up their
network configs).

3) Did you reboot, or was it just an `apt-get dist-upgrade` that you
ran?

Yes. It wasn't until I rebooted that I discovered that my host (and 4
others) was unreachable. I had to KVM into the VSI to "restore" what was
lost.

4) Please also attach what the cloud-init version was before and after
your apt-upgrade attempt.

I don't have the original, I've only restored what I "think" was lost based
on another host that hasn't been updated yet. They're working again, so I
assume that what I restored was correct.

Here's what's there now (I've obviously removed the actual IP's):

 This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
   dns-nameservers 10.0.x.x 10.0.x.x

auto eth0
iface eth0 inet static
   address 10.x.x.x/24
   post-up route add -net 10.0.0.0 netmask 255.0.0.0 gw 10.x.x.1 || true
   pre-down route del -net 10.0.0.0 netmask 255.0.0.0 gw 10.x.x.1. || true
   post-up route add -net 161.x.x.x netmask 255.255.0.0 gw 10.x.x.1 || true
   pre-down route del -net 161.x.x.x netmask 255.255.0.0 gw 10.x.x.1 || true

auto eth1
iface eth1 inet static
  address 169.x.x.x/27
  post-up route add default gw 169.x.x.x || true
  pre-down route del default gw 169.x.x.x || true

** Changed in: cloud-init
       Status: New => Incomplete

Let me know if you need more.

*James Tigert*

*"I am not bound to win, but I am bound to be true. I am not bound to
succeed,but I am bound to live by the light that I have. I must stand with
anybody that stands right, and stand with him while he is right, and part
with him when he goes wrong." -Abraham Lincoln*

On Tue, Apr 24, 2018 at 12:28 PM, David Britton <<email address hidden>
> wrote:

> Some questions...
>
> 1) Do you have the previous contents of 50-cloud-init.cfg?
>
> 2) Did you make modifications to the file, and they were "reverted"?
>
> 3) Did you reboot, or was it just an `apt-get dist-upgrade` that you
> ran?
>
> 4) Please also attach what the cloud-init version was before and after
> your apt-upgrade attempt.
>
>
> ** Changed in: cloud-init
> Status: New => Incomplete
>
> ** Tags removed: dsid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766401
>
> Title:
> full config file wiped after apt-upgrade issued
>
> Status in cloud-init:
> Incomplete
>
> Bug description:
> file: 50-cloud-init.cfg wiped of it's initial (working) configuration
> after a standard apt-upgrade was issued.
>
> Cloud provider is SoftLayer.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1766401/+subscriptions
>