[Yahoo-eng-team] [Bug 1322597] Re: Unable to update image members
** Changed in: horizon Status: Invalid = Confirmed -- 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/1322597 Title: Unable to update image members Status in OpenStack Dashboard (Horizon): Confirmed Bug description: Glance API let us update the image members, we should expose that functionality in Horizon To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1322597/+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 1322597] Re: Unable to update image members
The bug is not invalid, it will be fixed by the blueprint but it's still valid ** Changed in: horizon Status: Invalid = 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/1322597 Title: Unable to update image members Status in OpenStack Dashboard (Horizon): New Bug description: Glance API let us update the image members, we should expose that functionality in Horizon To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1322597/+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 1343477] [NEW] Unset metadata in aggregates fails
Public bug reported: In order to remove a key/value pair from an aggregate metadata, you are supposed to use key=None. This is failing because None is not a string or unicode and nova is trying to get the value length using string utils ** Affects: nova Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: nova Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1343477 Title: Unset metadata in aggregates fails Status in OpenStack Compute (Nova): New Bug description: In order to remove a key/value pair from an aggregate metadata, you are supposed to use key=None. This is failing because None is not a string or unicode and nova is trying to get the value length using string utils To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1343477/+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 1336264] [NEW] Membership step styles incorrectly applied to the whole workflow
Public bug reported: horizon.membership.js is adding the class .dropdown_fix to the _workflow.html to fix the overflow in the update members step. That class should not be applied to the whole workflow template but to the members step template ** Affects: horizon Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: horizon Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1336264 Title: Membership step styles incorrectly applied to the whole workflow Status in OpenStack Dashboard (Horizon): New Bug description: horizon.membership.js is adding the class .dropdown_fix to the _workflow.html to fix the overflow in the update members step. That class should not be applied to the whole workflow template but to the members step template To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1336264/+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 1334677] [NEW] Flavor extra specs should be refactored
Public bug reported: The IndexView is extending from ModalFormMixin when there is no intention to display a modal or allow form actions in the Index. The index only displays a table of the key/value pairs so extending from DataTableView should be enough The template _index.html is unnecessarily extending form _modal.html when there is no intention to display a modal ** 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/1334677 Title: Flavor extra specs should be refactored Status in OpenStack Dashboard (Horizon): New Bug description: The IndexView is extending from ModalFormMixin when there is no intention to display a modal or allow form actions in the Index. The index only displays a table of the key/value pairs so extending from DataTableView should be enough The template _index.html is unnecessarily extending form _modal.html when there is no intention to display a modal To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1334677/+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 1334428] Re: error when setting primary project during user creation
*** This bug is a duplicate of bug 1260439 *** https://bugs.launchpad.net/bugs/1260439 ** This bug has been marked a duplicate of bug 1260439 Error message when creating a user with the default member role -- 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/1334428 Title: error when setting primary project during user creation Status in OpenStack Dashboard (Horizon): New Bug description: During user creation if the primary project is set an error message pops-up. Error: Unable to add user to primary project. The logs contain this error: 2014-06-25 20:26:49,165 11965 WARNING horizon.exceptions Recoverable error: Conflict occurred attempting to store role grant. User 301ea4d0417a4455a3e4495b18d51431 already has role 9fe2ff9ee4384b1894a90878d3e92bab in tenant c2beab6987844587a8cacc352fd97dc1 (HTTP 409) It appears that the roles/tenant/etc is right so maybe you're trying to do multiple keystone operations when the first one worked? Using icehouse on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1334428/+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 1017600] Re: duplicate left name and header on images page.
Not reproducible in icehouse and juno ** 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/1017600 Title: duplicate left name and header on images page. Status in OpenStack Dashboard (Horizon): Invalid Bug description: When i go to the images snapshots page the left nav and header are duplicated inside the main content. It is showing on both FF 13 and google chrome 19.0.1084.56 on ubuntu 11.04. To get the error to show up I did nothing more then click on the link in the left nav. Screen shot of both browsers attached. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1017600/+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 1332074] [NEW] No filter option available in volume snapshots and in images
Public bug reported: Images table in Project and Admin should have the option to filter the table rows Volume Snapshots table in Project should have the option to filter the table rows ** Affects: horizon Importance: Undecided Status: New ** Tags: low-hanging-fruit ** Project changed: devstack = horizon ** Tags added: low-hanging-fruit -- 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/1332074 Title: No filter option available in volume snapshots and in images Status in OpenStack Dashboard (Horizon): New Bug description: Images table in Project and Admin should have the option to filter the table rows Volume Snapshots table in Project should have the option to filter the table rows To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1332074/+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 1332077] [NEW] Volume Snapshots are not displayed in Admin
Public bug reported: Volume Snapshots table is only displayed in Project. It should also be displayed in the Admin section ** Affects: horizon Importance: Undecided Status: New ** Tags: low-hanging-fruit ** Tags added: low-hanging-fruit -- 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/1332077 Title: Volume Snapshots are not displayed in Admin Status in OpenStack Dashboard (Horizon): New Bug description: Volume Snapshots table is only displayed in Project. It should also be displayed in the Admin section To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1332077/+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 1274924] Re: Settings the availability zone deletes all attached metadata
** Changed in: python-novaclient Status: In Progress = Invalid -- 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/1274924 Title: Settings the availability zone deletes all attached metadata Status in OpenStack Compute (Nova): Fix Released Status in Python client library for Nova: Invalid Bug description: I'm using latest git with devstack on Ubuntu 12.04. When I update the availability zone the attached metadata gets deleted. Steps to reproduce the problem: 1) nova aggregate-create testagg #assuming that this creates a new metadata entry with the Id 26 2) nova aggregate-set-metadata 26 x=y 3) nova aggregate-update 26 testagg zone1 Now the availability zone is set, but the x=y metadata is lost. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1274924/+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 1326341] Re: enable to configure the same image name more than once
** 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/1326341 Title: enable to configure the same image name more than once Status in OpenStack Dashboard (Horizon): Invalid Bug description: From an internal bug report: --- its possible to configure the same image name more than once in the ui . its might be confusing when user will need to choose from list same name . in my opinion the image name is not a key in database but it should be a key in the user interface . this seems somehow related to https://bugs.launchpad.net/horizon/+bug/1275934 I don't think Horizon should enforce restrictions that are not applied by the clients. In this case end-users would still be able to upload images with duplicate names using the Glance client. When end-users get a different behaviour depending on whether they use the CLI tools or the dashboard, it leads to confusion and bug reports. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1326341/+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 1322952] Re: Uptime in Overview and Instance tab change if system time changes.
I'm not sure we want to fix this one. The uptime is displayed that way because we are applying a time_since filter to the created_at field returned by nova. We are not changing the value at all, just displaying it in a more user friendly way. Bottom line, metering and billing should be ok. Maybe we could stop applying the filter so no matter what the user does with the system time settings, the column will always displayed the value returned by nova, but again...I would not fix this one :) ** Changed in: horizon Status: New = Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1322952 Title: Uptime in Overview and Instance tab change if system time changes. Status in OpenStack Dashboard (Horizon): Opinion Bug description: If the system time of server running Horizon is changed, the uptime of instances in overview and instances tab change accordingly. Steps to Reproduce 1) Launch an instance and leave it for few minutes. 2) Check if uptime is changed. 3) Log in to the server where horizon is started and change the time. 4) Scenario 1: Change it backward by few minutes but not less than the total uptime at the moment. Eg: If current uptime is 1 hour, decrease the time by 30 minutes only. The uptime is shows 30 minutes after refreshing the page. 5) Scenario 2: Change it backward by few minutes greater than the total uptime at the moment. Eg: If current uptime is 1 hour, decrease the time by 2 hour 30 minutes. The uptime shows 0 minutes in instances page and sometimes instance disappears from overview page. 6) Scenario 3: Change it forward by few minutes. Eg: If current uptime is 1 hour, increase the time by 30 minutes only. uptime is modified to 1 hour 30 minutes. The above mentioned bug may affect the metering and billing if uptime is considered for calculation Scenario 3 (By some mistake if system time is modified to future) can infact affect the end users by overcharging them, which would break the SLA. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1322952/+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 1325725] Re: tempest doesn't have integration testing on nova's quota-class API
** Project changed: horizon = tempest -- 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/1325725 Title: tempest doesn't have integration testing on nova's quota-class API Status in OpenStack Dashboard (Horizon): Confirmed Status in Tempest: New Bug description: Related: https://bugs.launchpad.net/horizon/+bug/1292589 Nova shouldn't have been able to remove that functionality if horizon was using it. So we have a gap in testing the APIs that horizon is using. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1325725/+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 1302097] Re: Unable to get images by image type
** Changed in: glance Status: Invalid = 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/1302097 Title: Unable to get images by image type Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: We should be able to get images by type. In Horizon for example, in order to populate the boot image from options, we currently retrieve all images and filter them by type To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1302097/+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 1273326] Re: glance image-list does not show deleted/killed images
I was not able to reproduce this bug in icehouse ** Changed in: glance Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1273326 Title: glance image-list does not show deleted/killed images Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: I have 3 killed images and one in the 'deleted' state which I can see in the postgres database. When I try to run glance image-list, however, none of them are shown. I tried debugging this and placed a pdb.set_trace() call in glance/registry/api/v1/images.py:Controller._get_images where the self.db_api.image_get_all call is made (https://github.com/openstack/glance/blob/stable/havana/glance/registry/api/v1/images.py#L108). If I try to make this call manually it returns an empty list on the first try, but all subsequent tries with the same arguments return the right list with all the 4 images. Does anyone know what's going on? I have only tried reproducing this on Havana. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1273326/+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 1324616] Re: Trove Launch Instance should be renamed
** Project changed: horizon = trove -- 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/1324616 Title: Trove Launch Instance should be renamed Status in Openstack Database (Trove): New Bug description: In the horizon dashboard we use terms such as: For nova instances: Launch Instance, Terminate Instance, Resize Instance For volumes: Create volume, Edit volume For Containers: Create container, Delete container For trove to be consistent we should change the UI to have: Launch Database, Terminate Database Note: The Launch Instance button already brings up the the 'Launch Database' dialog To manage notifications about this bug go to: https://bugs.launchpad.net/trove/+bug/1324616/+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 1302097] Re: Unable to get images by image type
** Changed in: glance Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1302097 Title: Unable to get images by image type Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: We should be able to get images by type. In Horizon for example, in order to populate the boot image from options, we currently retrieve all images and filter them by type To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1302097/+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 1156563] Re: Uptime/VCPU hours of stopped Instances Keep on increasing even if instance satus is in shutdown mode
This is not a valid bug. Uptime actually reflects the time since the instance was created, maybe the title is misleading but the value is correct. Vcpu hours are returned by nova, horizon just displays what nova returns ** 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/1156563 Title: Uptime/VCPU hours of stopped Instances Keep on increasing even if instance satus is in shutdown mode Status in OpenStack Dashboard (Horizon): Invalid Bug description: I am using Folsom on Ubunru 12.04 with Horizon. Created 5 instances on KVM on 12.04 (running nova-compute only )and with out stopping VM, restarted Host machine. Under Instance Tab status of all instance is Shutdown but under Overview Uptime of VM keeps on increasing. Same in case of VCPU hours. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1156563/+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 1322597] [NEW] Unable to update image members
Public bug reported: Glance API let us update the image members, we should expose that functionality in Horizon ** Affects: horizon Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: horizon Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1322597 Title: Unable to update image members Status in OpenStack Dashboard (Horizon): New Bug description: Glance API let us update the image members, we should expose that functionality in Horizon To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1322597/+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 1322610] [NEW] Improvements in Flavors
Public bug reported: Flavors page could be improved by: - Replacing the Public column with yes/no values by an Access column that could list the tenants with access to the flavor. In case it's a public flavor then Access = Public - Moving the extra specs to a column in the table ** 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/1322610 Title: Improvements in Flavors Status in OpenStack Dashboard (Horizon): New Bug description: Flavors page could be improved by: - Replacing the Public column with yes/no values by an Access column that could list the tenants with access to the flavor. In case it's a public flavor then Access = Public - Moving the extra specs to a column in the table To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1322610/+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 1322618] [NEW] Unable to set flavors extra spec during creation
Public bug reported: Users can't set extra specs to a flavor in the creation workflow. It would be nice to add a set extra specs step to the creation flavor where the users can set the extra specs ** 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/1322618 Title: Unable to set flavors extra spec during creation Status in OpenStack Dashboard (Horizon): New Bug description: Users can't set extra specs to a flavor in the creation workflow. It would be nice to add a set extra specs step to the creation flavor where the users can set the extra specs To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1322618/+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 1321334] [NEW] Non bootable volumes can be used as a bootable source
Public bug reported: The following command results in a successful vm creation: nova boot --boot-volume non-bootable-volume-id --flavor test-flavor test-name we should validate that the --boot-volume passed is actually a bootable volume and if it's not we should return an error explaining what went wrong ** 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/1321334 Title: Non bootable volumes can be used as a bootable source Status in OpenStack Compute (Nova): New Bug description: The following command results in a successful vm creation: nova boot --boot-volume non-bootable-volume-id --flavor test- flavor test-name we should validate that the --boot-volume passed is actually a bootable volume and if it's not we should return an error explaining what went wrong To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1321334/+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 1319900] [NEW] Non bootable volumes should not be included as boot source
Public bug reported: When users select Volume as boot source, all available volumes are displayed as options, even those which bootable flag is set to False. If bootable is False then the volume should not be included as a boot source ** Affects: horizon Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: horizon Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1319900 Title: Non bootable volumes should not be included as boot source Status in OpenStack Dashboard (Horizon): New Bug description: When users select Volume as boot source, all available volumes are displayed as options, even those which bootable flag is set to False. If bootable is False then the volume should not be included as a boot source To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1319900/+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 1319940] [NEW] Add bootable column to the volumes table and to the snapshots table
Public bug reported: Cinder is returning a bootable attribute for each volume and snapshot indicating whether the volume/snapshot is bootable or not. This information is useful and should be shown to the users ** Affects: horizon Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: horizon Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1319940 Title: Add bootable column to the volumes table and to the snapshots table Status in OpenStack Dashboard (Horizon): New Bug description: Cinder is returning a bootable attribute for each volume and snapshot indicating whether the volume/snapshot is bootable or not. This information is useful and should be shown to the users To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1319940/+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 1319387] [NEW] Availability zones should be moved to system info
Public bug reported: Availability zones are listed in the host aggregates panel but they should be moved to system info as that table is only showing information about the zones and there are no actions available. Moreover the it's confusing to show availability zones in a host aggregate panel ** 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/1319387 Title: Availability zones should be moved to system info Status in OpenStack Dashboard (Horizon): New Bug description: Availability zones are listed in the host aggregates panel but they should be moved to system info as that table is only showing information about the zones and there are no actions available. Moreover the it's confusing to show availability zones in a host aggregate panel To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1319387/+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 1294853] Re: service_get_all in nova.compute.api should return a List object and should not do a filtering
** No longer affects: tempest -- 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/1294853 Title: service_get_all in nova.compute.api should return a List object and should not do a filtering Status in OpenStack Compute (Nova): In Progress Bug description: service_get_all is filtering the results returned by the service object and returning an array. This api should return a List object instead and the filtering should be done in the sqlalchemy api To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1294853/+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 1318723] [NEW] Error_extending should not be an in progress status
Public bug reported: When a user tries to extend a volume and the extension fails. The volume status is set to error extending and a progress bar is displayed next to the status. Error extending indicates a completed action so the progress bar should be removed ** Affects: horizon Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: horizon Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1318723 Title: Error_extending should not be an in progress status Status in OpenStack Dashboard (Horizon): New Bug description: When a user tries to extend a volume and the extension fails. The volume status is set to error extending and a progress bar is displayed next to the status. Error extending indicates a completed action so the progress bar should be removed To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1318723/+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 1294132] Re: Volume status set to error extending when driver fails to extend the volume
** Changed in: horizon Status: In Progress = Invalid ** Changed in: cinder 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/1294132 Title: Volume status set to error extending when driver fails to extend the volume Status in Cinder: Invalid Status in OpenStack Dashboard (Horizon): Invalid Bug description: If the driver can't extend the volume because there's no enough space, the volume status is set to error_extending and the volume becomes unusable. The only options to the users are to delete the volume and create it again. Expected behavior would be: if the back-end doesn't have enough capacity to extend the volume, warn user with proper information and set volume status back to 'available' since the volume is untouched. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1294132/+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 1308189] [NEW] Instances in error state should not have Up Time
Public bug reported: When launch instance fails, the instance status is set to Error and the Uptime is updated every time the page is loaded even when the instance was never up. If the instance current status is Error then Uptime should be either --- or 0 ** Affects: horizon Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: horizon Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1308189 Title: Instances in error state should not have Up Time Status in OpenStack Dashboard (Horizon): New Bug description: When launch instance fails, the instance status is set to Error and the Uptime is updated every time the page is loaded even when the instance was never up. If the instance current status is Error then Uptime should be either --- or 0 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1308189/+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 1308191] [NEW] Create instance handle method should display an info message instead of a success message
Public bug reported: When a user creates an instance and click on the Launch button, a success message is displayed assuming that the instance will be successfully created. An info message should be displayed instead since the instance creation is in progress ** Affects: horizon Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: horizon Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1308191 Title: Create instance handle method should display an info message instead of a success message Status in OpenStack Dashboard (Horizon): New Bug description: When a user creates an instance and click on the Launch button, a success message is displayed assuming that the instance will be successfully created. An info message should be displayed instead since the instance creation is in progress To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1308191/+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 1294853] Re: service_get_all in nova.compute.api should return a List object and should not do a filtering
** Also affects: tempest Importance: Undecided Status: New ** Changed in: tempest Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1294853 Title: service_get_all in nova.compute.api should return a List object and should not do a filtering Status in OpenStack Compute (Nova): In Progress Status in Tempest: New Bug description: service_get_all is filtering the results returned by the service object and returning an array. This api should return a List object instead and the filtering should be done in the sqlalchemy api To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1294853/+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 1302097] [NEW] Unable to get images by image type
Public bug reported: We should be able to get images by type. In Horizon for example, in order to populate the boot image from options, we currently retrieve all images and filter them by type ** Affects: glance Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: glance Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1302097 Title: Unable to get images by image type Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: We should be able to get images by type. In Horizon for example, in order to populate the boot image from options, we currently retrieve all images and filter them by type To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1302097/+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 1291676] Re: Able to create multiple volumes and volume snapshots with the same name
So even when we could add a validation in horizon, people can still use the api to create the volumes/snapshots. Adding the validation on horizon might result in confusing situations since the users might end having duplicates names in the dashboard and yet beeing unable to create resources with duplicate names ** 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/1291676 Title: Able to create multiple volumes and volume snapshots with the same name Status in Cinder: Won't Fix Status in OpenStack Dashboard (Horizon): Invalid Bug description: Under Project - Volumes, create a new volume, say 'vol1'. Now create one or more snapshots from this volume and name them the same. Then create another new volume using the same name 'vol1' and create snapshots with the same name. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1291676/+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 1294132] Re: Volume status set to error extending when driver fails to extend the volume
So the implementation to fix this was not okI'm cool with that and I'll try to find a better way to fix this issue. In the meantime I'll add a description in Horizon warning the user that if there's not enough space the extend operation will fail and the volume will become unusable. ** Changed in: cinder Status: Opinion = 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/1294132 Title: Volume status set to error extending when driver fails to extend the volume Status in Cinder: New Status in OpenStack Dashboard (Horizon): In Progress Bug description: If the driver can't extend the volume because there's no enough space, the volume status is set to error_extending and the volume becomes unusable. The only options to the users are to delete the volume and create it again. Expected behavior would be: if the back-end doesn't have enough capacity to extend the volume, warn user with proper information and set volume status back to 'available' since the volume is untouched. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1294132/+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 1294132] Re: Volume status set to error extending when driver fails to extend the volume
The volume manager does know what happened during the extension and there's another possible (and likely) failure: not enough space 2014-03-21 07:33:50.009 ERROR cinder.brick.local_dev.lvm [req-7da4bbc0-7b2a-497f-962b-38f15215b383 b6548f770b23478baf8 cecea6c32ea92 a2470742fc4d41ce83c677bc69a6f73c] Error extending Volume 2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm Traceback (most recent call last): 2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm File /opt/stack/cinder/cinder/brick/local_dev/lvm.py, lin e 639, in extend_volume 2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm run_as_root=True) 2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm File /opt/stack/cinder/cinder/utils.py, line 136, in exec ute 2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm return processutils.execute(*cmd, **kwargs) 2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm File /opt/stack/cinder/cinder/openstack/common/processutil s.py, line 173, in execute 2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm cmd=' '.join(cmd)) 2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm ProcessExecutionError: Unexpected error while running command . 2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm Command: sudo cinder-rootwrap /etc/cinder/rootwrap.conf lvext end -L 12g stack-volumes/volume-a3a21fc8-4bc1-4451-bbb3-808cc363aca1 2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm Exit code: 5 2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm Stdout: ' Extending logical volume volume-a3a21fc8-4bc1-4451 -bbb3-808cc363aca1 to 12.00 GiB\n' 2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm Stderr: ' Insufficient free space: 2816 extents needed, but only 2306 available\n' I'm ok with generating an explicit exception for no space left and as I stated in my previous comment, we could just show that exception to the users. Once again, if a user wants to extend a volume and he is not able to do it because there's not enough space, that volume should remain usable/available. It's just wrong to set the volume status to error_extending because there was not enough space to extend the volume ** Changed in: cinder Status: Invalid = 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/1294132 Title: Volume status set to error extending when driver fails to extend the volume Status in Cinder: New Status in OpenStack Dashboard (Horizon): In Progress Bug description: If the driver can't extend the volume because for example, there's no enough space, the volume status is set to error_extending and the volume becomes unusable. The only options to the users are to delete the volume and create it again To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1294132/+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 1294132] Re: Volume status set to error extending when new size exceeds quota
John your analysis is correct, however, I don't think this is the appropriate behavior. After what you described, the volume remains unusable and there's no option either from command line or from horizon to fix it. The user can only delete the volume and create it again. If I'm trying to extend the volume and I for some reason I can't do it, I expect the system to tell me why I can't do it and I also expect to be able to continue using the volume. ** Summary changed: - Volume status set to error extending when new size exceeds quota + Volume status set to error extending when driver fails to extend the volume ** Description changed: - extend_volume in cinder.volume.manager should not set the status to - error_extending when the quota was exceeded. The status should still be - available + If the driver can't extend the volume because for example, there's no + enough space, the volume status is set to error_extending and the + volume becomes unusable. The only options to the users are to delete the + volume and create it again ** Changed in: cinder Status: Invalid = 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/1294132 Title: Volume status set to error extending when driver fails to extend the volume Status in Cinder: New Status in OpenStack Dashboard (Horizon): In Progress Bug description: If the driver can't extend the volume because for example, there's no enough space, the volume status is set to error_extending and the volume becomes unusable. The only options to the users are to delete the volume and create it again To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1294132/+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 1294853] [NEW] service_get_all in nova.compute.api should return a List object and should not do a filtering
Public bug reported: service_get_all is filtering the results returned by the service object and returning an array. This api should return a List object instead and the filtering should be done in the sqlalchemy api ** Affects: nova Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: nova Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1294853 Title: service_get_all in nova.compute.api should return a List object and should not do a filtering Status in OpenStack Compute (Nova): New Bug description: service_get_all is filtering the results returned by the service object and returning an array. This api should return a List object instead and the filtering should be done in the sqlalchemy api To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1294853/+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 1290544] Re: Extend volume not showing current size
** Changed in: horizon Status: In Progress = Invalid ** Changed in: horizon Status: Invalid = Confirmed ** Description changed: - When extending a volume, the form should automatically be populated with - the current volume size + When extending a volume, the form should display the current volume size -- 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/1290544 Title: Extend volume not showing current size Status in OpenStack Dashboard (Horizon): Confirmed Bug description: When extending a volume, the form should display the current volume size To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1290544/+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 1189070] Re: Availability zones in nested host aggregates are concatenated
** Changed in: nova Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1189070 Title: Availability zones in nested host aggregates are concatenated Status in OpenStack Compute (Nova): Fix Released Status in Python client library for Nova: Invalid Bug description: If I create two host aggregates with unique availability zones for the same host (named 'global' and '1' here), a subsequent call to 'nova availability-zone-list' reports the following: $ nova availability-zone-list +--+---+ | Name | Status| +--+---+ | 1,global | available | +--+---+ I would suggest we don't join the AZ names and report them individually like this: $ nova availability-zone-list ++---+ | Name | Status| ++---+ | 1 | available | | global | available | ++---+ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1189070/+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 1292644] [NEW] get_aggregate_list in nova.compute.api should return a List object
Public bug reported: nova.compute.api should return a List object, and that List should be converted into the REST API expected results in the aggregates API extensions. ** Affects: nova Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: nova Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1292644 Title: get_aggregate_list in nova.compute.api should return a List object Status in OpenStack Compute (Nova): New Bug description: nova.compute.api should return a List object, and that List should be converted into the REST API expected results in the aggregates API extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1292644/+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 1291676] Re: Able to create multiple volumes and volume snapshots with the same name
This bug also affect Cinder since, the api provided by Cinder is allowing duplicate volumes and snapshots names ** Also affects: cinder Importance: Undecided Status: New ** Changed in: cinder Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1291676 Title: Able to create multiple volumes and volume snapshots with the same name Status in Cinder: New Status in OpenStack Dashboard (Horizon): New Bug description: Under Project - Volumes, create a new volume, say 'vol1'. Now create one or more snapshots from this volume and name them the same. Then create another new volume using the same name 'vol1' and create snapshots with the same name. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1291676/+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 1292084] [NEW] User can't select rules while creating a security group
Public bug reported: In order to assign rules to a new security group, the user has to create the security group first and then edit the rules, which option in fact opens a new tab with no reference to security groups. ** Affects: horizon Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: horizon Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1292084 Title: User can't select rules while creating a security group Status in OpenStack Dashboard (Horizon): New Bug description: In order to assign rules to a new security group, the user has to create the security group first and then edit the rules, which option in fact opens a new tab with no reference to security groups. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1292084/+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 1291069] [NEW] Modifying flavor access list modifies the flavor info
Public bug reported: When the user modifies the flavor access list, the flavor is removed and created again even when the flavor information hasn't chance so there was no need to update the flavor information ** Affects: horizon Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: horizon Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1291069 Title: Modifying flavor access list modifies the flavor info Status in OpenStack Dashboard (Horizon): New Bug description: When the user modifies the flavor access list, the flavor is removed and created again even when the flavor information hasn't chance so there was no need to update the flavor information To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1291069/+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 1290544] [NEW] Extend volume not showing current size
Public bug reported: When extending a volume, the form should automatically be populated with the current volume size ** Affects: horizon Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: neutron Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) ** Project changed: neutron = horizon -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1290544 Title: Extend volume not showing current size Status in OpenStack Dashboard (Horizon): New Bug description: When extending a volume, the form should automatically be populated with the current volume size To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1290544/+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 1286293] [NEW] Edit flavor access does not update removed access
Public bug reported: Steps to reproduce: 1. In the Flavors section within Admin, edit any of the available flavors 2. Add an access to the flavor and save the changes 3. Edit again. Remove the access added in step 2 and add a new access and save the changes 4. Once again edit the same flavor, access added in step 2 should not be part of the flavor access since it was removed in step 3 but it is actually showing up as one of the flavor accesses ** Affects: horizon Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: horizon Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1286293 Title: Edit flavor access does not update removed access Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce: 1. In the Flavors section within Admin, edit any of the available flavors 2. Add an access to the flavor and save the changes 3. Edit again. Remove the access added in step 2 and add a new access and save the changes 4. Once again edit the same flavor, access added in step 2 should not be part of the flavor access since it was removed in step 3 but it is actually showing up as one of the flavor accesses To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1286293/+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 1286297] [NEW] Creating a flavor with access is throwing an error
Public bug reported: Steps to reproduce 1. Create a new flavor, setting an access in the flavor access tab 2. The flavor is created but an error is displayed saying Unable to set flavor access for project. ** Affects: horizon Importance: Undecided Assignee: Santiago Baldassin (santiago-b-baldassin) Status: New ** Changed in: horizon Assignee: (unassigned) = Santiago Baldassin (santiago-b-baldassin) -- 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/1286297 Title: Creating a flavor with access is throwing an error Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce 1. Create a new flavor, setting an access in the flavor access tab 2. The flavor is created but an error is displayed saying Unable to set flavor access for project. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1286297/+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
