Activity log for bug #1543535

Date Who What changed Old value New value Message
2016-02-09 11:21:20 Timur Nurlygayanov bug added bug
2016-02-09 11:23:20 Timur Nurlygayanov description This issue reproduced not is 100% of cases, and it is probably regression issue. It is Critical because sometimes fuel can randomly change the mapping of ETH interfaces with logical networks and this will lead to fail of deployments / networks verification after the deployment. This issue was found by MOS QA automated test suite (Neutron destructive suite) Template which was used for deployment: https://github.com/Mirantis/mos-ci-deployment-scripts/blob/master/3_controllers_2compute_neutron_env_template.yaml Steps To Reproduce: 1. Run fuel master node and 3 slave nodes 2. Configure environment with 3 controllers, 3 computes, Neutron VxVLAN, L2pop and L3 HA features enabled 3. Check networks configuration and make sure that everything works fine 4. Deploy the environment 5. Start networks check one more time after the deployment Expected Result: Deployment will pass, network connectivity checks will pass as well Observed Result: Deployment passed (in my case, it depends on the interfaces which will be affected be the issue during the deployment, in fact, it can fail the deployment) Network verification fails with the error: AssertionError: Task 'check_networks' has incorrect status. error != ready, 'Some untagged networks are assigned to the same physical interface. You should assign them to different physical interfaces. Affected: "admin (PXE)", "storage" networks at node "slave-03_controller_cinder"' Diagnostic snapshot and screenshots are attached. This issue reproduced not is 100% of cases, and it is probably regression issue. It is Critical because sometimes fuel can randomly change the mapping of ETH interfaces with logical networks and this will lead to fail of deployments / networks verification after the deployment. This issue was found by MOS QA automated test suite (Neutron destructive suite) Template which was used for deployment: https://github.com/Mirantis/mos-ci-deployment-scripts/blob/master/3_controllers_2compute_neutron_env_template.yaml and https://github.com/Mirantis/mos-ci-deployment-scripts/blob/master/mos_tests.yaml Steps To Reproduce: 1. Run fuel master node and 3 slave nodes 2. Configure environment with 3 controllers, 3 computes, Neutron VxVLAN, L2pop and L3 HA features enabled 3. Check networks configuration and make sure that everything works fine 4. Deploy the environment 5. Start networks check one more time after the deployment Expected Result: Deployment will pass, network connectivity checks will pass as well Observed Result: Deployment passed (in my case, it depends on the interfaces which will be affected be the issue during the deployment, in fact, it can fail the deployment) Network verification fails with the error: AssertionError: Task 'check_networks' has incorrect status. error != ready, 'Some untagged networks are assigned to the same physical interface. You should assign them to different physical interfaces. Affected: "admin (PXE)", "storage" networks at node "slave-03_controller_cinder"' Diagnostic snapshot and screenshots are attached.
2016-02-09 11:32:06 Timur Nurlygayanov nominated for series fuel/8.0.x
2016-02-09 11:32:06 Timur Nurlygayanov bug task added fuel/8.0.x
2016-02-09 11:32:11 Timur Nurlygayanov fuel: milestone 9.0
2016-02-09 11:32:15 Timur Nurlygayanov fuel/8.0.x: milestone 8.0
2016-02-09 11:32:30 Timur Nurlygayanov fuel: importance Undecided Critical
2016-02-09 11:32:32 Timur Nurlygayanov fuel/8.0.x: importance Undecided Critical
2016-02-09 11:49:15 Timur Nurlygayanov attachment added fuel-snapshot-2016-02-09_11-36-23.tar.xz https://bugs.launchpad.net/fuel/+bug/1543535/+attachment/4567656/+files/fuel-snapshot-2016-02-09_11-36-23.tar.xz
2016-02-09 11:50:07 Timur Nurlygayanov fuel: assignee Dennis Dmitriev (ddmitriev)
2016-02-09 11:50:10 Timur Nurlygayanov fuel/8.0.x: assignee Dennis Dmitriev (ddmitriev)
2016-02-09 11:56:19 Timur Nurlygayanov description This issue reproduced not is 100% of cases, and it is probably regression issue. It is Critical because sometimes fuel can randomly change the mapping of ETH interfaces with logical networks and this will lead to fail of deployments / networks verification after the deployment. This issue was found by MOS QA automated test suite (Neutron destructive suite) Template which was used for deployment: https://github.com/Mirantis/mos-ci-deployment-scripts/blob/master/3_controllers_2compute_neutron_env_template.yaml and https://github.com/Mirantis/mos-ci-deployment-scripts/blob/master/mos_tests.yaml Steps To Reproduce: 1. Run fuel master node and 3 slave nodes 2. Configure environment with 3 controllers, 3 computes, Neutron VxVLAN, L2pop and L3 HA features enabled 3. Check networks configuration and make sure that everything works fine 4. Deploy the environment 5. Start networks check one more time after the deployment Expected Result: Deployment will pass, network connectivity checks will pass as well Observed Result: Deployment passed (in my case, it depends on the interfaces which will be affected be the issue during the deployment, in fact, it can fail the deployment) Network verification fails with the error: AssertionError: Task 'check_networks' has incorrect status. error != ready, 'Some untagged networks are assigned to the same physical interface. You should assign them to different physical interfaces. Affected: "admin (PXE)", "storage" networks at node "slave-03_controller_cinder"' Diagnostic snapshot and screenshots are attached. This issue reproduced not is 100% of cases, and it is probably regression issue. It is Critical because sometimes fuel can randomly change the mapping of ETH interfaces with logical networks and this will lead to fail of deployments / networks verification after the deployment. This issue was found by MOS QA automated test suite (Neutron destructive suite) Template which was used for deployment: https://github.com/Mirantis/mos-ci-deployment-scripts/blob/master/3_controllers_2compute_neutron_env_template.yaml and https://github.com/Mirantis/mos-ci-deployment-scripts/blob/master/mos_tests.yaml We used fuel-qa code from commit 87df82b0a7d204d2b43025f50ad232997bf0a35b (master branch) Steps To Reproduce: 1. Run fuel master node and 3 slave nodes 2. Configure environment with 3 controllers, 3 computes, Neutron VxVLAN, L2pop and L3 HA features enabled 3. Check networks configuration and make sure that everything works fine 4. Deploy the environment 5. Start networks check one more time after the deployment Expected Result: Deployment will pass, network connectivity checks will pass as well Observed Result: Deployment passed (in my case, it depends on the interfaces which will be affected be the issue during the deployment, in fact, it can fail the deployment) Network verification fails with the error: AssertionError: Task 'check_networks' has incorrect status. error != ready, 'Some untagged networks are assigned to the same physical interface. You should assign them to different physical interfaces. Affected: "admin (PXE)", "storage" networks at node "slave-03_controller_cinder"' Diagnostic snapshot and screenshots are attached.
2016-02-09 11:56:48 Timur Nurlygayanov tags area-library area-qa system-tests
2016-02-09 11:57:39 Timur Nurlygayanov attachment added Screenshot from 2016-02-09 14:24:17.png https://bugs.launchpad.net/fuel/+bug/1543535/+attachment/4567657/+files/Screenshot%20from%202016-02-09%2014%3A24%3A17.png
2016-02-09 12:03:01 Tatyanka fuel: status New Incomplete
2016-02-09 12:03:04 Tatyanka fuel/8.0.x: status New Incomplete
2016-02-09 12:03:07 Tatyanka fuel/8.0.x: importance Critical Undecided
2016-02-09 12:03:16 Tatyanka fuel: importance Critical Undecided
2016-02-09 12:03:56 Tatyanka fuel: assignee Dennis Dmitriev (ddmitriev) Timur Nurlygayanov (tnurlygayanov)
2016-02-09 12:04:19 Tatyanka fuel/8.0.x: assignee Dennis Dmitriev (ddmitriev) Timur Nurlygayanov (tnurlygayanov)
2016-02-09 12:29:47 Timur Nurlygayanov attachment added fuel-snapshot-2016-02-09_11-36-23.tar.xz https://bugs.launchpad.net/fuel/+bug/1543535/+attachment/4567664/+files/fuel-snapshot-2016-02-09_11-36-23.tar.xz
2016-02-09 12:32:42 Tatyanka marked as duplicate 1532823
2016-02-09 12:38:20 Dennis Dmitriev removed duplicate marker 1532823
2016-02-09 12:39:44 Dennis Dmitriev fuel/8.0.x: status Incomplete Confirmed
2016-02-09 12:39:49 Dennis Dmitriev fuel/8.0.x: importance Undecided Medium
2016-02-09 12:42:34 Dennis Dmitriev tags area-library area-qa system-tests area-python
2016-02-09 12:42:43 Dennis Dmitriev fuel/8.0.x: assignee Timur Nurlygayanov (tnurlygayanov) Fuel Python Team (fuel-python)
2016-02-09 12:45:33 Timur Nurlygayanov fuel: status Incomplete Confirmed
2016-02-09 12:45:43 Tatyanka marked as duplicate 1532823
2016-02-11 13:47:17 Timur Nurlygayanov attachment added docker-logs.tar.gz https://bugs.launchpad.net/fuel/+bug/1543535/+attachment/4569257/+files/docker-logs.tar.gz