subnet IPAM in GUI shows wrong object (always the first)
Bug #1675083 reported by
Slobodan Blatnjak
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juniper Openstack |
Fix Committed
|
Undecided
|
Unassigned | ||
| R3.2 |
Fix Committed
|
Undecided
|
Siva Bavanasi | ||
| OpenContrail |
Fix Committed
|
Undecided
|
Siva Bavanasi | ||
Bug Description
When looking at an object IPAM in the contrail GUI it will always show the first IPAM policy in the list as the attached IPAM.
To other way around is correct:
When looking at the association of the IPAM object you will see that the correct network is attached.
See attached screenshots.
On the first one you can see that the network references IPAM A
In the second you can see IPAM A has no attached networks but IPAM does.
Revision history for this message
| Slobodan Blatnjak (sblatnjak) wrote | #1 |
Revision history for this message
| Slobodan Blatnjak (sblatnjak) wrote | #2 |
Revision history for this message
| Slobodan Blatnjak (sblatnjak) wrote | #3 |
| Changed in opencontrail: | |
| assignee: | nobody → Siva Bavanasi (kbsiva) |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote [Review update] R3.2 | #4 |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote A change has been merged | #6 |
Revision history for this message
| Siva Bavanasi (kbsiva) wrote | #7 |
| Changed in opencontrail: | |
| status: | New → Fix Committed |
| Changed in juniperopenstack: | |
| status: | New → Fix Committed |
To post a comment you must log in.
The issue is replicated with 3.2.1.0-29.
Please take a look at doc screenshots.
Any change in network (add policy) will cause setting the first IPAM object in the list.
1) Create 2 IPAMs bar & foo
2) Create network foonet with subnet in IPAM foo
3) Edit network policy for foonet network
4) Check IP Blocks in IPAM
Step 2 should show correct foonet ip block in IPAM foo. Step 4 should show foonet block in incorect IPAM (bar).
So network will switch to wrong IPAM, and as result of that different dns server will be used.