[GitHub] [cloudstack] svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0) URL: https://github.com/apache/cloudstack/issues/3321#issuecomment-501234383 If you look at the [CHANGELOG](https://github.com/hashicorp/packer/blob/master/CHANGELOG.md) you'll see that the CloudStack fix is not part of `1.4.1` but is merged into master and will be part of the `1.4.2` release. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0) URL: https://github.com/apache/cloudstack/issues/3321#issuecomment-501217050 @nlindblo no problem! I think Packer should work as expected (it already updated to support 4.12. Terraform should work as well, except for creating certain network types. If you encounter any specific errors that seems other then mentioned here, please open an issue with the related tool. Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0) URL: https://github.com/apache/cloudstack/issues/3321#issuecomment-501211503 @nlindblo please define `this will be fixed`? Not sure what you mean with `this` here 😉 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0) URL: https://github.com/apache/cloudstack/issues/3321#issuecomment-499052571 > Another solution I was thinking of is to check whether there already is an address on the interface and first add an extra one if there is none yet. That could also work. In the Terraform network resource I added a [source_nat_ip](https://github.com/terraform-providers/terraform-provider-cloudstack/blob/master/cloudstack/resource_cloudstack_network.go#L115) option that adds the NAT IP right after creating the network. This abstracts the problem for our users a little, but now fails with 4.12.x.x This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0) URL: https://github.com/apache/cloudstack/issues/3321#issuecomment-499038556 @DaanHoogland as already mentioned, option 1 works and allows me to test all the logic using the simulator. So that is good news! But my remaining issue (worry) is that when people are using the updated code against a real environment they will encounter the same issue. And then asking everyone to update their network offerings seems like as poor solution for them. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0) URL: https://github.com/apache/cloudstack/issues/3321#issuecomment-495982918 @DaanHoogland I tested it again and I think I didn't test it correctly last time, as now it worked as expected when I updated the network offering to be persistent. So the good thing is that I could now test all the changes and make sure the changes work. The bad thing is that if I release an updated provider using this code, people using 4.12.0.0 will still hit this error. As workaround I can tell them to use a persistent network offering, but a much better solution would be a bug fix release to mitigate this issue. Could that be an option? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0) URL: https://github.com/apache/cloudstack/issues/3321#issuecomment-495194404 Yes I did! And sorry for the late reply... But t doesn't seem to make a difference. I can do some more tests early next week (I hope). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0) URL: https://github.com/apache/cloudstack/issues/3321#issuecomment-492551591 @DaanHoogland I will try to test with this today and let you know how it worked out. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0) URL: https://github.com/apache/cloudstack/issues/3321#issuecomment-491256328 Ok... And is there a change we can get a 4.12.1.0 or something? As this means both Terraform and Packer will not be able to play nice with 4.12.x.x (https://github.com/hashicorp/packer/issues/7557). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0) URL: https://github.com/apache/cloudstack/issues/3321#issuecomment-491192125 Yep, that seems to be it. Good find 👍 So now the question is if this is actually the desired behavior, or that it was an oversight that this will make it harder (if not impossible) to configure a network properly before using it now? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0) URL: https://github.com/apache/cloudstack/issues/3321#issuecomment-491188620 Cool, yeah that is indeed the call that I'm trying to make... This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
svanharmelen commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0) URL: https://github.com/apache/cloudstack/issues/3321#issuecomment-490976870 @DaanHoogland as discussed previously, here is an issue to track this problem. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
