cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [cloudstack] DaanHoogland commented on issue #3321: Cannot associate a public IP to a new isolated network (4.12.0.0)
Date Tue, 04 Jun 2019 08:53:03 GMT
DaanHoogland 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-498583398
 
 
   @svanharmelen I had a discussion about the problem. there are two possible fixes but the
underlying problem will remain in both cases.
   1. start the network with a persistent offering and make sure you wait till it started
before configuring further. as this is an automated test in a simulator there might be issues
with timing which also might have caused the test to pass earlier while no real network traffic
was possible, before (in theory, not confirmed!).
   2. implement a global configuration item that disables the check for 'allocated' vs. 'implemented'
state, which will allow the old behaviour. This will fix your automarted test in simulator
but most probably won't work in real hypervisors.
   
   Can you test solution 1? I think it is more viable in production environments than solution
2.
   
   of course there is a third solution, refactoring the way IpAddressManager works, but this
will require the most time. I cannot even start planning that.
   
   /cc @rhtyd @PaulAngus 

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message