| 2019-08-16 13:50:11 |
Tobias Urdin |
bug |
|
|
added bug |
| 2019-08-16 13:53:13 |
OpenStack Infra |
horizon: status |
New |
In Progress |
|
| 2019-08-16 13:53:13 |
OpenStack Infra |
horizon: assignee |
|
Tobias Urdin (tobias-urdin) |
|
| 2019-08-19 06:03:51 |
Akihiro Motoki |
tags |
|
neutron |
|
| 2019-08-19 06:03:57 |
Akihiro Motoki |
horizon: importance |
Undecided |
Medium |
|
| 2019-08-19 06:04:06 |
Akihiro Motoki |
tags |
neutron |
neutron stein-backport-potential |
|
| 2019-08-19 07:39:59 |
OpenStack Infra |
horizon: assignee |
Tobias Urdin (tobias-urdin) |
Akihiro Motoki (amotoki) |
|
| 2019-08-19 18:14:57 |
OpenStack Infra |
horizon: status |
In Progress |
Fix Released |
|
| 2019-08-19 20:40:21 |
Tobias Urdin |
tags |
neutron stein-backport-potential |
neutron rocky-backport-potential stein-backport-potential |
|
| 2019-08-23 08:52:19 |
OpenStack Infra |
tags |
neutron rocky-backport-potential stein-backport-potential |
in-stable-stein neutron rocky-backport-potential stein-backport-potential |
|
| 2019-09-26 15:00:13 |
OpenStack Infra |
tags |
in-stable-stein neutron rocky-backport-potential stein-backport-potential |
in-stable-rocky in-stable-stein neutron rocky-backport-potential stein-backport-potential |
|
| 2019-10-03 20:10:00 |
Edward Hope-Morley |
bug task added |
|
horizon (Ubuntu) |
|
| 2019-10-03 20:10:22 |
Edward Hope-Morley |
nominated for series |
|
Ubuntu Disco |
|
| 2019-10-03 20:10:22 |
Edward Hope-Morley |
bug task added |
|
horizon (Ubuntu Disco) |
|
| 2019-10-03 20:10:22 |
Edward Hope-Morley |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-10-03 20:10:22 |
Edward Hope-Morley |
bug task added |
|
horizon (Ubuntu Bionic) |
|
| 2019-10-03 20:19:54 |
Edward Hope-Morley |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-10-03 20:19:54 |
Edward Hope-Morley |
bug task added |
|
horizon (Ubuntu Eoan) |
|
| 2019-10-09 16:20:53 |
OpenStack Infra |
tags |
in-stable-rocky in-stable-stein neutron rocky-backport-potential stein-backport-potential |
in-stable-queens in-stable-rocky in-stable-stein neutron rocky-backport-potential stein-backport-potential |
|
| 2019-10-19 18:59:46 |
Rodrigo Barbieri |
summary |
Fails to list security groups if one or more exists without rules |
[SRU] Fails to list security groups if one or more exists without rules |
|
| 2019-10-19 19:33:11 |
Rodrigo Barbieri |
description |
Horizon 14.0.2 (rocky)
If a security group without any rules exists the listing of security groups fails with a KeyError.
Traceback (most recent call last):
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/utils.py", line 127, in _wrapped
data = function(self, request, *args, **kw)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/network.py", line 44, in get
security_groups = api.neutron.security_group_list(request)
File "/usr/lib/python2.7/site-packages/horizon/utils/memoized.py", line 95, in wrapped
value = cache[key] = func(*args, **kwargs)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 1641, in security_group_list
return SecurityGroupManager(request).list(**params)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 372, in list
return self._list(**params)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 359, in _list
return [SecurityGroup(sg) for sg in secgroups.get('security_groups')]
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 240, in __init__
for rule in sg['security_group_rules']]
KeyError: 'security_group_rules' |
Horizon 14.0.2 (rocky)
If a security group without any rules exists the listing of security groups fails with a KeyError.
Traceback (most recent call last):
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/utils.py", line 127, in _wrapped
data = function(self, request, *args, **kw)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/network.py", line 44, in get
security_groups = api.neutron.security_group_list(request)
File "/usr/lib/python2.7/site-packages/horizon/utils/memoized.py", line 95, in wrapped
value = cache[key] = func(*args, **kwargs)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 1641, in security_group_list
return SecurityGroupManager(request).list(**params)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 372, in list
return self._list(**params)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 359, in _list
return [SecurityGroup(sg) for sg in secgroups.get('security_groups')]
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 240, in __init__
for rule in sg['security_group_rules']]
KeyError: 'security_group_rules'
=======================================================================
[Impact]
By default, new security groups created through horizon or CLI include 2 default security rules. Upon managing those rules and removing them (to perhaps add others or limit traffic completely), the security group page errors out and prevents listing of *all* security groups if the empty security group is within the list to be displayed. Therefore, not only is the empty security group affected, but all others as well, as they cannot be listed. The root cause of the bug is that the payload does not include the expected key "security_group_rules" for that security group when there are no rules.
A fix has been implemented for Train (from master), Stein, Rocky and Queens releases and should be backported so the issue is addressed on previous those releases. The fix prevents the crash by ensuring the key "security_group_rules" is present with an empty list in case it was not included in the payload.
[Test Case]
1. Reproducing the issue
1a. Go to the Security Group section at Project > Network > Security Groups
1b. Create a security group
1c. Click the Manage Rules button for that security group you just created
1d. Delete the two default rules
1e. Go back to the Security Group section at Project > Network > Security Groups
1f. Security groups are no longer being listed and there will be an error popup: "Error: Unable to retrieve security groups.".
2. Install the package with the fixed code
3. Confirm bug has been fixed
3a. Repeat step 1a, you will notice that now security groups can be listed, including the empty one you had previously created
3b. Repeat steps 1b through 1e, the newly created and emptied security group can also be listed along the others.
[Regression Potential]
Given the following indicators:
a. Upstream CI passed, for all releases the fix is being backported.
b. The small scope of the problem: a key error prevents the page from being rendered. The fix is to make sure the key is always present, since it is always expected.
c. The fix is very simple, and during tests we can see that the other pages handle an empty list properly as the value for the "security_group_rules".
We can safely say there the regression potential is negligible. |
|
| 2019-10-19 19:33:42 |
Rodrigo Barbieri |
description |
Horizon 14.0.2 (rocky)
If a security group without any rules exists the listing of security groups fails with a KeyError.
Traceback (most recent call last):
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/utils.py", line 127, in _wrapped
data = function(self, request, *args, **kw)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/network.py", line 44, in get
security_groups = api.neutron.security_group_list(request)
File "/usr/lib/python2.7/site-packages/horizon/utils/memoized.py", line 95, in wrapped
value = cache[key] = func(*args, **kwargs)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 1641, in security_group_list
return SecurityGroupManager(request).list(**params)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 372, in list
return self._list(**params)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 359, in _list
return [SecurityGroup(sg) for sg in secgroups.get('security_groups')]
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 240, in __init__
for rule in sg['security_group_rules']]
KeyError: 'security_group_rules'
=======================================================================
[Impact]
By default, new security groups created through horizon or CLI include 2 default security rules. Upon managing those rules and removing them (to perhaps add others or limit traffic completely), the security group page errors out and prevents listing of *all* security groups if the empty security group is within the list to be displayed. Therefore, not only is the empty security group affected, but all others as well, as they cannot be listed. The root cause of the bug is that the payload does not include the expected key "security_group_rules" for that security group when there are no rules.
A fix has been implemented for Train (from master), Stein, Rocky and Queens releases and should be backported so the issue is addressed on previous those releases. The fix prevents the crash by ensuring the key "security_group_rules" is present with an empty list in case it was not included in the payload.
[Test Case]
1. Reproducing the issue
1a. Go to the Security Group section at Project > Network > Security Groups
1b. Create a security group
1c. Click the Manage Rules button for that security group you just created
1d. Delete the two default rules
1e. Go back to the Security Group section at Project > Network > Security Groups
1f. Security groups are no longer being listed and there will be an error popup: "Error: Unable to retrieve security groups.".
2. Install the package with the fixed code
3. Confirm bug has been fixed
3a. Repeat step 1a, you will notice that now security groups can be listed, including the empty one you had previously created
3b. Repeat steps 1b through 1e, the newly created and emptied security group can also be listed along the others.
[Regression Potential]
Given the following indicators:
a. Upstream CI passed, for all releases the fix is being backported.
b. The small scope of the problem: a key error prevents the page from being rendered. The fix is to make sure the key is always present, since it is always expected.
c. The fix is very simple, and during tests we can see that the other pages handle an empty list properly as the value for the "security_group_rules".
We can safely say there the regression potential is negligible. |
Horizon 14.0.2 (rocky)
If a security group without any rules exists the listing of security groups fails with a KeyError.
Traceback (most recent call last):
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/utils.py", line 127, in _wrapped
data = function(self, request, *args, **kw)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/network.py", line 44, in get
security_groups = api.neutron.security_group_list(request)
File "/usr/lib/python2.7/site-packages/horizon/utils/memoized.py", line 95, in wrapped
value = cache[key] = func(*args, **kwargs)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 1641, in security_group_list
return SecurityGroupManager(request).list(**params)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 372, in list
return self._list(**params)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 359, in _list
return [SecurityGroup(sg) for sg in secgroups.get('security_groups')]
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 240, in __init__
for rule in sg['security_group_rules']]
KeyError: 'security_group_rules'
=======================================================================
[Impact]
By default, new security groups created through horizon or CLI include 2 default security rules. Upon managing those rules and removing them (to perhaps add others or limit traffic completely), the security group page errors out and prevents listing of *all* security groups if the empty security group is within the list to be displayed. Therefore, not only is the empty security group affected, but all others as well, as they cannot be listed. The root cause of the bug is that the payload does not include the expected key "security_group_rules" for that security group when there are no rules.
A fix has been implemented for Train (from master), Stein, Rocky and Queens releases and should be backported so the issue is addressed on previous those releases. The fix prevents the crash by ensuring the key "security_group_rules" is present with an empty list in case it was not included in the payload.
[Test Case]
1. Reproducing the issue
1a. Go to the Security Group section at Project > Network > Security Groups
1b. Create a security group
1c. Click the Manage Rules button for that security group you just created
1d. Delete the two default rules
1e. Go back to the Security Group section at Project > Network > Security Groups
1f. Security groups are no longer being listed and there will be an error popup: "Error: Unable to retrieve security groups.".
2. Install the package with the fixed code
3. Confirm bug has been fixed
3a. Repeat step 1a, you will notice that now security groups can be listed, including the empty one you had previously created
3b. Repeat steps 1b through 1e, the newly created and emptied security group can also be listed along the others.
[Regression Potential]
Given the following indicators:
a. Upstream CI passed, for all releases the fix is being backported.
b. The small scope of the problem: a key error prevents the page from being rendered. The fix is to make sure the key is always present, since it is always expected.
c. The fix is very simple, and during tests we can see that the other pages handle an empty list properly as the value for the "security_group_rules".
We can safely state that the regression potential is negligible. |
|
| 2019-10-19 19:34:28 |
Rodrigo Barbieri |
description |
Horizon 14.0.2 (rocky)
If a security group without any rules exists the listing of security groups fails with a KeyError.
Traceback (most recent call last):
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/utils.py", line 127, in _wrapped
data = function(self, request, *args, **kw)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/network.py", line 44, in get
security_groups = api.neutron.security_group_list(request)
File "/usr/lib/python2.7/site-packages/horizon/utils/memoized.py", line 95, in wrapped
value = cache[key] = func(*args, **kwargs)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 1641, in security_group_list
return SecurityGroupManager(request).list(**params)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 372, in list
return self._list(**params)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 359, in _list
return [SecurityGroup(sg) for sg in secgroups.get('security_groups')]
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 240, in __init__
for rule in sg['security_group_rules']]
KeyError: 'security_group_rules'
=======================================================================
[Impact]
By default, new security groups created through horizon or CLI include 2 default security rules. Upon managing those rules and removing them (to perhaps add others or limit traffic completely), the security group page errors out and prevents listing of *all* security groups if the empty security group is within the list to be displayed. Therefore, not only is the empty security group affected, but all others as well, as they cannot be listed. The root cause of the bug is that the payload does not include the expected key "security_group_rules" for that security group when there are no rules.
A fix has been implemented for Train (from master), Stein, Rocky and Queens releases and should be backported so the issue is addressed on previous those releases. The fix prevents the crash by ensuring the key "security_group_rules" is present with an empty list in case it was not included in the payload.
[Test Case]
1. Reproducing the issue
1a. Go to the Security Group section at Project > Network > Security Groups
1b. Create a security group
1c. Click the Manage Rules button for that security group you just created
1d. Delete the two default rules
1e. Go back to the Security Group section at Project > Network > Security Groups
1f. Security groups are no longer being listed and there will be an error popup: "Error: Unable to retrieve security groups.".
2. Install the package with the fixed code
3. Confirm bug has been fixed
3a. Repeat step 1a, you will notice that now security groups can be listed, including the empty one you had previously created
3b. Repeat steps 1b through 1e, the newly created and emptied security group can also be listed along the others.
[Regression Potential]
Given the following indicators:
a. Upstream CI passed, for all releases the fix is being backported.
b. The small scope of the problem: a key error prevents the page from being rendered. The fix is to make sure the key is always present, since it is always expected.
c. The fix is very simple, and during tests we can see that the other pages handle an empty list properly as the value for the "security_group_rules".
We can safely state that the regression potential is negligible. |
Horizon 14.0.2 (rocky)
If a security group without any rules exists the listing of security groups fails with a KeyError.
Traceback (most recent call last):
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/utils.py", line 127, in _wrapped
data = function(self, request, *args, **kw)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/network.py", line 44, in get
security_groups = api.neutron.security_group_list(request)
File "/usr/lib/python2.7/site-packages/horizon/utils/memoized.py", line 95, in wrapped
value = cache[key] = func(*args, **kwargs)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 1641, in security_group_list
return SecurityGroupManager(request).list(**params)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 372, in list
return self._list(**params)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 359, in _list
return [SecurityGroup(sg) for sg in secgroups.get('security_groups')]
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 240, in __init__
for rule in sg['security_group_rules']]
KeyError: 'security_group_rules'
=======================================================================
[Impact]
By default, new security groups created through horizon or CLI include 2 default security rules. Upon managing those rules and removing them (to perhaps add others or limit traffic completely), the security group page errors out and prevents listing of *all* security groups if the empty security group is within the list to be displayed. Therefore, not only is the empty security group affected, but all others as well, as they cannot be listed. The root cause of the bug is that the payload does not include the expected key "security_group_rules" for that security group when there are no rules.
A fix has been implemented for Train (from master), Stein, Rocky and Queens releases and should be backported so the issue is addressed on previous those releases. The fix prevents the crash by ensuring the key "security_group_rules" is present with an empty list in case it was not included in the payload.
[Test Case]
1. Reproducing the issue
1a. Go to the Security Group section at Project > Network > Security Groups
1b. Create a security group
1c. Click the Manage Rules button for that security group you just created
1d. Delete the two default rules
1e. Go back to the Security Group section at Project > Network > Security Groups
1f. Security groups are no longer being listed and there will be an error popup: "Error: Unable to retrieve security groups.".
2. Install the package with the fixed code
3. Confirm bug has been fixed
3a. Repeat step 1a, you will notice that now security groups can be listed, including the empty one you had previously created
3b. Repeat steps 1b through 1e, the newly created and emptied security group can also be listed along the others.
[Regression Potential]
Given the following indicators:
a. Upstream CI passed, for all releases the fix is being backported.
b. The small scope of the problem: a key error prevents the page from being rendered. The fix is to make sure the key is always present, since it is always expected.
c. The fix is very simple, and during tests we can see that the other pages handle an empty list properly as the value for the "security_group_rules" key.
We can safely state that the regression potential is negligible. |
|
| 2019-10-19 19:35:05 |
Rodrigo Barbieri |
attachment added |
|
lp1840465_disco.debdiff https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1840465/+attachment/5298451/+files/lp1840465_disco.debdiff |
|
| 2019-10-19 19:35:33 |
Rodrigo Barbieri |
attachment added |
|
lp1840465_cosmic.debdiff https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1840465/+attachment/5298452/+files/lp1840465_cosmic.debdiff |
|
| 2019-10-19 19:35:53 |
Rodrigo Barbieri |
attachment added |
|
lp1840465_bionic.debdiff https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1840465/+attachment/5298453/+files/lp1840465_bionic.debdiff |
|
| 2019-10-19 19:54:05 |
Rodrigo Barbieri |
horizon (Ubuntu Bionic): status |
New |
In Progress |
|
| 2019-10-19 19:54:12 |
Rodrigo Barbieri |
horizon (Ubuntu Disco): status |
New |
In Progress |
|
| 2019-10-19 19:54:17 |
Rodrigo Barbieri |
horizon (Ubuntu Eoan): status |
New |
In Progress |
|
| 2019-10-21 14:04:15 |
Rodrigo Barbieri |
tags |
in-stable-queens in-stable-rocky in-stable-stein neutron rocky-backport-potential stein-backport-potential |
in-stable-queens in-stable-rocky in-stable-stein neutron rocky-backport-potential stein-backport-potential sts-sru-needed |
|
| 2019-10-21 20:36:50 |
Corey Bryant |
horizon (Ubuntu Eoan): status |
In Progress |
Fix Released |
|
| 2019-10-21 20:37:31 |
Corey Bryant |
bug task added |
|
cloud-archive |
|
| 2019-10-21 20:37:48 |
Corey Bryant |
nominated for series |
|
cloud-archive/train |
|
| 2019-10-21 20:37:48 |
Corey Bryant |
bug task added |
|
cloud-archive/train |
|
| 2019-10-21 20:37:48 |
Corey Bryant |
nominated for series |
|
cloud-archive/rocky |
|
| 2019-10-21 20:37:48 |
Corey Bryant |
bug task added |
|
cloud-archive/rocky |
|
| 2019-10-21 20:37:48 |
Corey Bryant |
nominated for series |
|
cloud-archive/queens |
|
| 2019-10-21 20:37:48 |
Corey Bryant |
bug task added |
|
cloud-archive/queens |
|
| 2019-10-21 20:37:48 |
Corey Bryant |
nominated for series |
|
cloud-archive/stein |
|
| 2019-10-21 20:37:48 |
Corey Bryant |
bug task added |
|
cloud-archive/stein |
|
| 2019-10-21 20:38:02 |
Corey Bryant |
cloud-archive/queens: importance |
Undecided |
Medium |
|
| 2019-10-21 20:38:02 |
Corey Bryant |
cloud-archive/queens: status |
New |
Triaged |
|
| 2019-10-21 20:38:18 |
Corey Bryant |
cloud-archive/rocky: importance |
Undecided |
Medium |
|
| 2019-10-21 20:38:18 |
Corey Bryant |
cloud-archive/rocky: status |
New |
Triaged |
|
| 2019-10-21 20:38:54 |
Corey Bryant |
cloud-archive/stein: importance |
Undecided |
Medium |
|
| 2019-10-21 20:38:54 |
Corey Bryant |
cloud-archive/stein: status |
New |
Triaged |
|
| 2019-10-21 20:39:04 |
Corey Bryant |
cloud-archive/train: status |
New |
Fix Released |
|
| 2019-10-21 20:39:19 |
Corey Bryant |
cloud-archive/train: importance |
Undecided |
Medium |
|
| 2019-10-21 20:39:32 |
Corey Bryant |
horizon (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2019-10-21 20:39:45 |
Corey Bryant |
horizon (Ubuntu Disco): importance |
Undecided |
Medium |
|
| 2019-10-21 20:41:04 |
Corey Bryant |
horizon (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-10-21 20:41:27 |
Corey Bryant |
horizon (Ubuntu): importance |
Undecided |
Medium |
|
| 2019-10-21 20:41:27 |
Corey Bryant |
horizon (Ubuntu): status |
New |
Fix Released |
|
| 2019-10-21 20:58:45 |
Jacolex |
bug |
|
|
added subscriber Jacolex |
| 2019-10-22 12:28:17 |
Corey Bryant |
cloud-archive/rocky: status |
Triaged |
Fix Committed |
|
| 2019-10-22 12:28:19 |
Corey Bryant |
tags |
in-stable-queens in-stable-rocky in-stable-stein neutron rocky-backport-potential stein-backport-potential sts-sru-needed |
in-stable-queens in-stable-rocky in-stable-stein neutron rocky-backport-potential stein-backport-potential sts-sru-needed verification-rocky-needed |
|
| 2019-10-23 03:52:32 |
Akihiro Motoki |
tags |
in-stable-queens in-stable-rocky in-stable-stein neutron rocky-backport-potential stein-backport-potential sts-sru-needed verification-rocky-needed |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-rocky-needed |
|
| 2019-11-14 19:57:58 |
Rodrigo Barbieri |
tags |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-rocky-needed |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-rocky-done |
|
| 2019-11-21 13:34:21 |
Łukasz Zemczak |
horizon (Ubuntu Disco): status |
In Progress |
Fix Committed |
|
| 2019-11-21 13:34:25 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-11-21 13:34:29 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2019-11-21 13:34:32 |
Łukasz Zemczak |
tags |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-rocky-done |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-needed verification-needed-disco verification-rocky-done |
|
| 2019-11-21 13:46:18 |
Łukasz Zemczak |
horizon (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-11-21 13:46:25 |
Łukasz Zemczak |
tags |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-needed verification-needed-disco verification-rocky-done |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-needed verification-needed-bionic verification-needed-disco verification-rocky-done |
|
| 2019-11-21 19:07:16 |
Corey Bryant |
cloud-archive/queens: status |
Triaged |
Fix Committed |
|
| 2019-11-21 19:07:18 |
Corey Bryant |
tags |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-needed verification-needed-bionic verification-needed-disco verification-rocky-done |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-needed verification-needed-bionic verification-needed-disco verification-queens-needed verification-rocky-done |
|
| 2019-11-27 19:33:24 |
Rodrigo Barbieri |
tags |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-needed verification-needed-bionic verification-needed-disco verification-queens-needed verification-rocky-done |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-done-bionic verification-needed verification-needed-disco verification-queens-done verification-rocky-done |
|
| 2019-11-28 15:28:52 |
Rodrigo Barbieri |
tags |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-done-bionic verification-needed verification-needed-disco verification-queens-done verification-rocky-done |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-done-bionic verification-done-disco verification-needed verification-queens-done verification-rocky-done |
|
| 2019-12-02 11:13:45 |
Launchpad Janitor |
horizon (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
| 2019-12-02 11:13:51 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-12-02 11:18:56 |
Launchpad Janitor |
horizon (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-12-02 14:53:49 |
Corey Bryant |
cloud-archive/stein: status |
Triaged |
Fix Committed |
|
| 2019-12-02 14:53:51 |
Corey Bryant |
tags |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-done-bionic verification-done-disco verification-needed verification-queens-done verification-rocky-done |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-done-bionic verification-done-disco verification-needed verification-queens-done verification-rocky-done verification-stein-needed |
|
| 2019-12-03 10:26:12 |
Hemanth Nakkina |
tags |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-done-bionic verification-done-disco verification-needed verification-queens-done verification-rocky-done verification-stein-needed |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-done-bionic verification-done-disco verification-needed verification-queens-done verification-rocky-done verification-stein-done |
|
| 2019-12-09 14:39:35 |
Edward Hope-Morley |
tags |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-done-bionic verification-done-disco verification-needed verification-queens-done verification-rocky-done verification-stein-done |
in-stable-queens in-stable-rocky in-stable-stein neutron sts-sru-needed verification-done verification-done-bionic verification-done-disco verification-queens-done verification-rocky-done verification-stein-done |
|
| 2019-12-09 15:19:59 |
Corey Bryant |
cloud-archive/stein: status |
Fix Committed |
Fix Released |
|
| 2019-12-09 15:20:45 |
Corey Bryant |
cloud-archive/rocky: status |
Fix Committed |
Fix Released |
|
| 2019-12-09 15:21:32 |
Corey Bryant |
cloud-archive/queens: status |
Fix Committed |
Fix Released |
|
