Fuel for OpenStack

[qa] Tests logs report that nova/flatdhcp is used for network configuration, but actually cluster with nova/vlan is deployed

Bug #1398071 reported by Dennis Dmitriev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Dennis Dmitriev
Fuel for OpenStack 6.0
5.1.x
Fix Released
Medium
Dennis Dmitriev
Fuel for OpenStack 5.1.1-updates
6.0.x
Fix Released
Medium
Dennis Dmitriev
Fuel for OpenStack 6.0
6.1.x
Fix Released
Medium
Dennis Dmitriev
Fuel for OpenStack 6.1

Bug Description

Affected tests:

deploy_simple_vlan()
deploy_reset_on_ready()
deploy_ha_vlan()
upgrade_ha_env()
create_delete_ip_n_times_nova_vlan()

Example: http://jenkins-product.srt.mirantis.net:8080/view/5.1_swarm/job/5.1_fuelmain.system_test.ubuntu.thread_2/63/ ,
test 'deploy_simple_vlan':
==================
2014-12-01 03:27:04,150 - INFO nailgun_client.py:258 -- cluster name is SimpleVlan
2014-12-01 03:27:04,150 - INFO nailgun_client.py:259 -- cluster id is 1
2014-12-01 03:27:04,150 - INFO fuel_web_client.py:338 -- The cluster id is 1
2014-12-01 03:27:04,150 - INFO fuel_web_client.py:340 -- Set cluster settings to {'password': 'novaSimpleVlan', 'user': 'novaSimpleVlan', 'tenant': 'novaSimpleVlan'}
2014-12-01 03:27:04,180 - INFO fuel_web_client.py:362 -- Set DEBUG MODE to True
2014-12-01 03:27:04,247 - INFO fuel_web_client.py:781 -- Update network settings of cluster 1
2014-12-01 03:27:04,336 - INFO fuel_web_client.py:798 -- Network settings for push: {u'networking_parameters': {u'dns_nameservers': [u'8.8.4.4', u'8.8.8.8'], u'net_manager': u'FlatDHCPManager',
...
==================

Looks like the method fuel_web_client/update_vlan_network_fixed() doesn't work properly.

Tags: system-tests
Dennis Dmitriev (ddmitriev)
no longer affects: fuel/6.1.x
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

This issue affects 6 systests, which we recheck in acceptance circle for release, move to 5.1.2. this might not cause of missed issues.

Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

as okosse find, test deployed correct configuration and error is in Logging that log not actual data.
I beleive we can just remove info logging in 798L , according we get the same data by @logwrap that are more actual.

Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

I propose not to remove this line but put into DEBUG log both original and updated network settings. Just for getting some additional checkpoints of network setting evolution.

Here is an example of updated settings after running appropriate patch: http://paste.openstack.org/show/152370/

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-main (master)

Fix proposed to branch: master
Review: https://review.openstack.org/142532

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-main (stable/6.0)

Fix proposed to branch: stable/6.0
Review: https://review.openstack.org/142535

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-main (stable/5.1)

Fix proposed to branch: stable/5.1
Review: https://review.openstack.org/142536

Artem Panchenko (apanchenko-8)
summary: - Tests that should use nova/vlan are actually deploying network using
- nova/flatdhcp
+ [qa] Tests logs report that nova/flatdhcp is used for network
+ configuration, but actually cluster with nova/vlan is deployed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-main (stable/6.0)

Reviewed: https://review.openstack.org/142535
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=aa24c52ae6cbe7db0d6b58be2288fd15867c796a
Submitter: Jenkins
Branch: stable/6.0

commit aa24c52ae6cbe7db0d6b58be2288fd15867c796a
Author: Dennis Dmitriev <email address hidden>
Date: Wed Dec 17 20:30:14 2014 +0200

    Remove network settings logging from 'info' channel

    When we create a cluster with nova-network then FlatDHCP selected
    by default. Latelly the network configuration can be updated but
    'info' log provides inaccurate information.

    This logging is redundant because all necessary information is
    logged with @logwrap

    Change-Id: Ieef687b815e18ff22c7660e41863e1596c352b91
    Closes-Bug: #1398071

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-main (master)

Reviewed: https://review.openstack.org/142532
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=4ee8cd0b9bbc0377850564e55d7f27a3c49e5e5f
Submitter: Jenkins
Branch: master

commit 4ee8cd0b9bbc0377850564e55d7f27a3c49e5e5f
Author: Dennis Dmitriev <email address hidden>
Date: Wed Dec 17 20:30:14 2014 +0200

    Remove network settings logging from 'info' channel

    When we create a cluster with nova-network then FlatDHCP selected
    by default. Latelly the network configuration can be updated but
    'info' log provides inaccurate information.

    This logging is redundant because all necessary information is
    logged with @logwrap

    Change-Id: Ieef687b815e18ff22c7660e41863e1596c352b91
    Closes-Bug: #1398071

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-main (stable/5.1)

Reviewed: https://review.openstack.org/142536
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=9fc9ddde4f042575d3069e88b8f3f41692d5872a
Submitter: Jenkins
Branch: stable/5.1

commit 9fc9ddde4f042575d3069e88b8f3f41692d5872a
Author: Dennis Dmitriev <email address hidden>
Date: Mon Dec 22 13:43:04 2014 +0200

    Remove network settings logging from 'info' channel

    When we create a cluster with nova-network then FlatDHCP selected
    by default. Latelly the network configuration can be updated but
    'info' log provides inaccurate information.

    This logging is redundant because all necessary information is
    logged with @logwrap

    Change-Id: Ib409176a4ebfb9e1ab18215ec8cfaf6a8d478e9e
    Closes-Bug: #1398071

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.