Network verification failed with expected vlan 9959969979989991000

[Sergey Galkin]

api: '1.0'
astute_sha: 3f1ece0318e5e93eaf48802fefabf512ca1dce40
auth_required: true
build_id: 2015-03-26_21-32-43
build_number: '233'
feature_groups:
- mirantis
fuellib_sha: 9c7716bc2ce6075065d7d9dcf96f4c94662c0b56
fuelmain_sha: 320b5f46fc1b2798f9e86ed7df51d3bda1686c10
nailgun_sha: b163f6fc77d6639aaffd9dd992e1ad96951c3bbf
ostf_sha: a4cf5f218c6aea98105b10c97a4aed8115c15867
production: docker
python-fuelclient_sha: e5e8389d8d481561a4d7107a99daae07c6ec5177
release: '6.1'

Steps to reproduce:
1. Deploy cluster with vlan on CentoOS on 50 HW servers
2. After deploy run Network verification

Verification failed with strange vlans number
On example

Node Name Node MAC address Node Interface Expected VLAN (not received)
compute_31 00:25:90:e3:36:d2 eth0 untagged
compute_31 0c:c4:7a:1d:93:fe eth2 9959969979989991000

Screenshot attached

[Aleksey Kasatkin (alekseyk-ru)]

Please provide diagnostic snapshot.

[Sergey Galkin (sgalkin)]

Another deployment but the same issue. build_number: is '233' also

[Sergey Galkin (sgalkin)]

snapshot - http://mos-scale-share.mirantis.com/fuel-snapshot-2015-04-07_17-18-34.tar.xz

[Andriy Popovych (popovych-andrey)]

"Strange" VLAN numbers have been fixed in https://github.com/stackforge/fuel-web/commit/781d4af60d7da25256c93dd033ddf9b9a915f20c