[Yahoo-eng-team] [Bug 1455102] Re: some test jobs broken by tox 2.0 not passing env variables
And heat: http://logs.openstack.org/31/182531/3/gate/check-heat-dsvm-functional- mysql/33d2a34/console.html#_2015-05-14_08_56_59_665 ** Also affects: heat 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/1455102 Title: some test jobs broken by tox 2.0 not passing env variables Status in OpenStack Neutron (virtual network service): New Status in OpenStack Gate Infrastructure: Confirmed Status in python-manilaclient: New Status in Python client library for Nova: In Progress Bug description: Tox 2.0 brings environment isolation, which is good. Except a lot of test jobs assume passing critical variables via environment (like credentials). There are multiple ways to fix this: 1. stop using environment to pass things, instead use a config file of some sort 2. allow explicit pass through via - http://tox.readthedocs.org/en/latest/config.html#confval-passenv =SPACE-SEPARATED-GLOBNAMES This bug mostly exists for tracking patches, and ensuring that people realize there is a larger change here. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1455102/+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 1455102] Re: some test jobs broken by tox 2.0 not passing env variables
Neutron is also impacted: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwidG94LkNvbmZpZ0Vycm9yOiBDb25maWdFcnJvcjogc3Vic3RpdHV0aW9uIGtleSAnZW52YmluZGlyJyBub3QgZm91bmRcIiBBTkQgdGFnczpcImNvbnNvbGVcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQzMTYxMjQ4MzM5NywibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIifQ== ** 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/1455102 Title: some test jobs broken by tox 2.0 not passing env variables Status in OpenStack Neutron (virtual network service): New Status in OpenStack Gate Infrastructure: Confirmed Status in Python client library for Nova: In Progress Bug description: Tox 2.0 brings environment isolation, which is good. Except a lot of test jobs assume passing critical variables via environment (like credentials). There are multiple ways to fix this: 1. stop using environment to pass things, instead use a config file of some sort 2. allow explicit pass through via - http://tox.readthedocs.org/en/latest/config.html#confval-passenv =SPACE-SEPARATED-GLOBNAMES This bug mostly exists for tracking patches, and ensuring that people realize there is a larger change here. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1455102/+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 1455093] [NEW] VMs fail to get DHCP response when a network is dual stacked.
Public bug reported: When creating a dual stack provider network under Icehouse, there is a chance that instances fail to get their v4 DHCP responses due to a bug in the securitygroup rule creation. ** Affects: neutron Importance: Undecided Assignee: sridhar basam (sri-7) Status: In Progress ** Changed in: neutron Assignee: (unassigned) = sridhar basam (sri-7) ** Changed in: neutron Status: New = In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1455093 Title: VMs fail to get DHCP response when a network is dual stacked. Status in OpenStack Neutron (virtual network service): In Progress Bug description: When creating a dual stack provider network under Icehouse, there is a chance that instances fail to get their v4 DHCP responses due to a bug in the securitygroup rule creation. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1455093/+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 1455102] Re: some test jobs broken by tox 2.0 not passing env variables
And python-manilaclient: http://logs.openstack.org/36/181236/1/gate/gate-python-manilaclient- python26/fc90626/console.html ** Also affects: python-manilaclient Importance: Undecided Status: New ** No longer affects: heat -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1455102 Title: some test jobs broken by tox 2.0 not passing env variables Status in OpenStack Neutron (virtual network service): New Status in OpenStack Gate Infrastructure: Confirmed Status in python-manilaclient: New Status in Python client library for Nova: In Progress Bug description: Tox 2.0 brings environment isolation, which is good. Except a lot of test jobs assume passing critical variables via environment (like credentials). There are multiple ways to fix this: 1. stop using environment to pass things, instead use a config file of some sort 2. allow explicit pass through via - http://tox.readthedocs.org/en/latest/config.html#confval-passenv =SPACE-SEPARATED-GLOBNAMES This bug mostly exists for tracking patches, and ensuring that people realize there is a larger change here. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1455102/+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 1455034] Re: Deleting nonexistent end-point gives incorrect error message
** Project changed: keystone = python-openstackclient ** Summary changed: - Deleting nonexistent end-point gives incorrect error message + Deleting nonexistent endpoint gives incorrect error message ** Tags removed: error-messge ** Tags added: error-message user-experience -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1455034 Title: Deleting nonexistent endpoint gives incorrect error message Status in OpenStack Command Line Client: New Bug description: I'm trying to delete an end-point with invalid id or id that does not exist in the system and getting the below error message: ERROR: openstack More than one endpoint exists with the name 'non-existing-id'. While the more appropriate message would be to say, No endpoint exists with the name 'non-existing-id'. osc:/ # openstack --version openstack 0.4.1 osc:/ # openstack --insecure endpoint list +--+---+--+--+-+---+---+ | ID | Region| Service Name | Service Type | Enabled | Interface | URL | +--+---+--+--+-+---+---+ | 14d171e5d9914d8fa19c6bc539acd34a | None | keystone | identity | True| admin | https://keystone:35357/v3 | +--+---+--+--+-+---+---+ osc:/ # openstack --insecure endpoint delete 14d171e5d9914d8fa19c6bc539acd34b ERROR: openstack More than one endpoint exists with the name '14d171e5d9914d8fa19c6bc539acd34b'. osc:/ # openstack --insecure endpoint delete non-existing-id ERROR: openstack More than one endpoint exists with the name 'non-existing-id'. # zypper info openstack-keystone Loading repository data... Reading installed packages... Information for package openstack-keystone: --- Repository: staging Name: openstack-keystone Version: 2014.2.3.dev15-1.1 Arch: noarch Vendor: obs://build.opensuse.org/Cloud:OpenStack Installed: Yes Status: up-to-date Installed Size: 81.9 KiB Summary: OpenStack Identity Service (Keystone) Description: Keystone is an OpenStack project that provides Identity, Token, Catalog and Policy services for use specifically by projects in the OpenStack family. To manage notifications about this bug go to: https://bugs.launchpad.net/python-openstackclient/+bug/1455034/+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 1455179] [NEW] Horizon dashboard does not provide an option to specify the container-format of an image while importing to image registry
Public bug reported: Specifying container-format while image improt is supported through Glance command line only. Horizon dashboard does not provide an option to specify the container-format of an image while importing images to the image registry. This is needed incase of importing images with specific container-format, for example for docker images when used with nova-docker driver. ** 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/1455179 Title: Horizon dashboard does not provide an option to specify the container- format of an image while importing to image registry Status in OpenStack Dashboard (Horizon): New Bug description: Specifying container-format while image improt is supported through Glance command line only. Horizon dashboard does not provide an option to specify the container-format of an image while importing images to the image registry. This is needed incase of importing images with specific container-format, for example for docker images when used with nova-docker driver. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1455179/+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 1455126] [NEW] Launch Instance (NG) network needs to use controller-as
Public bug reported: As suggested by: https://github.com/johnpapa/angular-styleguide#style-y030 The Launch Instance network-step controller should use 'controller-as' syntax. ** 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/1455126 Title: Launch Instance (NG) network needs to use controller-as Status in OpenStack Dashboard (Horizon): New Bug description: As suggested by: https://github.com/johnpapa/angular-styleguide#style-y030 The Launch Instance network-step controller should use 'controller-as' syntax. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1455126/+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 1455118] [NEW] Missing dependency on python-keystoneclient
Public bug reported: We import keystone client code directly, but don't have an entry in requirements.txt ** Affects: nova Importance: Undecided Assignee: Stuart McLaren (stuart-mclaren) Status: In Progress -- 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/1455118 Title: Missing dependency on python-keystoneclient Status in OpenStack Compute (Nova): In Progress Bug description: We import keystone client code directly, but don't have an entry in requirements.txt To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1455118/+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 1455141] [NEW] tox -egenconfig failure (no glance-search.conf)
Public bug reported: I tried to generate the config samples but ended up with: $ tox -e genconfig [...] genconfig runtests: commands[5] | oslo-config-generator --config-file etc/oslo-config-generator/glance-search.conf Traceback (most recent call last): File .tox/genconfig/bin/oslo-config-generator, line 11, in module sys.exit(main()) File /home/gpocentek/Workspace/OpenStack/glance/.tox/genconfig/local/lib/python2.7/site-packages/oslo_config/generator.py, line 331, in main conf(args, version=version) File /home/gpocentek/Workspace/OpenStack/glance/.tox/genconfig/local/lib/python2.7/site-packages/oslo_config/cfg.py, line 1853, in __call__ raise ConfigFilesNotFoundError(self._namespace._files_not_found) oslo_config.cfg.ConfigFilesNotFoundError: Failed to find some config files: /home/gpocentek/Workspace/OpenStack/glance/etc/oslo-config-generator/glance-search.conf I couldn't find a reference to glance-search.conf in the git history. This happens on master and stable/kilo. ** 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/1455141 Title: tox -egenconfig failure (no glance-search.conf) Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: I tried to generate the config samples but ended up with: $ tox -e genconfig [...] genconfig runtests: commands[5] | oslo-config-generator --config-file etc/oslo-config-generator/glance-search.conf Traceback (most recent call last): File .tox/genconfig/bin/oslo-config-generator, line 11, in module sys.exit(main()) File /home/gpocentek/Workspace/OpenStack/glance/.tox/genconfig/local/lib/python2.7/site-packages/oslo_config/generator.py, line 331, in main conf(args, version=version) File /home/gpocentek/Workspace/OpenStack/glance/.tox/genconfig/local/lib/python2.7/site-packages/oslo_config/cfg.py, line 1853, in __call__ raise ConfigFilesNotFoundError(self._namespace._files_not_found) oslo_config.cfg.ConfigFilesNotFoundError: Failed to find some config files: /home/gpocentek/Workspace/OpenStack/glance/etc/oslo-config-generator/glance-search.conf I couldn't find a reference to glance-search.conf in the git history. This happens on master and stable/kilo. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1455141/+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 1455134] [NEW] User data configuration such as runcmd or write_files not working when using NoCloud datasource
Public bug reported:
When using NoCloud as data source in an Ubuntu VM, some cloud config
commands work properly (setting password and hostname), while others do
not work properly.
I have installed cloud-init in an Ubuntu VM (14.04)
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename: trusty
I have run 'dpkg-reconfigure cloud-init' and set the NoCloud as the only
datasource.
Then I have created meta-data and user-data:
meta-data:
local-hostname: test5
network-interfaces: |
auto eth1
iface eth1 inet static
address 10.250.1.5
netmask 255.255.255.0
user-data:
#cloud-config
hostname: test5
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True
runcmd:
- [ sh, -xc, echo $(date) ': hello world!' /home/ubuntu/fichero.txt ]
write_files:
- encoding: b64
content: CiMgVGhpcyBmaWxlIGNvbnRyb2xzIHRoZSBzdGF0ZSBvZiBTRUxpbnV4...
owner: ubuntu:ubuntu
path: /home/ubuntu/kk
permissions: ’0644’
- content: |
# My new /etc/sysconfig/samba file
SMBDOPTIONS=-D
path: /home/ubuntu/samba
I have created a disk with:
truncate --size 2M init.img
mkfs.vfat -n cidata init.img
mcopy -oi init.img user-data meta-data ::
I have shut the VM down, attached the disk and then I have started the
VM again. The VM changes the name, the password and the interfaces
according to meta-data and user-data, but the configuration under runcmd
and write_files files has not been applied. I have noticed that the
information is available in the VM.
The same happens if I create a mime-multipart file with boothooks and
user-scripts.
Any suggestions?
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1455134
Title:
User data configuration such as runcmd or write_files not working when
using NoCloud datasource
Status in Init scripts for use on cloud images:
New
Bug description:
When using NoCloud as data source in an Ubuntu VM, some cloud config
commands work properly (setting password and hostname), while others
do not work properly.
I have installed cloud-init in an Ubuntu VM (14.04)
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename: trusty
I have run 'dpkg-reconfigure cloud-init' and set the NoCloud as the
only datasource.
Then I have created meta-data and user-data:
meta-data:
local-hostname: test5
network-interfaces: |
auto eth1
iface eth1 inet static
address 10.250.1.5
netmask 255.255.255.0
user-data:
#cloud-config
hostname: test5
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True
runcmd:
- [ sh, -xc, echo $(date) ': hello world!' /home/ubuntu/fichero.txt ]
write_files:
- encoding: b64
content: CiMgVGhpcyBmaWxlIGNvbnRyb2xzIHRoZSBzdGF0ZSBvZiBTRUxpbnV4...
owner: ubuntu:ubuntu
path: /home/ubuntu/kk
permissions: ’0644’
- content: |
# My new /etc/sysconfig/samba file
SMBDOPTIONS=-D
path: /home/ubuntu/samba
I have created a disk with:
truncate --size 2M init.img
mkfs.vfat -n cidata init.img
mcopy -oi init.img user-data meta-data ::
I have shut the VM down, attached the disk and then I have started the
VM again. The VM changes the name, the password and the interfaces
according to meta-data and user-data, but the configuration under
runcmd and write_files files has not been applied. I have noticed that
the information is available in the VM.
The same happens if I create a mime-multipart file with boothooks and
user-scripts.
Any suggestions?
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1455134/+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 1455233] [NEW] read_seeded broken
Public bug reported: util.read_seeded uses load_tfile_or_url, but then treats the return value as if it was a response. this regressed in revno 1067. ** Affects: cloud-init Importance: Medium Status: Confirmed ** Affects: cloud-init (Ubuntu) Importance: Medium Status: Confirmed ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init Status: New = Confirmed ** Changed in: cloud-init (Ubuntu) Status: New = Confirmed ** Changed in: cloud-init Importance: Undecided = Medium ** Changed in: cloud-init (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1455233 Title: read_seeded broken Status in Init scripts for use on cloud images: Confirmed Status in cloud-init package in Ubuntu: Confirmed Bug description: util.read_seeded uses load_tfile_or_url, but then treats the return value as if it was a response. this regressed in revno 1067. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1455233/+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 1455213] [NEW] Permission error given when selecting Project Name and not Set as Active Project
Public bug reported: Users receive a You do not have permission to access the resource: /identity/XX/detail/ Login as different user or go back to home page When they select the name of the project, instead of clicking the button Set as active Project To reproduce: User must belong to more than 30 projects so that the Project selector in the Upper Left hand corner is more than what can be displayed. This leads the user to select the option More Projects'. Once in the projects listing page, the user selects the link that contains the name of the project. This will produce the above error. If the user select Set as Active Project, they will not see an error and everything would work as expected. ** 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/1455213 Title: Permission error given when selecting Project Name and not Set as Active Project Status in OpenStack Dashboard (Horizon): New Bug description: Users receive a You do not have permission to access the resource: /identity/XX/detail/ Login as different user or go back to home page When they select the name of the project, instead of clicking the button Set as active Project To reproduce: User must belong to more than 30 projects so that the Project selector in the Upper Left hand corner is more than what can be displayed. This leads the user to select the option More Projects'. Once in the projects listing page, the user selects the link that contains the name of the project. This will produce the above error. If the user select Set as Active Project, they will not see an error and everything would work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1455213/+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 1452886] Re: Port stuck in BUILD state results in limited instance connectivity
*** This bug is a duplicate of bug 1327124 *** https://bugs.launchpad.net/bugs/1327124 Right, I'm going to mark as a duplicate. Comment here if it doesn't look like it was fixed. ** This bug has been marked a duplicate of bug 1327124 Instance stuck at spawning status after rescheduling -- 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/1452886 Title: Port stuck in BUILD state results in limited instance connectivity Status in OpenStack Compute (Nova): Incomplete Bug description: I am currently experiencing (random) cases of instances that are spun up having limited connectivity. There are about 650 instances in the environment and 45 networks. Network Info: - ML2/LinuxBridge/l2pop - VXLAN networks Symptoms: - On the local compute node, the instance tap is in the bridge. Everything looks good. - Instance is reachable from some, but not all, instances/devices in the same subnet across all compute and network nodes - On some compute nodes and network nodes, the ARP and FDB entries for the instance do not exist. Instances/devices on these nodes cannot communicate with the new instance. - No errors are logged Here are some observations for the non-working instances: - The corresponding Neutron port is stuck in a BUILD state - The binding:host_id value of the port (ie. compute-xxx) does not match the OS-EXT-SRV-ATTR:host value of the instance (ie. compute-zzz). For working instances, these values match. I am unable to replicate this consistently at this time, nor am I sure where to begin pinpointing the issue. Any help is appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1452886/+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 1455246] [NEW] remove old way to access config via REST
Public bug reported: https://review.openstack.org/#/c/170351/ supercedes https://review.openstack.org/#/c/150573/ as the way to retrieve user's local settings via REST for the Angular work. ** Affects: horizon Importance: Undecided Assignee: Cindy Lu (clu-m) Status: In Progress -- 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/1455246 Title: remove old way to access config via REST Status in OpenStack Dashboard (Horizon): In Progress Bug description: https://review.openstack.org/#/c/170351/ supercedes https://review.openstack.org/#/c/150573/ as the way to retrieve user's local settings via REST for the Angular work. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1455246/+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 1455252] [NEW] enabling serial console breaks live migration
Public bug reported: Version: openstack-nova-compute-2014.2.2-1.el7.noarch Enabling serial console causes the live migration process to fail with the following error in nova-compute.log: nova[12362]: 2015-05-14 21:57:21.108 ERROR nova.virt.libvirt.driver [-] [instance: a4d0bd8f-666e-4606-9e2a-4c583719719e] Live Migration failure: internal error: process exited while connecting to monitor: Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. qemu-kvm: -chardev socket,id=charserial0,host=1.2.3.4,port=1,server,nowait: Failed to bind socket: Cannot assign requested address qemu-kvm: -chardev socket,id=charserial0,host=1.2.3.4,port=1,server,nowait: chardev: opening backend socket failed The host IP is coming from the proxyclient_address setting which can't be 0.0.0.0, but even if it is changed to 0.0.0.0 the port number stays the same and will likely conflict on the destination. If there is no port conflict the live migration will succeed. ** 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/1455252 Title: enabling serial console breaks live migration Status in OpenStack Compute (Nova): New Bug description: Version: openstack-nova-compute-2014.2.2-1.el7.noarch Enabling serial console causes the live migration process to fail with the following error in nova-compute.log: nova[12362]: 2015-05-14 21:57:21.108 ERROR nova.virt.libvirt.driver [-] [instance: a4d0bd8f-666e-4606-9e2a-4c583719719e] Live Migration failure: internal error: process exited while connecting to monitor: Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. qemu-kvm: -chardev socket,id=charserial0,host=1.2.3.4,port=1,server,nowait: Failed to bind socket: Cannot assign requested address qemu-kvm: -chardev socket,id=charserial0,host=1.2.3.4,port=1,server,nowait: chardev: opening backend socket failed The host IP is coming from the proxyclient_address setting which can't be 0.0.0.0, but even if it is changed to 0.0.0.0 the port number stays the same and will likely conflict on the destination. If there is no port conflict the live migration will succeed. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1455252/+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 1454369] Re: nova needs to move to using the 'volume' service type
@Jay, per Cinder has added version discovery in Liberty so Nova should
go back to using the 'volume' service type as the volumev2 service type
will go away and version discovery should take care of making sure the
right API version is used. - what is the cinder version discovery
change mentioned? Is that in cinder - can you link to the patch?
Also, I think this is novaclient which means if the version discovery in
cinder is only liberty, we can't assume novaclient isn't talking to a
kilo cinder.
** Also affects: python-novaclient
Importance: Undecided
Status: New
** Changed in: python-novaclient
Status: New = Confirmed
** Changed in: python-novaclient
Importance: Undecided = Low
** No longer affects: nova
** Summary changed:
- nova needs to move to using the 'volume' service type
+ novaclient needs to move to using the 'volume' service type
--
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/1454369
Title:
novaclient needs to move to using the 'volume' service type
Status in Python client library for Nova:
Confirmed
Bug description:
It appears that there are still places in Nova that are being
hardcoded to use the Cinder V1 api. Evidence of this can be seen by
setting enable_v1_api to false in Cinder and then trying to use any of
the 'nova volume' commands. Errors like the following are produced:
[root@controller-x86-KVM-SCE-Refstack-SCERest-430gm-abd12ca7 ˜]# nova --debug
volume-create 1
DEBUG (session:195) REQ: curl -g -i -X GET http://169.55.21.52:5000/v2.0 -H
Accept: application/json -H User-Agent: python-keystoneclient
INFO (connectionpool:194) Starting new HTTP connection (1): 169.55.21.52
DEBUG (connectionpool:360) GET /v2.0 HTTP/1.1 200 338
DEBUG (session:224) RESP: [200] date: Sun, 10 May 2015 19:02:38 GMT vary:
X-Auth-Token content-length: 338 content-type: application/json
RESP BODY: {version: {status: stable, updated:
2014-04-17T00:00:00Z, media-types: [{base: application/json, type:
application/vnd.openstack.identity-v2.0+json}], id: v2.0, links:
[{href: http://169.55.21.52:5000/v2.0/;, rel: self}, {href:
http://docs.openstack.org/;, type: text/html, rel: describedby}]}}
DEBUG (v2:76) Making authentication request to
http://169.55.21.52:5000/v2.0/tokens
DEBUG (connectionpool:360) POST /v2.0/tokens HTTP/1.1 200 4531
DEBUG (iso8601:171) Parsed 2015-05-10T20:02:38Z into {'tz_sign': None,
'second_fraction': None, 'hour': u'20', 'daydash': u'10', 'tz_hour': None,
'month': None, 'timezone': u'Z', 'second': u'38', 'tz_minute': None, 'year':
u'2015', 'separator': u'T', 'monthdash': u'05', 'day': None, 'minute': u'02'}
with default timezone iso8601.iso8601.Utc object at 0x1a26bd0
DEBUG (iso8601:127) Got u'2015' for 'year' with default None
DEBUG (iso8601:127) Got u'05' for 'monthdash' with default None
DEBUG (iso8601:127) Got 5 for 'month' with default 5
DEBUG (iso8601:127) Got u'10' for 'daydash' with default None
DEBUG (iso8601:127) Got 10 for 'day' with default 10
DEBUG (iso8601:127) Got u'20' for 'hour' with default None
DEBUG (iso8601:127) Got u'02' for 'minute' with default None
DEBUG (iso8601:127) Got u'38' for 'second' with default None
DEBUG (session:195) REQ: curl -g -i -X POST
http://169.55.21.52:8776/v1/a7d1b663366740859037201fa8a48b03/volumes -H
User-Agent: python-novaclient -H Content-Type: application/json -H Accept:
application/json -H X-Auth-Token:
{SHA1}3724d0d949251ec67dd2d3b67201b7e196f36c47 -d '{volume: {display_name:
null, imageRef: null, availability_zone: null, volume_type: null,
display_description: null, snapshot_id: null, size: 1}}'
INFO (connectionpool:194) Starting new HTTP connection (1): 169.55.21.52
DEBUG (connectionpool:360) POST /v1/a7d1b663366740859037201fa8a48b03/volumes
HTTP/1.1 400 141
DEBUG (session:224) RESP:
DEBUG (shell:914) The server could not comply with the request since it is
either malformed or otherwise incorrect. (HTTP 400)
Traceback (most recent call last):
File /usr/lib/python2.7/site-packages/novaclient/shell.py, line 911, in
main
OpenStackComputeShell().main(argv)
File /usr/lib/python2.7/site-packages/novaclient/shell.py, line 838, in
main
args.func(self.cs, args)
File /usr/lib/python2.7/site-packages/novaclient/v2/shell.py, line 2053,
in do_volume_create
imageRef=args.image_id)
File /usr/lib/python2.7/site-packages/novaclient/v2/volumes.py, line 72,
in create
return self._create('/volumes', body, 'volume')
File /usr/lib/python2.7/site-packages/novaclient/base.py, line 161, in
_create
_resp, body = self.api.client.post(url, body=body)
File /usr/lib/python2.7/site-packages/keystoneclient/adapter.py, line
176, in post
return self.request(url, 'POST', **kwargs)
File /usr/lib/python2.7/site-packages/novaclient/client.py, line 96, in
request
raise
[Yahoo-eng-team] [Bug 1455314] [NEW] Typo in doc about configuation
Public bug reported: You can find the typo by searching configuation in http://docs.openstack.org/developer/glance/controllingservers.html ** 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/1455314 Title: Typo in doc about configuation Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: You can find the typo by searching configuation in http://docs.openstack.org/developer/glance/controllingservers.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1455314/+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 1455317] [NEW] Dashboard crashed graphics which look like a text browser
Public bug reported: Using CentOS Linux release 7.0.1406 (Core) Name: openstack-dashboard Arch: noarch Version : 2014.2.2 Release : 1.el7 Size: 20 M Repo: installed From repo : openstack-juno Summary : Openstack web user interface reference implementation URL : http://horizon.openstack.org/ License : ASL 2.0 and BSD Description : Openstack Dashboard is a web user interface for Openstack. The package : provides a reference implementation using the Django Horizon project, : mostly consisting of JavaScript and CSS to tie it altogether as a standalone : site. This is the 3rd time I encountered this problems; but so far all other services is running on the background. Don't know really what the cause of this. Based on the log, found this error: 2015-05-07 04:09:24,014 13219 INFO horizon.tables.actions django.utils.functional.__proxy__ object at 0x7ffb4858f9d0: Windows7_Access 2015-05-07 04:42:53,182 13221 ERROR horizon.exceptions Not Found: Instance could not be found (HTTP 404) (Request-ID: req-b01e5808-08c8-4129-9186-aae0be1720ea) Traceback (most recent call last): File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/project/instances/views.py, line 268, in get_data instance = api.nova.server_get(self.request, instance_id) File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/nova.py, line 559, in server_get return Server(novaclient(request).servers.get(instance_id), request) File /usr/lib/python2.7/site-packages/novaclient/v1_1/servers.py, line 563, in get return self._get(/servers/%s % base.getid(server), server) File /usr/lib/python2.7/site-packages/novaclient/base.py, line 93, in _get _resp, body = self.api.client.get(url) File /usr/lib/python2.7/site-packages/novaclient/client.py, line 487, in get return self._cs_request(url, 'GET', **kwargs) File /usr/lib/python2.7/site-packages/novaclient/client.py, line 465, in _cs_request resp, body = self._time_request(url, method, **kwargs) File /usr/lib/python2.7/site-packages/novaclient/client.py, line 439, in _time_request resp, body = self.request(url, method, **kwargs) File /usr/lib/python2.7/site-packages/novaclient/client.py, line 433, in request raise exceptions.from_response(resp, body, url, method) NotFound: Instance could not be found (HTTP 404) (Request-ID: req-b01e5808-08c8-4129-9186-aae0be1720ea) 2015-05-07 04:54:31,672 13221 INFO openstack_auth.views Logging out user lumad. 2015-05-07 04:54:31,680 13221 INFO openstack_auth.views Could not delete token 2015-05-07 22:50:51,319 13217 INFO openstack_auth.forms Login successful for user lumad. 2015-05-07 22:53:05,866 13216 INFO horizon.tables.actions django.utils.functional.__proxy__ object at 0x7ffb53478c90: Windows7_Access 2015-05-07 23:03:43,950 13220 INFO openstack_auth.views Logging out user . 2015-05-07 23:03:45,930 13220 INFO openstack_auth.forms Login successful for user admin. 2015-05-07 23:04:02,510 13221 INFO horizon.tables.actions django.utils.functional.__proxy__ object at 0x7ffb485d54d0: Windows2k7_Office What I did before i used to remove the openstack-dashboard, reinstall and restore local_settings from the backup. I am afraid now to update as the Kilo is now release. Hope someone can enlighten. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: Picture of the said bug https://bugs.launchpad.net/bugs/1455317/+attachment/4397864/+files/text_dashboard.png ** Description changed: Using CentOS Linux release 7.0.1406 (Core) Name: openstack-dashboard Arch: noarch Version : 2014.2.2 Release : 1.el7 Size: 20 M Repo: installed From repo : openstack-juno Summary : Openstack web user interface reference implementation URL : http://horizon.openstack.org/ License : ASL 2.0 and BSD Description : Openstack Dashboard is a web user interface for Openstack. The package - : provides a reference implementation using the Django Horizon project, - : mostly consisting of JavaScript and CSS to tie it altogether as a standalone - : site. + : provides a reference implementation using the Django Horizon project, + : mostly consisting of JavaScript and CSS to tie it altogether as a standalone + : site. + This is the 3rd time I encountered this problems; but so far all other + services is running on the background. Don't know really what the cause + of this. - It always got bug, I don't what really cause with it. This is the 3rd time I encountered this problems; but so far all other services is running on the background. - + Based on the log, found this error: 2015-05-07 04:09:24,014 13219 INFO horizon.tables.actions django.utils.functional.__proxy__
[Yahoo-eng-team] [Bug 1455320] [NEW] OVS-agent: AttributeError: 'NoneType' object has no attribute 'update'
Public bug reported: change I90b4d2485e3e491f496dfb7bdee03d57f393be35 seems failing to handle cases where db_get_val returns None gracefully. http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIkF0dHJpYnV0ZUVycm9yOiAnTm9uZVR5cGUnIG9iamVjdCBoYXMgbm8gYXR0cmlidXRlICd1cGRhdGUnXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzE2NjIyOTg1NDZ9 [req-e235481e-8981-4f15-bf62-0c47b97505dd None None] Error while processing VIF ports 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent Traceback (most recent call last): 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/new/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1643, in rpc_loop 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent ovs_restarted) 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/new/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1412, in process_network_ports 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent devices_added_updated, ovs_restarted)) 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/new/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1318, in treat_devices_added_or_updated 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/new/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1220, in treat_vif_port 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent fixed_ips, device_owner, ovs_restarted) 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/new/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 730, in port_bound 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent port_other_config.update(vlan_mapping) 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent AttributeError: 'NoneType' object has no attribute 'update' 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent ** 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/1455320 Title: OVS-agent: AttributeError: 'NoneType' object has no attribute 'update' Status in OpenStack Neutron (virtual network service): New Bug description: change I90b4d2485e3e491f496dfb7bdee03d57f393be35 seems failing to handle cases where db_get_val returns None gracefully. http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIkF0dHJpYnV0ZUVycm9yOiAnTm9uZVR5cGUnIG9iamVjdCBoYXMgbm8gYXR0cmlidXRlICd1cGRhdGUnXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzE2NjIyOTg1NDZ9 [req-e235481e-8981-4f15-bf62-0c47b97505dd None None] Error while processing VIF ports 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent Traceback (most recent call last): 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/new/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1643, in rpc_loop 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent ovs_restarted) 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/new/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1412, in process_network_ports 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent devices_added_updated, ovs_restarted)) 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/new/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1318, in treat_devices_added_or_updated 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/new/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1220, in treat_vif_port 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent fixed_ips, device_owner, ovs_restarted) 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/new/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 730, in port_bound 2015-05-15 03:36:33.954 4996 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent
[Yahoo-eng-team] [Bug 1455303] [NEW] centos7 + firewalld leads to tempest ipv6 failures
Public bug reported: Right now, centos7+neutron fails in tempest due to not setting netfilter to run on bridges. I have a review out for that [1] However, correctly enabling these settings leads to two further tempest failures tempest.scenario.test_network_v6.TestGettingAddress.test_dhcp6_stateless_from_os [79.318876s] ... FAILED tempest.scenario.test_network_v6.TestGettingAddress.test_slaac_from_os [70.714588s] ... FAILED The failure is a lack of ipv6 communication tempest_lib.exceptions.SSHExecCommandFailed: Command 'ping6 -c1 -w1 -s56 2003::f816:3eff:fe6d:bd04', exit status: 1, Error: I have two runs just executing these tests: * fail with net.bridge.bridge-nf-call-ip6tables=1 - http://logs.openstack.org/89/179689/16/check/check-tempest-dsvm-centos7/8d6835c/ * pass with net.bridge.bridge-nf-call-ip6tables=0 - http://logs.openstack.org/89/179689/17/check/check-tempest-dsvm-centos7/dc97d29/ However, if I disable firewalld, this starts working (http://logs.openstack.org/89/179689/21/check/check-tempest-dsvm- centos7/530c356/) I note that RDO, redhat's own deployment method, disables firewalld, because it uses [2]. So I don't really expect this is high on anyone's priority list, but that's where the logs are if we want to dig into this [1] https://review.openstack.org/180867 [2] https://github.com/redhat-openstack/openstack-puppet-modules/blob/master/firewall/manifests/linux/redhat.pp#L27 ** 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/1455303 Title: centos7 + firewalld leads to tempest ipv6 failures Status in OpenStack Neutron (virtual network service): New Bug description: Right now, centos7+neutron fails in tempest due to not setting netfilter to run on bridges. I have a review out for that [1] However, correctly enabling these settings leads to two further tempest failures tempest.scenario.test_network_v6.TestGettingAddress.test_dhcp6_stateless_from_os [79.318876s] ... FAILED tempest.scenario.test_network_v6.TestGettingAddress.test_slaac_from_os [70.714588s] ... FAILED The failure is a lack of ipv6 communication tempest_lib.exceptions.SSHExecCommandFailed: Command 'ping6 -c1 -w1 -s56 2003::f816:3eff:fe6d:bd04', exit status: 1, Error: I have two runs just executing these tests: * fail with net.bridge.bridge-nf-call-ip6tables=1 - http://logs.openstack.org/89/179689/16/check/check-tempest-dsvm-centos7/8d6835c/ * pass with net.bridge.bridge-nf-call-ip6tables=0 - http://logs.openstack.org/89/179689/17/check/check-tempest-dsvm-centos7/dc97d29/ However, if I disable firewalld, this starts working (http://logs.openstack.org/89/179689/21/check/check-tempest-dsvm- centos7/530c356/) I note that RDO, redhat's own deployment method, disables firewalld, because it uses [2]. So I don't really expect this is high on anyone's priority list, but that's where the logs are if we want to dig into this [1] https://review.openstack.org/180867 [2] https://github.com/redhat-openstack/openstack-puppet-modules/blob/master/firewall/manifests/linux/redhat.pp#L27 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1455303/+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 1454966] [NEW] [Sahara] Job Exeuctions page should be Jobs
Public bug reported: The Jobs page has a title Job Executions, which is confusing, for job_execution was already deprecated in Sahara. Need to rename to Jobs. ** Affects: horizon Importance: Undecided Assignee: Ken Chen (ken-chen-i) Status: New ** Changed in: horizon Assignee: (unassigned) = Ken Chen (ken-chen-i) -- 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/1454966 Title: [Sahara] Job Exeuctions page should be Jobs Status in OpenStack Dashboard (Horizon): New Bug description: The Jobs page has a title Job Executions, which is confusing, for job_execution was already deprecated in Sahara. Need to rename to Jobs. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1454966/+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 1454968] [NEW] hard to understand the uri printed in the log
Public bug reported:
In keystone's log file, we can easily find some uri printed like this:
http://127.0.0.1:35357/v3/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens
seems there is something wrong when we are trying to log the uri in the log
file.
LOG.info('%(req_method)s %(uri)s', {
'req_method': req.environ['REQUEST_METHOD'].upper(),
'uri': wsgiref.util.request_uri(req.environ),
})
code is here:
https://github.com/openstack/keystone/blob/master/keystone/common/wsgi.py#L232,
but seems it has already been wrong when the req is passed in.
** 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/1454968
Title:
hard to understand the uri printed in the log
Status in OpenStack Identity (Keystone):
New
Bug description:
In keystone's log file, we can easily find some uri printed like this:
http://127.0.0.1:35357/v3/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens
seems there is something wrong when we are trying to log the uri in the log
file.
LOG.info('%(req_method)s %(uri)s', {
'req_method': req.environ['REQUEST_METHOD'].upper(),
'uri': wsgiref.util.request_uri(req.environ),
})
code is here:
https://github.com/openstack/keystone/blob/master/keystone/common/wsgi.py#L232,
but seems it has already been wrong when the req is passed in.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1454968/+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 1454974] [NEW] FWAAS
Public bug reported: FWAAS - After adding FW rule when previous ASSIGNED TO POLICY RULES exist the table is asymmetric - Image attached . We should leave the edit rule at the right side and the in policy field blank. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: Screenshot from 2015-05-13 15:21:06.png https://bugs.launchpad.net/bugs/1454974/+attachment/4397225/+files/Screenshot%20from%202015-05-13%2015%3A21%3A06.png -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1454974 Title: FWAAS Status in OpenStack Dashboard (Horizon): New Bug description: FWAAS - After adding FW rule when previous ASSIGNED TO POLICY RULES exist the table is asymmetric - Image attached . We should leave the edit rule at the right side and the in policy field blank. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1454974/+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 1454385] Re: can't boot vm instance on network with port_security_enabled=False
This is because subnet is missing. After creating subnet, vm booted. ** Changed in: nova Status: New = Invalid ** 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/1454385 Title: can't boot vm instance on network with port_security_enabled=False Status in OpenStack Neutron (virtual network service): Invalid Status in OpenStack Compute (Nova): Invalid Bug description: $ neutron net-create --port_security_enabled=False test-net Created a new network: +---+--+ | Field | Value| +---+--+ | admin_state_up| True | | id| 4811c94c-f7db-49bf-86c6-6aa270e79b3c | | mtu | 0| | name | test-net | | port_security_enabled | False| | provider:network_type | vxlan| | provider:physical_network | | | provider:segmentation_id | 1003 | | router:external | False| | shared| False| | status| ACTIVE | | subnets | | | tenant_id | dad7ba3715264009b90176bd29c779c2 | | vlan_transparent | False| +---+--+ $ nova boot --nic net-id=4811c94c-f7db-49bf-86c6-6aa270e79b3c --flavor m1.micro --image cirros-0.3.2-x86_64-uec net-test-vm ERROR (BadRequest): Network 4811c94c-f7db-49bf-86c6-6aa270e79b3c requires a subnet in order to boot instances on. (HTTP 400) (Request-ID: req-233d9113-96ae-49bd-abfe-e2f29350af1f) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1454385/+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 1454954] [NEW] [sahara] cluster page need more info
Public bug reported: We need to put plugin name and plugin version info in the clusters page table for easy reference. ** Affects: horizon Importance: Undecided Assignee: Ken Chen (ken-chen-i) Status: In Progress -- 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/1454954 Title: [sahara] cluster page need more info Status in OpenStack Dashboard (Horizon): In Progress Bug description: We need to put plugin name and plugin version info in the clusters page table for easy reference. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1454954/+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 1454978] [NEW] [iSCSI Multipath]Thousands of multipath -ll mp-id are executed during volume detachment when multiple LUNs are exposed on a same target
Public bug reported:
iSCSI multipath has performance issue on volume detachment when multiple
LUNs are exposed via single target(iqn).
1. We are using VNX as cinder backends. VNX is exposing multiple LUNs
via a iqn. And a LUN is exposed via different iqns for multipathing.
Libvirt driver is used in nova. And the virt_type is kvm.
2. After we attached 100 volumes to VMs, and then do volume detachment
in batch, we noticed that thousands of multipath -ll mp_id are
executed per a volume detachement. In out enviornment, a multipath -ll
mp_id takes about 0.2s, the performance is bad.
3. Why there are so many multipath -ll mp-id triggerred?
In order to find all pathes of a multipath device, the code went through all
the devices under /dev/disk/by-path which used the same iqn and execute
‘multipath –ll’ on each of them to get the multipath id. When the multipath id
of a device is the same as the volume to be detached. Then it is a path of the
volume. When each iqn only expose one LUN, this code do not expose performance
issue. However, when multiple luns are expose via a single iqn, the problems
comes out.
Assuming taht we have n LUNs attached. Each LUN has m iqns for multipathing,
then there will be m*n devices under /dev/disk/by-path. And they are sharing m
iqns. Then,
-- Code line 623- 644 will trigger o(n*m) times of multipath -ll mp-id
-- Code line 648-649 will trigger o(!m) times of multipath -ll mp-id
nova/nova/virt/libvirt/volume.py
LibvirtISCSIVolumeDriver._disconnect_volume_multipath_iscsi
618 out = self._run_iscsiadm_discover(iscsi_properties)
619
620 # Extract targets for the current multipath device.
621 ips_iqns = []
622 entries = self._get_iscsi_devices()
623 for ip, iqn in self._get_target_portals_from_iscsiadm_output(out):
624ip_iqn = %s-iscsi-%s % (ip.split(,)[0], iqn)
625for entry in entries:
626entry_ip_iqn = entry.split(-lun-)[0]
627if entry_ip_iqn[:3] == ip-:
628entry_ip_iqn = entry_ip_iqn[3:]
629elif entry_ip_iqn[:4] == pci-:
630# Look at an offset of len('pci-:00:00.0')
631offset = entry_ip_iqn.find(ip-, 16, 21)
632entry_ip_iqn = entry_ip_iqn[(offset + 3):]
633if (ip_iqn != entry_ip_iqn):
634continue
635entry_real_path = os.path.realpath(/dev/disk/by-path/%s %
636 entry)
637entry_mpdev = self._get_multipath_device_name(entry_real_path)
638if entry_mpdev == multipath_device:
639ips_iqns.append([ip, iqn])
640break
641
642 if not devices:
643 # disconnect if no other multipath devices
644 self._disconnect_mpath(iscsi_properties, ips_iqns)
645 return
646
647 # Get a target for all other multipath devices
648 other_iqns = [self._get_multipath_iqn(device)
649 for device in devices]
Code version =
stack@openstack-performance:~/tina/nova_iscsi_mp/nova$ git log -1
commit f4504f3575b35ec14390b4b678e441fcf953f47b
Merge: 3f21f60 5fbd852
Author: Jenkins jenk...@review.openstack.org
Date: Tue May 12 22:46:43 2015 +
Merge Remove db layer hard-code permission checks for
network_get_all_by_host
** Affects: nova
Importance: Undecided
Status: New
** Description changed:
- iSCSI multipath has performance issue on volume detachment when multiple LUNs
are exposed via single target(iqn).
- 1. We am using VNX as cinder backends. VNX is exposing multiple LUNs via a
iqn. And a LUN is exposed via different iqns for multipathing. Libvirt driver
is used in nova. And the virt_type is kvm.
+ iSCSI multipath has performance issue on volume detachment when multiple
+ LUNs are exposed via single target(iqn).
+
+ 1. We are using VNX as cinder backends. VNX is exposing multiple LUNs
+ via a iqn. And a LUN is exposed via different iqns for multipathing.
+ Libvirt driver is used in nova. And the virt_type is kvm.
2. After we attached 100 volumes to VMs, and then do volume detachment
in batch, we noticed that thousands of multipath -ll mp_id are
executed per a volume detachement. In out enviornment, a multipath -ll
mp_id takes about 0.2s, the performance is bad.
3. Why there are so many multipath -ll mp-id triggerred?
- In order to find all pathes of a multipath device, the code went through all
the devices under /dev/disk/by-path which used the same iqn and execute
‘multipath –ll’ on each of them to get the multipath id. When the multipath id
of a device is the same as the volume to be detached. Then it is a path of the
volume. When each iqn only expose one LUN, this code do not expose performance
issue. However, when multiple luns are expose via a single iqn, the problems
comes out.
+ In order to find all pathes of a multipath device, the code went through all
the devices under /dev/disk/by-path which used the same iqn and execute
‘multipath –ll’ on each of them
[Yahoo-eng-team] [Bug 1454986] [NEW] neutron lbaas-member-list with pool id shows all members
Public bug reported: In neutron, when using cli command lbaas-member-list with pool id as a parameter expecting to get only members of the specific pool, all members are shown same problem for lbaas-member-show CLI command members are shown whithout minding their pool belonging Example: mysql select id, pool_id from lbaas_members; +--+--+ | id | pool_id | +--+--+ | 479db14d-6368-4a9a-9892-4c19dc07c291 | 4ca0a46f-640c-497f-9860-89f705d955f8 | | b0b6b998-6031-4dfb-b6b3-0a77a3052d1c | 4ca0a46f-640c-497f-9860-89f705d955f8 | | dcdf3b94-16c7-4d3a-a80c-24ce727fb508 | 95e87b8f-2d6e-442d-b761-87ea3a446f17 | | b77a2059-7950-4355-9409-1af7bef9057f | 95e87b8f-2d6e-442d-b761-87ea3a446f17 | +--+--+ First 2 members belong to pool 4ca0a46f-640c-497f-9860-89f705d955f8 Last 2 members belong to pool 95e87b8f-2d6e-442d-b761-87ea3a446f17 CLI commands output: neutron lbaas-pool-list +--++--++ | id | name | protocol | admin_state_up | +--++--++ | 4ca0a46f-640c-497f-9860-89f705d955f8 | HTTP pool | HTTP | True | | 95e87b8f-2d6e-442d-b761-87ea3a446f17 | HTTPS pool | HTTP | True | +--++--++ neutron lbaas-member-list 4ca0a46f-640c-497f-9860-89f705d955f8 +--+---+---++--++ | id | address | protocol_port | weight | subnet_id| admin_state_up | +--+---+---++--++ | 479db14d-6368-4a9a-9892-4c19dc07c291 | 192.168.23.3 |80 | 1 | 2ed7e070-89bf-401d-b8d9-4a61522d0101 | True | | b0b6b998-6031-4dfb-b6b3-0a77a3052d1c | 192.168.23.38 |80 | 1 | 2ed7e070-89bf-401d-b8d9-4a61522d0101 | True | | b77a2059-7950-4355-9409-1af7bef9057f | 192.168.23.40 |80 | 1 | 2ed7e070-89bf-401d-b8d9-4a61522d0101 | True | | dcdf3b94-16c7-4d3a-a80c-24ce727fb508 | 192.168.23.39 |80 | 1 | 2ed7e070-89bf-401d-b8d9-4a61522d0101 | True | +--+---+---++--++ All members are shown neutron lbaas-member-show 479db14d-6368-4a9a-9892-4c19dc07c291 95e87b8f-2d6e-442d-b761-87ea3a446f17 ++--+ | Field | Value| ++--+ | address| 192.168.23.3 | | admin_state_up | True | | id | 479db14d-6368-4a9a-9892-4c19dc07c291 | | protocol_port | 80 | | subnet_id | 2ed7e070-89bf-401d-b8d9-4a61522d0101 | | tenant_id | 2d83e8e0f4584e3cacab9b2c38ac9e5e | | weight | 1| ++--+ Same here, member is shown while it actually belongs to other pool ** Affects: neutron Importance: Undecided Status: New ** Tags: lbaas ** Description changed: In neutron, when using cli command lbaas-member-list with pool id as a parameter expecting to get only members of the specific pool, all members are shown - same problem for lbaas-member-list CLI command - members are shown whithout minding theit pool belonging + same problem for lbaas-member-show CLI command + members are shown whithout minding their pool belonging Example: - mysql select id, pool_id from lbaas_members; +--+--+ | id | pool_id | +--+--+ | 479db14d-6368-4a9a-9892-4c19dc07c291 | 4ca0a46f-640c-497f-9860-89f705d955f8 | | b0b6b998-6031-4dfb-b6b3-0a77a3052d1c | 4ca0a46f-640c-497f-9860-89f705d955f8 | | dcdf3b94-16c7-4d3a-a80c-24ce727fb508 | 95e87b8f-2d6e-442d-b761-87ea3a446f17 | | b77a2059-7950-4355-9409-1af7bef9057f | 95e87b8f-2d6e-442d-b761-87ea3a446f17 | +--+--+ First 2 members belong to pool 4ca0a46f-640c-497f-9860-89f705d955f8 - Last 2 members belong to pool
[Yahoo-eng-team] [Bug 1455005] [NEW] DVR Cannot open network 'fip' namespace error when updating router's gateway
Public bug reported: When updating a distributed router's gateway when one is already set there is an error in l3 agent's log on the node where 'dvr_snat' is running. Cannot open network namespace fip-dc7937bc-2627-422b- 8c71-6779aa675a81: No such file or directory 2015-05-14 11:39:15.862 21386 DEBUG neutron.agent.linux.utils [-] Running command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'fip-dc7937bc-2627-422b-8c71-6779aa675a81', 'ip', '-o', 'link', 'show', 'fpr-43e4f718-e'] create_process /usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:84 2015-05-14 11:39:15.942 21386 DEBUG neutron.agent.linux.utils [-] Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'fip-dc7937bc-2627-422b-8c71-6779aa675a81', 'ip', '-o', 'link', 'show', 'fpr-43e4f718-e'] Exit code: 1 Stdin: Stdout: Stderr: Cannot open network namespace fip-dc7937bc-2627-422b-8c71-6779aa675a81: No such file or directory execute /usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:134 2015-05-14 11:39:15.943 21386 DEBUG neutron.agent.l3.router_info [-] No Interface for floating IPs router: 43e4f718-e0fc-435a-8144-445aa54eeecc process_floating_ip_addresses /usr/lib/python2.7/site-packages/neutron/agent/l3/router_info.py:229 It seems that it's not related to just this action but also for association of floating IP. Version == python-neutron-2015.1.0-1.el7ost.noarch ** 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/1455005 Title: DVR Cannot open network 'fip' namespace error when updating router's gateway Status in OpenStack Neutron (virtual network service): New Bug description: When updating a distributed router's gateway when one is already set there is an error in l3 agent's log on the node where 'dvr_snat' is running. Cannot open network namespace fip-dc7937bc-2627-422b- 8c71-6779aa675a81: No such file or directory 2015-05-14 11:39:15.862 21386 DEBUG neutron.agent.linux.utils [-] Running command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'fip-dc7937bc-2627-422b-8c71-6779aa675a81', 'ip', '-o', 'link', 'show', 'fpr-43e4f718-e'] create_process /usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:84 2015-05-14 11:39:15.942 21386 DEBUG neutron.agent.linux.utils [-] Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'fip-dc7937bc-2627-422b-8c71-6779aa675a81', 'ip', '-o', 'link', 'show', 'fpr-43e4f718-e'] Exit code: 1 Stdin: Stdout: Stderr: Cannot open network namespace fip-dc7937bc-2627-422b-8c71-6779aa675a81: No such file or directory execute /usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:134 2015-05-14 11:39:15.943 21386 DEBUG neutron.agent.l3.router_info [-] No Interface for floating IPs router: 43e4f718-e0fc-435a-8144-445aa54eeecc process_floating_ip_addresses /usr/lib/python2.7/site-packages/neutron/agent/l3/router_info.py:229 It seems that it's not related to just this action but also for association of floating IP. Version == python-neutron-2015.1.0-1.el7ost.noarch To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1455005/+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 1455000] [NEW] Ironic: nova delete doesn't work when instance is spawming
Public bug reported: The nova delete command can be issued while the instance is spawning and even Ironic support aborting a deployment mid-operation (when node is in WAITDEPLOY state). But if you issue a nova delete while the instance is spawming with the Ironic driver the instance will be stuck there and nothing will happen. That's because of a lock[1], basically the Ironic driver won't return from spawn() until the node have been successfully deployed or error out and that's holding the lock. WORKAROUND: As a work around, you can issue nova delete to the instance and that will mark the task_state as deleting. And then you can delete the instance directly via the Ironic API as well by doing: $ ironic node-set-provision-state node uuid deleted That will realease the instance. [1] https://github.com/openstack/nova/blob/3841b8254e0dd820d26377312b6c004f4bd9b58e/nova/compute/manager.py#L2431 ** Affects: nova Importance: Undecided Assignee: Lucas Alvares Gomes (lucasagomes) Status: New ** Tags: ironic ** Changed in: nova Assignee: (unassigned) = Lucas Alvares Gomes (lucasagomes) ** Tags added: ironic -- 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/1455000 Title: Ironic: nova delete doesn't work when instance is spawming Status in OpenStack Compute (Nova): New Bug description: The nova delete command can be issued while the instance is spawning and even Ironic support aborting a deployment mid-operation (when node is in WAITDEPLOY state). But if you issue a nova delete while the instance is spawming with the Ironic driver the instance will be stuck there and nothing will happen. That's because of a lock[1], basically the Ironic driver won't return from spawn() until the node have been successfully deployed or error out and that's holding the lock. WORKAROUND: As a work around, you can issue nova delete to the instance and that will mark the task_state as deleting. And then you can delete the instance directly via the Ironic API as well by doing: $ ironic node-set-provision-state node uuid deleted That will realease the instance. [1] https://github.com/openstack/nova/blob/3841b8254e0dd820d26377312b6c004f4bd9b58e/nova/compute/manager.py#L2431 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1455000/+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 1455034] [NEW] Deleting nonexistent end-point gives incorrect error message
Public bug reported: I'm trying to delete an end-point with invalid id or id that does not exist in the system and getting the below error message: ERROR: openstack More than one endpoint exists with the name 'non-existing-id'. While the more appropriate message would be to say, No endpoint exists with the name 'non-existing-id'. osc:/ # openstack --version openstack 0.4.1 osc:/ # openstack --insecure endpoint list +--+---+--+--+-+---+---+ | ID | Region| Service Name | Service Type | Enabled | Interface | URL | +--+---+--+--+-+---+---+ | 14d171e5d9914d8fa19c6bc539acd34a | None | keystone | identity | True| admin | https://keystone:35357/v3 | +--+---+--+--+-+---+---+ osc:/ # openstack --insecure endpoint delete 14d171e5d9914d8fa19c6bc539acd34b ERROR: openstack More than one endpoint exists with the name '14d171e5d9914d8fa19c6bc539acd34b'. osc:/ # openstack --insecure endpoint delete non-existing-id ERROR: openstack More than one endpoint exists with the name 'non-existing-id'. # zypper info openstack-keystone Loading repository data... Reading installed packages... Information for package openstack-keystone: --- Repository: staging Name: openstack-keystone Version: 2014.2.3.dev15-1.1 Arch: noarch Vendor: obs://build.opensuse.org/Cloud:OpenStack Installed: Yes Status: up-to-date Installed Size: 81.9 KiB Summary: OpenStack Identity Service (Keystone) Description: Keystone is an OpenStack project that provides Identity, Token, Catalog and Policy services for use specifically by projects in the OpenStack family. ** Affects: keystone Importance: Undecided Status: New ** Tags: error-messge -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1455034 Title: Deleting nonexistent end-point gives incorrect error message Status in OpenStack Identity (Keystone): New Bug description: I'm trying to delete an end-point with invalid id or id that does not exist in the system and getting the below error message: ERROR: openstack More than one endpoint exists with the name 'non-existing-id'. While the more appropriate message would be to say, No endpoint exists with the name 'non-existing-id'. osc:/ # openstack --version openstack 0.4.1 osc:/ # openstack --insecure endpoint list +--+---+--+--+-+---+---+ | ID | Region| Service Name | Service Type | Enabled | Interface | URL | +--+---+--+--+-+---+---+ | 14d171e5d9914d8fa19c6bc539acd34a | None | keystone | identity | True| admin | https://keystone:35357/v3 | +--+---+--+--+-+---+---+ osc:/ # openstack --insecure endpoint delete 14d171e5d9914d8fa19c6bc539acd34b ERROR: openstack More than one endpoint exists with the name '14d171e5d9914d8fa19c6bc539acd34b'. osc:/ # openstack --insecure endpoint delete non-existing-id ERROR: openstack More than one endpoint exists with the name 'non-existing-id'. # zypper info openstack-keystone Loading repository data... Reading installed packages... Information for package openstack-keystone: --- Repository: staging Name: openstack-keystone Version: 2014.2.3.dev15-1.1 Arch: noarch Vendor: obs://build.opensuse.org/Cloud:OpenStack Installed: Yes Status: up-to-date Installed Size: 81.9 KiB Summary: OpenStack Identity Service (Keystone) Description: Keystone is an OpenStack project that provides Identity, Token, Catalog and Policy services for use specifically by projects in the OpenStack family. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1455034/+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 1455040] [NEW] page title is missing in load balancer detail page
Public bug reported: Page title id missing in load balancer detail page ** Affects: horizon Importance: Undecided Assignee: Masco Kaliyamoorthy (masco) Status: New ** Changed in: horizon Assignee: (unassigned) = Masco Kaliyamoorthy (masco) -- 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/1455040 Title: page title is missing in load balancer detail page Status in OpenStack Dashboard (Horizon): New Bug description: Page title id missing in load balancer detail page To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1455040/+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 1455042] [NEW] Stale metadata processes are not cleaned up on l3 agent sync
Public bug reported: L3 agent cleans up stale namespaces of deleted routers during sync, but metadata processes are still running (forever :0) which leads to waste of resources. Can be easily reproduced by deleting router while l3 agent is stopped. After starting the agent will delete namespace but not md process. ** Affects: neutron Importance: Undecided Assignee: Oleg Bondarev (obondarev) 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/1455042 Title: Stale metadata processes are not cleaned up on l3 agent sync Status in OpenStack Neutron (virtual network service): New Bug description: L3 agent cleans up stale namespaces of deleted routers during sync, but metadata processes are still running (forever :0) which leads to waste of resources. Can be easily reproduced by deleting router while l3 agent is stopped. After starting the agent will delete namespace but not md process. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1455042/+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 1455012] [NEW] page title is missing in firewalls panel
Public bug reported: In firewalls panel, page title is missing and firewall, rule and policy detail pages not having proper page titles. ** Affects: horizon Importance: Undecided Assignee: Masco Kaliyamoorthy (masco) Status: New ** Changed in: horizon Assignee: (unassigned) = Masco Kaliyamoorthy (masco) -- 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/1455012 Title: page title is missing in firewalls panel Status in OpenStack Dashboard (Horizon): New Bug description: In firewalls panel, page title is missing and firewall, rule and policy detail pages not having proper page titles. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1455012/+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 1455026] [NEW] page titles for VPN panel detail pages are missing
Public bug reported: page title for VPN panel detail pages are missing or not correct. ** Affects: horizon Importance: Undecided Assignee: Masco Kaliyamoorthy (masco) Status: New ** Changed in: horizon Assignee: (unassigned) = Masco Kaliyamoorthy (masco) -- 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/1455026 Title: page titles for VPN panel detail pages are missing Status in OpenStack Dashboard (Horizon): New Bug description: page title for VPN panel detail pages are missing or not correct. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1455026/+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 1455298] [NEW] unreasonable error message returned when an empty body was posted to POST request
Public bug reported:
For now, if a POST request with an empty body, the bad request message
will return a code-level error info, this is unfriendly to end users.
The curl request of a POST request with a empty body:
curl -g -i --cacert /opt/stack/data/CA/int-ca/ca-chain.pem -X POST
http://10.250.10.15:35357/v2.0/users -H Content-Type: application/json
-H Accept: application/json -H X-Auth-Token:
b648b3deb12d4f3bb114a303eb153507 -d '{}'
the return message:
{error: {message: create_user() takes exactly 3 arguments (2
given), code: 400, title: Bad Request}}
The others keystone API has the same issue.
the reasonable return of a this type request is like this:
curl -g -i --cacert /opt/stack/data/CA/int-ca/ca-chain.pem -X POST
http://10.250.10.15:8776/v2/30be1fc9a03c4e94ab05c403a8a377f2/volumes -H
User-Agent: python-cinderclient -H Content-Type: application/json -H
Accept: application/json -H X-Auth-Token:
b648b3deb12d4f3bb114a303eb153507 -d '{}'
{badRequest: {message: Missing required element 'volume' in request
body, code: 400}}
** Affects: keystone
Importance: Undecided
Assignee: Liusheng (liusheng)
Status: New
** Changed in: keystone
Assignee: (unassigned) = Liusheng (liusheng)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1455298
Title:
unreasonable error message returned when an empty body was posted to
POST request
Status in OpenStack Identity (Keystone):
New
Bug description:
For now, if a POST request with an empty body, the bad request
message will return a code-level error info, this is unfriendly to end
users.
The curl request of a POST request with a empty body:
curl -g -i --cacert /opt/stack/data/CA/int-ca/ca-chain.pem -X POST
http://10.250.10.15:35357/v2.0/users -H Content-Type:
application/json -H Accept: application/json -H X-Auth-Token:
b648b3deb12d4f3bb114a303eb153507 -d '{}'
the return message:
{error: {message: create_user() takes exactly 3 arguments (2
given), code: 400, title: Bad Request}}
The others keystone API has the same issue.
the reasonable return of a this type request is like this:
curl -g -i --cacert /opt/stack/data/CA/int-ca/ca-chain.pem -X POST
http://10.250.10.15:8776/v2/30be1fc9a03c4e94ab05c403a8a377f2/volumes
-H User-Agent: python-cinderclient -H Content-Type:
application/json -H Accept: application/json -H X-Auth-Token:
b648b3deb12d4f3bb114a303eb153507 -d '{}'
{badRequest: {message: Missing required element 'volume' in
request body, code: 400}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1455298/+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 1455308] [NEW] The deprecated noauth middleware need to be removed
Public bug reported: As The TODO list in source code marked, the noauth middleware has been deprecated and should be removed in Liberty. So we should cleanup it now. ** Affects: nova Importance: Undecided Assignee: Liusheng (liusheng) Status: New ** Changed in: nova Assignee: (unassigned) = Liusheng (liusheng) -- 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/1455308 Title: The deprecated noauth middleware need to be removed Status in OpenStack Compute (Nova): New Bug description: As The TODO list in source code marked, the noauth middleware has been deprecated and should be removed in Liberty. So we should cleanup it now. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1455308/+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 1455311] [NEW] [v1] image-list doesn't honour the filter --is-public
Public bug reported: Recreation steps: 1. create a new image keeping is-public with False 2. run 'glance image-list --is-public True' ** Affects: glance Importance: High Assignee: Fei Long Wang (flwang) Status: In Progress ** Changed in: glance Assignee: (unassigned) = Fei Long Wang (flwang) ** Changed in: glance Importance: Undecided = High ** Changed in: glance Status: New = In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1455311 Title: [v1] image-list doesn't honour the filter --is-public Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Bug description: Recreation steps: 1. create a new image keeping is-public with False 2. run 'glance image-list --is-public True' To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1455311/+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
