Skip to content

dedicatePublicIpRange to domain doesn't work #2545

Closed

Description

@se-bre
ISSUE TYPE
  • Bug Report
COMPONENT NAME
Network (Public)
CLOUDSTACK VERSION
4.11.0.0
CONFIGURATION

advanced networking

OS / ENVIRONMENT

Ubuntu 16.04 (Management/Hypervisor)
KVM

SUMMARY

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)

Activity

  1. added this to the 4.11.1.0 milestone on Apr 23, 2018
  2. yadvr commented on May 9, 2018

    @yadvr
    Member

    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

  3. removed this from the 4.11.1.0 milestone on May 9, 2018
  4. yadvr commented on May 9, 2018

    @yadvr
    Member

    I've removed this from 4.11.1.0 until we can conclude that this is a valid bug.

  5. se-bre commented on May 11, 2018

    @se-bre
    Author

    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

  6. added this to the 4.11.1.0 milestone on May 11, 2018
  7. se-bre commented on May 16, 2018

    @se-bre
    Author

    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

  8. PaulAngus commented on May 22, 2018

    @PaulAngus
    Member

    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

  9. self-assigned this
    on May 23, 2018
  10. DaanHoogland commented on May 23, 2018

    @DaanHoogland
    Contributor

    @se-bre can you code your steps to reproduce in a marvin test (or otherwise a small script)?

  11. added a commit that references this issue on May 23, 2018
    7a3a882
  12. removed their assignment
    on Jun 13, 2023
  13. added a commit that references this issue on Feb 18, 2025
    32f72f5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions