[Yahoo-eng-team] [Bug 1316924] [NEW] Role can't be changed or added to user after the user is created
Public bug reported: the user can be assigned to a role upon creation, but can't change the role or add another roles anymore ** 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/1316924 Title: Role can't be changed or added to user after the user is created Status in OpenStack Dashboard (Horizon): New Bug description: the user can be assigned to a role upon creation, but can't change the role or add another roles anymore To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1316924/+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 1316928] [NEW] VMware driver does not change compute node state to unavailable after disconnecting from vCenter
Public bug reported: VMware driver does not change compute node state (from :-) to XXX) when it lost connection to vCenter. api_retry_count does not affect it at all. When connection to vCenter is lost and nova-compute is restarted it works. But it does not without restarting. After restart state is changed to XXX and nova-compute is still polling API connection (good behavior) but without restart nova-compute has still smile state despite of SessionConnectionException: NV-06475AF urllib2 error in RetrieveServiceContent: : urlopen error [Errno 113] EHOSTUNREACH Steps to reproduce: 1. Configure nova-compute to connect to VMware vCenter using vmware community driver. 2. Check state of compute-node, it should be available 3. Disconnect vCenter - for example just disconnect network from it 4. Check state of compute-node, it still be available Expected result: compute-node should be unavailable when vCenter is disconnected (maybe after api_retry_count?) without need to restart nova-compute. ** Affects: nova Importance: Undecided Status: New ** Tags: vmware ** Description changed: VMware driver does not change compute node state (from :-) to XXX) when it lost connection to vCenter. api_retry_count does not affect it at all. When connection to vCenter is lost and nova-compute is restarted it works. But it does not without restarting. After restart state is - changeg to XXX and nova-compute is still polling API connection (good + changed to XXX and nova-compute is still polling API connection (good behavior) but without restart nova-compute has still smile state despite of SessionConnectionException: NV-06475AF urllib2 error in RetrieveServiceContent: : urlopen error [Errno 113] EHOSTUNREACH Steps to reproduce: 1. Configure nova-compute to connect to VMware vCenter using vmware community driver. 2. Check state of compute-node, it should be available 3. Disconnect vCenter - for example just disconnect network from it 4. Check state of compute-node, it still be available Expected result: compute-node should be unavailable when vCenter is disconnected (maybe after api_retry_count?) without need to restart nova-compute. -- 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/1316928 Title: VMware driver does not change compute node state to unavailable after disconnecting from vCenter Status in OpenStack Compute (Nova): New Bug description: VMware driver does not change compute node state (from :-) to XXX) when it lost connection to vCenter. api_retry_count does not affect it at all. When connection to vCenter is lost and nova-compute is restarted it works. But it does not without restarting. After restart state is changed to XXX and nova-compute is still polling API connection (good behavior) but without restart nova-compute has still smile state despite of SessionConnectionException: NV-06475AF urllib2 error in RetrieveServiceContent: : urlopen error [Errno 113] EHOSTUNREACH Steps to reproduce: 1. Configure nova-compute to connect to VMware vCenter using vmware community driver. 2. Check state of compute-node, it should be available 3. Disconnect vCenter - for example just disconnect network from it 4. Check state of compute-node, it still be available Expected result: compute-node should be unavailable when vCenter is disconnected (maybe after api_retry_count?) without need to restart nova-compute. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1316928/+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 1316927] [NEW] Make the version of the glance api configurable for the image upload and download
Public bug reported: Nova uses glance client to upload or download the image. However, the version 1 is hard coded. The user cannot switch to another version. We need to add a flag for the configuration like glance_api_version to decide which glance api we are going to use. This part of work has already been done for cinder. ** Affects: nova Importance: Undecided Assignee: Vincent Hou (houshengbo) Status: New ** Changed in: nova Assignee: (unassigned) = Vincent Hou (houshengbo) -- 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/1316927 Title: Make the version of the glance api configurable for the image upload and download Status in OpenStack Compute (Nova): New Bug description: Nova uses glance client to upload or download the image. However, the version 1 is hard coded. The user cannot switch to another version. We need to add a flag for the configuration like glance_api_version to decide which glance api we are going to use. This part of work has already been done for cinder. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1316927/+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 1316935] [NEW] add missing languages
Public bug reported: With https://review.openstack.org/#/c/91523/ there will be added a lot of new language files to Horizon. The new languages should also be added to LANGUAGES in settings.py to be able to use them. ** Affects: horizon Importance: Undecided Assignee: Christian Berendt (berendt) Status: New ** Changed in: horizon Assignee: (unassigned) = Christian Berendt (berendt) -- 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/1316935 Title: add missing languages Status in OpenStack Dashboard (Horizon): New Bug description: With https://review.openstack.org/#/c/91523/ there will be added a lot of new language files to Horizon. The new languages should also be added to LANGUAGES in settings.py to be able to use them. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1316935/+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 1316959] [NEW] neutron unit test py27 failure
Public bug reported: This is likely some download/install related issue. http://logs.openstack.org/18/92018/3/gate/gate-neutron-python27/b57b3c6/console.html The py26 version of this job was successful. ** Affects: neutron Importance: Undecided Status: New ** Affects: openstack-ci Importance: Undecided Status: New ** Also affects: neutron 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/1316959 Title: neutron unit test py27 failure Status in OpenStack Neutron (virtual network service): New Status in OpenStack Core Infrastructure: New Bug description: This is likely some download/install related issue. http://logs.openstack.org/18/92018/3/gate/gate-neutron-python27/b57b3c6/console.html The py26 version of this job was successful. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1316959/+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 1316977] [NEW] implement a storage adapter for HDFS
Public bug reported: HDFS should be usable as storage backend for Glance. ** 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/1316977 Title: implement a storage adapter for HDFS Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: HDFS should be usable as storage backend for Glance. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1316977/+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 1316959] Re: neutron unit test py27 failure
*** This bug is a duplicate of bug 1316486 *** https://bugs.launchpad.net/bugs/1316486 ** This bug is no longer a duplicate of bug 1316906 unittests fail sporadically with import error for test_netscaler_driver ** This bug has been marked a duplicate of bug 1316486 Package is imported instead of module in neutron/tests/unit/services/loadbalancer/drivers/netscaler/test_netscaler_driver.py -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1316959 Title: neutron unit test py27 failure Status in OpenStack Neutron (virtual network service): New Status in OpenStack Core Infrastructure: New Bug description: This is likely some download/install related issue. http://logs.openstack.org/18/92018/3/gate/gate-neutron-python27/b57b3c6/console.html The py26 version of this job was successful. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1316959/+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 1317000] [NEW] notification is not generated for neutron l3-agent-router-add command
Public bug reported: notification_driver is configured in neutron.conf as shown below. notification_driver = neutron.openstack.common.notifier.log_notifier default_notification_level = INFO notification_topics = notifications When an administrator wants to host a particular router to a given l3 agent, then he/she has to execute the below command. neutron l3-agent-router-add as shown in the below example. root@preetictl:/usr/share/pyshared/neutron/db# neutron agent-list +--++--+---++ | id | agent_type | host | alive | admin_state_up | +--++--+---++ | 1d7de23f-318b-42ce-af0b-4bf359bf43ba | L3 agent | preetinn | :-) | True | | 3e6e04f3-9dd2-412a-a5e4-cc7d1fb3ef5a | DHCP agent | preetinn | :-) | True | | 7c771b8c-d3ed-47f5-a211-f7106590d021 | Open vSwitch agent | preetinn | :-) | True | | 9c136918-6dc7-4ded-b3bc-e5ddf5d8c8b3 | Metering agent | preetinn | :-) | True | | e5032227-7bf0-4be3-9abe-b97e5f9872ba | Open vSwitch agent | preeticn | :-) | True | | ef17dd6d-99cd-4f23-84d6-e051e3769592 | Metadata agent | preetinn | :-) | True | +--++--+---++root@preetictl:/usr/share/pyshared/neutron/db# neutron router-list root@preetictl:/usr/share/pyshared/neutron/db# neutron router-create r1 Created a new router: +---+--+ | Field | Value| +---+--+ | admin_state_up| True | | external_gateway_info | | | id| bbe93061-1d01-4700-87e7-64775ea0eed1 | | name | r1 | | status| ACTIVE | | tenant_id | 27f36508a3e1417facfac0d0809a1740 | +---+--+ root@preetictl:/usr/share/pyshared/neutron/db# neutron l3-agent-router-add 1d7de23f-318b-42ce-af0b-4bf359bf43ba bbe93061-1d01-4700-87e7-64775ea0eed1 Added router bbe93061-1d01-4700-87e7-64775ea0eed1 to L3 agent After this operation is successful, a notification is NOT generated although the notification_driver is configured. Similarly, neutron l3-agent-router-remove also does not generate notification. ** Affects: neutron Importance: Undecided Assignee: Maruti Kamat (maruti-kamat) Status: New ** Tags: l3-agent-router-add-remove ** Changed in: neutron Assignee: (unassigned) = Maruti Kamat (maruti-kamat) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1317000 Title: notification is not generated for neutron l3-agent-router-add command Status in OpenStack Neutron (virtual network service): New Bug description: notification_driver is configured in neutron.conf as shown below. notification_driver = neutron.openstack.common.notifier.log_notifier default_notification_level = INFO notification_topics = notifications When an administrator wants to host a particular router to a given l3 agent, then he/she has to execute the below command. neutron l3-agent-router-add as shown in the below example. root@preetictl:/usr/share/pyshared/neutron/db# neutron agent-list +--++--+---++ | id | agent_type | host | alive | admin_state_up | +--++--+---++ | 1d7de23f-318b-42ce-af0b-4bf359bf43ba | L3 agent | preetinn | :-) | True | | 3e6e04f3-9dd2-412a-a5e4-cc7d1fb3ef5a | DHCP agent | preetinn | :-) | True | | 7c771b8c-d3ed-47f5-a211-f7106590d021 | Open vSwitch agent | preetinn | :-) | True | | 9c136918-6dc7-4ded-b3bc-e5ddf5d8c8b3 | Metering agent | preetinn | :-) | True | | e5032227-7bf0-4be3-9abe-b97e5f9872ba | Open vSwitch agent | preeticn | :-) | True | | ef17dd6d-99cd-4f23-84d6-e051e3769592 | Metadata agent | preetinn | :-) | True | +--++--+---++root@preetictl:/usr/share/pyshared/neutron/db# neutron router-list root@preetictl:/usr/share/pyshared/neutron/db# neutron router-create r1 Created a new router: +---+--+ | Field |
[Yahoo-eng-team] [Bug 1317008] [NEW] notification is not generated for neutron dhcp-agent-network-add and dhcp-agent-network-remove commands
Public bug reported: notification_driver is configured in neutron.conf as shown below. notification_driver = neutron.openstack.common.notifier.log_notifier default_notification_level = INFO notification_topics = notifications When an administrator wants to associate a particular network to a given dhcp agent, then he/she has to execute the below command. neutron dhcp-agent-network-add as shown in the below example. root@preetictl:~# neutron agent-list +--++--+---++ | id | agent_type | host | alive | admin_state_up | +--++--+---++ | 1d7de23f-318b-42ce-af0b-4bf359bf43ba | L3 agent | preetinn | :-) | True | | 3e6e04f3-9dd2-412a-a5e4-cc7d1fb3ef5a | DHCP agent | preetinn | :-) | True | | 7c771b8c-d3ed-47f5-a211-f7106590d021 | Open vSwitch agent | preetinn | :-) | True | | 9c136918-6dc7-4ded-b3bc-e5ddf5d8c8b3 | Metering agent | preetinn | :-) | True | | e5032227-7bf0-4be3-9abe-b97e5f9872ba | Open vSwitch agent | preeticn | :-) | True | | ef17dd6d-99cd-4f23-84d6-e051e3769592 | Metadata agent | preetinn | :-) | True | +--++--+---++ root@preetictl:~# neutron net-list +--+++ | id | name | subnets | +--+++ | ab83913b-a66d-428d-96cd-269d7de1d3f3 | net1 | | +--+++ root@preetictl:~# neutron dhcp-agent-network-add 3e6e04f3-9dd2-412a-a5e4-cc7d1fb3ef5a ab83913b-a66d-428d-96cd-269d7de1d3f3 Added network ab83913b-a66d-428d-96cd-269d7de1d3f3 to DHCP agent After this operation is successful, a notification is NOT generated although the notification_driver is configured. Similarly, neutron dhcp-agent-network-remove also does not generate notification. ** Affects: neutron Importance: Undecided Assignee: Maruti Kamat (maruti-kamat) Status: New ** Tags: dhcp-agent-network-add-remove ** Changed in: neutron Assignee: (unassigned) = Maruti Kamat (maruti-kamat) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1317008 Title: notification is not generated for neutron dhcp-agent-network-add and dhcp-agent-network-remove commands Status in OpenStack Neutron (virtual network service): New Bug description: notification_driver is configured in neutron.conf as shown below. notification_driver = neutron.openstack.common.notifier.log_notifier default_notification_level = INFO notification_topics = notifications When an administrator wants to associate a particular network to a given dhcp agent, then he/she has to execute the below command. neutron dhcp-agent-network-add as shown in the below example. root@preetictl:~# neutron agent-list +--++--+---++ | id | agent_type | host | alive | admin_state_up | +--++--+---++ | 1d7de23f-318b-42ce-af0b-4bf359bf43ba | L3 agent | preetinn | :-) | True | | 3e6e04f3-9dd2-412a-a5e4-cc7d1fb3ef5a | DHCP agent | preetinn | :-) | True | | 7c771b8c-d3ed-47f5-a211-f7106590d021 | Open vSwitch agent | preetinn | :-) | True | | 9c136918-6dc7-4ded-b3bc-e5ddf5d8c8b3 | Metering agent | preetinn | :-) | True | | e5032227-7bf0-4be3-9abe-b97e5f9872ba | Open vSwitch agent | preeticn | :-) | True | | ef17dd6d-99cd-4f23-84d6-e051e3769592 | Metadata agent | preetinn | :-) | True | +--++--+---++ root@preetictl:~# neutron net-list +--+++ | id | name | subnets | +--+++ | ab83913b-a66d-428d-96cd-269d7de1d3f3 | net1 | |
[Yahoo-eng-team] [Bug 1311561] Re: editing a flavor changes it's ID
As Cindy indicated, this was done on purpose to avoid inaccuracies in the data (e.g. an instance is associated with flavor A which has 2 CPUs, which is later edited to have 35 CPUs - the initial instance doesn't have that but the data makes it look like it does). I don't think it's wise to switch the behaviour back and forth - so I will mark this as Won't Fix. If you strongly disagree, could you please start a discussion on the dev list [1] so we can come to a final consensus about it? As you noted, this isn't an operation that the CLI or API let you do. Personally I think it was a mistake for Horizon to try and allow it anyway, and it's caused a lot of bugs and confusion. [1] https://wiki.openstack.org/wiki/MailingLists#Future_Development ** Changed in: horizon Status: New = Won't Fix -- 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/1311561 Title: editing a flavor changes it's ID Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: try to edit a flavor in Horizon(in CLI we can only edit extra_spec field for a flavor, so in CLI nova flavor-key doesn't reproduce the bug). So open edit flavor dialog for any of them, change VCPUs or anything else, push save button = ID of the flavor will also change. m1.tiny had id=1, after the change it becomes the uuid and every next edit will change the ID field value... # nova flavor-list +--+---+---+--+---+--+---+-+---+ | ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | +--+---+---+--+---+--+---+-+---+ | 036c428f-3562-4a29-a690-56ed79c57742 | test2 | 50| 60 | 0 | | 4 | 1.0 | True | | 4| m1.large | 8192 | 80 | 0 | | 4 | 1.0 | True | | 5| m1.xlarge | 16384 | 160 | 0 | | 8 | 1.0 | True | | b16fc3d9-7dbf-494d-af06-53bf04b28494 | m1.tiny | 2048 | 10 | 0 | | 1 | 1.0 | True | | e0c68f91-c016-47be-871d-09a23c369115 | m1.medium | 4096 | 40 | 0 | 1024 | 2 | 1.0 | True | +--+---+---+--+---+--+---+-+---+ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1311561/+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 1317011] [NEW] You do not have permission to access the resource: /admin/ when a project is created and switch to it for the first time
Public bug reported: Test step: 1:create a new project 2:switch to this new project test result: You do not have permission to access the resource: /admin/ Login as different user or go back to home page ** Affects: horizon Importance: Undecided Status: New ** Summary changed: - You do not have permission to access the resource: /admin/ when a project is created and switch to it + You do not have permission to access the resource: /admin/ when a project is created and switch to it for the first time -- 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/1317011 Title: You do not have permission to access the resource: /admin/ when a project is created and switch to it for the first time Status in OpenStack Dashboard (Horizon): New Bug description: Test step: 1:create a new project 2:switch to this new project test result: You do not have permission to access the resource: /admin/ Login as different user or go back to home page To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1317011/+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 1317016] [NEW] User are not allowed to delete object which the user created under Container
Public bug reported: Testing step: 1: create a pseudo-folder object pf1 2: delete pf1 Testing result: Error: You are not allowed to delete object: pf1 ** Affects: horizon Importance: Undecided Status: New ** Summary changed: - User are not allowed to delete object which the user created in a under Container + User are not allowed to delete object which the user created under Container -- 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/1317016 Title: User are not allowed to delete object which the user created under Container Status in OpenStack Dashboard (Horizon): New Bug description: Testing step: 1: create a pseudo-folder object pf1 2: delete pf1 Testing result: Error: You are not allowed to delete object: pf1 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1317016/+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 1312833] Re: no error is reported or logged when we fail to create a volume on Image minDisk
*** This bug is a duplicate of bug 1241253 *** https://bugs.launchpad.net/bugs/1241253 This was fixed in Juno and is a duplicate of bug 1241253, I added the potential icehouse-backport tag to the other bug. ** This bug has been marked a duplicate of bug 1241253 Creation of Volume from Image should also validate the volume size is not smaller that min_disk Size of Image -- 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/1312833 Title: no error is reported or logged when we fail to create a volume on Image minDisk Status in OpenStack Dashboard (Horizon): New Bug description: I tried to create a volume from an image and gave the volume size which is less than the glance parameter: --min-disk All I got was an error that I cannot create the volume. there was nothing logged in horizon and since there is no image id it was really problematic trying to find anything in cinder logs. I only managed to debug this by running the cinder create command in cli and getting this error: [root@orange-vdsf ~(keystone_admin)]# cinder create 4 --image-id 6175a441-8cb2-4d35-9b7d-241d51eaa270 ERROR: Invalid input received: Image minDisk size 40 is larger than the volume size 4. (HTTP 400) (Request-ID: req-5b50c2db-19f1-40eb-8237-5f955a90caab) Can we add an error or print something to horizon log? To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1312833/+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 1317041] [NEW] cinder: volume details page does not show the source image details
Public bug reported: Cinder volume can be created from the given glance image. Once the volume is created, horizon does not show the image details in the volume details page. But as a user, i would expect this information should be reported. Technically, cinder stores this information in the volume's image meta data property ** Affects: horizon Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** Changed in: horizon Assignee: (unassigned) = Kanagaraj Manickam (kanagaraj-manickam) -- 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/1317041 Title: cinder: volume details page does not show the source image details Status in OpenStack Dashboard (Horizon): New Bug description: Cinder volume can be created from the given glance image. Once the volume is created, horizon does not show the image details in the volume details page. But as a user, i would expect this information should be reported. Technically, cinder stores this information in the volume's image meta data property To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1317041/+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 1275771] Re: Notifications do not work: AttributeError: 'RequestContext' object has no attribute 'iteritems'
Impacts on ceilometer alarm notification also since the oslo-messaging
switch-over:
2014-05-07 11:38:28.365 25696 DEBUG oslo.messaging._drivers.amqp [-] UNIQUE_ID
is 68d046edf6614bab854170f81aec72f1. _add_unique_id
/usr/lib/python2.7/site-packages/oslo/messaging/_drivers/amqp.py:251
2014-05-07 11:38:28.366 25696 ERROR ceilometer.alarm.evaluator [-] alarm state
update failed
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator Traceback (most
recent call last):
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator File
/opt/stack/ceilometer/ceilometer/alarm/evaluator/__init__.py, line 79, in
_refresh
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator
self.notifier.notify(alarm, previous, reason, reason_data)
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator File
/opt/stack/ceilometer/ceilometer/alarm/rpc.py, line 66, in notify
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator
'reason_data': reason_data})
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator File
/usr/lib/python2.7/site-packages/oslo/messaging/rpc/client.py, line 325, in
cast
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator
self.prepare().cast(ctxt, method, **kwargs)
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator File
/usr/lib/python2.7/site-packages/oslo/messaging/rpc/client.py, line 132, in
cast
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator
self.transport._send(self.target, ctxt, msg)
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator File
/usr/lib/python2.7/site-packages/oslo/messaging/transport.py, line 90, in
_send
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator
timeout=timeout)
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator File
/usr/lib/python2.7/site-packages/oslo/messaging/_drivers/amqpdriver.py, line
386, in send
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator return
self._send(target, ctxt, message, wait_for_reply, timeout)
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator File
/usr/lib/python2.7/site-packages/oslo/messaging/_drivers/amqpdriver.py, line
356, in _send
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator
rpc_amqp.pack_context(msg, context)
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator File
/usr/lib/python2.7/site-packages/oslo/messaging/_drivers/amqp.py, line 212,
in pack_context
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator context_d =
six.iteritems(context.to_dict())
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator File
/usr/lib/python2.7/site-packages/six.py, line 498, in iteritems
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator return
iter(getattr(d, _iteritems)(**kw))
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator AttributeError:
'RequestContext' object has no attribute 'iteritems'
2014-05-07 11:38:28.366 25696 TRACE ceilometer.alarm.evaluator
** Also affects: ceilometer
Importance: Undecided
Status: New
** Changed in: ceilometer
Milestone: None = juno-1
** Changed in: ceilometer
Importance: Undecided = Critical
--
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/1275771
Title:
Notifications do not work: AttributeError: 'RequestContext' object has
no attribute 'iteritems'
Status in OpenStack Telemetry (Ceilometer):
New
Status in OpenStack Compute (Nova):
Fix Released
Status in Messaging API for OpenStack:
Invalid
Bug description:
When enabling notification with notification_driver = messaging, I get
the following:
2014-02-03 14:20:41.152 ERROR oslo.messaging.notify._impl_messaging [-] Could
not send notification to notifications. Payload={'priority': 'INFO',
'_unique_id': 'da748b32fd144c25adc45ba5b393339d', 'event_type':
'compute.instance.create.end', 'timestamp': '2014-02-03 14:20:41.151419',
'publisher_id': 'compute.devstack', 'payload': {'node': u'devstack',
'state_description': '', 'ramdisk_id': u'37ad58df-c587-4bed-9062-9428ca14eaf0',
'created_at': '2014-02-03 14:20:33+00:00', 'access_ip_v6': None, 'disk_gb': 0,
'availability_zone': u'nova', 'terminated_at': '', 'ephemeral_gb': 0,
'instance_type_id': 6, 'instance_flavor_id': '42', 'image_name':
u'cirros-0.3.1-x86_64-uec', 'host': u'devstack', 'fixed_ips':
[FixedIP({'version': 4, 'floating_ips': [], 'label': u'private', 'meta': {},
'address': u'10.0.0.2', 'type': u'fixed'})], 'user_id':
u'6bcbc8f54d65473c9a0c4a55f64fb580', 'message': u'Success', 'deleted_at': '',
'reservation_id': u'r-jycyyveh', 'image_ref_url': u'http://162.209.87.220:9
292/images/7b8d712a-fb31-43b8-8a05-a74d70fd8a11', 'memory_mb': 64, 'root_gb':
0, 'display_name': u'dwq', 'instance_type': 'm1.nano', 'tenant_id':
u'cda1741ff4ef47f48fb3d9d76e302add',
[Yahoo-eng-team] [Bug 1317082] [NEW] LBaaS. When a Vip is created enable subnet selection
Public bug reported: When a Vip is created the user would like to be able to specify a Subnet for the Vip when it is different than the Pool's subnet. The current implementation uses the Pool Subnet and the user is not able to specify a diffrent subnet for the Vip. It is noted, that the LBaaS API for creating VIP DOES support specifying a different Vip subnet. ** Affects: horizon Importance: Undecided Status: New ** Tags: lbaas -- 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/1317082 Title: LBaaS. When a Vip is created enable subnet selection Status in OpenStack Dashboard (Horizon): New Bug description: When a Vip is created the user would like to be able to specify a Subnet for the Vip when it is different than the Pool's subnet. The current implementation uses the Pool Subnet and the user is not able to specify a diffrent subnet for the Vip. It is noted, that the LBaaS API for creating VIP DOES support specifying a different Vip subnet. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1317082/+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 1315014] Re: when using --size to create a qcow2 image image is creates it as raw but reported as qcow2
We don't have a nice way to support this just yet. This may (or may not) be supported in the future once we figure out what to do with image inspections/operations. I'll mark it as invalid for now. ** Changed in: glance Status: New = Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1315014 Title: when using --size to create a qcow2 image image is creates it as raw but reported as qcow2 Status in OpenStack Image Registry and Delivery Service (Glance): Won't Fix Bug description: I tried creating 20GB qcow2 image using --size and the image Here are the problems: 1. the image is not created with the selected size 2. the image is reported as qcow2 in glance-list but qemu-img shows it as raw (since the source image copied is a raw image we seem to be taking that parameter but reporting qcow2). This is create-image from an remote image which is raw: [root@orange-vdsf images(keystone_admin)]# glance image-create --name dafna_zise1 --disk-format qcow2 --container-format bare --copy-from http://download.eng.tlv.redhat.com/pub/rhel/released/RHEL-6/6.4/Appliance/rhel-client-x86_64-ec2-starter-6.4_20130130.0-1-sda.raw --size 2048 +--+--+ | Property | Value| +--+--+ | checksum | None | | container_format | bare | | created_at | 2014-05-01T09:53:04 | | deleted | False| | deleted_at | None | | disk_format | qcow2| | id | 292c11dd-a16b-46a0-b176-d665293273b3 | | is_public| False| | min_disk | 0| | min_ram | 0| | name | dafna_zise1 | | owner| 5502ab8e099843cfa39df71b3037ccd6 | | protected| False| | size | 2048 | | status | queued | | updated_at | 2014-05-01T09:53:04 | +--+--+ [root@orange-vdsf images(keystone_admin)]# glance image-list --human +--+-+-+--+-++ | ID | Name| Disk Format | Container Format | Size| Status | +--+-+-+--+-++ | | 292c11dd-a16b-46a0-b176-d665293273b3 | dafna_zise1 | qcow2 | bare | 19.5MB | saving | | +--+-+-+--+-++ [root@orange-vdsf images(keystone_admin)]# glance image-list --human +--+-+-+--+-++ | ID | Name| Disk Format | Container Format | Size| Status | +--+-+-+--+-++ | | 292c11dd-a16b-46a0-b176-d665293273b3 | dafna_zise1 | qcow2 | bare | 6GB | active | | +--+-+-+--+-++ [root@orange-vdsf images(keystone_admin)]# qemu-img info 292c11dd-a16b-46a0-b176-d665293273b3 image: 292c11dd-a16b-46a0-b176-d665293273b3 file format: raw virtual size: 6.0G (6442451456 bytes) disk size: 6.0G As you can see, the source image was a raw 6GB image. I created a qcow2 image from this image and tried giving it a 20GB size. the image is created as raw but reported as qcow To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1315014/+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 1317094] [NEW] neutron requires list amqplib dependency
Public bug reported: Neutron does not use amqplib directly (only via oslo.messaging or kombu). kombu already depends on either amqp or amqplib, so the extra dep is not necessary. ** Affects: neutron 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/1317094 Title: neutron requires list amqplib dependency Status in OpenStack Neutron (virtual network service): New Bug description: Neutron does not use amqplib directly (only via oslo.messaging or kombu). kombu already depends on either amqp or amqplib, so the extra dep is not necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1317094/+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 1317100] [NEW] User data should be redacted when logging request spec
Public bug reported: The filter scheduler has a Debug level log for the request spec, which includes in the instance properties the base64 encoded user_data. Since this may be used by the user to pass credentials into the VM this field should be redacted in the log enrty. User data is an opaque data blob as far as Nova is concerned (and hence of no practical use for debugging). ** Affects: nova Importance: Undecided Assignee: Phil Day (philip-day) Status: New ** Changed in: nova Assignee: (unassigned) = Phil Day (philip-day) -- 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/1317100 Title: User data should be redacted when logging request spec Status in OpenStack Compute (Nova): New Bug description: The filter scheduler has a Debug level log for the request spec, which includes in the instance properties the base64 encoded user_data. Since this may be used by the user to pass credentials into the VM this field should be redacted in the log enrty. User data is an opaque data blob as far as Nova is concerned (and hence of no practical use for debugging). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1317100/+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 1314102] Re: Horizon fail to send rebuild instance command
img.bytes was replaced with img.size as part of the fix for bug 1258349, which was fixed in time for the Icehouse RC. I cannot reproduce the issue on master. Feel free to reopen if you still see the issues, and give more information about the image you're using. Thank you. ** 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/1314102 Title: Horizon fail to send rebuild instance command Status in OpenStack Dashboard (Horizon): Invalid Bug description: Description of problem: The rebuild command fails when sent from the Horizon. The error in the horizon log is: 2014-04-29 08:51:57,586 27987 ERROR django.request Internal Server Error: /dashboard/project/instances/df65444f-7af6-4a52-a49e-98116c94e76e/rebuild Traceback (most recent call last): File /usr/lib/python2.6/site-packages/django/core/handlers/base.py, line 136, in get_response response = response.render() File /usr/lib/python2.6/site-packages/django/template/response.py, line 104, in render self._set_content(self.rendered_content) File /usr/lib/python2.6/site-packages/django/template/response.py, line 81, in rendered_content content = template.render(context) File /usr/lib/python2.6/site-packages/django/template/loader_tags.py, line 123, in render return compiled_parent._render(context) File /usr/lib/python2.6/site-packages/django/template/base.py, line 134, in _render return self.nodelist.render(context) File /usr/lib/python2.6/site-packages/django/template/base.py, line 823, in render bit = self.render_node(node, context) File /usr/lib/python2.6/site-packages/django/template/debug.py, line 74, in render_node return node.render(context) File /usr/lib/python2.6/site-packages/django/template/loader_tags.py, line 62, in render result = block.nodelist.render(context) File /usr/lib/python2.6/site-packages/django/template/base.py, line 823, in render bit = self.render_node(node, context) File /usr/lib/python2.6/site-packages/django/template/debug.py, line 74, in render_node return node.render(context) File /usr/lib/python2.6/site-packages/django/template/loader_tags.py, line 155, in render return self.render_template(self.template, context) File /usr/lib/python2.6/site-packages/django/template/loader_tags.py, line 137, in render_template output = template.render(context) File /usr/lib/python2.6/site-packages/django/template/base.py, line 140, in render return self._render(context) File /usr/lib/python2.6/site-packages/django/template/base.py, line 134, in _render return self.nodelist.render(context) File /usr/lib/python2.6/site-packages/django/template/base.py, line 823, in render bit = self.render_node(node, context) File /usr/lib/python2.6/site-packages/django/template/debug.py, line 74, in render_node return node.render(context) File /usr/lib/python2.6/site-packages/django/template/defaulttags.py, line 186, in render nodelist.append(node.render(context)) File /usr/lib/python2.6/site-packages/django/template/debug.py, line 87, in render output = force_unicode(output) File /usr/lib/python2.6/site-packages/django/utils/encoding.py, line 71, in force_unicode s = unicode(s) File /usr/lib/python2.6/site-packages/django/forms/forms.py, line 411, in __unicode__ return self.as_widget() File /usr/lib/python2.6/site-packages/django/forms/forms.py, line 458, in as_widget return widget.render(name, self.value(), attrs=attrs) File /usr/lib/python2.6/site-packages/django/forms/widgets.py, line 547, in render options = self.render_options(choices, [value]) File /usr/lib/python2.6/site-packages/django/forms/widgets.py, line 577, in render_options output.append(self.render_option(selected_choices, option_value, option_label)) File /usr/lib/python2.6/site-packages/horizon/utils/fields.py, line 127, in render_option option_label = self.transform(option_label) File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/project/instances/forms.py, line 34, in _image_choice_title gb = filesizeformat(img.bytes) AttributeError: 'NoneType' object has no attribute 'bytes' Version-Release number of selected component (if applicable): python-django-horizon-2013.2.3-1.el6ost.noarch How reproducible: 100% Steps to Reproduce: 1. launch an instance 2. send the rebuild command from the horizon 3. Actual results: the action fails Expected results: The command should reach the nova (at the very least). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1314102/+subscriptions -- Mailing list:
[Yahoo-eng-team] [Bug 1317124] [NEW] Datatables without filters are failing to update
Public bug reported:
If a datatable does not have a filter on it, dynamic updating of the
content is failing
It looks like the first update is attemptd when the page loads, but then in the
javascript console, the following appears...
TypeError: horizon.datatables.qs[$table.attr(...)] is undefined
That is causing further updates to not be attempted.
It looks like horizon.tables.js has the following code.
// Reset quicksearch's data cache.
horizon.datatables.qs[$table.attr('id')].cache();
I think it will work properly if we add the following check
// Reset quicksearch's data cache if necessary
if(horizon.datatables.qs[$table.attr('id')] != undefined) {
horizon.datatables.qs[$table.attr('id')].cache();
}
** 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/1317124
Title:
Datatables without filters are failing to update
Status in OpenStack Dashboard (Horizon):
New
Bug description:
If a datatable does not have a filter on it, dynamic updating of the
content is failing
It looks like the first update is attemptd when the page loads, but then in
the javascript console, the following appears...
TypeError: horizon.datatables.qs[$table.attr(...)] is undefined
That is causing further updates to not be attempted.
It looks like horizon.tables.js has the following code.
// Reset quicksearch's data cache.
horizon.datatables.qs[$table.attr('id')].cache();
I think it will work properly if we add the following check
// Reset quicksearch's data cache if necessary
if(horizon.datatables.qs[$table.attr('id')] != undefined) {
horizon.datatables.qs[$table.attr('id')].cache();
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1317124/+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 1316470] Re: the image file should be saved when refill the Create An Image table
I'm afraid this is a browser restriction, browsers won't let you specify a file by default when loading a form for security reasons, and we're reloading the entire form when there is a validation error. See also: http://stackoverflow.com/questions/7893236/django-form-file- field-disappears-on-form-error ** Changed in: horizon Status: New = Won't Fix -- 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/1316470 Title: the image file should be saved when refill the Create An Image table Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: When uploading an local image file, I forgot to set the image format before clicking Create Image button, so I need to refill the Create An Imagetable. Most content was saved except the image file. I have to reselect the image file and wait for uploading. Considering that uploading an local image usually takes a long time, I think it's better to save the image file in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1316470/+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 1316924] Re: Role can't be changed or added to user after the user is created
A role is only meaningful in the context of a project. If you go to Projects - Modify Users after creating a user, you can adjust their roles for the specific project there. ** 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/1316924 Title: Role can't be changed or added to user after the user is created Status in OpenStack Dashboard (Horizon): Invalid Bug description: the user can be assigned to a role upon creation, but can't change the role or add another roles anymore To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1316924/+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 1252973] Re: Can't control instances from the page other than first
*** This bug is a duplicate of bug 1287093 *** https://bugs.launchpad.net/bugs/1287093 This should be fixed in Icehouse with bug 1287093. ** This bug has been marked a duplicate of bug 1287093 Selected instances are not deleted with pagination -- 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/1252973 Title: Can't control instances from the page other than first Status in OpenStack Dashboard (Horizon): Confirmed Bug description: If you have many instances and want to control them (start/stop/restart etc.) from Horizon it does work only from the first page (20 items per page by default). If you click more and go to another page, then no errors/warns logged at all, you are not receiving success notification on action in Horizon and instance stays untouched. Controlling via nova command from console works fine. You can workaround this issue by setting up Items Per Page to some large value in Settings. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1252973/+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 1317011] Re: You do not have permission to access the resource: /admin/ when a project is created and switch to it for the first time
Did you give yourself the admin role on the new project? The 'admin' dashboard is only available for projects where the logged in user is an admin. I can only reproduce this if I give myself a member role. ** 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/1317011 Title: You do not have permission to access the resource: /admin/ when a project is created and switch to it for the first time Status in OpenStack Dashboard (Horizon): Invalid Bug description: Test step: 1:create a new project 2:switch to this new project test result: You do not have permission to access the resource: /admin/ Login as different user or go back to home page To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1317011/+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 1317180] [NEW] Hyper-v fails to attach volumes when using v1 volume utilites
Public bug reported: The following patch https://github.com/openstack/nova/commit/4c2f36bfe006cb0ef89ca7a706223f30488a182e #diff-5c6ee11140977e63b54542e2ff5763d3R22 caused a regression by changing the eventlet.subprocess.Popen with the builtin subprocess.Popen (by using the nova.utils execute method) without changing the way the args were parsed. In this module, the execution args were parsed separated by whitespaces, which is not allowed by the builtin subprocess.Popen, causing a not found error. This error is returned for example when attaching a volume, at the point where iscsicli tool is used to login the iSCSI target or portal. Trace: http://paste.openstack.org/show/79418/ ** Affects: nova Importance: Undecided Status: New ** Tags: hyper-v volumes -- 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/1317180 Title: Hyper-v fails to attach volumes when using v1 volume utilites Status in OpenStack Compute (Nova): New Bug description: The following patch https://github.com/openstack/nova/commit/4c2f36bfe006cb0ef89ca7a706223f30488a182e #diff-5c6ee11140977e63b54542e2ff5763d3R22 caused a regression by changing the eventlet.subprocess.Popen with the builtin subprocess.Popen (by using the nova.utils execute method) without changing the way the args were parsed. In this module, the execution args were parsed separated by whitespaces, which is not allowed by the builtin subprocess.Popen, causing a not found error. This error is returned for example when attaching a volume, at the point where iscsicli tool is used to login the iSCSI target or portal. Trace: http://paste.openstack.org/show/79418/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1317180/+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 1317174] [NEW] novnc console failure after Icehouse upgrade
Public bug reported: After upgrading my Havana installation to Icehouse, VNC console logins are no longer working (1006 error). The version in use is: openstack-nova-novncproxy-2014.1-2.el6.noarch from RDO. This is the full error in the logs: 2014-05-07 17:12:58.003 13074 AUDIT nova.consoleauth.manager [req-684f9e8d-3c0a-4647-aa66-44f0bb35c4df None None] Checking Token: dbbd1b9b-002f-46b6-bf79-0d90e92c034e, True 2014-05-07 17:12:58.112 13074 ERROR oslo.messaging.rpc.dispatcher [-] Exception during message handling: tuple index out of range Traceback (most recent call last): File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py, line 133, in _dispatch_and_reply incoming.message)) File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py, line 176, in _dispatch return self._do_dispatch(endpoint, method, ctxt, args) File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py, line 122, in _do_dispatch result = getattr(endpoint, method)(ctxt, **new_args) File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/server.py, line 139, in inner return func(*args, **kwargs) File /usr/lib/python2.6/site-packages/nova/compute/manager.py, line 390, in decorated_function args = (_load_instance(args[0]),) + args[1:] IndexError: tuple index out of range 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py, line 133, in _dispatch_and_reply 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py, line 176, in _dispatch 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args) 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py, line 122, in _do_dispatch 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher result = getattr(endpoint, method)(ctxt, **new_args) 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.6/site-packages/nova/consoleauth/manager.py, line 117, in check_token 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher if self._validate_token(context, token): 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.6/site-packages/nova/consoleauth/manager.py, line 108, in _validate_token 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher token['console_type']) 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.6/site-packages/nova/compute/rpcapi.py, line 506, in validate_console_port 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher console_type=console_type) 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/client.py, line 150, in call 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher wait_for_reply=True, timeout=timeout) 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.6/site-packages/oslo/messaging/transport.py, line 90, in _send 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher timeout=timeout) 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.6/site-packages/oslo/messaging/_drivers/amqpdriver.py, line 412, in send 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher return self._send(target, ctxt, message, wait_for_reply, timeout) 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.6/site-packages/oslo/messaging/_drivers/amqpdriver.py, line 405, in _send 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher raise result 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher IndexError: tuple index out of range 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py, line 133, in _dispatch_and_reply 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py, line 176, in _dispatch 2014-05-07 17:12:58.112 13074 TRACE oslo.messaging.rpc.dispatcher
[Yahoo-eng-team] [Bug 1317181] [NEW] do not allow lauch of instances with memory less than 512
Public bug reported: I can create a flavor with 1MB of memory and launch instances. since as far as I know we do not have any computers that run on less than 512MB (even that is rare today) I am not sure allowing less than 512MB should be allowed. ** Affects: nova Importance: Undecided Status: New ** Tags: api -- 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/1317181 Title: do not allow lauch of instances with memory less than 512 Status in OpenStack Compute (Nova): New Bug description: I can create a flavor with 1MB of memory and launch instances. since as far as I know we do not have any computers that run on less than 512MB (even that is rare today) I am not sure allowing less than 512MB should be allowed. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1317181/+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 1311968] Re: Show admin/project instance details in a modal
Ok, thank you for the update. I will close this one in the meantime. ** 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/1311968 Title: Show admin/project instance details in a modal Status in OpenStack Dashboard (Horizon): Invalid Bug description: Today, when we click on the instances we can redirected to the instance details page. Doing so causes us to lose track of where we were previously. This requires us to navigate back to the instances page, and if paginated, requires us to page. It would be nice to have this information show up inside of a dialog instead. Implements: https://blueprints.launchpad.net/horizon/+spec/instance-detail-modal To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1311968/+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 1317208] [NEW] Xen live-migrate with volume attached ends with FIELD_TYPE_ERROR failure
Public bug reported: The relevant portion of an example stack trace is below: 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packa ges/nova/virt/xenapi/vmops.py, line 2316, in attach_block_device_volumes 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher volume_utils.forget_sr(self._session, sr_uuid_map[sr_re f]) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packages/nova/openstack/common/excutils.py, line 68, in __exit__ 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packages/nova/virt/xenapi/vmops.py, line 2307, in attach_block_device_volumes 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher hotplug=False) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packages/nova/virt/xenapi/volumeops.py, line 53, in attach_volume 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher vm_ref = vm_utils.vm_ref_or_raise(self._session, instance_name) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packages/nova/virt/xenapi/vm_utils.py, line 2661, in vm_ref_or_raise 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher vm_ref = lookup(session, instance_name) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packages/nova/virt/xenapi/vm_utils.py, line 1743, in lookup 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher vm_refs = session.call_xenapi(VM.get_by_name_label, name_label) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packages/nova/virt/xenapi/client/session.py, line 179, in call_xenapi 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher return session.xenapi_request(method, args) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packages/XenAPI.py, line 133, in xenapi_request 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher result = _parse_result(getattr(self, methodname)(*full_params)) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packages/XenAPI.py, line 203, in _parse_result 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher raise Failure(result['ErrorDescription']) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher Failure: ['FIELD_TYPE_ERROR', 'label'] attach_block_device_volumes() in nova/virt/xenapi/vmops.py calls attach_volume() in nova/virt/xenapi/volumops.py and passes None for instance_name, and this causes a failure when looking up the vm_ref. ** 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/1317208 Title: Xen live-migrate with volume attached ends with FIELD_TYPE_ERROR failure Status in OpenStack Compute (Nova): New Bug description: The relevant portion of an example stack trace is below: 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packa ges/nova/virt/xenapi/vmops.py, line 2316, in attach_block_device_volumes 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher volume_utils.forget_sr(self._session, sr_uuid_map[sr_re f]) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packages/nova/openstack/common/excutils.py, line 68, in __exit__ 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packages/nova/virt/xenapi/vmops.py, line 2307, in attach_block_device_volumes 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher hotplug=False) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File /opt/rackstack/615.44/nova/lib/python2.6/site-packages/nova/virt/xenapi/volumeops.py, line 53, in attach_volume 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher vm_ref = vm_utils.vm_ref_or_raise(self._session, instance_name) 2014-05-01 10:25:37.027 13905 TRACE oslo.messaging.rpc.dispatcher File
[Yahoo-eng-team] [Bug 1310571] Re: ovs pluging floods auth.log (~200Mb/day)
I don't think there is any change in Neutron code that can be done to avoid logging such messages. ** 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/1310571 Title: ovs pluging floods auth.log (~200Mb/day) Status in OpenStack Neutron (virtual network service): Invalid Status in Ubuntu: New Bug description: ovs plugin floods auth.log with repeative messages: Apr 20 06:25:20 pp3 sudo: neutron : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovs-vsctl --timeout=2 --format=json -- --columns=name,external_ids list Interface Apr 20 06:25:20 pp3 sudo: pam_unix(sudo:session): session opened for user root by (uid=108) Apr 20 06:25:20 pp3 sudo: pam_unix(sudo:session): session closed for user root Those messages has no meaning, I think they should be disabled in rsyslog configuration. Here same bug was fixed by cisco: https://bugs.launchpad.net /openstack-cisco/+bug/1197428 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1310571/+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 1314384] Re: The popup don't appear when click on 'Launch an Instance'
I've changed a wrong parameter in my nova.conf, deleted my temporary files, reset / restart Firefox and now it's solved. ** 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/1314384 Title: The popup don't appear when click on 'Launch an Instance' Status in OpenStack Dashboard (Horizon): Invalid Bug description: When I click on 'Launch Instance', just Loading ... screen is displayed infinitely. I press 'Escape', I click on another control button, this other popup is displayed. When I close (or valid) this new popup, I can see the popup 'Launch an Instance' , like it was in background.. After that, even when the 'Instance' popup is displayed, the Tabs (AccessSecurity, Networking..) are displayed all-in-one tab.. I've tried Horizon with Firefox 26.0 on Linux Mint and Windows 7. This bug is not blocking : Deployment by Horizon (or by nova boot) works perfectly ! To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1314384/+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 1317238] [NEW] Duplicated get_policy_target() method across code
Public bug reported:
This chunk of code is copied all over the place:
def get_policy_target(self, request, datum=None):
project_id = None
if datum:
project_id = getattr(datum, 'tenant_id', None)
return {project_id: project_id}
(Though sometimes with a different key in the return dict.)
Would it make more sense to create a mixin or update a super-class somewhere?
** 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/1317238
Title:
Duplicated get_policy_target() method across code
Status in OpenStack Dashboard (Horizon):
New
Bug description:
This chunk of code is copied all over the place:
def get_policy_target(self, request, datum=None):
project_id = None
if datum:
project_id = getattr(datum, 'tenant_id', None)
return {project_id: project_id}
(Though sometimes with a different key in the return dict.)
Would it make more sense to create a mixin or update a super-class somewhere?
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1317238/+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 1317261] [NEW] auth tests should not require admin token
Public bug reported: Currently all the v3 auth tests are calling self.post(), which eventually going through v3_request() https://github.com/openstack/keystone/blob/master/keystone/tests/test_v3.py#L353 that's always an admin request as auth token is required. But since V3 auth is an unprotected API, there's no need for an auth token in order to make the request. We need to have a optional argument which indicating whether a token is require, and fix all the auth tests to not asking for an auth token in order to make the call. ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1317261 Title: auth tests should not require admin token Status in OpenStack Identity (Keystone): New Bug description: Currently all the v3 auth tests are calling self.post(), which eventually going through v3_request() https://github.com/openstack/keystone/blob/master/keystone/tests/test_v3.py#L353 that's always an admin request as auth token is required. But since V3 auth is an unprotected API, there's no need for an auth token in order to make the request. We need to have a optional argument which indicating whether a token is require, and fix all the auth tests to not asking for an auth token in order to make the call. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1317261/+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 1317181] Re: do not allow lauch of instances with memory less than 512
** Changed in: nova Status: New = Triaged ** Changed in: nova Status: Triaged = Opinion ** Changed in: nova Importance: Undecided = Wishlist -- 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/1317181 Title: do not allow lauch of instances with memory less than 512 Status in OpenStack Compute (Nova): Opinion Bug description: I can create a flavor with 1MB of memory and launch instances. since as far as I know we do not have any computers that run on less than 512MB (even that is rare today) I am not sure allowing less than 512MB should be allowed. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1317181/+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 1271426] Re: protected property change not rejected if a subsequent rule match accepts them
This has been published as OSSN-0013 to the mailing lists (openstack and openstack-dev), and the OpenStack wiki: https://wiki.openstack.org/wiki/OSSN/OSSN-0013 ** Changed in: ossn Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1271426 Title: protected property change not rejected if a subsequent rule match accepts them Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Glance havana series: Fix Released Status in OpenStack Security Notes: Fix Released Bug description: See initial report here: http://lists.openstack.org/pipermail /openstack-dev/2014-January/024861.html What is happening is that if there is a specific rule that would reject an action and a less specific rule that comes after that would accept the action, then the action is being accepted. It should be rejected. This is because we iterate through the property protection rules rather than just finding the first match. This bug does not occur when policies are used to determine property protections, only when roles are used directly. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1271426/+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 1315121] Re: lack of logging when an invalid store is used leads to confusion
Cannot repro in icehouse since it looks like it's loading all stores. Also the section with the warning in icehouse has some deprecation nodes and a to be removed in Juno note, so I'm going to close this one for now. ** Changed in: glance Status: In Progress = Invalid ** Changed in: glance Assignee: Matt Fischer (mfisch) = (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1315121 Title: lack of logging when an invalid store is used leads to confusion Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: EDIT: Havana h.2 is what we're using on Ubuntu When the http method in known_stores is disabled, mistakenly or not, the failure mode is annoyingly silent. I spent a day trying to track down why I could not load images from a URL and the logs were completely non-helpful, even with debug enabled in glance-api. We had enabled the rbd store only after enabling ceph. The only useful output came after enabling default_log_levels=eventlet.wsgi.server=DEBUG. This was the final useful message: File /usr/lib/python2.7/dist-packages/glance/store/location.py, line 73, in get_location_from_uri raise exception.UnknownScheme(scheme=pieces.scheme) UnknownScheme: Unknown scheme 'http' found in URI write /usr/lib/python2.7/dist-packages/glance/common/wsgi.py:98 When a user loads to an invalid store, we should not have to enable esoteric log levels (which we didn't even know about before asking) to find out. root@chrcnc01-control-001:~# glance -v --debug image-create --name coke --min-disk 20 --min-ram 1024 --location http://download.cirros-cloud.net/0.3.2/cirros-0.3.2-x86_64-disk.img --disk-format qcow2 --container-format bare curl -i -X POST -H 'x-image-meta-container_format: bare' -H 'x-image-meta-location: http://download.cirros-cloud.net/0.3.2/cirros-0.3.2-x86_64-disk.img' -H 'x-image-meta-min_disk: 20' -H 'User-Agent: python-glanceclient' -H 'x-image-meta-is_public: False' -H 'x-image-meta-min_ram: 1024' -H 'X-Auth-Token: 0b0bcc164e0f4d1cbba63d9edc13ac8d' -H 'Content-Type: application/octet-stream' -H 'x-image-meta-disk_format: qcow2' -H 'x-image-meta-name: coke' http://1.2.3.4:9292/v1/images HTTP/1.1 500 Internal Server Error date: Thu, 01 May 2014 19:20:53 GMT content-length: 0 content-type: text/plain connection: close Request returned failure status. HTTPInternalServerError (HTTP 500) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1315121/+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 1317314] [NEW] making an image public should be only admin by default
Public bug reported: Uploading an image with --is-public=True should by default only be allowed by the admin. Allowing anyone to upload an image as public is likely a security concern. ** Affects: glance Importance: Undecided Assignee: Aaron Rosen (arosen) Status: In Progress ** Changed in: glance Assignee: (unassigned) = Aaron Rosen (arosen) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1317314 Title: making an image public should be only admin by default Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Bug description: Uploading an image with --is-public=True should by default only be allowed by the admin. Allowing anyone to upload an image as public is likely a security concern. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1317314/+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 1317321] [NEW] Add extra unit test case for more than 1 ephemeral disk in BDM
Public bug reported: There was a comment on https://review.openstack.org/#/c/90583/ (after it was approved for merge) to add an extra test case to handle more than 1 ephemeral disk, as well as correct a comment in the code to be more accurate. The purpose of this bug is to add the extra test case for _get_instance_block_device_info to test more than 1 ephemeral disk and correct one of the comments in _get_instance_block_device_info. ** Affects: nova Importance: Low Assignee: Thang Pham (thang-pham) Status: New ** Changed in: nova Assignee: (unassigned) = Thang Pham (thang-pham) ** Changed in: nova Importance: Undecided = Low ** Description changed: - There was a comment on https://review.openstack.org/#/c/90583/ to add an - extra test case to handle more than 1 ephemeral disk as well as correct - a comment in the code to be more accurate. The purpose of this bug is - to add the extra test case for _get_instance_block_device_info to test - more than 1 ephemeral disk and correct one of the comments in - _get_instance_block_device_info. + There was a comment on https://review.openstack.org/#/c/90583/ (after it + was approved for merge) to add an extra test case to handle more than 1 + ephemeral disk, as well as correct a comment in the code to be more + accurate. The purpose of this bug is to add the extra test case for + _get_instance_block_device_info to test more than 1 ephemeral disk and + correct one of the comments in _get_instance_block_device_info. -- 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/1317321 Title: Add extra unit test case for more than 1 ephemeral disk in BDM Status in OpenStack Compute (Nova): New Bug description: There was a comment on https://review.openstack.org/#/c/90583/ (after it was approved for merge) to add an extra test case to handle more than 1 ephemeral disk, as well as correct a comment in the code to be more accurate. The purpose of this bug is to add the extra test case for _get_instance_block_device_info to test more than 1 ephemeral disk and correct one of the comments in _get_instance_block_device_info. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1317321/+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 1301363] Re: Refactor functional tests to create base class for agent functional tests
** Changed in: neutron Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1301363 Title: Refactor functional tests to create base class for agent functional tests Status in OpenStack Neutron (virtual network service): Fix Released Bug description: I'm writing additional functional tests which require sudo. There is also additional shared code from some existing agent tests which would be nice to use. It makes sense to refactor the functional tests to provide a base class which all these classes can inherit from. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1301363/+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 1301101] Re: Add functional tests to verify VXLAN support
** Changed in: neutron Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1301101 Title: Add functional tests to verify VXLAN support Status in OpenStack Neutron (virtual network service): Fix Released Bug description: Functional tests to verify that a host can support VXLAN are needed. These can also test the logic in ovs_lib and compare the results of the functional test to the ovs_lib result. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1301101/+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 1317363] [NEW] Unable to update external network subnet's gateway-ip
Public bug reported: I am trying below scenario:- 1. Create one external network i.e. with router:external=True option. 2. Create one subnet under the above network with gateway-ip provided. 3. Create one router. 4. Issue command “neutron router-gateway-set routerID-point3 above networkID-point1 above” 5. Update the subnet in point2 above with new gateway IP i.e “neutron subnet-update subnetID-point2 --gateway-ip newIP” 6. I can see success-full subnet updated response on cli. 7. For validating the changed gateway-ip I verified router namespace present on Network node by using command “ip netns exec router-namespace-point3 route -n”. But in the output the new gateway-ip is not updated it is still showing the old one. Brief about my setup:- 1. It has one controller node, one Network node and 2 Compute nodes. 2. I am on Icehouse-GA. If the Subnet update API does not have a constraint to prevent the change then the L3 agent should affect it properly. ** Affects: neutron Importance: Undecided Status: New ** Tags: l3-ipam-dhcp -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1317363 Title: Unable to update external network subnet's gateway-ip Status in OpenStack Neutron (virtual network service): New Bug description: I am trying below scenario:- 1.Create one external network i.e. with router:external=True option. 2.Create one subnet under the above network with gateway-ip provided. 3.Create one router. 4.Issue command “neutron router-gateway-set routerID-point3 above networkID-point1 above” 5.Update the subnet in point2 above with new gateway IP i.e “neutron subnet-update subnetID-point2 --gateway-ip newIP” 6.I can see success-full subnet updated response on cli. 7.For validating the changed gateway-ip I verified router namespace present on Network node by using command “ip netns exec router-namespace-point3 route -n”. But in the output the new gateway-ip is not updated it is still showing the old one. Brief about my setup:- 1.It has one controller node, one Network node and 2 Compute nodes. 2.I am on Icehouse-GA. If the Subnet update API does not have a constraint to prevent the change then the L3 agent should affect it properly. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1317363/+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
