You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
dedicatePublicIpRange to domain doesn't work #2545
dedicate a public IP range to a domain doesn't work
STEPS TO REPRODUCE
create a new (should not be the first) public IP range
dedicate this range to a domain
acquire a new public IP in a project which is located in the specified domain
EXPECTED RESULTS
get a IP which is located in the specified IP range for this domain
ACTUAL RESULTS
ip is acquired from an other public pool (first created public IP range - with no assignment for domain)
Since a project can tie users/accounts from different domains, IP range dedicated to an account/domain cannot be used by a project. Can you advise exactly how you were testing this? /cc @PaulAngus
hi rohit, hi paul,
we create a domain for each customer.
some customers come with their own public ip range.
so we dedicate those ip ranges to their domain.
the result is, that they build up their own projects and they can use their own public ip range in all their projects in their domain
this was working up to 4.9 (4.10 untested from our side)
when we dedicate a public ip range to a domain now, this isn't working any more - they will get a ip from an other range.
I've confirmed that this behaviour used to work in 4.9.3 (projects would use IP dedicated to the domain that the project was in) and no longer works in 4.11.0 cc @DaanHoogland
Activity
yadvr commentedon May 9, 2018
Since a project can tie users/accounts from different domains, IP range dedicated to an account/domain cannot be used by a project. Can you advise exactly how you were testing this? /cc @PaulAngus
yadvr commentedon May 9, 2018
I've removed this from 4.11.1.0 until we can conclude that this is a valid bug.
se-bre commentedon May 11, 2018
hi rohit, hi paul,
we create a domain for each customer.
some customers come with their own public ip range.
so we dedicate those ip ranges to their domain.
the result is, that they build up their own projects and they can use their own public ip range in all their projects in their domain
this was working up to 4.9 (4.10 untested from our side)
when we dedicate a public ip range to a domain now, this isn't working any more - they will get a ip from an other range.
br, sebastian
@rhtyd @PaulAngus
se-bre commentedon May 16, 2018
we are not 100% sure, but we may found the commit where the relavant code was removed:
b2f7f9a#diff-0f5b97d5dceac89ff4509fbcf07d2330
File: server/src/com/cloud/network/IpAddressManagerImpl.java
Lines: 712 - 716
don't know if there was a reason for this @priyankparihar
PaulAngus commentedon May 22, 2018
I've confirmed that this behaviour used to work in 4.9.3 (projects would use IP dedicated to the domain that the project was in) and no longer works in 4.11.0 cc @DaanHoogland
DaanHoogland commentedon May 23, 2018
@se-bre can you code your steps to reproduce in a marvin test (or otherwise a small script)?
server: Fixes #2545 revert dedicate vlan code removal (#2664)
Merge branch 'Issue-Adicionar-Link-VPC-Infocard-VR' into '4.20.0.0-sc…