Activity log for bug #1518979

Date Who What changed Old value New value Message
2015-11-23 13:39:03 Atsuko Ito bug added bug
2015-11-23 14:19:04 Atsuko Ito fuel: assignee Fuel QA Team (fuel-qa)
2015-11-24 11:56:56 Maciej Relewicz fuel: importance Undecided Medium
2015-11-25 08:38:51 Maciej Relewicz tags feature area-qa feature
2015-11-27 13:06:46 Maciej Relewicz fuel: status New Confirmed
2015-12-30 10:31:30 Tatyanka nominated for series fuel/future
2015-12-30 10:31:30 Tatyanka bug task added fuel/future
2015-12-30 10:31:39 Tatyanka fuel/future: milestone 9.0
2015-12-30 10:31:44 Tatyanka fuel/future: importance Undecided High
2015-12-30 10:31:46 Tatyanka fuel/future: status New Confirmed
2015-12-30 10:31:49 Tatyanka fuel: status Confirmed Won't Fix
2015-12-30 10:36:02 Tatyanka fuel/future: assignee Fuel QA Team (fuel-qa)
2015-12-30 10:53:26 Atsuko Ito description We have to test all cases that Fuel 7.0 and 8.0 is supported now, otherwise we could easily broke down existing capabilities like this bug https://bugs.launchpad.net/mos/+bug/1515607. Documentation should cover next topics: # Requirements, planning and deploying steps to setup OpenStack with Fuel with provider networks # Managing IPv6 subnets, including addressing types comparsion and cases # Setting up virtual routers and corresponding changes on end user’s infrastructure I've already started to write it https://docs.google.com/a/mirantis.com/document/d/1W6KwaxkxnuLmJBmpOPi4R6eQ9degrMCguDyPlVodTfU/edit?usp=sharing Cases we have to test: # IPv6 Security Groups Rules is working # SLAAC and DHCPv6 Stateful addressing modes is working and instances are receiving their addresses # DHCPv6 advertises IPv6 name server correctly # Virtual routers is working between two networks, and instances are receiving default routes and reaching each other We have to test all cases that Fuel 7.0 and 8.0 is supported now, otherwise we could easily broke down existing capabilities like this bug https://bugs.launchpad.net/mos/+bug/1515607. Cases we have to test with Fuel: #. IPv6 Security Groups Rules is working, because Tempest is verifying only IPv4 ones (I'll re-verify it). #. DHCPv6 Stateful addressing modes is working and instances are receiving their addresses. #. Virtual routers is working between two networks, and instances are receiving default routes and reaching each other.
2015-12-30 10:55:52 Atsuko Ito fuel: importance Medium High
2015-12-30 10:55:57 Atsuko Ito fuel: status Won't Fix In Progress
2015-12-30 10:58:28 Tatyanka fuel: status In Progress Confirmed
2015-12-30 10:58:31 Tatyanka fuel/future: status Confirmed In Progress
2015-12-30 11:57:56 Atsuko Ito summary Existing IPv6 features in product should be covered with tests and documentation Check that IPv6 addressing and routing is working in Fuel 8.0
2015-12-30 13:25:03 Atsuko Ito description We have to test all cases that Fuel 7.0 and 8.0 is supported now, otherwise we could easily broke down existing capabilities like this bug https://bugs.launchpad.net/mos/+bug/1515607. Cases we have to test with Fuel: #. IPv6 Security Groups Rules is working, because Tempest is verifying only IPv4 ones (I'll re-verify it). #. DHCPv6 Stateful addressing modes is working and instances are receiving their addresses. #. Virtual routers is working between two networks, and instances are receiving default routes and reaching each other. Almost all functionality is already tested with Tempest on Neutron gates, and then Fuel ISO is re-tested with Tempest again. There should be a test that validates next IPv6 functionality: 1. IPv6 addressing is working and instances are receiving their addresses. 2. IPv6 Security Groups Rules is working. 3. Virtual routers is working between two networks, and instances are receiving default routes and reaching each other. Test plan to check it: 1. Get a public network from user. 2. Create two dualstack network, IPv6 subnets should be in SLAAC mode, address space should not intersect. 3. Create virtual router and set gateway. 4. Attach this subnets to the router. 5. Lease a floating IP. 6. Create a Security Group, that allows SSH and ICMP for both IPv4 and IPv6. 6. Launch two instances, one for eeah network. 7. Attach Floating IP for one instance — main instance. 8. SSH to the main instance and ping6 another instance. Expected result: IPv6 addresses will be assigned to both of instances. Virtual router will forward IPv6 traffic. Security Groups will allow IPv6 traffic to pass.
2015-12-30 13:25:24 Atsuko Ito description Almost all functionality is already tested with Tempest on Neutron gates, and then Fuel ISO is re-tested with Tempest again. There should be a test that validates next IPv6 functionality: 1. IPv6 addressing is working and instances are receiving their addresses. 2. IPv6 Security Groups Rules is working. 3. Virtual routers is working between two networks, and instances are receiving default routes and reaching each other. Test plan to check it: 1. Get a public network from user. 2. Create two dualstack network, IPv6 subnets should be in SLAAC mode, address space should not intersect. 3. Create virtual router and set gateway. 4. Attach this subnets to the router. 5. Lease a floating IP. 6. Create a Security Group, that allows SSH and ICMP for both IPv4 and IPv6. 6. Launch two instances, one for eeah network. 7. Attach Floating IP for one instance — main instance. 8. SSH to the main instance and ping6 another instance. Expected result: IPv6 addresses will be assigned to both of instances. Virtual router will forward IPv6 traffic. Security Groups will allow IPv6 traffic to pass. Almost all functionality is already tested with Tempest on Neutron gates, and then Fuel ISO is re-tested with Tempest again. There should be a test that validates next IPv6 functionality: 1. IPv6 addressing is working and instances are receiving their addresses. 2. IPv6 Security Groups Rules is working. 3. Virtual routers is working between two networks, and instances are receiving default routes and reaching each other. Test plan to check it: 1. Get a public network from user. 2. Create two dualstack network, IPv6 subnets should be in SLAAC mode, address space should not intersect. 3. Create virtual router and set gateway. 4. Attach this subnets to the router. 5. Lease a floating IP. 6. Create a Security Group, that allows SSH and ICMP for both IPv4 and IPv6. 7. Launch two instances, one for eeah network. 8. Attach Floating IP for one instance — main instance. 9. SSH to the main instance and ping6 another instance. Expected result: IPv6 addresses will be assigned to both of instances. Virtual router will forward IPv6 traffic. Security Groups will allow IPv6 traffic to pass.
2015-12-30 13:47:50 Fuel Devops McRobotson bug task deleted fuel/future
2015-12-30 13:47:52 Fuel Devops McRobotson fuel: status Confirmed New
2015-12-30 13:47:52 Fuel Devops McRobotson fuel: milestone 8.0 9.0
2015-12-30 13:47:55 Fuel Devops McRobotson fuel/8.0.x: importance Undecided High
2015-12-30 13:47:55 Fuel Devops McRobotson fuel/8.0.x: status New Confirmed
2015-12-30 13:47:55 Fuel Devops McRobotson fuel/8.0.x: milestone 8.0
2015-12-30 13:47:55 Fuel Devops McRobotson fuel/8.0.x: assignee Fuel QA Team (fuel-qa)
2015-12-30 13:47:58 Fuel Devops McRobotson fuel/future: milestone next
2015-12-30 13:47:58 Fuel Devops McRobotson fuel/future: assignee Fuel QA Team (fuel-qa)
2015-12-31 10:16:19 Szymon Banka fuel/future: status New Invalid
2015-12-31 10:16:21 Szymon Banka fuel/future: importance Undecided High
2015-12-31 11:46:50 Aleksey Zvyagintsev fuel: status New Confirmed
2016-01-14 11:53:45 OpenStack Infra fuel: status Confirmed In Progress
2016-01-14 11:53:45 OpenStack Infra fuel: assignee Fuel QA Team (fuel-qa) Alexey Stepanov (astepanov-m)
2016-01-16 10:31:04 OpenStack Infra fuel: status In Progress Fix Committed
2016-01-18 12:43:10 Nastya Urlapova fuel/8.0.x: assignee Fuel QA Team (fuel-qa) Alexey Stepanov (astepanov-m)
2016-01-18 12:43:16 Nastya Urlapova bug task deleted fuel/future
2016-01-18 12:43:23 Nastya Urlapova fuel/8.0.x: status Confirmed In Progress
2016-01-18 16:14:27 Aleksei Stepanov fuel/8.0.x: status In Progress Fix Committed
2016-02-03 12:38:58 Tatyanka fuel/8.0.x: status Fix Committed Fix Released
2016-02-03 12:39:00 Tatyanka fuel: status Fix Committed Fix Released