[Yahoo-eng-team] [Bug 1619624] Re: Pagination is not present for Identity-->Projects .

2016-09-07 Thread Brad Pokorny 
Looks like this still works for Keystone v2.0. I just tried it against a
v2.0 endpoint with the latest Horizon master, and the images per page
setting worked.

Horizon just can't support it for v3 yet, since Keystone v3 doesn't
support it.

There was a blueprint for Keystone v3 to support it, but it got shot down:
https://blueprints.launchpad.net/keystone/+spec/pagination

** Changed in: horizon
   Status: Confirmed => Invalid

-- 
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/1619624

Title:
  Pagination is not present for Identity-->Projects .

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  In Mitaka, there is no pagination for Identity-->Projects
  and Number of items per page settings does not work in this page .

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1619624/+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 1618578] [NEW] Image metadata deletion doesn't work from the Update Metadata widget

2016-08-30 Thread Brad Pokorny 
Public bug reported:

Deleting image metadata doesn't work from the Update Metadata widget
when deleting metadata items that have existing metadata definitions. It
works for deleting custom metadata items.

Steps to reproduce:

Start with the latest master Horizon code as of 8/30/16.

- To to Project -> Compute -> Images.
- Select the "Update Metadata" button for an image.
- If you have metadata definitions defined in your glance installation, you 
should see categories for existing metadata definitions under "Available 
Metadata".
- Add a metadata item from the "Available Metadata" categories, such as "Common 
Operating System Properties" -> "OS Version". Give it a value and Save the 
change. This works fine.
- Select the "Update Metadata" button for the same image and note that the 
metadata item you just added (such as os_version) now appears in the "Existing 
Metadata" section.
- Remove the metadata item and click Save.
- No errors are displayed and no errors are written to the Horizon logs.
- Select the "Update Metadata" button for the same image and note that the 
metadata item you just tried to remove is still there.

** 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/1618578

Title:
  Image metadata deletion doesn't work from the Update Metadata widget

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Deleting image metadata doesn't work from the Update Metadata widget
  when deleting metadata items that have existing metadata definitions.
  It works for deleting custom metadata items.

  Steps to reproduce:

  Start with the latest master Horizon code as of 8/30/16.

  - To to Project -> Compute -> Images.
  - Select the "Update Metadata" button for an image.
  - If you have metadata definitions defined in your glance installation, you 
should see categories for existing metadata definitions under "Available 
Metadata".
  - Add a metadata item from the "Available Metadata" categories, such as 
"Common Operating System Properties" -> "OS Version". Give it a value and Save 
the change. This works fine.
  - Select the "Update Metadata" button for the same image and note that the 
metadata item you just added (such as os_version) now appears in the "Existing 
Metadata" section.
  - Remove the metadata item and click Save.
  - No errors are displayed and no errors are written to the Horizon logs.
  - Select the "Update Metadata" button for the same image and note that the 
metadata item you just tried to remove is still there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1618578/+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 1613372] [NEW] Custom properties don't display correctly in image details with angular images

2016-08-15 Thread Brad Pokorny 
Public bug reported:

Steps to reproduce:
- Start with the latest master code
- Set HORIZON_CONFIG.update({"images_panel": "angular"}) in local_settings.py
- Set a metadata property on an image (I set os_distro = centos7, for example)
- Go to Project->Compute->Images. Note that "OS Distro" is correctly displayed 
with its value in the drawer of the image.
- Click on the image name to show the image details page. Under "Custom 
Properties", "os_distro" shows up as a property, but its value isn't shown. See 
http://imgur.com/a/eUYql

** Affects: horizon
 Importance: Undecided
 Status: New


** Tags: angularjs glance

** Tags added: angularjs glance

-- 
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/1613372

Title:
  Custom properties don't display correctly in image details with
  angular images

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Steps to reproduce:
  - Start with the latest master code
  - Set HORIZON_CONFIG.update({"images_panel": "angular"}) in local_settings.py
  - Set a metadata property on an image (I set os_distro = centos7, for example)
  - Go to Project->Compute->Images. Note that "OS Distro" is correctly 
displayed with its value in the drawer of the image.
  - Click on the image name to show the image details page. Under "Custom 
Properties", "os_distro" shows up as a property, but its value isn't shown. See 
http://imgur.com/a/eUYql

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1613372/+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 1596691] [NEW] Delete port confirmation is missing port name or ID

2016-06-27 Thread Brad Pokorny 
Public bug reported:

Steps to reproduce:

- This can be reproduced using the latest master code as of 6/27/16.

- Go to Admin -> System -> Networks -> select a network -> Ports tab ->
select a port -> Click "Delete Port"

The "Confirm Delete Port" text says:

"You have selected: . Please confirm your selection. This action cannot
be undone."

So we are missing the port name or ID.

This applies to other resources as well, such as Subnets.

** 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/1596691

Title:
  Delete port confirmation is missing port name or ID

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Steps to reproduce:

  - This can be reproduced using the latest master code as of 6/27/16.

  - Go to Admin -> System -> Networks -> select a network -> Ports tab
  -> select a port -> Click "Delete Port"

  The "Confirm Delete Port" text says:

  "You have selected: . Please confirm your selection. This action
  cannot be undone."

  So we are missing the port name or ID.

  This applies to other resources as well, such as Subnets.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1596691/+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 1595335] [NEW] Add image location fails when show_multiple_locations = false

2016-06-22 Thread Brad Pokorny 
Public bug reported:

Background:
I'm working on getting full glance v2 support into Horizon with this patch: 
https://review.openstack.org/#/c/320039/

I provided the curl calls below for clarity to reproduce this, but
Horizon uses python-glanceclient to send the REST api calls.

I reproduced this issue with the latest devstack as of 6/22/16 on ubuntu
14.04.

Steps to reproduce:

1. Create an image via the glance v2 api (seems to work fine):
curl -g -i -X POST -H 'Accept-Encoding: gzip, deflate' -H 'Accept: */*' -H 
'User-Agent: python-glanceclient' -H 'Connection: keep-alive' -H 'X-Auth-Token: 
[token]' -H 'Content-Type: application/json' -d '{"name": "testimage", 
"container_format": "bare", "min_ram": 0, "disk_format": "iso", "visibility": 
"private", "protected": false, "min_disk": 0}' 
http://192.168.43.128:9292/v2/images

{"status": "queued", "name": "bradtest", "tags": [], "container_format":
"bare", "created_at": "2016-06-22T13:29:03Z", "size": null,
"disk_format": "iso", "updated_at": "2016-06-22T13:29:03Z",
"visibility": "private", "self":
"/v2/images/a507654f-9315-4677-ba68-417eedc49810", "min_disk": 0,
"protected": false, "id": "a507654f-9315-4677-ba68-417eedc49810",
"file": "/v2/images/a507654f-9315-4677-ba68-417eedc49810/file",
"checksum": null, "owner": "21856121680744f9b8da04a3f9290c03",
"virtual_size": null, "min_ram": 0, "schema": "/v2/schemas/image"}


2. Update the image with a location:
curl -g -i -X PATCH -H 'Accept-Encoding: gzip, deflate' -H 'Accept: */*' -H 
'User-Agent: python-glanceclient' -H 'Connection: keep-alive' -H 'X-Auth-Token: 
[token]' -H 'Content-Type: application/openstack-images-v2.1-json-patch' -d 
'[{"path": "/locations/-", "value": {"url": 
"http://mirrors.liquidweb.com/CentOS/7/isos/x86_64/CentOS-7-x86_64-Minimal-1511.iso;,
 "metadata": {}}, "op": "add"}]' 
http://192.168.43.128:9292/v2/images/a507654f-9315-4677-ba68-417eedc49810

The update call fails with this error:

403 Forbidden
It's not allowed to add locations if locations are invisible.


I see this in the glance-api log:

2016-06-22 07:17:35.083 29566 INFO eventlet.wsgi.server [req-ec3f939f-
fa7c-4c79-804a-09a3b5904b8d 94c7ed5c69984ce39ea89bc1337807d7
21856121680744f9b8da04a3f9290c03 - - -] 192.168.43.128 - - [22/Jun/2016
07:17:35] "PATCH /v2/images/06afff49-8658-4e58-a28a-fd6e02a379c0
HTTP/1.1" 403 295 0.045951


If I set show_multiple_locations = true, the error doesn't occur. So
that's a workaround, but there are security implications to setting that
value.

It's entirely possible we're doing something wrong in Horizon when using
the v2 api, but I'm wondering if this behavior from the v2 api is
expected.

** Affects: glance
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1595335

Title:
  Add image location fails when show_multiple_locations = false

Status in Glance:
  New

Bug description:
  Background:
  I'm working on getting full glance v2 support into Horizon with this patch: 
https://review.openstack.org/#/c/320039/

  I provided the curl calls below for clarity to reproduce this, but
  Horizon uses python-glanceclient to send the REST api calls.

  I reproduced this issue with the latest devstack as of 6/22/16 on
  ubuntu 14.04.

  Steps to reproduce:

  1. Create an image via the glance v2 api (seems to work fine):
  curl -g -i -X POST -H 'Accept-Encoding: gzip, deflate' -H 'Accept: */*' -H 
'User-Agent: python-glanceclient' -H 'Connection: keep-alive' -H 'X-Auth-Token: 
[token]' -H 'Content-Type: application/json' -d '{"name": "testimage", 
"container_format": "bare", "min_ram": 0, "disk_format": "iso", "visibility": 
"private", "protected": false, "min_disk": 0}' 
http://192.168.43.128:9292/v2/images

  {"status": "queued", "name": "bradtest", "tags": [],
  "container_format": "bare", "created_at": "2016-06-22T13:29:03Z",
  "size": null, "disk_format": "iso", "updated_at":
  "2016-06-22T13:29:03Z", "visibility": "private", "self":
  "/v2/images/a507654f-9315-4677-ba68-417eedc49810", "min_disk": 0,
  "protected": false, "id": "a507654f-9315-4677-ba68-417eedc49810",
  "file": "/v2/images/a507654f-9315-4677-ba68-417eedc49810/file",
  "checksum": null, "owner": "21856121680744f9b8da04a3f9290c03",
  "virtual_size": null, "min_ram": 0, "schema": "/v2/schemas/image"}

  
  2. Update the image with a location:
  curl -g -i -X PATCH -H 'Accept-Encoding: gzip, deflate' -H 'Accept: */*' -H 
'User-Agent: python-glanceclient' -H 'Connection: keep-alive' -H 'X-Auth-Token: 
[token]' -H 'Content-Type: application/openstack-images-v2.1-json-patch' -d 
'[{"path": "/locations/-", "value": {"url": 
"http://mirrors.liquidweb.com/CentOS/7/isos/x86_64/CentOS-7-x86_64-Minimal-1511.iso;,
 "metadata": {}}, "op": "add"}]' 
http://192.168.43.128:9292/v2/images/a507654f-9315-4677-ba68-417eedc49810

  The update call fails with this error:

  403 Forbidden
  It's

[Yahoo-eng-team] [Bug 1566455] Re: Using V3 Auth throws error TypeError at /auth/login/ __init__() got an unexpected keyword argument 'unscoped'

2016-06-09 Thread Brad Pokorny 
The DOA patch has been abandoned, since stable/kilo will soon be EOL.

** Also affects: django-openstack-auth
   Importance: Undecided
   Status: New

** Changed in: django-openstack-auth
   Status: New => In Progress

** Changed in: django-openstack-auth
 Assignee: (unassigned) => Brad Pokorny (bpokorny)

** Changed in: horizon
   Status: In Progress => Invalid

-- 
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/1566455

Title:
  Using V3 Auth throws error TypeError at /auth/login/ __init__() got an
  unexpected keyword argument 'unscoped'

Status in django-openstack-auth:
  In Progress
Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  PasswordPlugin class creates a plugin with 'unscoped' parameter. This
  is throwing the following error:

  TypeError at /auth/login/
  __init__() got an unexpected keyword argument 'unscoped'

  LOG.debug('Attempting to authenticate for %s', username)
  if utils.get_keystone_version() >= 3:
  return v3_auth.Password(auth_url=auth_url,
  username=username,
  password=password,
  user_domain_name=user_domain_name,
  unscoped=True) ---> 
Deleting this line removes the error and authenticates successfully.
  else:
  return v2_auth.Password(auth_url=auth_url,
  username=username,
  password=password) 

  I have V3 API and URL configured in Horizon settings. Using Horizon
  Kilo version.

  Is there some other setting that is needed?

To manage notifications about this bug go to:
https://bugs.launchpad.net/django-openstack-auth/+bug/1566455/+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 1571875] Re: Domain role hidden by project role

2016-05-11 Thread Brad Pokorny 
After looking back into the code, I remembered why we made it work this
way. The Admin dashboard is for users who can perform admin operations
across services. Only Keystone understands domains, so for a user to
have access to all things the Admin dashboard lets them do, the user
needs to be a cloud admin from a Keystone perspective *and* have the
admin role on the project they're scoped to. So if both of those
conditions aren't met, we hide the admin dashboard.

To give people a fighting chance at figuring this out, I added a new
"Cloud Admin Confusion" section to my blog post (might take a few hours
to reflect the update publicly):

https://www-secure.symantec.com/connect/blogs/domain-support-horizon-
here

In summary, yes, this is confusing, but we had to do it this way
because.. OpenStack.

I'll invalidate this bug, but let me know if there are any questions.

** Changed in: keystone
   Status: New => Invalid

** Changed in: horizon
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1571875

Title:
  Domain role hidden by project role

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  Follow the steps below to see the problem.

  1. From the CLI, create a user and assign admin role to the default
  domain but assign no projects. Log into horizon, you will see the
  admin dashboard available to you.

  2. From the CLI, assign the user to the demo project and give the user
  the _member_ role. Log into horizon, you will no longer see the admin
  dashboard.

  Horizon automatically detects the projects you are assigned to and
  scope you to that project instantly. There needs to be a way to
  unscope the project so you can do admin related things. I think we
  need an option to uncheck the project so that you can log in under the
  domain role.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1571875/+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 1567634] Re: tox -e py34 is not working in horizon

2016-04-07 Thread Brad Pokorny 
This will be handled with this blueprint:
https://blueprints.launchpad.net/horizon/+spec/enhance-tox

** Changed in: horizon
   Status: New => Invalid

-- 
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/1567634

Title:
  tox -e py34 is not working in horizon

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  when i got the lasted horizon code and run tox -e py34.

  It got a lot of errors like bellow.

  It seem it is connected with novaclient.

  novaclient release 3.4 version on 2016-04-08.

  ==
  ERROR: openstack_dashboard.test.test_data.utils.load_test_data
  --
  Traceback (most recent call last):
File 
"/home/chenpengzi/timetest/horizon/.tox/py34/lib/python3.4/site-packages/nose/case.py",
 line 198, in runTest
  self.test(*self.arg)
File 
"/home/chenpengzi/timetest/horizon/openstack_dashboard/test/test_data/utils.py",
 line 44, in load_test_data
  return TestData(*loaders)
File 
"/home/chenpengzi/timetest/horizon/openstack_dashboard/test/test_data/utils.py",
 line 70, in __init__
  data_func(self)
File 
"/home/chenpengzi/timetest/horizon/openstack_dashboard/test/test_data/nova_data.py",
 line 570, in data
  TEST.usages.add(usage_obj_2)
File 
"/home/chenpengzi/timetest/horizon/openstack_dashboard/test/test_data/utils.py",
 line 90, in add
  if obj not in self._objects:
File 
"/home/chenpengzi/timetest/horizon/.tox/py34/lib/python3.4/site-packages/novaclient/base.py",
 line 204, in __eq__
  if hasattr(self, 'id') and hasattr(other, 'id'):
File 
"/home/chenpengzi/timetest/horizon/.tox/py34/lib/python3.4/site-packages/novaclient/base.py",
 line 173, in __getattr__
  self.get()
File 
"/home/chenpengzi/timetest/horizon/.tox/py34/lib/python3.4/site-packages/novaclient/v2/usage.py",
 line 35, in get
  start = oslo_utils.timeutils.parse_strtime(self.start, fmt=fmt)
File 
"/home/chenpengzi/timetest/horizon/.tox/py34/lib/python3.4/site-packages/oslo_utils/timeutils.py",
 line 97, in parse_strtime
  return datetime.datetime.strptime(timestr, fmt)
File "/usr/lib/python3.4/_strptime.py", line 500, in _strptime_datetime
  tt, fraction = _strptime(data_string, format)
File "/usr/lib/python3.4/_strptime.py", line 337, in _strptime
  (data_string, format))
  ValueError: time data '2012-01-01 00:00:00' does not match format 
'%Y-%m-%dT%H:%M:%S.%f'

  Slowest 5 tests took 1.23 secs:
  0.35NeutronApiTests.test_port_create_with_policy_profile
  0.28VPNTests.test_add_ipsecpolicy_get
  0.24
NetworkSubnetTests.test_subnet_create_post_invalid_pools_ip_network_with_subnetpool
  0.19InstanceAjaxTests.test_row_update
  0.16SecurityGroupsNeutronTests.test_detail_delete_rule_exception
  --
  Ran 1549 tests in 8.361s

  FAILED (SKIP=11, errors=1538)
  Destroying test database for alias 'default'...
  ERROR: InvocationError: 
'/home/chenpengzi/timetest/horizon/.tox/py34/bin/python -u manage.py test 
--settings=openstack_dashboard.test.settings 
--exclude-dir=openstack_dashboard/test/integration_tests openstack_dashboard'
  
___
 summary 
___
  ERROR:   py34: commands failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1567634/+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 1440244] Re: Horizon throws unauthorized error for cloud admin when domain feature is setup

2016-03-15 Thread Brad Pokorny 
This should now be resolved with this patch:
https://review.openstack.org/#/c/148082/

** Changed in: horizon
 Assignee: (unassigned) => Brad Pokorny (bpokorny)

** Changed in: horizon
   Status: New => Fix Released

-- 
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/1440244

Title:
  Horizon throws unauthorized error for cloud admin when domain feature
  is setup

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  I have a devstack running following components
  1.keystone
  2.heat
  3.nova
  4.horizon
  5.cinder

  For this open stack setup I wanted to enable domain feature, define admin 
boundaries. To enable the domains, these changes were made :
  1. Changed the token format from PKI to UUID
  2. added auth_version = v3.0 under [auth_token:fillter] section of all the 
api-paste.ini file of all the services
  3. updated the endpoints to point to v3
  4. restarted all the services
  5. Changed the default keystone policy.json with policy.v3sample.json and set 
the admin_domain_id to default

  I horizons local_settings.py file
  1. set the OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT to True
  2. updated the enpoint to point to localhost:5000/v3

  after all these changes when I try to login into the default domain
  with admin credentials , i get ubale retirve domain list , unable
  retrive project list errors horizons dashboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1440244/+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 1462020] Re: For non Cloud Admin user, Quota and Usage table actions should not be displayed (Keystone v3 Domains)

2016-03-15 Thread Brad Pokorny 
I think this is all handled now that this patch merged:
https://review.openstack.org/#/c/148082/

** Changed in: horizon
   Status: In Progress => Fix Released

-- 
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/1462020

Title:
  For non Cloud Admin user, Quota and Usage table actions should not be
  displayed (Keystone v3 Domains)

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  When domain scoped tokens are used against Keystone v3, the Domain Admin
  user should not have the permissions to manage or list quotas, nor the
  permissions to view usages for projects. These table actions should be
  removed within the Identity/Projects table if the logged in user is not
  the Cloud Admin.

  Note: this bug will only be present when Horizon is configured with a
  keystone v3 policy file and all the dependent patches related to
  domain scoped tokens applied to horizon, keystone, django-openstack-
  auth and python-keystoneclient.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1462020/+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 1332726] Re: Multi-region management from Horizon requires endless authentications

2016-02-25 Thread Brad Pokorny 
I'm going to close this one as won't fix, as there hasn't been any
activity on the original issue for a while, and there's no good way to
solve this in Horizon.

As David mentions, if Keystone tokens can't be authenticated across
regions, the only way to not require logging into a previously logged in
region would be to store extra tokens in the session. That's highly
undesirable.

We deal with this issue in our production environment currently (we
currently use PKI tokens), and our plan is to use Fernet tokens. Fernet
tokens should enable tokens to be authenticated across different
Keystones, as long as the Keystones share Fernet keys.

** Changed in: horizon
   Status: Triaged => Invalid

-- 
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/1332726

Title:
  Multi-region management from Horizon requires endless authentications

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  I am deploying Horizon to manage multiple regions by updating
  AVAILABLE_REGIONS in
  /opt/stack/horizon/openstack_dashboard/local/local_settings.py.

  I notice that it asks for authentication for each region to login -
  which is OK. However, once authenticated for all regions, when I try
  to switch to an already authenticated region, it asks for
  authentication regardless. This makes this solution very annoying.

  Once authenticated for all regions, it should not require to keep
  authenticating.

  Is there a work around for this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1332726/+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 1437407] Re: With using V3 cloud admin policy, domain admin unable to list role assignment for projects in his domain

2016-01-22 Thread Brad Pokorny 
I agree.  This now works in Horizon with the fixes Guang mentioned.

** Changed in: keystone
   Status: In Progress => Fix Committed

** Also affects: python-keystoneclient
   Importance: Undecided
   Status: New

** Changed in: python-keystoneclient
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1437407

Title:
  With using V3 cloud admin policy, domain admin unable to list role
  assignment for projects in his domain

Status in OpenStack Identity (keystone):
  Fix Committed
Status in python-keystoneclient:
  Fix Committed

Bug description:
  With v3 cloud admin policy file, domain admin can assignment roles to
  user for projects in his domain. However, he's unable to list those
  assignment.

  The expectation is that domain admin should be able to list role
  assignments for projects in his own domain.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1437407/+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 1483370] Re: Wishlist: Attach specific metadata within add tenant screen

2016-01-22 Thread Brad Pokorny 
I'll close this one.  Feel free to open a blueprint if there's still a
need for this.  It would be a valuable addition that should be handled
as a new feature.

** Changed in: horizon
   Status: New => Invalid

-- 
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/1483370

Title:
  Wishlist: Attach specific metadata within add tenant screen

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Ability to attach specific metadata to add tenant screen. Example
  need: cloud administrators may require attaching specific metadata to
  a tenant for proper post-processing and inventory of VM

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1483370/+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 1535490] Re: gate-horizon-releasenotes job failing

2016-01-19 Thread Brad Pokorny 
The strange error message about the missing file was just a red herring.
The real issue was that I had some bad formatting in the release notes
file I created.  After fixing the formatting, the releasenotes job
succeeds.

The misleading error message has now been fixed as well, with this
commit:

https://review.openstack.org/#/c/268225/

** Changed in: horizon
   Status: Confirmed => Invalid

-- 
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/1535490

Title:
  gate-horizon-releasenotes job failing

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  When trying to add new release notes, the gate-horizon-releasenotes
  job is failing.

  https://review.openstack.org/#/c/148082/

  The job logs are showing it fails looking for a file that was removed.

  http://logs.openstack.org/82/148082/98/check/gate-horizon-
  releasenotes/eaf7602/console.html

  2016-01-18 23:29:52.017 | reading sources... [100%] unreleased
  2016-01-18 23:29:52.017 | [reno] scanning 
/home/jenkins/workspace/gate-horizon-releasenotes/releasenotes/notes for 
current branch release notes
  2016-01-18 23:29:52.018 | fatal: Path 
'releasenotes/notes/angularize-images-table-api-eb54206cc9ecc329.yaml' does not 
exist in '8ff8e8a00e108f82c3604fe79881a24484e96c4a'
  2016-01-18 23:29:52.019 | 
  2016-01-18 23:29:52.019 | Exception occurred:
  2016-01-18 23:29:52.019 |   File 
"/home/jenkins/workspace/gate-horizon-releasenotes/.tox/releasenotes/local/lib/python2.7/site-packages/reno/formatter.py",
 line 37, in _indent_for_list
  2016-01-18 23:29:52.020 | lines = text.splitlines()
  2016-01-18 23:29:52.020 | AttributeError: 'dict' object has no attribute 
'splitlines'

  Here's the review that removed the file in question:

  https://review.openstack.org/#/c/259279/

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1535490/+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 1535490] [NEW] gate-horizon-releasenotes job failing

2016-01-18 Thread Brad Pokorny 
Public bug reported:

When trying to add new release notes, the gate-horizon-releasenotes job
is failing.

https://review.openstack.org/#/c/148082/

The job logs are showing it fails looking for a file that was removed.

http://logs.openstack.org/82/148082/98/check/gate-horizon-
releasenotes/eaf7602/console.html

2016-01-18 23:29:52.017 | reading sources... [100%] unreleased
2016-01-18 23:29:52.017 | [reno] scanning 
/home/jenkins/workspace/gate-horizon-releasenotes/releasenotes/notes for 
current branch release notes
2016-01-18 23:29:52.018 | fatal: Path 
'releasenotes/notes/angularize-images-table-api-eb54206cc9ecc329.yaml' does not 
exist in '8ff8e8a00e108f82c3604fe79881a24484e96c4a'
2016-01-18 23:29:52.019 | 
2016-01-18 23:29:52.019 | Exception occurred:
2016-01-18 23:29:52.019 |   File 
"/home/jenkins/workspace/gate-horizon-releasenotes/.tox/releasenotes/local/lib/python2.7/site-packages/reno/formatter.py",
 line 37, in _indent_for_list
2016-01-18 23:29:52.020 | lines = text.splitlines()
2016-01-18 23:29:52.020 | AttributeError: 'dict' object has no attribute 
'splitlines'

Here's the review that removed the file in question:

https://review.openstack.org/#/c/259279/

** Affects: horizon
 Importance: Undecided
 Assignee: Brad Pokorny (bpokorny)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) => Brad Pokorny (bpokorny)

-- 
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/1535490

Title:
  gate-horizon-releasenotes job failing

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When trying to add new release notes, the gate-horizon-releasenotes
  job is failing.

  https://review.openstack.org/#/c/148082/

  The job logs are showing it fails looking for a file that was removed.

  http://logs.openstack.org/82/148082/98/check/gate-horizon-
  releasenotes/eaf7602/console.html

  2016-01-18 23:29:52.017 | reading sources... [100%] unreleased
  2016-01-18 23:29:52.017 | [reno] scanning 
/home/jenkins/workspace/gate-horizon-releasenotes/releasenotes/notes for 
current branch release notes
  2016-01-18 23:29:52.018 | fatal: Path 
'releasenotes/notes/angularize-images-table-api-eb54206cc9ecc329.yaml' does not 
exist in '8ff8e8a00e108f82c3604fe79881a24484e96c4a'
  2016-01-18 23:29:52.019 | 
  2016-01-18 23:29:52.019 | Exception occurred:
  2016-01-18 23:29:52.019 |   File 
"/home/jenkins/workspace/gate-horizon-releasenotes/.tox/releasenotes/local/lib/python2.7/site-packages/reno/formatter.py",
 line 37, in _indent_for_list
  2016-01-18 23:29:52.020 | lines = text.splitlines()
  2016-01-18 23:29:52.020 | AttributeError: 'dict' object has no attribute 
'splitlines'

  Here's the review that removed the file in question:

  https://review.openstack.org/#/c/259279/

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1535490/+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 1531674] [NEW] Prevent an admin from removing their own custom admin role

2016-01-06 Thread Brad Pokorny 
Public bug reported:

Horizon currently prevents admins from removing their own "admin" roles
from the currently-scoped project[1]/domain[2].  Now that Horizon
supports custom admin roles[3], we should prevent admins from removing
their custom admin roles.


[1] 
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/identity/projects/workflows.py#L666
[2] 
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/identity/domains/workflows.py#L359
[3] https://review.openstack.org/#/c/123745/

** Affects: horizon
 Importance: Undecided
 Assignee: Brad Pokorny (bpokorny)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) => Brad Pokorny (bpokorny)

-- 
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/1531674

Title:
  Prevent an admin from removing their own custom admin role

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Horizon currently prevents admins from removing their own "admin"
  roles from the currently-scoped project[1]/domain[2].  Now that
  Horizon supports custom admin roles[3], we should prevent admins from
  removing their custom admin roles.

  
  [1] 
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/identity/projects/workflows.py#L666
  [2] 
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/identity/domains/workflows.py#L359
  [3] https://review.openstack.org/#/c/123745/

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1531674/+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 1518134] [NEW] Allow reassociate for associated FIPs

2015-11-19 Thread Brad Pokorny 
Public bug reported:

The Compute -> Access & Security -> Floating IPs tab should provide the
Associate button for FIPs that are already associated.  The nova CLI
allows a user to associate an already associated FIP, with the behavior
being that the FIP is transferred from one VM to another.

$ openstack --debug ip floating add [Already associated IP] [VM to reassign the 
FIP to]

REQ: curl -g -i -X POST https://nova-api.example.com/v2/[project 
ID]/servers/[Instance ID]/action -H "User-Agent: python-novaclient" -H 
"Content-Type: application/json" -H "Accept: application/json" -H 
"X-Auth-Token: {SHA1} [token hash]" -d '{"addFloatingIp": {"address": "[IP 
address]"}}'
"POST /v2/[project ID]/servers/[Instance ID]/action HTTP/1.1" 202 0



The single API call to nova associates the IP with the new VM and disassociates 
it from the old VM.  The CLI behavior is especially useful for service IP's, 
where switching an IP from one VM to another quickly is important.

** Affects: horizon
 Importance: Undecided
 Assignee: Brad Pokorny (bpokorny)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) => Brad Pokorny (bpokorny)

-- 
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/1518134

Title:
  Allow reassociate for associated FIPs

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The Compute -> Access & Security -> Floating IPs tab should provide
  the Associate button for FIPs that are already associated.  The nova
  CLI allows a user to associate an already associated FIP, with the
  behavior being that the FIP is transferred from one VM to another.

  $ openstack --debug ip floating add [Already associated IP] [VM to reassign 
the FIP to]
  
  REQ: curl -g -i -X POST https://nova-api.example.com/v2/[project 
ID]/servers/[Instance ID]/action -H "User-Agent: python-novaclient" -H 
"Content-Type: application/json" -H "Accept: application/json" -H 
"X-Auth-Token: {SHA1} [token hash]" -d '{"addFloatingIp": {"address": "[IP 
address]"}}'
  "POST /v2/[project ID]/servers/[Instance ID]/action HTTP/1.1" 202 0
  

  
  The single API call to nova associates the IP with the new VM and 
disassociates it from the old VM.  The CLI behavior is especially useful for 
service IP's, where switching an IP from one VM to another quickly is important.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1518134/+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 1504234] Re: Checkmarks in project picker in the wrong place

2015-10-09 Thread Brad Pokorny 
Thanks, Lin.  Rerunning collectstatic did the trick.  I didn't
specifically have to drop the static folder, but just ran these
commands:

$ ./manage.py collectstatic
$ ./manage.py compress

And the checkmark is now in the right place.  So seems like we need to
run collectstatic now after switching Horizon to use v3 keystone.

I'll close this bug as invalid.  Could you link the similar bug you
mentioned to this one?

** Changed in: horizon
   Status: Incomplete => Invalid

-- 
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/1504234

Title:
  Checkmarks in project picker in the wrong place

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  The checkmark showing the current project has changed positions in
  some cases and looks strange.  I've seen cases where it's still in the
  right place, but other places where it looks like this:

  http://imgur.com/1oTPf9M

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1504234/+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 1504234] [NEW] Checkmarks in project picker in the wrong place

2015-10-08 Thread Brad Pokorny 
Public bug reported:

The checkmark showing the current project has changed positions in some
cases and looks strange.  I've seen cases where it's still in the right
place, but other places where it looks like this:

http://imgur.com/1oTPf9M

** 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/1504234

Title:
  Checkmarks in project picker in the wrong place

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The checkmark showing the current project has changed positions in
  some cases and looks strange.  I've seen cases where it's still in the
  right place, but other places where it looks like this:

  http://imgur.com/1oTPf9M

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1504234/+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 1426341] Re: loadbalancer not able to associate monitor from the horizon dashboard

2015-06-10 Thread Brad Pokorny 
*** This bug is a duplicate of bug 1398754 ***
https://bugs.launchpad.net/bugs/1398754

** This bug is no longer a duplicate of bug 1404471
   Can't associate a health monitor for a neutron load balance pool
** This bug has been marked a duplicate of bug 1398754
   LBaas v1 Associate Monitor to Pool Fails

-- 
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/1426341

Title:
  loadbalancer not able to associate monitor from the horizon dashboard

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  i try to search around but can't find any answer, even try to post it
  inside ask.openstack.org but no luck. currently running on juno. from
  the dashboard,  when create we create a monitor and click on the
  monitor name we can see it has been assign to a pool. but we run
  command neutron lb-healthmonitor-show MONITORID it shows that the
  monitor haven't being assign to any pools yet.  from the dashboard, we
  cannot associate pool with monitor as it does not show the list of
  available pools.  there is not even a disassociate monitor menu. but
  when we manually associate a monitor to the pool from the cli.  the
  result of lb-healthmonitor-show MONITORID will show that the monitor
  is associated to the pool. and from the dashboard we can see that
  there is a menu to disassociate monitor whereas the associate monitor
  is not shown anymore. i believe this is something wrong with the
  horizon. Please advise if there is something that we can do on our
  side to solve this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1426341/+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 1419070] Re: Dropdown for Domains and Projects always shows Default for Domains

2015-04-03 Thread Brad Pokorny 
After more work with domains, I found the dropdown wasn't changing
because it shows the user domain name, rather than the project domain
name.  If the user is in a domain other than default, I validated the
dropdown does reflect that.

I'll invalidate this bug.

** Changed in: horizon
   Status: New = Invalid

-- 
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/1419070

Title:
  Dropdown for Domains and Projects always shows Default for Domains

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  After logging into Horizon with a domain other than Default, the
  dropdown for Domains and Projects always shows Default for the
  Domains.  It would make more sense to users if it showed the domain
  they logged in with.

  I've been doing some testing with
  https://review.openstack.org/#/c/141153/ and
  https://review.openstack.org/#/c/148082/ , and this situation still
  exists - even though we can now get a token scoped to the domain the
  user logged in with.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1419070/+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 1419996] [NEW] OPENSTACK_KEYSTONE_DEFAULT_DOMAIN in the settings file should be the domain ID

2015-02-09 Thread Brad Pokorny 
Public bug reported:

Per the discussion in https://review.openstack.org/#/c/148082/ ,
OPENSTACK_KEYSTONE_DEFAULT_DOMAIN in local_settings.py should refer to a
domain ID, rather than a domain name.

The comments in the settings file should be updated to reflect this and
the default value should be 'default', as most installations use
'default' for the default domain ID.

** Affects: horizon
 Importance: Undecided
 Assignee: Brad Pokorny (bpokorny)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) = Brad Pokorny (bpokorny)

-- 
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/1419996

Title:
  OPENSTACK_KEYSTONE_DEFAULT_DOMAIN in the settings file should be the
  domain ID

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Per the discussion in https://review.openstack.org/#/c/148082/ ,
  OPENSTACK_KEYSTONE_DEFAULT_DOMAIN in local_settings.py should refer to
  a domain ID, rather than a domain name.

  The comments in the settings file should be updated to reflect this
  and the default value should be 'default', as most installations use
  'default' for the default domain ID.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1419996/+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 1419996] Re: OPENSTACK_KEYSTONE_DEFAULT_DOMAIN in the settings file should be the domain ID

2015-02-09 Thread Brad Pokorny 
Marking this invalid, as it's being handled here:
https://review.openstack.org/#/c/148082/

** Changed in: horizon
   Status: New = Invalid

-- 
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/1419996

Title:
  OPENSTACK_KEYSTONE_DEFAULT_DOMAIN in the settings file should be the
  domain ID

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Per the discussion in https://review.openstack.org/#/c/148082/ ,
  OPENSTACK_KEYSTONE_DEFAULT_DOMAIN in local_settings.py should refer to
  a domain ID, rather than a domain name.

  The comments in the settings file should be updated to reflect this
  and the default value should be 'default', as most installations use
  'default' for the default domain ID.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1419996/+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 1419070] [NEW] Dropdown for Domains and Projects always shows Default for Domains

2015-02-06 Thread Brad Pokorny 
Public bug reported:

After logging into Horizon with a domain other than Default, the
dropdown for Domains and Projects always shows Default for the
Domains.  It would make more sense to users if it showed the domain
they logged in with.

I've been doing some testing with
https://review.openstack.org/#/c/141153/ and
https://review.openstack.org/#/c/148082/ , and this situation still
exists - even though we can now get a token scoped to the domain the
user logged in with.

** 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/1419070

Title:
  Dropdown for Domains and Projects always shows Default for Domains

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  After logging into Horizon with a domain other than Default, the
  dropdown for Domains and Projects always shows Default for the
  Domains.  It would make more sense to users if it showed the domain
  they logged in with.

  I've been doing some testing with
  https://review.openstack.org/#/c/141153/ and
  https://review.openstack.org/#/c/148082/ , and this situation still
  exists - even though we can now get a token scoped to the domain the
  user logged in with.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1419070/+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 1367976] [NEW] Horizon failure when floating IP and port are in different projects

2014-09-10 Thread Brad Pokorny 
Public bug reported:

The Admin - Overview screen returns a 500 error page if a floating IP
is assigned to a different project than one of the ports associated with
the floating IP.

Example floating IP and port:

$ neutron floatingip-show 9ebcde9f-9d9c-497d-bace-799a5fb8de56
+-+--+
| Field   | Value|
+-+--+
| fixed_ip_address| 10.100.0.253 |
| floating_ip_address | 10.116.126.157   |
| floating_network_id | 76c8b58a-5d59-45ec-a48a-6ed22f3648f4 |
| id  | 9ebcde9f-9d9c-497d-bace-799a5fb8de56 |
| port_id | d87e7af3-ad35-409b-b60d-88ebc49f6931 |
| router_id   |  |
| tenant_id   | 3013df710d604ed68ce8e3daf8089386 |
+-+--+
$ neutron port-show d87e7af3-ad35-409b-b60d-88ebc49f6931
+---+-+
| Field | Value 
  |
+---+-+
| admin_state_up| True  
  |
| binding:capabilities  | {port_filter: true} 
  |
| binding:vif_type  | vrouter   
  |
| device_id | 82193f2f-cae1-436e-a1ca-d4a81f753967  
  |
| device_owner  |   
  |
| fixed_ips | {subnet_id: 495f8399-ef52-4a28-9c57-7321148bf38d, 
ip_address: 10.100.0.253} |
| id| d87e7af3-ad35-409b-b60d-88ebc49f6931  
  |
| mac_address   | 02:d8:7e:7a:f3:ad 
  |
| name  | d87e7af3-ad35-409b-b60d-88ebc49f6931  
  |
| network_id| 915b3c98-1ffd-4a26-a193-be8ef55c6999  
  |
| port_security_enabled | True  
  |
| security_groups   | 42714b40-acfe-4231-a6ca-5b5bd7145a45  
  |
| status| ACTIVE
  |
| tenant_id | 2a62c9ba436e46c59a9621a7f1618a83  
  |
+---+-+


Error seen on the Horizon page when debug is enabled:

KeyError at /admin/

u'd87e7af3-ad35-409b-b60d-88ebc49f6931'

Request Method: GET
Request URL:http://example.net/horizon/admin/
Django Version: 1.6.1
Exception Type: KeyError
Exception Value:

u'd87e7af3-ad35-409b-b60d-88ebc49f6931'

Exception Location: 
/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/neutron.py
 in list, line 340
Python Executable:  /usr/bin/python
Python Version: 2.7.6
Python Path:

['/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../..',
 '/usr/lib/python2.7',
 '/usr/lib/python2.7/plat-x86_64-linux-gnu',
 '/usr/lib/python2.7/lib-tk',
 '/usr/lib/python2.7/lib-old',
 '/usr/lib/python2.7/lib-dynload',
 '/usr/local/lib/python2.7/dist-packages',
 '/usr/lib/python2.7/dist-packages',
 '/usr/lib/pymodules/python2.7',
 '/usr/share/openstack-dashboard/',
 '/usr/share/openstack-dashboard/openstack_dashboard']

** 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/1367976

Title:
  Horizon failure when floating IP and port are in different projects

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The Admin - Overview screen returns a 500 error page if a floating IP
  is assigned to a different project than one of the ports associated
  with the floating IP.

  Example floating IP and port:

  $ neutron floatingip-show 9ebcde9f-9d9c-497d-bace-799a5fb8de56
  +-+--+
  | Field   | Value|
  +-+--+
  | fixed_ip_address| 10.100.0.253 |
  | floating_ip_address |

[Yahoo-eng-team] [Bug 1320028] Re: libvirt volume.py's _run_iscsiadm function logs iscsi node.session.auth.password if debug

2014-05-18 Thread Brad Pokorny 
This requires changes to the oslo mask password code as well.

** Also affects: oslo
   Importance: Undecided
   Status: New

** Changed in: oslo
 Assignee: (unassigned) = Brad Pokorny (bpokorny)

-- 
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/1320028

Title:
  libvirt volume.py's _run_iscsiadm function logs iscsi
  node.session.auth.password if debug

Status in OpenStack Compute (Nova):
  In Progress
Status in Oslo - a Library of Common OpenStack Code:
  New

Bug description:
  If debug logging is enabled, the  _run_iscsiadm function in volume.py
  logs the iscsi node.session.auth.password in plain text.

  2014-05-13 08:12:21.915 29013 DEBUG nova.virt.libvirt.volume [req-
  d21bb680-feb9-4242-9d18-057af79d26e8 0
  3112d0d7268b458bb5c997c33cd8a8c0] iscsiadm ('--op', 'update', '-n',
  'node.session.auth.password', '-v', u'password'): stdout= stderr=
  _run_iscsiadm /usr/lib/python2.7/site-
  packages/nova/virt/libvirt/volume.py:248

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1320028/+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 1320028] [NEW] libvirt volume.py's _run_iscsiadm function logs iscsi node.session.auth.password if debug

2014-05-15 Thread Brad Pokorny 
Public bug reported:

If debug logging is enabled, the  _run_iscsiadm function in volume.py
logs the iscsi node.session.auth.password in plain text.

2014-05-13 08:12:21.915 29013 DEBUG nova.virt.libvirt.volume [req-
d21bb680-feb9-4242-9d18-057af79d26e8 0 3112d0d7268b458bb5c997c33cd8a8c0]
iscsiadm ('--op', 'update', '-n', 'node.session.auth.password', '-v',
u'password'): stdout= stderr= _run_iscsiadm /usr/lib/python2.7/site-
packages/nova/virt/libvirt/volume.py:248

** Affects: nova
 Importance: Undecided
 Assignee: Brad Pokorny (bpokorny)
 Status: New

** Changed in: nova
 Assignee: (unassigned) = Brad Pokorny (bpokorny)

-- 
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/1320028

Title:
  libvirt volume.py's _run_iscsiadm function logs iscsi
  node.session.auth.password if debug

Status in OpenStack Compute (Nova):
  New

Bug description:
  If debug logging is enabled, the  _run_iscsiadm function in volume.py
  logs the iscsi node.session.auth.password in plain text.

  2014-05-13 08:12:21.915 29013 DEBUG nova.virt.libvirt.volume [req-
  d21bb680-feb9-4242-9d18-057af79d26e8 0
  3112d0d7268b458bb5c997c33cd8a8c0] iscsiadm ('--op', 'update', '-n',
  'node.session.auth.password', '-v', u'password'): stdout= stderr=
  _run_iscsiadm /usr/lib/python2.7/site-
  packages/nova/virt/libvirt/volume.py:248

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1320028/+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 1207576] Re: python package amqp, should not run in debug mode when nova is in debug mode

2013-12-19 Thread Brad Pokorny 
This one looks to me like something that would affect all OpenStack
projects.  Also, the proposed fix for this one is a change to log.py,
which is synced from oslo to nova.  So the fix should go into oslo so
all projects can take advantage of it.

** Also affects: oslo
   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/1207576

Title:
  python package amqp, should not run in debug mode when nova is in
  debug mode

Status in OpenStack Compute (Nova):
  In Progress
Status in Oslo - a Library of Common OpenStack Code:
  New

Bug description:
  Currently the python package amqp runs in debug mode when nova is in
  debug mode.When specifying debug level logs in nova generally we
  are trying to debug nova not its dependencies. So by default amqp
  and other python dependencies shouldn't be running in debug mode when
  nova is.

  http://logs.openstack.org/47/36947/5/check/gate-tempest-devstack-vm-
  full/37958/logs/screen-n-sch.txt.gz

  2013-07-31 20:52:43.207 28626 DEBUG amqp [-] Start from server, version: 0.9, 
properties: {u'information': u'Licensed under the MPL.  See 
http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright 
(C) 2007-2011 VMware, Inc.', u'capabilities': {u'exchange_exchange_bindings': 
True, u'consumer_cancel_notify': True, u'publisher_confirms': True, 
u'basic.nack': True}, u'platform': u'Erlang/OTP', u'version': u'2.7.1'}, 
mechanisms: [u'PLAIN', u'AMQPLAIN'], locales: [u'en_US'] _start 
/usr/local/lib/python2.7/dist-packages/amqp/connection.py:706
  2013-07-31 20:52:43.208 28626 DEBUG amqp [-] Open OK! _open_ok 
/usr/local/lib/python2.7/dist-packages/amqp/connection.py:592
  2013-07-31 20:52:43.208 28626 DEBUG amqp [-] using channel_id: 1 __init__ 
/usr/local/lib/python2.7/dist-packages/amqp/channel.py:70
  2013-07-31 20:52:43.208 28626 DEBUG amqp [-] Channel open _open_ok 
/usr/local/lib/python2.7/dist-packages/amqp/channel.py:420

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1207576/+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