[Maas-devel] "Static IP Address with this Ip already exists." with 1.6+bzr2496
Julian Edwards
julian.edwards at canonical.com
Fri Jul 4 03:14:12 UTC 2014
On 04/07/14 05:21, Andreas Hasenack wrote:
> On Thu, Jul 3, 2014 at 3:54 PM, Andreas Hasenack <andreas at canonical.com
> <mailto:andreas at canonical.com>> wrote:
>
> Hi,
>
> I upgraded my trusty maas to 1.6+bzr2496 and started some
> deployments with it.
>
> I updated the cluster configuration now that we have a new range to
> fill in, static and dynamic addresses. This is what I have:
>
> DHCP low: 10.0.5.150
> DHCP high: 10.0.5.250
> static low: 10.0.5.50
> static high: 10.0.5.100
> network: 10.0.5.0/24 <http://10.0.5.0/24>
>
> I started a cloud deployment on it, but got this provisioning error
> for all machines but the juju bootstrap node:
> "1":
> agent-state-info: 'gomaasapi: got error back from server: 400
> BAD REQUEST ({"ip":
> ["Static IP Address with this Ip already exists."]})'
> instance-id: pending
> series: trusty
>
> Any specific idea where to start debugging?
>
>
> I can bootstrap just fine, anytime. But juju deploy <something> always
> fails with the above provisioning error.
I cannot recreate this, everything seems to work fine when I do a
bootstrap and then a simple "juju deploy mysql". What, exactly, is a
"cloud deployment" and what is it doing with maas?
Since we don't overlap much I'll try and suggest a few things:
- what version of juju? I am using the stock one in trusty (1.18.4)
- Is that error in the maas.log?
- can you see what juju is sending to maas to get that error back?
- what host maps exist in the leases file for the static range you defined?
Can you destroy the env and try again, too, just to make sure.
J
More information about the Maas-devel
mailing list