| 2017-02-27 21:35:40 |
Ann Taraday |
bug |
|
|
added bug |
| 2017-02-28 22:06:47 |
OpenStack Infra |
neutron: status |
New |
In Progress |
|
| 2017-03-01 06:08:05 |
Anindita Das |
neutron: importance |
Undecided |
Medium |
|
| 2017-03-01 21:13:52 |
Ann Taraday |
attachment added |
|
neutron logs https://bugs.launchpad.net/neutron/+bug/1668410/+attachment/4829315/+files/neutron_l3ha_logs.tar |
|
| 2017-03-04 02:09:36 |
OpenStack Infra |
tags |
l3-ha mitaka-backport-potential |
in-stable-mitaka l3-ha mitaka-backport-potential |
|
| 2017-06-02 12:59:24 |
Denis Gubanov |
bug |
|
|
added subscriber Denis Gubanov |
| 2017-08-04 13:58:11 |
Basel Darvish |
information type |
Public |
Public Security |
|
| 2017-08-04 13:58:37 |
Basel Darvish |
bug |
|
|
added subscriber Basel Darvish |
| 2017-08-04 14:07:45 |
foboss |
bug |
|
|
added subscriber foboss |
| 2017-08-04 15:09:07 |
Jeremy Stanley |
bug task added |
|
ossa |
|
| 2017-08-04 15:09:50 |
Jeremy Stanley |
ossa: status |
New |
Incomplete |
|
| 2017-08-04 15:35:12 |
Jeremy Stanley |
ossa: status |
Incomplete |
Won't Fix |
|
| 2017-08-04 15:35:20 |
Jeremy Stanley |
information type |
Public Security |
Public |
|
| 2017-08-04 15:35:34 |
Jeremy Stanley |
tags |
in-stable-mitaka l3-ha mitaka-backport-potential |
in-stable-mitaka l3-ha mitaka-backport-potential security |
|
| 2017-08-04 15:55:13 |
Denis Gubanov |
bug task added |
|
neutron (Ubuntu) |
|
| 2017-08-11 14:36:30 |
Corey Bryant |
neutron (Ubuntu): status |
New |
Triaged |
|
| 2017-08-11 14:36:33 |
Corey Bryant |
neutron (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-08-30 02:50:46 |
Hua Zhang |
description |
Latest Mitaka code, L3 HA
After running rally create_and_delete_routers (concurrency 100 and times 100, or more) neutron l3 agent logs on nodes filled (every .003 second timestamp) with such traces:
http://paste.openstack.org/show/599851/
which causes cluster fall when log partition will filled up. |
[Impact]
When deleting a router the logfile is filled up. See full log - http://paste.ubuntu.com/25429257/
I can see the error 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' occured 3343386 times from _safe_router_removed() [1]:
$ grep -r 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' |wc -l
3343386
This _safe_router_removed() is invoked by L488 [2], if _safe_router_removed() goes wrong it will return False, then self._resync_router(update) [3] will make the code _safe_router_removed be run again and again. So we saw so many errors 'Error while deleting router XXXXX'.
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L361
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488
[3] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L457
[Test Case]
That's because race condition between neutron server and L3 agent, after neutron server deletes HA interfaces the L3 agent may sync a HA router without HA interface info (just need to trigger L708[1] after deleting HA interfaces and before deleting HA router). If we delete HA router at this time, this problem will happen. So test case we design is as below:
1, Create ha_router
neutron router-create harouter --ha=True
2, Delete ports associated with ha_router before deleting ha_router
neutron router-port-list harouter |grep 'HA port' |awk '{print $2}' |xargs -l neutron port-delete
neutron router-port-list harouter
3, Update ha_router to trigger l3-agent to update ha_router info without ha_port into self.router_info
neutron router-update harouter --description=test
4, Delete ha_router this time
neutron router-delete harouter
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/db/l3_hamode_db.py#L708
[Regression Potential]
The fixed patch [1] will no longer return ha_router which is missing ha_ports, so L488 will no longer have chance to call _safe_router_removed() for a ha_router, so the problem has been fundamentally fixed by this patch and no regression potential.
Besides, this fixed patch has been in mitaka-eol branch now, and neutron-server mitaka package is based on neutron-8.4.0, so we need to backport it to xenial and mitaka.
$ git tag --contains 8c77ee6b20dd38cc0246e854711cb91cffe3a069
mitaka-eol
[1] https://review.openstack.org/#/c/440799/2/neutron/db/l3_hamode_db.py
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488 |
|
| 2017-08-30 02:51:07 |
Hua Zhang |
summary |
Infinite loop trying to delete deleted HA router |
[SRU] Infinite loop trying to delete deleted HA router |
|
| 2017-08-30 02:54:50 |
Hua Zhang |
description |
[Impact]
When deleting a router the logfile is filled up. See full log - http://paste.ubuntu.com/25429257/
I can see the error 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' occured 3343386 times from _safe_router_removed() [1]:
$ grep -r 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' |wc -l
3343386
This _safe_router_removed() is invoked by L488 [2], if _safe_router_removed() goes wrong it will return False, then self._resync_router(update) [3] will make the code _safe_router_removed be run again and again. So we saw so many errors 'Error while deleting router XXXXX'.
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L361
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488
[3] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L457
[Test Case]
That's because race condition between neutron server and L3 agent, after neutron server deletes HA interfaces the L3 agent may sync a HA router without HA interface info (just need to trigger L708[1] after deleting HA interfaces and before deleting HA router). If we delete HA router at this time, this problem will happen. So test case we design is as below:
1, Create ha_router
neutron router-create harouter --ha=True
2, Delete ports associated with ha_router before deleting ha_router
neutron router-port-list harouter |grep 'HA port' |awk '{print $2}' |xargs -l neutron port-delete
neutron router-port-list harouter
3, Update ha_router to trigger l3-agent to update ha_router info without ha_port into self.router_info
neutron router-update harouter --description=test
4, Delete ha_router this time
neutron router-delete harouter
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/db/l3_hamode_db.py#L708
[Regression Potential]
The fixed patch [1] will no longer return ha_router which is missing ha_ports, so L488 will no longer have chance to call _safe_router_removed() for a ha_router, so the problem has been fundamentally fixed by this patch and no regression potential.
Besides, this fixed patch has been in mitaka-eol branch now, and neutron-server mitaka package is based on neutron-8.4.0, so we need to backport it to xenial and mitaka.
$ git tag --contains 8c77ee6b20dd38cc0246e854711cb91cffe3a069
mitaka-eol
[1] https://review.openstack.org/#/c/440799/2/neutron/db/l3_hamode_db.py
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488 |
[Impact]
When deleting a router the logfile is filled up. See full log - http://paste.ubuntu.com/25429257/
I can see the error 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' occured 3343386 times from _safe_router_removed() [1]:
$ grep -r 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' |wc -l
3343386
This _safe_router_removed() is invoked by L488 [2], if _safe_router_removed() goes wrong it will return False, then self._resync_router(update) [3] will make the code _safe_router_removed be run again and again. So we saw so many errors 'Error while deleting router XXXXX'.
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L361
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488
[3] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L457
[Test Case]
That's because race condition between neutron server and L3 agent, after neutron server deletes HA interfaces the L3 agent may sync a HA router without HA interface info (just need to trigger L708[1] after deleting HA interfaces and before deleting HA router). If we delete HA router at this time, this problem will happen. So test case we design is as below:
1, Create ha_router
neutron router-create harouter --ha=True
2, Delete ports associated with ha_router before deleting ha_router
neutron router-port-list harouter |grep 'HA port' |awk '{print $2}' |xargs -l neutron port-delete
neutron router-port-list harouter
3, Update ha_router to trigger l3-agent to update ha_router info without ha_port into self.router_info
neutron router-update harouter --description=test
4, Delete ha_router this time
neutron router-delete harouter
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/db/l3_hamode_db.py#L708
[Regression Potential]
The fixed patch [1] for neutron-server will no longer return ha_router which is missing ha_ports, so L488 will no longer have chance to call _safe_router_removed() for a ha_router, so the problem has been fundamentally fixed by this patch and no regression potential.
Besides, this fixed patch has been in mitaka-eol branch now, and neutron-server mitaka package is based on neutron-8.4.0, so we need to backport it to xenial and mitaka.
$ git tag --contains 8c77ee6b20dd38cc0246e854711cb91cffe3a069
mitaka-eol
[1] https://review.openstack.org/#/c/440799/2/neutron/db/l3_hamode_db.py
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488 |
|
| 2017-08-30 02:55:36 |
Hua Zhang |
tags |
in-stable-mitaka l3-ha mitaka-backport-potential security |
in-stable-mitaka l3-ha mitaka-backport-potential security sts sts-sru-needed |
|
| 2017-08-30 02:56:31 |
Hua Zhang |
attachment added |
|
mitaka.debdiff https://bugs.launchpad.net/neutron/+bug/1668410/+attachment/4941145/+files/mitaka.debdiff |
|
| 2017-08-30 03:12:43 |
Hua Zhang |
description |
[Impact]
When deleting a router the logfile is filled up. See full log - http://paste.ubuntu.com/25429257/
I can see the error 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' occured 3343386 times from _safe_router_removed() [1]:
$ grep -r 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' |wc -l
3343386
This _safe_router_removed() is invoked by L488 [2], if _safe_router_removed() goes wrong it will return False, then self._resync_router(update) [3] will make the code _safe_router_removed be run again and again. So we saw so many errors 'Error while deleting router XXXXX'.
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L361
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488
[3] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L457
[Test Case]
That's because race condition between neutron server and L3 agent, after neutron server deletes HA interfaces the L3 agent may sync a HA router without HA interface info (just need to trigger L708[1] after deleting HA interfaces and before deleting HA router). If we delete HA router at this time, this problem will happen. So test case we design is as below:
1, Create ha_router
neutron router-create harouter --ha=True
2, Delete ports associated with ha_router before deleting ha_router
neutron router-port-list harouter |grep 'HA port' |awk '{print $2}' |xargs -l neutron port-delete
neutron router-port-list harouter
3, Update ha_router to trigger l3-agent to update ha_router info without ha_port into self.router_info
neutron router-update harouter --description=test
4, Delete ha_router this time
neutron router-delete harouter
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/db/l3_hamode_db.py#L708
[Regression Potential]
The fixed patch [1] for neutron-server will no longer return ha_router which is missing ha_ports, so L488 will no longer have chance to call _safe_router_removed() for a ha_router, so the problem has been fundamentally fixed by this patch and no regression potential.
Besides, this fixed patch has been in mitaka-eol branch now, and neutron-server mitaka package is based on neutron-8.4.0, so we need to backport it to xenial and mitaka.
$ git tag --contains 8c77ee6b20dd38cc0246e854711cb91cffe3a069
mitaka-eol
[1] https://review.openstack.org/#/c/440799/2/neutron/db/l3_hamode_db.py
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488 |
[Impact]
When deleting a router the logfile is filled up. See full log - http://paste.ubuntu.com/25429257/
I can see the error 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' occured 3343386 times from _safe_router_removed() [1]:
$ grep -r 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' |wc -l
3343386
This _safe_router_removed() is invoked by L488 [2], if _safe_router_removed() goes wrong it will return False, then self._resync_router(update) [3] will make the code _safe_router_removed be run again and again. So we saw so many errors 'Error while deleting router XXXXX'.
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L361
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488
[3] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L457
[Test Case]
That's because race condition between neutron server and L3 agent, after neutron server deletes HA interfaces the L3 agent may sync a HA router without HA interface info (just need to trigger L708[1] after deleting HA interfaces and before deleting HA router). If we delete HA router at this time, this problem will happen. So test case we design is as below:
1, First update fixed package, and restart neutron-server by 'sudo service neutron-server restart'
2, Create ha_router
neutron router-create harouter --ha=True
3, Delete ports associated with ha_router before deleting ha_router
neutron router-port-list harouter |grep 'HA port' |awk '{print $2}' |xargs -l neutron port-delete
neutron router-port-list harouter
4, Update ha_router to trigger l3-agent to update ha_router info without ha_port into self.router_info
neutron router-update harouter --description=test
5, Delete ha_router this time
neutron router-delete harouter
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/db/l3_hamode_db.py#L708
[Regression Potential]
The fixed patch [1] for neutron-server will no longer return ha_router which is missing ha_ports, so L488 will no longer have chance to call _safe_router_removed() for a ha_router, so the problem has been fundamentally fixed by this patch and no regression potential.
Besides, this fixed patch has been in mitaka-eol branch now, and neutron-server mitaka package is based on neutron-8.4.0, so we need to backport it to xenial and mitaka.
$ git tag --contains 8c77ee6b20dd38cc0246e854711cb91cffe3a069
mitaka-eol
[1] https://review.openstack.org/#/c/440799/2/neutron/db/l3_hamode_db.py
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488 |
|
| 2017-08-30 04:20:00 |
Ubuntu Foundations Team Bug Bot |
tags |
in-stable-mitaka l3-ha mitaka-backport-potential security sts sts-sru-needed |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed |
|
| 2017-08-30 04:20:09 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2017-08-31 02:38:17 |
Billy Olsen |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-08-31 02:39:09 |
Billy Olsen |
bug task added |
|
cloud-archive |
|
| 2017-08-31 02:39:24 |
Billy Olsen |
nominated for series |
|
cloud-archive/mitaka |
|
| 2017-08-31 02:41:58 |
Hua Zhang |
tags |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sru-sponsors sts sts-sru-needed |
|
| 2017-08-31 03:14:51 |
Hua Zhang |
tags |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sru-sponsors sts sts-sru-needed |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed |
|
| 2017-08-31 06:21:45 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
| 2017-08-31 18:05:47 |
Corey Bryant |
bug task added |
|
cloud-archive/mitaka |
|
| 2017-08-31 18:05:59 |
Corey Bryant |
bug task added |
|
neutron (Ubuntu Xenial) |
|
| 2017-08-31 18:06:13 |
Corey Bryant |
cloud-archive/mitaka: status |
New |
Triaged |
|
| 2017-08-31 18:06:20 |
Corey Bryant |
neutron (Ubuntu Xenial): status |
New |
Triaged |
|
| 2017-08-31 18:06:23 |
Corey Bryant |
cloud-archive/mitaka: importance |
Undecided |
High |
|
| 2017-08-31 18:06:27 |
Corey Bryant |
neutron (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2017-08-31 18:06:41 |
Corey Bryant |
neutron (Ubuntu): status |
Triaged |
Invalid |
|
| 2017-08-31 18:06:52 |
Corey Bryant |
cloud-archive: status |
New |
Invalid |
|
| 2017-08-31 18:10:31 |
Corey Bryant |
description |
[Impact]
When deleting a router the logfile is filled up. See full log - http://paste.ubuntu.com/25429257/
I can see the error 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' occured 3343386 times from _safe_router_removed() [1]:
$ grep -r 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' |wc -l
3343386
This _safe_router_removed() is invoked by L488 [2], if _safe_router_removed() goes wrong it will return False, then self._resync_router(update) [3] will make the code _safe_router_removed be run again and again. So we saw so many errors 'Error while deleting router XXXXX'.
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L361
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488
[3] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L457
[Test Case]
That's because race condition between neutron server and L3 agent, after neutron server deletes HA interfaces the L3 agent may sync a HA router without HA interface info (just need to trigger L708[1] after deleting HA interfaces and before deleting HA router). If we delete HA router at this time, this problem will happen. So test case we design is as below:
1, First update fixed package, and restart neutron-server by 'sudo service neutron-server restart'
2, Create ha_router
neutron router-create harouter --ha=True
3, Delete ports associated with ha_router before deleting ha_router
neutron router-port-list harouter |grep 'HA port' |awk '{print $2}' |xargs -l neutron port-delete
neutron router-port-list harouter
4, Update ha_router to trigger l3-agent to update ha_router info without ha_port into self.router_info
neutron router-update harouter --description=test
5, Delete ha_router this time
neutron router-delete harouter
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/db/l3_hamode_db.py#L708
[Regression Potential]
The fixed patch [1] for neutron-server will no longer return ha_router which is missing ha_ports, so L488 will no longer have chance to call _safe_router_removed() for a ha_router, so the problem has been fundamentally fixed by this patch and no regression potential.
Besides, this fixed patch has been in mitaka-eol branch now, and neutron-server mitaka package is based on neutron-8.4.0, so we need to backport it to xenial and mitaka.
$ git tag --contains 8c77ee6b20dd38cc0246e854711cb91cffe3a069
mitaka-eol
[1] https://review.openstack.org/#/c/440799/2/neutron/db/l3_hamode_db.py
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488 |
[Descriptoin]
When deleting a router the logfile is filled up. See full log - http://paste.ubuntu.com/25429257/
I can see the error 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' occured 3343386 times from _safe_router_removed() [1]:
$ grep -r 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' |wc -l
3343386
This _safe_router_removed() is invoked by L488 [2], if _safe_router_removed() goes wrong it will return False, then self._resync_router(update) [3] will make the code _safe_router_removed be run again and again. So we saw so many errors 'Error while deleting router XXXXX'.
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L361
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488
[3] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L457
[Test Case]
That's because race condition between neutron server and L3 agent, after neutron server deletes HA interfaces the L3 agent may sync a HA router without HA interface info (just need to trigger L708[1] after deleting HA interfaces and before deleting HA router). If we delete HA router at this time, this problem will happen. So test case we design is as below:
1, First update fixed package, and restart neutron-server by 'sudo service neutron-server restart'
2, Create ha_router
neutron router-create harouter --ha=True
3, Delete ports associated with ha_router before deleting ha_router
neutron router-port-list harouter |grep 'HA port' |awk '{print $2}' |xargs -l neutron port-delete
neutron router-port-list harouter
4, Update ha_router to trigger l3-agent to update ha_router info without ha_port into self.router_info
neutron router-update harouter --description=test
5, Delete ha_router this time
neutron router-delete harouter
[1] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/db/l3_hamode_db.py#L708
[Regression Potential]
The fixed patch [1] for neutron-server will no longer return ha_router which is missing ha_ports, so L488 will no longer have chance to call _safe_router_removed() for a ha_router, so the problem has been fundamentally fixed by this patch and no regression potential.
Besides, this fixed patch has been in mitaka-eol branch now, and neutron-server mitaka package is based on neutron-8.4.0, so we need to backport it to xenial and mitaka.
$ git tag --contains 8c77ee6b20dd38cc0246e854711cb91cffe3a069
mitaka-eol
[1] https://review.openstack.org/#/c/440799/2/neutron/db/l3_hamode_db.py
[2] https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488 |
|
| 2017-09-06 09:43:53 |
Hua Zhang |
bug |
|
|
added subscriber Hua Zhang |
| 2017-09-07 20:26:08 |
Brian Murray |
neutron (Ubuntu Xenial): status |
Triaged |
Fix Committed |
|
| 2017-09-07 20:26:15 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-09-07 20:26:18 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2017-09-07 20:26:22 |
Brian Murray |
tags |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed verification-needed verification-needed-xenial |
|
| 2017-09-07 20:26:48 |
Brian Murray |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2017-09-12 11:10:28 |
Hua Zhang |
tags |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed verification-needed verification-needed-xenial |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed verification-done-xenial |
|
| 2017-09-12 11:12:16 |
Hua Zhang |
tags |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed verification-done-xenial |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed verification-done verification-done-xenial |
|
| 2017-09-18 15:22:08 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-09-18 15:32:12 |
Launchpad Janitor |
neutron (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-09-18 17:47:04 |
Ryan Beisner |
cloud-archive/mitaka: status |
Triaged |
Fix Committed |
|
| 2017-09-18 17:47:07 |
Ryan Beisner |
tags |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed verification-done verification-done-xenial |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed verification-done verification-done-xenial verification-mitaka-needed |
|
| 2017-09-19 13:53:56 |
Corey Bryant |
tags |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed verification-done verification-done-xenial verification-mitaka-needed |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed verification-done verification-done-xenial verification-mitaka-done |
|
| 2017-09-19 14:00:04 |
Ryan Beisner |
cloud-archive/mitaka: status |
Fix Committed |
Fix Released |
|
| 2017-10-02 14:44:42 |
Edward Hope-Morley |
tags |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-needed verification-done verification-done-xenial verification-mitaka-done |
in-stable-mitaka l3-ha mitaka-backport-potential patch security sts sts-sru-done verification-done verification-done-xenial verification-mitaka-done |
|
| 2020-02-07 19:10:22 |
Brian Haley |
neutron: status |
In Progress |
Fix Released |
|
