[Yahoo-eng-team] [Bug 1401013] [NEW] performance regression
Public bug reported: The fix https://review.openstack.org/137547 for bug https://bugs.launchpad.net/horizon/+bug/1394900 introduced a small performance issue as pointed out in https://review.openstack.org/#/c/140280/1 : Is it possible to set the filtering as search_opts: snaps = cinder.volume_snapshot_list(request, search_opts=dict(status=api.cinder.VOLUME_STATE_AVAILABLE, bootable='true')) ** Affects: horizon Importance: Medium Assignee: Liyingjun (liyingjun) Status: New ** Tags: juno-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1401013 Title: performance regression Status in OpenStack Dashboard (Horizon): New Bug description: The fix https://review.openstack.org/137547 for bug https://bugs.launchpad.net/horizon/+bug/1394900 introduced a small performance issue as pointed out in https://review.openstack.org/#/c/140280/1 : Is it possible to set the filtering as search_opts: snaps = cinder.volume_snapshot_list(request, search_opts=dict(status=api.cinder.VOLUME_STATE_AVAILABLE, bootable='true')) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1401013/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1394962] Re: Incorrect IP on Router Interface to External Net
** Changed in: neutron Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1394962 Title: Incorrect IP on Router Interface to External Net Status in OpenStack Neutron (virtual network service): Invalid Bug description: A user with sufficient permissions creates a new router through Dashboard. Instead of assigning a gateway as normal, the user chooses to add a new interface connected to the external network. The user is given the option to enter an IP, but it can be left black so that the system chooses “the first host IP address in the subnet” according to [1]. But instead of the expected behavior, OpenStack chooses an IP address neither included in the subnet pool, nor the first IP in the network. [1] http://docs.openstack.org/user- guide/content/dashboard_create_networks.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1394962/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1401004] [NEW] policy.json prevents regular user from creating HA router
Public bug reported: This line in the policy.json prevents a regular user from creating an HA router. "create_router:ha": "rule:admin_only", There was a bug related to creating l3ha as regular user, but that was fixed and backported to juno 2014.2.1. I have tested and confirm that updating the policy.json I can successfully create an l3ha router as a user. Related-Bug: #1388716 ** Affects: neutron Importance: Undecided Status: New ** Tags: l3ha policy.json -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1401004 Title: policy.json prevents regular user from creating HA router Status in OpenStack Neutron (virtual network service): New Bug description: This line in the policy.json prevents a regular user from creating an HA router. "create_router:ha": "rule:admin_only", There was a bug related to creating l3ha as regular user, but that was fixed and backported to juno 2014.2.1. I have tested and confirm that updating the policy.json I can successfully create an l3ha router as a user. Related-Bug: #1388716 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1401004/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400945] [NEW] User quota could be set greater than tenant quota
Public bug reported: Reproduce: 1.Create new tenant and user. $ keystone tenant-create --name quota --description "Quota test" $ keystone user-create --name quotauser --pass quotauser $ keystone user-role-add --user quotauser --tenant quota --role _member_ 2.Set tenant quota $nova quota-update $tenant_id --instances 20 3.Set user quota to a value greater than tenant quota $nova quota-update $tenant_id --user $user_id --instances 40 Result: The user quota update succeeded. Then the user quota is greater than the tenant quota. $ nova quota-show --tenant $tenant_id +-+---+ | Quota | Limit | +-+---+ | instances | 20| $ nova quota-show --tenant $tenant_id --user $user_id +-+---+ | Quota | Limit | +-+---+ | instances | 40| ** Affects: nova Importance: Undecided Assignee: Hironori Shiina (shiina-hironori) Status: New ** Changed in: nova Assignee: (unassigned) => Hironori Shiina (shiina-hironori) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1400945 Title: User quota could be set greater than tenant quota Status in OpenStack Compute (Nova): New Bug description: Reproduce: 1.Create new tenant and user. $ keystone tenant-create --name quota --description "Quota test" $ keystone user-create --name quotauser --pass quotauser $ keystone user-role-add --user quotauser --tenant quota --role _member_ 2.Set tenant quota $nova quota-update $tenant_id --instances 20 3.Set user quota to a value greater than tenant quota $nova quota-update $tenant_id --user $user_id --instances 40 Result: The user quota update succeeded. Then the user quota is greater than the tenant quota. $ nova quota-show --tenant $tenant_id +-+---+ | Quota | Limit | +-+---+ | instances | 20| $ nova quota-show --tenant $tenant_id --user $user_id +-+---+ | Quota | Limit | +-+---+ | instances | 40| To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1400945/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400944] [NEW] Nova per-project quota usage can become inaccurate.
Public bug reported: I am still working on diagnosing the exact steps to reproduce, but on test systems it is possible to get nova's quota tracking into an inaccurate state. This was triggered via randomized testing with a focus on create server images as well as rebooting and resizing the test servers. In the example below, after running some randomized tests, there are no active servers on the project, yet 'nova absolute-limits' output lists cores as being used (the quotas-usage table data reflects this). No cores are listed as used in the admin view for hypervisor usage, but this inaccurate state will prevent the project from spinning up machines. nova list ++--+++-+--+ | ID | Name | Status | Task State | Power State | Networks | ++--+++-+--+ ++--+++-+--+ pcrews@erlking-dev:~/git/rannsaka$ nova absolute-limits +-+---+ | Name| Value | +-+---+ | maxServerMeta | 128 | | maxPersonality | 5 | | totalServerGroupsUsed | 0 | | maxImageMeta| 128 | | maxPersonalitySize | 10240 | | maxTotalRAMSize | 51200 | | maxTotalKeypairs| 100 | | maxSecurityGroupRules | 20| | maxServerGroups | 10| | totalCoresUsed | 8 | | totalRAMUsed| 26368 | | maxSecurityGroups | 10| | totalFloatingIpsUsed| 0 | | totalInstancesUsed | 0 | | totalSecurityGroupsUsed | 1 | | maxTotalFloatingIps | 10| | maxTotalInstances | 20| | maxTotalCores | 20| | maxServerGroupMembers | 10| +-+---+ mysql> select * from quota_usages; +-+-+++--+-++--+---+-+--+ | created_at | updated_at | deleted_at | id | project_id | resource| in_use | reserved | until_refresh | deleted | user_id | +-+-+++--+-++--+---+-+--+ | 2014-12-09 23:28:12 | 2014-12-10 00:40:06 | NULL | 1 | 078e0e1371f44e2e9e6d9691342ed02d | instances | 0 |0 | NULL | 0 | d2197b1accca4a51b2dbb964d9fc7683 | | 2014-12-09 23:28:12 | 2014-12-10 00:40:06 | NULL | 2 | 078e0e1371f44e2e9e6d9691342ed02d | ram | 26368 | 3968 | NULL | 0 | d2197b1accca4a51b2dbb964d9fc7683 | | 2014-12-09 23:28:12 | 2014-12-10 00:40:06 | NULL | 3 | 078e0e1371f44e2e9e6d9691342ed02d | cores | 8 |2 | NULL | 0 | d2197b1accca4a51b2dbb964d9fc7683 | | 2014-12-09 23:28:12 | 2014-12-09 23:28:12 | NULL | 4 | 078e0e1371f44e2e9e6d9691342ed02d | security_groups | 1 |0 | NULL | 0 | d2197b1accca4a51b2dbb964d9fc7683 | | 2014-12-09 23:28:14 | 2014-12-10 00:40:05 | NULL | 5 | 078e0e1371f44e2e9e6d9691342ed02d | fixed_ips | 0 |0 | NULL | 0 | NULL | +-+-+++--+-++--+---+-+--+ ** Affects: nova Importance: Undecided Status: New ** Description changed: I am still working on diagnosing the exact steps to reproduce, but on test systems it is possible to get nova's quota tracking into an inaccurate state. This was triggered via randomized testing with a focus on create server - images, rebooting, and resizing them. + images as well as rebooting and resizing the test servers. In the example below, after running some randomized tests, there are no active servers on the project, yet 'nova absolute-limits' output lists cores as being used (the quotas-usage table data reflects this). No cores are listed as used in the admin view for hypervisor usage, but this inaccurate state will prevent the project from spinning up machines. nova list ++--+++-+--+ | ID | Name | Status | Task State | Power State | Networks | ++--+++-+--+ ++--+++-+--+ pcrews@erlking-dev:~/git/rannsaka$ nova absolute-limits +-+---+ | Name| Value | +-+---+ | maxServerMeta | 128 | | maxPersonality | 5 | | totalServerGroupsUsed | 0 | | maxImageM
[Yahoo-eng-team] [Bug 1400946] [NEW] Upload Object - Object name with a "/" at the end makes it a Pseudo-folder
Public bug reported: 1. Login to Devstack as admin 2. Create the container "C_1" 3. Inside C_1 container, try to upload an object with "/" at the end of the name. Observed that the uploaded object will turn into a Pseudo-Folder. As per the design "/" should work only for "Create Pseudo-folder" function to created nested folders. It should not have any effect when used while creating an object cuz, objects cannot be nested. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: "Step.doc" https://bugs.launchpad.net/bugs/1400946/+attachment/4277271/+files/Step.doc -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1400946 Title: Upload Object - Object name with a "/" at the end makes it a Pseudo- folder Status in OpenStack Dashboard (Horizon): New Bug description: 1. Login to Devstack as admin 2. Create the container "C_1" 3. Inside C_1 container, try to upload an object with "/" at the end of the name. Observed that the uploaded object will turn into a Pseudo-Folder. As per the design "/" should work only for "Create Pseudo-folder" function to created nested folders. It should not have any effect when used while creating an object cuz, objects cannot be nested. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1400946/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400941] [NEW] [LBaaS V2] Report information on session_persistence on GET calls for /pools/ not working
Public bug reported:
When I make a GET call on the ../pools/ , I get back the information
on all the attributes as shown below. However the information on
session_persistence is missing.
When I originally created the pool, I did not set the
session_persistence. However the parameter should still be returned with
an empty or null value , as is happening for (description,members) etc
DEBUG: neutronclient.client
REQ: curl -i
http://10.0.1.9:9696/v2.0/lbaas/pools/b4b5a5ae-f098-4173-97ec-bd5682b4df6a.json
-X GET -H "X-Auth-Token: bb744f089159 4ffcb3b7267b76ffaf44" -H "Content-Type:
application/json" -H "Accept: application/json" -H "User-Agent:
python-neutronclient"
DEBUG: neutronclient.client RESP:200 CaseInsensitiveDict({'date': 'Tue, 09 Dec
2014 21:35:32 GMT', 'content-length': '279', 'conte
nt-type': 'application/json; charset=UTF-8', 'x-openstack-request-id':
'req-7d792980-5df5-4380-889f-05c418698d93'}) {"pool": {"lb_
algorithm": "ROUND_ROBIN", "status": "DEFERRED", "protocol": "HTTP",
"description": "", "admin_state_up": true, "tenant_id": "b952
fe0f90a24ddba97f5872fa0f42e8", "healthmonitor_id": null, "members": [], "id":
"b4b5a5ae-f098-4173-97ec-bd5682b4df6a", "name": "poo l1"}}
+--+--+
| Field| Value|
+--+--+
| admin_state_up | True |
| description | |
| healthmonitor_id | |
| id | b4b5a5ae-f098-4173-97ec-bd5682b4df6a |
| lb_algorithm | ROUND_ROBIN |
| members | |
| name | pool1|
| protocol | HTTP |
| status | DEFERRED |
| tenant_id| b952fe0f90a24ddba97f5872fa0f42e8 |
+--+--+
** Affects: neutron
Importance: Undecided
Assignee: German Eichberger (german-eichberger)
Status: New
** Description changed:
When I make a GET call on the ../pools/ , I get back the information
on all the attributes as shown below. However the information on
session_persistence is missing.
When I originally created the pool, I did not set the
session_persistence. However the parameter should still be returned with
an empty or null value , as is happening for (description,members) etc
DEBUG: neutronclient.client
REQ: curl -i
http://10.0.1.9:9696/v2.0/lbaas/pools/b4b5a5ae-f098-4173-97ec-bd5682b4df6a.json
-X GET -H "X-Auth-Token: bb744f089159 4ffcb3b7267b76ffaf44" -H "Content-Type:
application/json" -H "Accept: application/json" -H "User-Agent:
python-neutronclient"
DEBUG: neutronclient.client RESP:200 CaseInsensitiveDict({'date': 'Tue, 09
Dec 2014 21:35:32 GMT', 'content-length': '279', 'conte
nt-type': 'application/json; charset=UTF-8', 'x-openstack-request-id':
'req-7d792980-5df5-4380-889f-05c418698d93'}) {"pool": {"lb_
algorithm": "ROUND_ROBIN", "status": "DEFERRED", "protocol": "HTTP",
"description": "", "admin_state_up": true, "tenant_id": "b952
fe0f90a24ddba97f5872fa0f42e8", "healthmonitor_id": null, "members": [], "id":
"b4b5a5ae-f098-4173-97ec-bd5682b4df6a", "name": "poo l1"}}
+--+--+
| Field| Value|
+--+--+
| admin_state_up | True |
| description | |
| healthmonitor_id | |
| id | b4b5a5ae-f098-4173-97ec-bd5682b4df6a |
| lb_algorithm | ROUND_ROBIN |
| members | |
| name | pool1|
| protocol | HTTP |
| status | DEFERRED |
| tenant_id| b952fe0f90a24ddba97f5872fa0f42e8 |
+--+--+
-
- was:
-
- When I make a GET call on the ../pools/ , I get back the information
- on all the attributes as shown below. However the information on
- session_persistence is missing.
-
- When I originally created the pool, I did not set the
- session_persistence. However the parameter should still be returned with
- an empty or null value , as is happening for (description,members) etc
-
- DEBUG: neutronclient.client
- REQ: curl -i
http://10.0.1.9:9696/v2.0/lbaas/pools/b4b5a5ae-f098-4173-97ec-bd5682b4df6a.json
-X GET -H "X-Auth-Token: bb744f089159 4ffcb3b7267b76ffaf44" -H "Content-Type:
application/json" -H "Accept: application/json" -H "User-Agent:
python-neutronclient"
-
- DEBUG: neutr
[Yahoo-eng-team] [Bug 1400915] [NEW] Archlinux Network Config Broken
Public bug reported:
The networking code in 'distros/arch.py' is severely broken, I wonder if
it had ever at worked.
1. In method _write_network in arch.py line 71 there is:
net_fn = self.network_conf_dir + dev
the definition for the output file name. Since
network_conf_dir = "/etc/netctl"
and
dev = "eth0" (for example)
net_fn will be "/etc/netctleth0" where it should be "/etc/netctl/eth0"
2. Also in method "_write_network" in line 79 there is
'DNS': str(tuple(info.get('dns-nameservers'))).replace(',', '')
which causes a crash of the whole provider in case a 'dns-nameserver' is
not defined in 'meta-data'.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1400915
Title:
Archlinux Network Config Broken
Status in Init scripts for use on cloud images:
New
Bug description:
The networking code in 'distros/arch.py' is severely broken, I wonder
if it had ever at worked.
1. In method _write_network in arch.py line 71 there is:
net_fn = self.network_conf_dir + dev
the definition for the output file name. Since
network_conf_dir = "/etc/netctl"
and
dev = "eth0" (for example)
net_fn will be "/etc/netctleth0" where it should be "/etc/netctl/eth0"
2. Also in method "_write_network" in line 79 there is
'DNS': str(tuple(info.get('dns-nameservers'))).replace(',', '')
which causes a crash of the whole provider in case a 'dns-nameserver'
is not defined in 'meta-data'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1400915/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400566] Re: Table actions that are not allowed should be disabled instead of removed
Broadened the description, since this UX is pervasive.
** Description changed:
- How to reproduce
+ Throughout horizon actions are controlled through their allowed
+ function; if true, the button is shown; otherwise the button is hidden.
+
+ There are some concerns that when an action is not available, it could
+ confuse users when the button disappears. One suggestion is that
+ instead of hiding the button, make it disabled.
+
+ Before making this sweeping change, we should get direction from the UX
+ folks.
+
+ How to reproduce:
Project - > volumes create a volume and attach an instance on it. The
delete button should not show up for that volume.
Currently when volumes are in not deletable state, we use "allowed"
method in the tables.py to hide the delete button. Volumes in the
following states are deletable : DELETABLE_STATES = ("available",
"error", "error_extending")
-
- There are some concerns that when the delete button is not available, it
- could confuse users why the button disappears. One suggestion is that
- instead of hiding it , make deletable button disabled.
-
- We need UX folks overall strategy to help resolve this kind of UX
- concern.
** Changed in: horizon
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1400566
Title:
Table actions that are not allowed should be disabled instead of
removed
Status in OpenStack Dashboard (Horizon):
Opinion
Bug description:
Throughout horizon actions are controlled through their allowed
function; if true, the button is shown; otherwise the button is
hidden.
There are some concerns that when an action is not available, it could
confuse users when the button disappears. One suggestion is that
instead of hiding the button, make it disabled.
Before making this sweeping change, we should get direction from the
UX folks.
How to reproduce:
Project - > volumes create a volume and attach an instance on it. The
delete button should not show up for that volume.
Currently when volumes are in not deletable state, we use "allowed"
method in the tables.py to hide the delete button. Volumes in the
following states are deletable : DELETABLE_STATES = ("available",
"error", "error_extending")
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1400566/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400889] [NEW] [Sahara] Nodegroup template details displays security groups as IDs
Public bug reported: Steps to repro: 1. Create nodegroup template with security groups selected 2. Open nodegroup template details Observed behavior: Security groups are displayed as IDs. Something like = Security Groups * 1961bfea-eaa5-4a86-9e65-b74a7d484fb9 * fd9f3cad-97e7-4f10-9750-17396e73e77a = ** Affects: horizon Importance: Undecided Status: New ** Tags: sahara ** Description changed: Steps to repro: - 1. Create nodegroup with security groups selected + 1. Create nodegroup template with security groups selected 2. Open nodegroup template details Observed behavior: Security groups are displayed as IDs. Something like = Security Groups * 1961bfea-eaa5-4a86-9e65-b74a7d484fb9 * fd9f3cad-97e7-4f10-9750-17396e73e77a = -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1400889 Title: [Sahara] Nodegroup template details displays security groups as IDs Status in OpenStack Dashboard (Horizon): New Bug description: Steps to repro: 1. Create nodegroup template with security groups selected 2. Open nodegroup template details Observed behavior: Security groups are displayed as IDs. Something like = Security Groups * 1961bfea-eaa5-4a86-9e65-b74a7d484fb9 * fd9f3cad-97e7-4f10-9750-17396e73e77a = To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1400889/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400872] Re: Show password feature should be configurable
Pretty sure this is a security hardening opportunity, not a vulnerability for which we would publish an advisory, and so I have classified it accordingly. ** Also affects: ossa Importance: Undecided Status: New ** Changed in: ossa Status: New => Won't Fix ** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1400872 Title: Show password feature should be configurable Status in OpenStack Dashboard (Horizon): Confirmed Status in OpenStack Security Advisories: Won't Fix Bug description: Horizon allows the password field to be displayed in plain text. This introduces a potential security risk. Imagine a user leaving their desktop unlock, if the user saved their password on the browser, a malicious user could go into the Login page and display the Openstack password. The show password feature should be made configurable for operators who wants a more secure deployment of Horizon. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1400872/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400872] [NEW] Show password feature should be configurable
*** This bug is a security vulnerability *** Public security bug reported: Horizon allows the password field to be displayed in plain text. This introduces a potential security risk. Imagine a user leaving their desktop unlock, if the user saved their password on the browser, a malicious user could go into the Login page and display the Openstack password. The show password feature should be made configurable for operators who wants a more secure deployment of Horizon. ** Affects: horizon Importance: High Assignee: Cindy Lu (clu-m) Status: Confirmed ** Tags: security ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1400872 Title: Show password feature should be configurable Status in OpenStack Dashboard (Horizon): Confirmed Bug description: Horizon allows the password field to be displayed in plain text. This introduces a potential security risk. Imagine a user leaving their desktop unlock, if the user saved their password on the browser, a malicious user could go into the Login page and display the Openstack password. The show password feature should be made configurable for operators who wants a more secure deployment of Horizon. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1400872/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400873] [NEW] [Sahara] Hadoop options are not displayed on nodegroup template details page
Public bug reported: Steps to reproduce 1. Start creation of hadoop1 nodegroup template 2. Select tasktracker process 3. Set "mapred.child.java.opts" option to "-Xmx201m" 4. Click 'Create' 5. Click to template name to get nodegroup template details 6. Go to 'service configurations' Observed behavior: Page displays that "mapred.child.java.opts" parameter is overwritten, but doesn't display value (see screenshot attached). Manual request to sahara shows that sahara returns correct value. So, problem is on horizon side. ** Affects: horizon Importance: Undecided Assignee: Andrew Lazarev (alazarev) Status: New ** Tags: sahara ** Attachment added: "Screen Shot 2014-12-09 at 12.55.37 PM.png" https://bugs.launchpad.net/bugs/1400873/+attachment/4277218/+files/Screen%20Shot%202014-12-09%20at%2012.55.37%20PM.png ** Changed in: horizon Assignee: (unassigned) => Andrew Lazarev (alazarev) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1400873 Title: [Sahara] Hadoop options are not displayed on nodegroup template details page Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce 1. Start creation of hadoop1 nodegroup template 2. Select tasktracker process 3. Set "mapred.child.java.opts" option to "-Xmx201m" 4. Click 'Create' 5. Click to template name to get nodegroup template details 6. Go to 'service configurations' Observed behavior: Page displays that "mapred.child.java.opts" parameter is overwritten, but doesn't display value (see screenshot attached). Manual request to sahara shows that sahara returns correct value. So, problem is on horizon side. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1400873/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400869] [NEW] [Sahara] Create Nodegroup template is overloaded
Public bug reported: Create Nodegroup template page was overloaded before. After adding security groups feature that can display all security groups on the same page it is overloaded much more. Proposed change: extract security options to the separate tab ** Affects: horizon Importance: Undecided Assignee: Andrew Lazarev (alazarev) Status: New ** Tags: sahara ** Changed in: horizon Assignee: (unassigned) => Andrew Lazarev (alazarev) ** Description changed: - Create Nodegroup template was overloaded before. After adding security - groups feature that can display all security groups on the same page it - is overloaded much more. + Create Nodegroup template page was overloaded before. After adding + security groups feature that can display all security groups on the same + page it is overloaded much more. Proposed change: extract security options to the separate tab -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1400869 Title: [Sahara] Create Nodegroup template is overloaded Status in OpenStack Dashboard (Horizon): New Bug description: Create Nodegroup template page was overloaded before. After adding security groups feature that can display all security groups on the same page it is overloaded much more. Proposed change: extract security options to the separate tab To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1400869/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400825] Re: Deleting a nested pseudo-folder deletes the parent folders
Deleting pseudo/folder/name from the swift command line does exactly the same thing, so this is not strictly a horizon issue. The reason is that the separate intermediate pseudo folders are not created when you specify a nested pseudo folder in one string. If, on the other hand, you were to create them in horizon one at a time, it would work as you expect; i.e. create 'pseudo', go into that one, create 'folder', go into that one, and create 'name'. Then delete 'name', and 'pseudo' and 'folder' will still exist. While this behavior may be a bit different from what you may expect from working with an operating system and real directories, it is consisent with swift's use of pseudo folders. ** Changed in: horizon Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1400825 Title: Deleting a nested pseudo-folder deletes the parent folders Status in OpenStack Dashboard (Horizon): Opinion Bug description: 1. Login to Devstack 2. Create the container "C_1" 2. Create the Create pseudo-folder as "pseudo/folder/name". This creates "pseudo" folder -> a subfolder "folder" inside pseudo -> a sub folder "name" inside folder. Deleting the child folder "name", deletes the parent folders too. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1400825/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400860] [NEW] server group policy not honored for targeted evacuations
Public bug reported: This was observed in the Juno release. Because targeted evacuations do not go through the scheduler for policy- based decision making, a VM could be evacuated to a host that would violate the policy of the server group it belongs to. If a VM belongs to a server group, the group policy will need to be checked in the compute manager at the time of evacuation to ensure that: 1. VMs in a server group with affinity rule can't be evacuated. 2. VMs in a server group with anti-affinity rule don't move to a host that would violate the rule. This is related to Bug #1399815, where the same issue is seen with migration. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1400860 Title: server group policy not honored for targeted evacuations Status in OpenStack Compute (Nova): New Bug description: This was observed in the Juno release. Because targeted evacuations do not go through the scheduler for policy-based decision making, a VM could be evacuated to a host that would violate the policy of the server group it belongs to. If a VM belongs to a server group, the group policy will need to be checked in the compute manager at the time of evacuation to ensure that: 1. VMs in a server group with affinity rule can't be evacuated. 2. VMs in a server group with anti-affinity rule don't move to a host that would violate the rule. This is related to Bug #1399815, where the same issue is seen with migration. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1400860/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400825] [NEW] Create pseudo-folder as "pseudo/folder/name". This creates "pseudo" folder -> a subfolder "folder" inside pseudo -> a subfolder "name" inside folder. Deleting the
Public bug reported: 1. Login to Devstack 2. Create the container "C_1" 2. Create the Create pseudo-folder as "pseudo/folder/name". This creates "pseudo" folder -> a subfolder "folder" inside pseudo -> a sub folder "name" inside folder. Deleting the child folder "name", deletes the parent folders too. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1400825 Title: Create pseudo-folder as "pseudo/folder/name". This creates "pseudo" folder -> a subfolder "folder" inside pseudo -> a subfolder "name" inside folder. Deleting the child folder "name", deletes the parent folders too. Status in OpenStack Dashboard (Horizon): New Bug description: 1. Login to Devstack 2. Create the container "C_1" 2. Create the Create pseudo-folder as "pseudo/folder/name". This creates "pseudo" folder -> a subfolder "folder" inside pseudo -> a sub folder "name" inside folder. Deleting the child folder "name", deletes the parent folders too. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1400825/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400818] [NEW] Create Pseudo-folder - add "/" at the end of folder name, creates a sub folder with the same name.
Public bug reported: 1. Login to Devstack as admin 2. Create the container "C_1" 3. Inside C_1 container create the pseudo folder "abc/" (with the "/" at the end of the folder name) Observe that child folder with the same name as parent folder created (abc). when try to delete the child folder error message is displayed. When nothing has specified after “/”, creating child folder with the same name as parent is not expected. In addition, both parent and child folders are refused to delete. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: "C2.PNG" https://bugs.launchpad.net/bugs/1400818/+attachment/4277134/+files/C2.PNG -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1400818 Title: Create Pseudo-folder - add "/" at the end of folder name, creates a sub folder with the same name. Status in OpenStack Dashboard (Horizon): New Bug description: 1. Login to Devstack as admin 2. Create the container "C_1" 3. Inside C_1 container create the pseudo folder "abc/" (with the "/" at the end of the folder name) Observe that child folder with the same name as parent folder created (abc). when try to delete the child folder error message is displayed. When nothing has specified after “/”, creating child folder with the same name as parent is not expected. In addition, both parent and child folders are refused to delete. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1400818/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400819] [NEW] Create pseudo-folder - a folder with just "/" as a name gets create but doesn't show up
Public bug reported: 1. Login to Devstack 2. Create the container "C_1" 3. Create the pseduo folder with the name "/" Observe that success message is displayed but no new folder is created. Expected: Display error message for wrong folder name format. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1400819 Title: Create pseudo-folder - a folder with just "/" as a name gets create but doesn't show up Status in OpenStack Dashboard (Horizon): New Bug description: 1. Login to Devstack 2. Create the container "C_1" 3. Create the pseduo folder with the name "/" Observe that success message is displayed but no new folder is created. Expected: Display error message for wrong folder name format. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1400819/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1101404] Re: nova syslog logging to /dev/log race condition in python 2.6
** Also affects: neutron Importance: Undecided Status: New ** Also affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1101404 Title: nova syslog logging to /dev/log race condition in python 2.6 Status in OpenStack Image Registry and Delivery Service (Glance): New Status in OpenStack Identity (Keystone): Confirmed Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): Confirmed Status in Logging configuration library for OpenStack: Confirmed Bug description: running nova-api-ec2 running rsyslog service rsyslog restart ; service nova-api-ec2 restart nova-api-ec2 consumes up to 100% of the available CPU (or at least a full core) and s not responsive. /var/log/nova/nova-api-ec2.lgo states the socket is already in use. strace the process sendto(3, "<142>2013-01-18 20:00:22 24882 INFO nova.service [-] Caught SIGTERM, exiting\0", 77, 0, NULL, 0) = -1 ENOTCONN (Transport endpoint is not connected) service nova-api-ec2 restart fails as upstart already thinks the process has been terminated. The only way to recover is to pkill -9 nova-api-ec2 and then restart it with 'service nova-api-ec2 restart'. The same behavior has been seen in all nova-api services. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1101404/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1398128] Re: ironic tempest tests periodically failing: No valid host was found
Reviewed: https://review.openstack.org/139770
Committed:
https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=0354640587cde740aa0299c722f019ae1c01e05d
Submitter: Jenkins
Branch:master
commit 0354640587cde740aa0299c722f019ae1c01e05d
Author: Adam Gandelman
Date: Fri Dec 5 16:49:12 2014 -0800
Move ironic ssh key creation early in preparation
SSH creds should be in place before nodes are enrolled. If not,
ironic cannot sync power state causing nova to skip nodes in
its resource tracker.
Change-Id: I6b98ae57ce33783f69e2cf9ba357807d384b3012
Closes-bug: #1398128
** Changed in: devstack
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1398128
Title:
ironic tempest tests periodically failing: No valid host was found
Status in devstack - openstack dev environments:
Fix Released
Status in OpenStack Bare Metal Provisioning Service (Ironic):
Invalid
Status in OpenStack Compute (Nova):
Invalid
Bug description:
This was noticed on the stable/juno ironic sideways grenade jobs, but
is also confirmed to be happening on the check-tempest-dsvm-ironic-
parallel-nv job, which runs a similarly configured tempest run against
Ironic:
http://logs.openstack.org/84/137684/1/check/check-grenade-dsvm-ironic-
sideways/6d118bc/
A number of the early compute tests will fail to spawn an instance,
getting a scheduling error on the client side:
BuildErrorException: Server %(server_id)s failed to build and is in ERROR
status
Details: Server eb81ee40-ceba-484d-b665-92ec3bf4fedd failed to build and is
in ERROR status
Details: {u'message': u'No valid host was found. ', u'created':
u'2014-11-27T17:44:05Z', u'code': 500}
Looking through the nova logs, the request never even makes to the
nova-scheduler. The last error is reported in conductor:
2014-11-27 17:44:01.005 WARNING nova.scheduler.driver [req-a3c046e5
-66db-4bca-a6f8-2263763e49a6 SecurityGroupsTestJSON-2119055496
SecurityGroupsTestJSON-1381566740] [instance: 9008811a-f400-42ae-
98d5-caf828fa34dc] NoValidHost exception with message: 'No valid host
was found.'
Looking at the time stamps of the requests, the first instance is
requested at 17:44:00
2014-11-27 17:44:00.944 24730 DEBUG tempest.common.rest_client [req-
a3c046e5-66db-4bca-a6f8-2263763e49a6 None] Request
(SecurityGroupsTestJSON:test_server_security_groups): 202 POST
http://127.0.0.1:8774/v2/adf4838f0d15462da4601a5d853eafbf/servers
0.515s
However, on the nova-compute side, the resource tracker has not been
updated to include the enlisted Ironic nodes until much later. This
first time the tracker contains any of the ironic resources is at
17:44:06:
2014-11-27 17:44:06.224 21645 AUDIT nova.compute.resource_tracker [-]
Total physical ram (MB): 512, total allocated virtual ram (MB): 0
So there's a race between the resource tracker's initial inclusion of
available resources and Tempest running the first set of tests that
require an instance. This can be worked around in a couple of ways:
* Adjust the periodic task interval on nova-compute to update much more
frequently, tho this will just narrow the window.
* Have tempest run an admin 'nova hypervisor-stats' call on the client side
and wait for resources before running any instances (in the case of baremetal
only)
* Adjust devstack's nova cpu deployment to spin until hypervisor-stats
reflect the ironic node parameters
To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1398128/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400793] [NEW] default merging for cloud-config is not right.
Public bug reported:
long ago, 2 cloud-configs merged in one way.
after new the new mergers that seems to be changed.
$ cat f1.yaml
#cloud-config
snappy:
packages: [orig_pkg1, orig_pkg2]
ssh_enabled: True
ssh_authorized_keys:
- mykey@smoser
$ cat f2.yaml
#cloud-config
snappy:
packages: [updated_pkg1, updated_pkg2]
$ PYTHONPATH=$PWD ./tools/ccfg-merge-debug f1.yaml f2.yaml
#cloud-config
# from 2 files
# part-001
# part-002
---
snappy:
packages:
- updated_pkg1
- updated_pkg2
ssh_authorized_keys:
- mykey@smoser
...
the above is different than the expected behavior from long ago, which is to
act like 'mergemanydict' does:
$ cat oldmerge.py
#!/usr/bin/python
from cloudinit import util
import sys, yaml
print util.mergemanydict([yaml.load(open(f)) for f in sys.argv[1:]],
reverse=True)
$ python oldmerge.py f1.yaml f2.yaml
{'snappy': {'packages': ['updated_pkg1', 'updated_pkg2'], 'ssh_enabled': True},
'ssh_authorized_keys': ['mykey@smoser']}
The bug here is that 'ssh_enabled' got dropped. as the second config's 'snappy'
completely replaced the first.
Note, also that its not sufficient to just change the DEF_MERGERS to be
'dict('no_replace')'.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1400793
Title:
default merging for cloud-config is not right.
Status in Init scripts for use on cloud images:
New
Bug description:
long ago, 2 cloud-configs merged in one way.
after new the new mergers that seems to be changed.
$ cat f1.yaml
#cloud-config
snappy:
packages: [orig_pkg1, orig_pkg2]
ssh_enabled: True
ssh_authorized_keys:
- mykey@smoser
$ cat f2.yaml
#cloud-config
snappy:
packages: [updated_pkg1, updated_pkg2]
$ PYTHONPATH=$PWD ./tools/ccfg-merge-debug f1.yaml f2.yaml
#cloud-config
# from 2 files
# part-001
# part-002
---
snappy:
packages:
- updated_pkg1
- updated_pkg2
ssh_authorized_keys:
- mykey@smoser
...
the above is different than the expected behavior from long ago, which is to
act like 'mergemanydict' does:
$ cat oldmerge.py
#!/usr/bin/python
from cloudinit import util
import sys, yaml
print util.mergemanydict([yaml.load(open(f)) for f in sys.argv[1:]],
reverse=True)
$ python oldmerge.py f1.yaml f2.yaml
{'snappy': {'packages': ['updated_pkg1', 'updated_pkg2'], 'ssh_enabled':
True}, 'ssh_authorized_keys': ['mykey@smoser']}
The bug here is that 'ssh_enabled' got dropped. as the second config's
'snappy' completely replaced the first.
Note, also that its not sufficient to just change the DEF_MERGERS to be
'dict('no_replace')'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1400793/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400784] [NEW] Cold migration fails when using vnic_type=direct
Public bug reported: When launching an instance with port with vnic_type direct and using nova migrate I get an error: "Device :05:11.5 not found: could not access /sys/bus/pci/devices/:05:11.5/config: No such file or directory" How to Reproduce === #neutron port-create tenant1-net1 --binding:vnic-type direct #nova boot --flavor m1.small --image rhel7 --nic port-id= vm1 #nova migrate After a white run nova show and the error should be in the 'fault' entry. Version === RHEL7.0 openstack-nova-common-2014.2-2.el7ost.noarch openstack-nova-compute-2014.2-2.el7ost.noarch python-nova-2014.2-2.el7ost.noarch ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1400784 Title: Cold migration fails when using vnic_type=direct Status in OpenStack Compute (Nova): New Bug description: When launching an instance with port with vnic_type direct and using nova migrate I get an error: "Device :05:11.5 not found: could not access /sys/bus/pci/devices/:05:11.5/config: No such file or directory" How to Reproduce === #neutron port-create tenant1-net1 --binding:vnic-type direct #nova boot --flavor m1.small --image rhel7 --nic port-id= vm1 #nova migrate After a white run nova show and the error should be in the 'fault' entry. Version === RHEL7.0 openstack-nova-common-2014.2-2.el7ost.noarch openstack-nova-compute-2014.2-2.el7ost.noarch python-nova-2014.2-2.el7ost.noarch To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1400784/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400770] [NEW] fail to upload object if swift proxy-server is deployed in apache 2.4
Public bug reported:
fail to upload object if swift proxy-server is deployed in apache 2.4:
Environment:
Ubuntu 14.04.1 LTS
horizon (github master branch source code install)
python-swiftclient (github master branch source code install)
swift (github master branch source code install)
Apache/2.4.7 log:
[Sun Dec 07 00:26:55.329422 2014] [:error] [pid 18608:tid 140692826650368]
WARNING:urllib3.connectionpool:HttpConnectionPool is full, discarding
connection: 192.168.1.151
[Sun Dec 07 00:26:55.329525 2014] [:error] [pid 18608:tid 140692826650368] REQ:
curl -i
http://192.168.1.151:8080/v1/AUTH_faf24933fa804ece91c2da2afdfa4127/testestset/setup.py
-X PUT -H "X-Auth-Token: 312a22b6c61b43e08455303003fc72a0"
[Sun Dec 07 00:26:55.329935 2014] [:error] [pid 18608:tid 140692826650368] RESP
STATUS: 411 Length Required
[Sun Dec 07 00:26:55.330003 2014] [:error] [pid 18608:tid 140692826650368] RESP
HEADERS: [('date', 'Sat, 06 Dec 2014 16:26:55 GMT'), ('content-length', '318'),
('content-type', 'text/html; charset=iso-8859-1'), ('connection', 'close'),
('server', 'Apache/2.4.7 (Ubuntu)')]
[Sun Dec 07 00:26:55.330050 2014] [:error] [pid 18608:tid 140692826650368] RESP
BODY:
[Sun Dec 07 00:26:55.330058 2014] [:error] [pid 18608:tid 140692826650368]
[Sun Dec 07 00:26:55.330063 2014] [:error] [pid 18608:tid 140692826650368]
411 Length Required
[Sun Dec 07 00:26:55.330068 2014] [:error] [pid 18608:tid 140692826650368]
[Sun Dec 07 00:26:55.330073 2014] [:error] [pid 18608:tid 140692826650368]
Length Required
[Sun Dec 07 00:26:55.330078 2014] [:error] [pid 18608:tid 140692826650368] A
request of the requested method PUT requires a valid Content-length.
[Sun Dec 07 00:26:55.330083 2014] [:error] [pid 18608:tid 140692826650368]
[Sun Dec 07 00:26:55.330088 2014] [:error] [pid 18608:tid 140692826650368]
[Sun Dec 07 00:26:55.330093 2014] [:error] [pid 18608:tid 140692826650368]
Apache/2.4.7 (Ubuntu) Server at 192.168.1.151 Port 8080
[Sun Dec 07 00:26:55.330098 2014] [:error] [pid 18608:tid 140692826650368]
[Sun Dec 07 00:26:55.330103 2014] [:error] [pid 18608:tid 140692826650368]
[Sun Dec 07 00:26:55.330295 2014] [:error] [pid 18608:tid 140692826650368]
Object PUT failed:
http://192.168.1.151:8080/v1/AUTH_faf24933fa804ece91c2da2afdfa4127/testestset/setup.py
411 Length Required [first 60 chars of response]
[Sun Dec 07 00:26:55.330306 2014] [:error] [pid 18608:tid 140692826650368]
http://192.168.1.151:8080/v1/AUTH_faf24933fa804ece91c2da2afdfa4127/testestset/setup.py
411 Length Required [first 60 chars of response]
[Sun Dec 07 00:26:55.330343 2014] [:error] [pid 18608:tid 140692826650368]
http://192.168.1.151:8080/v1/AUTH_faf24933fa804ece91c2da2afdfa4127/testestset/setup.py
411 Length Required [first 60 chars of response]
[Sun Dec 07 00:26:55.330525 2014] [:error] [pid 18608:tid 140692826650368]
http://192.168.1.151:8080/v1/AUTH_faf24933fa804ece91c2da2afdfa4127/testestset/setup.py
-X PUT -H "X-Auth-Token: 312a22b6c61b43e08455303003fc72a0"
HTTP/1.1 411 Length Required
Date: Sat, 06 Dec 2014 16:41:14 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Trans-Id: tx0bff2b699baa499baddbd-00548331aa
Content-Length: 30
Connection: close
Content-Type: text/plain
Missing Content-Length header.
Horizon Code:
openstack_dashboard/dashboards/swift.py:
def swift_upload_object(request, container_name, object_name,
object_file=None):
headers = {}
size = 0
if object_file:
headers['X-Object-Meta-Orig-Filename'] = object_file.name
size = object_file.size
** Affects: horizon
Importance: Undecided
Assignee: LIU Yulong (dragon889)
Status: In Progress
** Summary changed:
- fail to upload object if swift proxy-server is in apache 2.4
+ fail to upload object if swift proxy-server is deployed in apache 2.4
** Description changed:
- fail to upload object if swift proxy-server is in apache 2.4:
+ fail to upload object if swift proxy-server is deployed in apache 2.4:
Environment:
Ubuntu 14.04.1 LTS
horizon (github master branch source code install)
swift-client (github master branch source code install)
swift (github master branch source code install)
Apache/2.4.7 log:
[Sun Dec 07 00:26:55.329422 2014] [:error] [pid 18608:tid 140692826650368]
WARNING:urllib3.connectionpool:HttpConnectionPool is full, discarding
connection: 192.168.1.151
[Sun Dec 07 00:26:55.329525 2014] [:error] [pid 18608:tid 140692826650368]
REQ: curl -i
http://192.168.1.151:8080/v1/AUTH_faf24933fa804ece91c2da2afdfa4127/testestset/setup.py
-X PUT -H "X-Auth-Token: 312a22b6c61b43e08455303003fc72a0"
[Sun Dec 07 00:26:55.329935 2014] [:error] [pid 18608:tid 140692826650368]
RESP STATUS: 411 Length Required
[Sun Dec 07 00:26:55.330003 2014] [:error] [pid 18608:tid 140692826650368]
RESP HEADERS: [('date', 'Sat, 06 Dec 2014 16:26:55 GMT'), ('content-length',
'318'), ('content-type', 'text/html; charset=iso-8859-1'), ('connection',
'close'), ('server', 'Apache
[Yahoo-eng-team] [Bug 1400764] [NEW] Compute manager NotFound exception inconsistent
Public bug reported: Nova compute manager calls the compute driver to get the instance state in both _get_power_state() and _query_driver_power_state_and_sync(), however it's inconsistent in what exception is expected when an instance does not exist. In _get_power_state() it expects NotFound and returns NOSTATE In _query_driver_power_state_and_sync() it expects InstanceNotFound and uses NOSTATE as the current instance state. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1400764 Title: Compute manager NotFound exception inconsistent Status in OpenStack Compute (Nova): New Bug description: Nova compute manager calls the compute driver to get the instance state in both _get_power_state() and _query_driver_power_state_and_sync(), however it's inconsistent in what exception is expected when an instance does not exist. In _get_power_state() it expects NotFound and returns NOSTATE In _query_driver_power_state_and_sync() it expects InstanceNotFound and uses NOSTATE as the current instance state. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1400764/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400737] [NEW] An index name is inappropriate to a naming convention
Public bug reported: The index added in the 54 version was named inappropriate to the naming convention used by models. Need to fix index name. ** Affects: keystone Importance: Undecided Assignee: Ilya Pekelny (i159) Status: In Progress ** Changed in: keystone Assignee: (unassigned) => Ilya Pekelny (i159) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1400737 Title: An index name is inappropriate to a naming convention Status in OpenStack Identity (Keystone): In Progress Bug description: The index added in the 54 version was named inappropriate to the naming convention used by models. Need to fix index name. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1400737/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400725] [NEW] Typo in a unittest for allowed-address-pairs extension which may lead to false-positives
Public bug reported: http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/unit/test_extension_allowedaddresspairs.py#n263 The right alias for the security-group extension is 'security-group' and not 'security-groups', with this typo, the if block will be skipped and in most of the time will cause the test to pass but not for the right reason. ** Affects: neutron Importance: Undecided Assignee: Roey Chen (roeyc) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1400725 Title: Typo in a unittest for allowed-address-pairs extension which may lead to false-positives Status in OpenStack Neutron (virtual network service): In Progress Bug description: http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/unit/test_extension_allowedaddresspairs.py#n263 The right alias for the security-group extension is 'security-group' and not 'security-groups', with this typo, the if block will be skipped and in most of the time will cause the test to pass but not for the right reason. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1400725/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1397489] Re: VM boot failure since nova to neutron port notification fails
** Changed in: neutron Assignee: (unassigned) => KaiLin (linkai3) ** No longer affects: nova -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1397489 Title: VM boot failure since nova to neutron port notification fails Status in OpenStack Neutron (virtual network service): New Bug description: When I run the latest devstack and use nova boot to create a VM,but it failed. Nova show the VM,it show:"message": "Build of instance cb509a04-ca8a- 491f-baf1-be01b15f4946 aborted: Failed to allocate the network(s), not rescheduling.", "code": 500, "details": " File \"/opt/stack/nova/nova/compute/manager.py\", line 2030, in _do_build_and_run_instance and the following error in the nova-compute.log: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1714, in _spawn block_device_info) File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2266, in spawn block_device_info) File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3681, in _create_domain_and_network raise exception.VirtualInterfaceCreateException() VirtualInterfaceCreateException: Virtual Interface creation failed Adding "vif_plugging_is_fatal = False" and "vif_plugging_timeout = 5" to the compute nodes stops the missing message from being fatal and guests can then be spawned normally and accessed over the network. In the bug: https://bugs.launchpad.net/nova/+bug/1348103 says it happened in cells environment,but it doesn't happen only in cells environment.This problem should arouse our attention more. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1397489/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400667] Re: Unclear message is displayed while deleting a network
** Project changed: nova => horizon -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1400667 Title: Unclear message is displayed while deleting a network Status in OpenStack Dashboard (Horizon): New Bug description: If a network is associated with a vm and if we try to delete it then it raises following error: Error: Failed to delete network 000550a1-0465-491d-9d44-01fa4f5cfaff which is very unclear to the user. I don't know whether horizon knows the reason or not but if horizon have the reason then it should get displayed. Error should be like: Error: Unable to delete network. Steps to reproduce: 1. Create a network. 2. Launch an instance and assign new network to the vm. 3. Try to delete the network I am using stable-icehouse To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1400667/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400667] [NEW] Unclear message is displayed while deleting a network
Public bug reported: If a network is associated with a vm and if we try to delete it then it raises following error: Error: Failed to delete network 000550a1-0465-491d-9d44-01fa4f5cfaff which is very unclear to the user. I don't know whether horizon knows the reason or not but if horizon have the reason then it should get displayed. Error should be like: Error: Unable to delete network. Steps to reproduce: 1. Create a network. 2. Launch an instance and assign new network to the vm. 3. Try to delete the network I am using stable-icehouse ** Affects: nova Importance: Undecided Assignee: Kanchan Gupta (kanchan-gupta1) Status: New ** Changed in: nova Assignee: (unassigned) => Kanchan Gupta (kanchan-gupta1) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1400667 Title: Unclear message is displayed while deleting a network Status in OpenStack Compute (Nova): New Bug description: If a network is associated with a vm and if we try to delete it then it raises following error: Error: Failed to delete network 000550a1-0465-491d-9d44-01fa4f5cfaff which is very unclear to the user. I don't know whether horizon knows the reason or not but if horizon have the reason then it should get displayed. Error should be like: Error: Unable to delete network. Steps to reproduce: 1. Create a network. 2. Launch an instance and assign new network to the vm. 3. Try to delete the network I am using stable-icehouse To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1400667/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1241759] Re: lbaas backup member flag
** Changed in: neutron Status: Triaged => Won't Fix ** Changed in: neutron Assignee: Eugene Nikanorov (enikanorov) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1241759 Title: lbaas backup member flag Status in OpenStack Neutron (virtual network service): Won't Fix Bug description: Haproxy supports a flag on members to tell it not to ever use the member unless all others have failed. This allows you to setup apology servers. I don't see any way to set this flag using the neutron lbaas member settings. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1241759/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1398422] Re: Hard-coded alembic methods in DB heal script is inflexible
Closing per comments above. ** Changed in: neutron Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1398422 Title: Hard-coded alembic methods in DB heal script is inflexible Status in OpenStack Neutron (virtual network service): Won't Fix Bug description: See http://lists.openstack.org/pipermail/openstack- dev/2014-December/051897.html Also see review comments in https://review.openstack.org/137989 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1398422/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1400627] [NEW] HA routers don't show on Network Topology screen
Public bug reported: Legacy routers do. HA routers don't ** Affects: horizon Importance: Undecided Status: New ** Tags: l3-ha ** Tags added: l3-ha -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1400627 Title: HA routers don't show on Network Topology screen Status in OpenStack Dashboard (Horizon): New Bug description: Legacy routers do. HA routers don't To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1400627/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1398992] Re: quota-update succeeds for nonexistent tenant_id
This puts another consistency question: what if, even if we validate tenant_id when creating a quota, it is removed afterwards? It's still an inconsistency. I don't think it makes sense to do anything about it at this point. Quota API is for admins, so it think it's a fair bit of system knowledge that is required to operate quotas. ** Changed in: neutron Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1398992 Title: quota-update succeeds for nonexistent tenant_id Status in OpenStack Neutron (virtual network service): Opinion Bug description: Possibly related to https://bugs.launchpad.net/neutron/+bug/1307506 Issue a CLI request to update the quota for a nonexistent tenant_id (not in keystone tenant-list). The update succeeds and "neutron quota-list" gets a new entry for tenant_id foo. $ neutron quota-update --tenant_id foo --port 75 +-+---+ | Field | Value | +-+---+ | floatingip | 50| | network | 10| | port| 75| | router | 10| | security_group | 10| | security_group_rule | 100 | | subnet | 10| +-+---+ Expected behavior: The CLI (at the very least) or neutron (at most) would prevent this from succeeding. Pardon the whitespace mangling. Can't be helped: https://bugs.launchpad.net/launchpad/+bug/2627 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1398992/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1399149] Re: Horizon does not link to an object when assigning an floating IP to a load balancer
I don't think neutron can be changed in anyway to fix this issue. It's totally related to horizon. ** No longer affects: neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1399149 Title: Horizon does not link to an object when assigning an floating IP to a load balancer Status in OpenStack Dashboard (Horizon): New Bug description: When assigning a floating IP to a load balancer Horizon does not point to any object. Steps to reproduce: Create Pool Add VIP to created pool. Allocate Floating IP to project Associate IP to newly created VIP Instance field is empty When clicking on link - the instances page opens up and an error is presented. Version Icehouse To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1399149/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1399454] Re: Nexus VXLAN gateway: 4K VLANs limitation
VLANs are always limited to 4k per specification (IEEE 802.1Q) ** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1399454 Title: Nexus VXLAN gateway: 4K VLANs limitation Status in OpenStack Neutron (virtual network service): Invalid Bug description: With the Nexus VXLAN gateway, each Compute host still has the 4K VLANs limitation. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1399454/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
