CLI command "fuel network upload" not functional

Bug #1416613 reported by Pavel Vaylov on 2015-01-31
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
High
Fuel Python (Deprecated)

Bug Description

I've created an environment but want to change some network settings:

- Change range for management network (reduce range) because configure CIDR only it not enough.
- Change management VIP.

To do it:

1. Download network settings:

fuel --env 1 network --download

2. Make changes in /root/network_1.yaml :

For example:
- cidr: 10.20.28.0/22
  gateway: null
  group_id: 1
  id: 44
  ip_ranges:
  - - 10.20.24.2
    - 10.20.27.254

Change to:

  - - 10.20.24.10
    - 10.20.27.254

3. Upload settings back with debug option to ensure that everything went fine.

fuel --env 1 network upload --debug

4. Check result by downloading settings one more time and inspecting Nailgun's database:

fuel --env 1 network --download

Expected result:

New file as well as database will contain new network settings.

Actual result:

Settings still the same

  - - 10.20.24.2
    - 10.20.27.254

Workaround:

Carefully make changes into Nailgun's database before adding nodes to the environment.

  nailgun=# SELECT * FROM ip_addr_ranges;
 id | network_group_id | first | last
----+------------------+--------------+--------------
  1 | 1 | 10.20.16.200 | 10.20.19.254
 40 | 2 | 10.20.20.128 | 10.20.20.250
 42 | 3 | 10.20.24.2 | 10.20.27.254
 44 | 4 | 10.20.28.2 | 10.20.31.254

UPDATE ip_addr_ranges SET first = '10.20.24.10' WHERE id = '42';
UPDATE ip_addr_ranges SET first = '10.20.28.10' WHERE id = '44';

Related blueprint https://blueprints.launchpad.net/fuel/+spec/smart-ip-assigning

Changed in fuel:
assignee: nobody → Fuel Python Team (fuel-python)
milestone: none → 6.1
importance: Undecided → High
Pavel Vaylov (pvaylov) wrote :

Actually this bug report duplicates that one https://bugs.launchpad.net/fuel/+bug/1365368

Aleksey Kasatkin (alekseyk-ru) wrote :

All these three have the same root cause but different simptoms. VIP setting is slightly different story. It was not mentioned before and was not in scope of advanced-networking. Possible workarounds are the same though. I'll add it there or into some another ticket.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers