[Yahoo-eng-team] [Bug 1267140] Re: The output of security group rules does not include egress rules.
I've checked Nova and CLI outputs and the error belongs to the first one. Then, I am changing the affected project. ** Project changed: python-novaclient = nova -- 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/1267140 Title: The output of security group rules does not include egress rules. Status in OpenStack Compute (Nova): Confirmed Bug description: The output of security group rules does not include egress rules. Description of problem: === The output of security group rules does not include egress rules. Version-Release number of selected component (if applicable): = Tested on RHEL Icehouse: python-nova-2014.1-0.5.b1.el6.noarch How reproducible: = Always Steps to Reproduce: === 1. Add an egress security group rule (I did it via horizon) 2. via CLI: nova secgroup-list-rules sec group name Actual results: === List of ingress rules. Expected results: = List of both ingress and egress rules. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1267140/+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 1325684] Re: Launch Instance dialog - nic should probably be capitalized on the Networking tab
To fix this bug completely, it is needed to update the localization files, I am creating a new entry for i18n team. The localization changes have to be done over the horizon modifications to be submitted soon. ** Also affects: openstack-i18n 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/1325684 Title: Launch Instance dialog - nic should probably be capitalized on the Networking tab Status in OpenStack Dashboard (Horizon): New Status in OpenStack I18n L10n: New Bug description: On the Networking tab of the Launch Instance dialog, nic is all lowercase. Generally acronyms are capitalized. nic is used both for each interface, and in the description on the right pane. Somewhat related to that, on the same dialog and tab, we say Selected Networks and underneath that, Available networks, which don't follow the same capitalization conventions. Available Networks would match what seems to be used elsewhere in the UI. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1325684/+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 1314352] Re: non-ascii volume type name causes problems
I think the issue is python-cinderclient not Horizon, I am changing the component. I will submit the bug fix soon. Thanks! ** Project changed: horizon = python-cinderclient -- 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/1314352 Title: non-ascii volume type name causes problems Status in Python client library for Cinder: Confirmed Bug description: ==How to Reproduce== 1. Go to Admin Volumes 2. Click on 'Create Volume Type' 3. Enter in a non-ascii string. I used: zarządzania 4. This will create an entry in the table successfully. Problem arises if you go to Admin System Info. Please see screenshot. Not sure if this is just known and accepted behavior for now or a bug. If it is a bug, it may be relevant across other dashboards too. To manage notifications about this bug go to: https://bugs.launchpad.net/python-cinderclient/+bug/1314352/+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 1217874] Re: cinder shows wrong device name for attached volume
** Project changed: cinder = nova
--
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/1217874
Title:
cinder shows wrong device name for attached volume
Status in OpenStack Compute (Nova):
Confirmed
Bug description:
Using grizzly on centos 6.4, attached volumes are shown with wrong device
names in cinder. E.g. I have this volume wich I attach, cinder tells me its
attached as /dev/vdb:
| attachments | [{u'device': u'/dev/vdb', u'server_id':
u'3318b373-8792-4109-b65c-ee138dcd525f', u'id':
u'c424719d-1031-4e29-8086-8a62b385d99a', u'volume_id':
u'c424719d-1031-4e29-8086-8a62b385d99a'}] |
but on the machine (ubuntu 12.04 cloud image) the device is /dev/vdc:
root@u15:~# cat /proc/partitions
major minor #blocks name
25302097152 vda
25312088450 vda1
253 16400 vdb
- attaching volume to instance:
root@u15:~# cat /proc/partitions
major minor #blocks name
25302097152 vda
25312088450 vda1
253 16400 vdb
253 321048576 vdc
253 331047552 vdc1
Maybe this is not cinders fault, as it the volume seems to be the
second attached storage device? could be due to ubuntus image, but
still, the device name is wrong.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1217874/+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
