Are you certain this is related to the cpu constraint, rather than any
of the others you had set? The logic there with respect to floats and
gte is correct, there are tests in the codebase for that aspect.
Please try the following:
1) `juju destroy-environment`
2) `juju bootstrap`
3) `juju set-constraints cpu=1.0`
4) `juju deploy <something>`
I suspect the issue was with the maas-name constraint you have set
there, once you have the bootstrap node on that machine, all further
attempts to allocate a machine will fail as it's already in use.
** Changed in: maas
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154803
Title:
Constraints prevents the allocation of nodes if they are equal to the
HW.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1154803/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
