Correct, The above string is "instance-type=3.75" and then some other
constraint "GB" that we don't recognize. Looking at the rackspace pricing
page: https://www.rackspace.com/cloud/servers/pricing
I don't see any instance type names with spaces. I see "Compute1-4" which
matches 3.75GB (and presumably v1 compute).
Am I missing the instance-types that rackspace exposes?
--constraints "instance-type=Compute1-4"
seems like it should work.
On Sun, Apr 14, 2019 at 3:45 AM Goran Miskovic <email address hidden> wrote:
> I believe that the original problem was not fixed.
>
> Juju is complaining about spaces in the instace_type value.
>
> juju --debug deploy ~/charms/bionic/webserver tomcms --config
> ~/charms/bionic/cmsadmin.yaml --series bionic --constraints
> "instance-type=3.75 GB Compute v1"
> 00:55:20 INFO juju.cmd supercommand.go:57 running juju [2.5.4 gc go1.10.4]
> 00:55:20 DEBUG juju.cmd supercommand.go:58 args:
> []string{"/snap/juju/7206/bin/juju", "--debug", "deploy",
> "~/charms/bionic/webserver", "tomcms", "--config",
> "~/charms/bionic/cmsadmin.yaml", "--series", "bionic", "--constraints",
> "instance-type=3.75 GB Compute v1"}
> ERROR malformed constraint "GB"
> 00:55:20 DEBUG cmd supercommand.go:496 error stack:
> /build/juju/parts/juju/go/src/
> github.com/juju/juju/constraints/constraints.go:413: malformed constraint
> "GB"
> /build/juju/parts/juju/go/src/
> github.com/juju/juju/constraints/constraints.go:318:
>
> Since multiple constraints are separated by space eg --constraints
> "mem=5G cores=2" parssing value --constraints "instance-type=3.75 GB
> Compute v1" will obviously fail.
>
> See
>
> https://github.com/juju/juju/blob/1db915832ead46583f32341ad04753fb5c93c07d/core/constraints/constraints.go#L328
>
> Perhaps urldecode might be a way to go. urlenclded value as "instance-
> type=3.75%20GB%20Compute%20v1" will pass validation but unless decoded,
> the value will not match valid values.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1641224
>
> Title:
> Instance-type constraint in rackspace fails
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1641224/+subscriptions
>
Correct, The above string is "instance- type=3. 75" and then some other /www.rackspace. com/cloud/ servers/ pricing
constraint "GB" that we don't recognize. Looking at the rackspace pricing
page:
https:/
I don't see any instance type names with spaces. I see "Compute1-4" which
matches 3.75GB (and presumably v1 compute).
Am I missing the instance-types that rackspace exposes?
--constraints "instance- type=Compute1- 4"
seems like it should work.
On Sun, Apr 14, 2019 at 3:45 AM Goran Miskovic <email address hidden> wrote:
> I believe that the original problem was not fixed. bionic/ webserver tomcms --config bionic/ cmsadmin. yaml --series bionic --constraints "/snap/ juju/7206/ bin/juju" , "--debug", "deploy", bionic/ webserver" , "tomcms", "--config", bionic/ cmsadmin. yaml", "--series", "bionic", "--constraints", juju/parts/ juju/go/ src/ com/juju/ juju/constraint s/constraints. go:413: malformed constraint juju/parts/ juju/go/ src/ com/juju/ juju/constraint s/constraints. go:318: /github. com/juju/ juju/blob/ 1db915832ead465 83f32341ad04753 fb5c93c07d/ core/constraint s/constraints. go#L328 75%20GB% 20Compute% 20v1" will pass validation but unless decoded, /bugs.launchpad .net/bugs/ 1641224 /bugs.launchpad .net/juju/ +bug/1641224/ +subscriptions
>
> Juju is complaining about spaces in the instace_type value.
>
> juju --debug deploy ~/charms/
> ~/charms/
> "instance-type=3.75 GB Compute v1"
> 00:55:20 INFO juju.cmd supercommand.go:57 running juju [2.5.4 gc go1.10.4]
> 00:55:20 DEBUG juju.cmd supercommand.go:58 args:
> []string{
> "~/charms/
> "~/charms/
> "instance-type=3.75 GB Compute v1"}
> ERROR malformed constraint "GB"
> 00:55:20 DEBUG cmd supercommand.go:496 error stack:
> /build/
> github.
> "GB"
> /build/
> github.
>
> Since multiple constraints are separated by space eg --constraints
> "mem=5G cores=2" parssing value --constraints "instance-type=3.75 GB
> Compute v1" will obviously fail.
>
> See
>
> https:/
>
> Perhaps urldecode might be a way to go. urlenclded value as "instance-
> type=3.
> the value will not match valid values.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> Instance-type constraint in rackspace fails
>
> To manage notifications about this bug go to:
> https:/
>