Cli.Network configuration does not appropriate to content of uploded json

Bug #1326370 reported by Egor Kotko on 2014-06-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fuel Python (Deprecated)

Bug Description

{"build_id": "2014-06-04_09-16-08", "mirantis": "yes", "build_number": "341", "nailgun_sha": "a828d6b7610f872980d5a2113774f1cda6f6810b", "ostf_sha": "c959aa55f83fe2555cf2d382559271c7a9b17467", "fuelmain_sha": "7ed0f85acc0bab4b9157703a618b8cc9fd7de3e1", "astute_sha": "55df06b2e84fa5d71a1cc0e78dbccab5db29d968", "release": "4.1B", "fuellib_sha": "0e96fc5a340cd57f75c454ea8536471379299494"}

Steps to reproduce:
1. Setup master node
2. Configure environment via UI - Centos, multinode, Neutron Vlan, 1 Controller, 1 Compute, configure interfaces on all nodes like on screenshot "Before".
3. Via cli save configuration of environment:
-fuel net --download --json --env 1;
-fuel deployment --default --json --env 1;
-fuel --env-id 1 settings --download --json
4. Deploy one more master, copy previously saved jsons and use its for creation of environment:
-fuel env create --name=test --mode=multinode --network-mode neutron --net-segment-type vlan --rel=1
-fuel node -s --env 1 --node-id=1 --role=controller
-fuel node -s --env 1 --node-id=2 --role=compute
-fuel net --upload --dir /dir/with_jsons/ --json --env 1;
-fuel deployment --upload --dir /dir/with_jsons/ --json --env 1;
-fuel --env-id 1 settings --upload --dir /dir/with_jsons/ --json;
-fuel deploy-changes --env 1

Expected result:
Networks should be assigned in the same way on the same interfaces
Actual result:
Private Storage and management networks are assigned on the inappropriate interface (see screenshot "After")

Tags: cli Edit Tag help
Egor Kotko (ykotko) wrote :
Egor Kotko (ykotko) wrote :
Egor Kotko (ykotko) wrote :
Changed in fuel:
importance: Low → Medium
assignee: nobody → Fuel Python Team (fuel-python)
Changed in fuel:
milestone: 4.1.1 → 4.1.2
Dima Shulyak (dshulyak) wrote :

I dont see any configuration in this jsons that maps networks to nodes interfaces,
is this expected behaviour ?

seems like you need additional steps:
fuel node --node-id 2 --network --download --dir path/to/directory
and then for new node id
fuel node --node-id 3 --disk --upload --dir path/to/directory

Changed in fuel:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers