| 2020-08-04 21:49:36 |
james beedy |
bug |
|
|
added bug |
| 2020-08-04 21:49:36 |
james beedy |
attachment added |
|
Screen Shot 2020-08-04 at 2.40.55 PM.png https://bugs.launchpad.net/bugs/1890347/+attachment/5398756/+files/Screen%20Shot%202020-08-04%20at%202.40.55%20PM.png |
|
| 2020-08-04 21:51:33 |
james beedy |
description |
I have added a space to my model. I am trying to deploy some charms to the space. I have added constraints to the charms in my bundle that constrain them to the space and add root-disk=20G.
The root-disk constraint seems to be applied, but the spaces constraint doesn't stick.
juju spaces https://paste.ubuntu.com/p/MkQCmPqMXV/
bundle.yaml https://paste.ubuntu.com/p/fvxJkkTknk/
juju status https://paste.ubuntu.com/p/W8FpRjmrXR/
juju run --all "ip a | grep 'ens\|eth'" https://paste.ubuntu.com/p/FtsBKN23f3/
You can see from the attached screen shot that the NAT_COMMON_* subnets have the addresses that match the subnets that are in my space, and from the output of the juju run command that the ip addresses of the machines in my model aren't in the space I have constrained them to.
This is the first time I have used spaces in aws with juju > 2.7.6. Using spaces via constraints seems to work fine using the jaas controller. |
I have added a space to my model. I am trying to deploy some charms to the space. I have added constraints to the charms in my bundle that constrain them to the space and add root-disk=20G.
The root-disk constraint seems to be applied, but the spaces constraint doesn't stick.
juju spaces https://paste.ubuntu.com/p/MkQCmPqMXV/
bundle.yaml https://paste.ubuntu.com/p/fvxJkkTknk/
juju status https://paste.ubuntu.com/p/W8FpRjmrXR/
juju run --all "ip a | grep 'ens\|eth'" https://paste.ubuntu.com/p/FtsBKN23f3/
You can see from the attached screen shot that the NAT_COMMON_* subnets have the addresses that match the subnets that are in my space, and from the output of the juju run command that the ip addresses of the machines in my model aren't in the space I have constrained them to.
It might be worth adding that this is the first time I have used spaces in aws with juju > 2.7.6. Using spaces in this same way works as expected when I use the jaas controller which is < 2.8. |
|
| 2020-08-04 22:06:55 |
james beedy |
description |
I have added a space to my model. I am trying to deploy some charms to the space. I have added constraints to the charms in my bundle that constrain them to the space and add root-disk=20G.
The root-disk constraint seems to be applied, but the spaces constraint doesn't stick.
juju spaces https://paste.ubuntu.com/p/MkQCmPqMXV/
bundle.yaml https://paste.ubuntu.com/p/fvxJkkTknk/
juju status https://paste.ubuntu.com/p/W8FpRjmrXR/
juju run --all "ip a | grep 'ens\|eth'" https://paste.ubuntu.com/p/FtsBKN23f3/
You can see from the attached screen shot that the NAT_COMMON_* subnets have the addresses that match the subnets that are in my space, and from the output of the juju run command that the ip addresses of the machines in my model aren't in the space I have constrained them to.
It might be worth adding that this is the first time I have used spaces in aws with juju > 2.7.6. Using spaces in this same way works as expected when I use the jaas controller which is < 2.8. |
I have added a space to my model. I am trying to deploy some charms to the space. I have added constraints to the charms in my bundle that constrain them to the space and add root-disk=20G.
The root-disk constraint seems to be applied, but the spaces constraint doesn't stick.
juju spaces https://paste.ubuntu.com/p/MkQCmPqMXV/
bundle.yaml https://paste.ubuntu.com/p/fvxJkkTknk/
juju status https://paste.ubuntu.com/p/W8FpRjmrXR/
juju run --all "ip a | grep 'ens\|eth'" https://paste.ubuntu.com/p/FtsBKN23f3/
You can see from the attached screen shot that the NAT_COMMON_* subnets have the addresses that match the subnets that are in my space, and from the output of the juju run command that the ip addresses of the machines in my model aren't in the space I have constrained them to.
It might be worth adding that this is the first time I have used spaces in aws with juju > 2.7.6. Using spaces in this same way works as expected when I use the jaas controller which is < 2.8.
This can be replicated by adding a space to an aws model running juju > 2.8 and deploying a charm to the space using juju deploy ubuntu --constraints spaces=<myspace>.
The expected result is that the charm doesn't land in a subnet that is mapped to your space. |
|
| 2020-08-04 22:08:22 |
james beedy |
description |
I have added a space to my model. I am trying to deploy some charms to the space. I have added constraints to the charms in my bundle that constrain them to the space and add root-disk=20G.
The root-disk constraint seems to be applied, but the spaces constraint doesn't stick.
juju spaces https://paste.ubuntu.com/p/MkQCmPqMXV/
bundle.yaml https://paste.ubuntu.com/p/fvxJkkTknk/
juju status https://paste.ubuntu.com/p/W8FpRjmrXR/
juju run --all "ip a | grep 'ens\|eth'" https://paste.ubuntu.com/p/FtsBKN23f3/
You can see from the attached screen shot that the NAT_COMMON_* subnets have the addresses that match the subnets that are in my space, and from the output of the juju run command that the ip addresses of the machines in my model aren't in the space I have constrained them to.
It might be worth adding that this is the first time I have used spaces in aws with juju > 2.7.6. Using spaces in this same way works as expected when I use the jaas controller which is < 2.8.
This can be replicated by adding a space to an aws model running juju > 2.8 and deploying a charm to the space using juju deploy ubuntu --constraints spaces=<myspace>.
The expected result is that the charm doesn't land in a subnet that is mapped to your space. |
I have added a space to my model. I am trying to deploy some charms to the space. I have added constraints to the charms in my bundle that constrain them to the space and add root-disk=20G.
The root-disk constraint seems to be applied, but the spaces constraint doesn't stick.
juju spaces https://paste.ubuntu.com/p/MkQCmPqMXV/
bundle.yaml https://paste.ubuntu.com/p/fvxJkkTknk/
juju status https://paste.ubuntu.com/p/W8FpRjmrXR/
juju run --all "ip a | grep 'ens\|eth'" https://paste.ubuntu.com/p/FtsBKN23f3/
You can see from the attached screen shot that the NAT_COMMON_* subnets have the addresses that match the subnets that are in my space, and from the output of the juju run command that the ip addresses of the machines in my model aren't in the space I have constrained them to.
It might be worth adding that this is the first time I have used spaces in aws with juju > 2.7.6. Using spaces in this same way works as expected when I use the jaas controller which is < 2.8.
This can be replicated by adding a space to an aws model running juju > 2.8 and deploying a charm to the space using juju add-space myspace <subnet1> <subnet2> <subnet3> && juju deploy ubuntu --constraints spaces=myspace.
The expected result is that the charm doesn't land in a subnet that is mapped to the space. |
|
| 2020-08-06 06:36:38 |
John A Meinel |
juju: status |
New |
Triaged |
|
| 2020-08-06 06:36:40 |
John A Meinel |
juju: importance |
Undecided |
High |
|
| 2020-08-06 07:38:03 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2020-08-06 12:48:33 |
Joseph Phillips |
juju: assignee |
|
Joseph Phillips (manadart) |
|
| 2020-08-06 12:48:35 |
Joseph Phillips |
juju: status |
Triaged |
In Progress |
|
| 2020-08-11 09:48:17 |
Joseph Phillips |
juju: milestone |
|
2.8.2 |
|
| 2020-08-11 14:39:41 |
Joseph Phillips |
juju: status |
In Progress |
Fix Committed |
|
| 2020-09-15 02:08:10 |
Canonical Juju QA Bot |
juju: status |
Fix Committed |
Fix Released |
|
