Admin ip-address does not change when yaml uploaded back to nailgun
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Invalid
|
Medium
|
Fuel Python (Deprecated) | ||
| 8.0.x |
Invalid
|
Medium
|
Fuel Python (Deprecated) | ||
Bug Description
MOS does not change admin ip-address when you upload the yaml config.
You should change table nailgun.ip_addr after yaml upload.
For example:
I had admin-ip 172.30.72.253
I have uploaded this:
{
admin_interface: eth2
network_data:
eth0:
interface: eth0
ipaddr: none
eth1:
interface: eth1
ipaddr: none
eth2:
interface: eth2
ipaddr:
- 172.30.72.47/25
eth2.2000:
interface: eth2.2000
ipaddr:
- 172.30.64.47/25
eth2.2002:
gateway: 172.30.80.1
interface: eth2.2002
ipaddr:
- 172.30.80.47/25
eth2.2004:
interface: eth2.2004
ipaddr:
- 172.30.96.47/25
eth3:
interface: eth3
ipaddr: none
lo:
interface: lo
ipaddr: 127.0.0.1/8
}
But when I install operating system ip-address still the same.
DNSmasq is not changed too, as leases as a cobbler.
| tags: | added: admin-ip-addr nailgun |
| Changed in fuel: | |
| milestone: | none → 6.0 |
| assignee: | nobody → Fuel Python Team (fuel-python) |
| Changed in fuel: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in fuel: | |
| milestone: | 6.0 → 6.1 |
| Changed in fuel: | |
| status: | Triaged → Confirmed |
| tags: | added: feature |
| Changed in fuel: | |
| milestone: | 6.1 → 7.0 |
| milestone: | 7.0 → next |
| tags: |
added: module-networks removed: admin-ip-addr nailgun |
| Changed in fuel: | |
| milestone: | next → 7.0 |
| Aleksey Kasatkin (alekseyk-ru) wrote | #1 |
| Changed in fuel: | |
| status: | Confirmed → Won't Fix |
| Sebastian Kalinowski (prmtl) wrote | #2 |
| tags: | added: area-python |
| Changed in fuel: | |
| milestone: | 7.0 → 8.0 |
It's a feature. Does not break deployment. Moving to 8.0.
AFAIC, other changes from example provided are not applied as well as API does not support such a flexibility. But this is partly solved with network templates where user can create subinterfaces flexibly. It does not solve the problem with Admin IPs though.
It's not clear from the description what API request or CLI command was executed. Please clarify.