If user assign nodes to other nodegroup in env, these nodes became 'error'

[Anastasia Palkina]

1. Create new default environment
2. Add 1 controller (node-1), 1 compute (node-2), 2 cinder (node-3,4)
3. Create 'test' nodegroup in existing environment

[root@fuel ~]# fuel nodegroup --create --env 1 --name test
WARNING: In VLAN segmentation type, there will be no connectivity over private network between instances running on hypervisors in different segments and that it's a user's responsibility to handle this situation.
Node group 'test' with id=2 in environment 1 was created!
[root@fuel ~]#

4. Assign nodes to 'default' and 'test' nodegroups

[root@fuel ~]# fuel nodegroup --list
id | cluster | name
---|---------|--------
1 | 1 | default
2 | 1 | test
[root@fuel ~]# fuel nodegroup --assign --node 1 --group 1
[root@fuel ~]# fuel nodegroup --assign --node 2,3 --group 2

5. Node-2,3 became 'error' and notifications appear:
Node 'node-3' has IP '10.20.0.7' that does not match its own Admin network '9.9.9.0/24'
Node 'node-2' has IP '10.20.0.4' that does not match its own Admin network '9.9.9.0/24'

6. Assign nodes-2,3 to 'default' nodegroup
[root@fuel ~]# fuel nodegroup --assign --node 2,3 --group 1

Nodes became 'Pending Addition' again.

"release_versions": {"2015.1.0-8.0": {"VERSION": {"fuel-upgrade_sha": "1e894e26d4e1423a9b0d66abd6a79505f4175ff6", "fuel-createmirror_sha": "a034dcb06520df58a7338816900a431a6b61d83f", "shotgun_sha": "25dd78a3118267e3616df0727ce746e7dead2d67", "api": "1.0", "fuelmain_sha": "45b79c9121a08c2b467a3246dc1fa714e4c2043d", "astute_sha": "959b06c5ef8143125efd1727d350c050a922eb12", "fuel-ostf_sha": "9690a2de829d3b063ed1e64b0b10dde39f711dc0", "openstack_version": "2015.1.0-8.0", "build_id": "154", "fuelmenu_sha": "8a32c53c1fa13b036000f589f96e876277dbd071", "build_number": "154", "fuel-library_sha": "1e690ed95452297294c710a2f5886ef671d6b6da", "fuel-nailgun-agent_sha": "3e9d17211d65c80bf97c8d83979979f6c7feb687", "fuel-nailgun_sha": "37a535e11a7939e206ffababf3ecf12504cd91c4", "fuel-agent_sha": "07560a9fc3ce5301ace04d2d3e5d68db6ee4f8d5", "production": "docker", "network-checker_sha": "a57e1d69acb5e765eb22cab0251c589cd76f51da", "feature_groups": ["mirantis"], "release": "8.0", "python-fuelclient_sha": "e685d68c1c0d0fa0491a250f07d9c3a8d0f9608c"}}}, "fuel-upgrade_sha": "1e894e26d4e1423a9b0d66abd6a79505f4175ff6", "fuel-createmirror_sha": "a034dcb06520df58a7338816900a431a6b61d83f", "shotgun_sha": "25dd78a3118267e3616df0727ce746e7dead2d67", "api": "1.0", "fuelmain_sha": "45b79c9121a08c2b467a3246dc1fa714e4c2043d", "astute_sha": "959b06c5ef8143125efd1727d350c050a922eb12", "fuel-ostf_sha": "9690a2de829d3b063ed1e64b0b10dde39f711dc0", "openstack_version": "2015.1.0-8.0", "build_id": "154", "fuelmenu_sha": "8a32c53c1fa13b036000f589f96e876277dbd071", "build_number": "154", "auth_required": true, "fuel-library_sha": "1e690ed95452297294c710a2f5886ef671d6b6da", "fuel-nailgun-agent_sha": "3e9d17211d65c80bf97c8d83979979f6c7feb687", "fuel-nailgun_sha": "37a535e11a7939e206ffababf3ecf12504cd91c4", "fuel-agent_sha": "07560a9fc3ce5301ace04d2d3e5d68db6ee4f8d5", "production": "docker", "network-checker_sha": "a57e1d69acb5e765eb22cab0251c589cd76f51da", "feature_groups": ["mirantis"], "release": "8.0", "python-fuelclient_sha": "e685d68c1c0d0fa0491a250f07d9c3a8d0f9608c"

[Aleksandr Didenko (adidenko)]

This is expected behaviour:
https://github.com/openstack/fuel-specs/blob/master/specs/8.0/multi-rack-static.rst#notifications-impact

Fuel won't be able to provision such nodes, because they were bootstrapped on different PXE networks. This is why it marks such nodes as error. Closing this bug.