maas-devel team mailing list archive

[Andreas Hasenack <andreas@xxxxxxxxxxxxx>]

On Fri, Jul 11, 2014 at 6:40 PM, Andreas Hasenack <andreas@xxxxxxxxxxxxx>
wrote:

> On Thu, Jul 10, 2014 at 2:29 AM, Julian Edwards <
> julian.edwards@xxxxxxxxxxxxx> wrote:
>
>> See ppa:maas-maintainers/testing which contains maas
>> 1.6+bzr2532-0ubuntu1~beta4~ppa1
>>
>> Changes since beta 3:
>>  - Added a "static-ipaddresses" to the API capability reference
>>
>>  - https://bugs.launchpad.net/maas/+bug/1337683 fixed - allow multiple
>> GET values with the same key in the api client
>>
>>  - https://bugs.launchpad.net/bugs/1339631 fixed (ensure find_nodegroups
>> api call doesn't crash if given an IPv6 address)
>>
>>  - Further fix for https://bugs.launchpad.net/bugs/1338402, ensure that
>> new upper and lower bounds for a static range can overlap with an
>> existing address.
>>
>>
>
> I upgraded another MAAS 1.5.2 to this beta4 and here are my observations:
> - apparently one needs to import boot images again. Machines were just not
> booting correctly, getting iscsi errors, images not found, etc. I clicked
> on the import images button, waited for a while (had to use a network
> monitor to know something was going on) and eventually had the magic number
> for boot images available (129). Then booting worked again on my nodes.
> - some nodes that were already in the ready state before the upgrade were
> still booting with the old IP after the upgrade, instead of the new static
> range. Do we need to clear out the leases file or something? Or trigger a
> DNS rewrite by changing the hostname temporarily? No nodes were in use when
> I did the upgrade: all were just "ready".
>
> I'm still debugging this last issue in a node. It boots on a 10.96.1.x
> address (old) but dns already points to the new 10.96.5.x one (from the
> static range). I recomissioned it again, and now it doesn't even have a dns
> entry anymore.
>

I gave up and nuked the leases file. That seemed to have solved the
problems. All machines got an ip from the static range now. I was having
issues before in 1.5.2 with CNAMEs disappearing, and other symptoms that
were pointing at that bug about dhcp IP conflicts, that's what prompted the
upgrade to maas 1.6. Maybe upgrading while in that state is what caused
this, or rather, didn't fix it.