[Yahoo-eng-team] [Bug 1424537] [NEW] Error creating nova Instance for cirros image 0.3.1 on AIO-HAVANA Ubuntu 12.0.4 package
Public bug reported: Problem - Error creating Nova Instance using Cirros 0.3.1 image on AIO- HAVANA Ubuntu 12.04 LTS package. Steps to reproduce - -Install VMware workstation. -Create VM with 2-VCPU, 1 GB RAM, 40 GB DIsk, 2 NICs, VT-X enabled. -Install Ubuntu 12.04 LTS. -Install GIT, and Openstack packages keystone, glance, nova, python, etc. -Using SSH open Horizon Dashboard. -Create an instance using Cirros 0.3.1 image. -Observe the error. -Try to give a soft reboot, again observe an error "Not enough permissions" Refer this for detailed installation procedure that was folowed == http://www.discoposse.com/index.php/2014/01/26/openstack-havana-all-in- one-lab-on-vmware-workstation/ Snapshots and logs are attached. ** Affects: horizon Importance: Undecided Status: New ** Tags: nova ** Attachment added: "Horizon Dashboard snap." https://bugs.launchpad.net/bugs/1424537/+attachment/4325230/+files/Untitled.png ** Description changed: Problem - Error creating Nova Instance using Cirros 0.3.1 image on AIO- HAVANA Ubuntu 12.04 LTS package. Steps to reproduce - -Install VMware workstation. -Create VM with 2-VCPU, 1 GB RAM, 40 GB DIsk, 2 NICs, VT-X enabled. -Install Ubuntu 12.04 LTS. -Install GIT, and Openstack packages keystone, glance, nova, python, etc. -Using SSH open Horizon Dashboard. -Create an instance using Cirros 0.3.1 image. -Observe the error. -Try to give a soft reboot, again observe an error "Not enough permissions" + Refer this for detailed installation procedure that was folowed == + http://www.discoposse.com/index.php/2014/01/26/openstack-havana-all-in- + one-lab-on-vmware-workstation/ + Snapshots and logs are attached. -- 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/1424537 Title: Error creating nova Instance for cirros image 0.3.1 on AIO-HAVANA Ubuntu 12.0.4 package Status in OpenStack Dashboard (Horizon): New Bug description: Problem - Error creating Nova Instance using Cirros 0.3.1 image on AIO-HAVANA Ubuntu 12.04 LTS package. Steps to reproduce - -Install VMware workstation. -Create VM with 2-VCPU, 1 GB RAM, 40 GB DIsk, 2 NICs, VT-X enabled. -Install Ubuntu 12.04 LTS. -Install GIT, and Openstack packages keystone, glance, nova, python, etc. -Using SSH open Horizon Dashboard. -Create an instance using Cirros 0.3.1 image. -Observe the error. -Try to give a soft reboot, again observe an error "Not enough permissions" Refer this for detailed installation procedure that was folowed == http://www.discoposse.com/index.php/2014/01/26/openstack-havana-all- in-one-lab-on-vmware-workstation/ Snapshots and logs are attached. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1424537/+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 1424532] [NEW] setup() takes at least 2 arguments (1 given)
Public bug reported:
Trying to install devstack K on CI slave.
Local conf:
[[local|localrc]]
HOST_IP=10.140.0.3
FLAT_INTERFACE=eth0
FIXED_RANGE=10.150.0.0/16
FIXED_NETWORK_SIZE=255
FLOATING_RANGE=10.140.0.0/16
PUBLIC_NETWORK_GATEWAY=10.140.0.3
NETWORK_GATEWAY=10.150.0.1
MULTI_HOST=0
SYSLOG=False
SCREEN_LOGDIR=/opt/stack/logs/screen-logs
LOGFILE=/opt/stack/logs/stack.sh.log
ADMIN_PASSWORD=*
MYSQL_PASSWORD=*
RABBIT_PASSWORD=*
SERVICE_PASSWORD=*
SERVICE_TOKEN=*
CINDER_REPO=https://review.openstack.org/openstack/cinder
CINDER_BRANCH=refs/changes/01/152401/21
Error during install:
15-02-23 06:30:11.138 | ++ ls /opt/stack/status/stack/n-novnc.failure
2015-02-23 06:30:11.141 | + failures=/opt/stack/status/stack/n-novnc.failure
2015-02-23 06:30:11.141 | + for service in '$failures'
2015-02-23 06:30:11.142 | ++ basename /opt/stack/status/stack/n-novnc.failure
2015-02-23 06:30:11.143 | + service=n-novnc.failure
2015-02-23 06:30:11.143 | + service=n-novnc
2015-02-23 06:30:11.143 | + echo 'Error: Service n-novnc is not running'
2015-02-23 06:30:11.143 | Error: Service n-novnc is not running
2015-02-23 06:30:11.143 | + '[' -n /opt/stack/status/stack/n-novnc.failure ']'
2015-02-23 06:30:11.143 | + die 1494 'More details about the above errors can
be found with screen, with ./rejoin-stack.sh'
2015-02-23 06:30:11.143 | + local exitcode=0
2015-02-23 06:30:11.143 | [Call Trace]
2015-02-23 06:30:11.143 | /opt/devstack/stack.sh:1297:service_check
2015-02-23 06:30:11.143 | /opt/devstack/functions-common:1494:die
2015-02-23 06:30:11.147 | [ERROR] /opt/devstack/functions-common:1494 More
details about the above errors can be found with screen, with ./rejoin-stack.sh
2015-02-23 06:30:12.151 | Error on exit
Novnc screen:
stack@d-p-c-local-01-995:/opt/devstack$ /usr/local/bin/nova-novncproxy
--config-
file /etc/nova/nova.conf --web /opt/stack/noVNC & echo $!
>/opt/stack/status/sta
ck/n-novnc.pid; fg || echo "n-novnc failed to start" | tee
"/opt/stack/status/st
ack/n-novnc.failure"
[1] 10200
/usr/local/bin/nova-novncproxy --config-file /etc/nova/nova.conf --web
/opt/stack/noVNC
Traceback (most recent call last):
File "/usr/local/bin/nova-novncproxy", line 9, in
load_entry_point('nova==2015.1.dev387', 'console_scripts',
'nova-novncproxy')()
File "/opt/stack/nova/nova/cmd/novncproxy.py", line 45, in main
port=CONF.novncproxy_port)
File "/opt/stack/nova/nova/cmd/baseproxy.py", line 57, in proxy
logging.setup("nova")
TypeError: setup() takes at least 2 arguments (1 given)
n-novnc failed to start
stack@d-p-c-local-01-995:/opt/devstack$
** 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/1424532
Title:
setup() takes at least 2 arguments (1 given)
Status in OpenStack Compute (Nova):
New
Bug description:
Trying to install devstack K on CI slave.
Local conf:
[[local|localrc]]
HOST_IP=10.140.0.3
FLAT_INTERFACE=eth0
FIXED_RANGE=10.150.0.0/16
FIXED_NETWORK_SIZE=255
FLOATING_RANGE=10.140.0.0/16
PUBLIC_NETWORK_GATEWAY=10.140.0.3
NETWORK_GATEWAY=10.150.0.1
MULTI_HOST=0
SYSLOG=False
SCREEN_LOGDIR=/opt/stack/logs/screen-logs
LOGFILE=/opt/stack/logs/stack.sh.log
ADMIN_PASSWORD=*
MYSQL_PASSWORD=*
RABBIT_PASSWORD=*
SERVICE_PASSWORD=*
SERVICE_TOKEN=*
CINDER_REPO=https://review.openstack.org/openstack/cinder
CINDER_BRANCH=refs/changes/01/152401/21
Error during install:
15-02-23 06:30:11.138 | ++ ls /opt/stack/status/stack/n-novnc.failure
2015-02-23 06:30:11.141 | + failures=/opt/stack/status/stack/n-novnc.failure
2015-02-23 06:30:11.141 | + for service in '$failures'
2015-02-23 06:30:11.142 | ++ basename /opt/stack/status/stack/n-novnc.failure
2015-02-23 06:30:11.143 | + service=n-novnc.failure
2015-02-23 06:30:11.143 | + service=n-novnc
2015-02-23 06:30:11.143 | + echo 'Error: Service n-novnc is not running'
2015-02-23 06:30:11.143 | Error: Service n-novnc is not running
2015-02-23 06:30:11.143 | + '[' -n /opt/stack/status/stack/n-novnc.failure ']'
2015-02-23 06:30:11.143 | + die 1494 'More details about the above errors can
be found with screen, with ./rejoin-stack.sh'
2015-02-23 06:30:11.143 | + local exitcode=0
2015-02-23 06:30:11.143 | [Call Trace]
2015-02-23 06:30:11.143 | /opt/devstack/stack.sh:1297:service_check
2015-02-23 06:30:11.143 | /opt/devstack/functions-common:1494:die
2015-02-23 06:30:11.147 | [ERROR] /opt/devstack/functions-common:1494 More
details about the above errors can be found with screen, with ./rejoin-stack.sh
2015-02-23 06:30:12.151 | Error on exit
Novnc screen:
stack@d-p-c-local-01-995:/opt/devstack$ /usr/local/bin/nova-novncproxy
--config-
file /etc/nova/nova.conf --web /opt/stack/noVNC & echo $!
>/opt/stack/status/sta
ck/n-novnc.pid; fg || echo "n-novnc failed to start" | tee
"/opt/stack/status/st
ack/n
[Yahoo-eng-team] [Bug 1416953] Re: Region can be created with empty body, need confirm if we need some required parameters for CreateRegion
I think technically this is working as designed, the comment in the code
says that region creation takes no parameters.
I tried:
curl -s -H "X-Auth-Token: openstack" -H "Content-Type: application/json" -d
'{ "region": {}}' http://localhost:5000/v3/regions | python -mjson.tool
and it worked fine,
description is optional, and so is parent_region_id.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1416953
Title:
Region can be created with empty body, need confirm if we need some
required parameters for CreateRegion
Status in OpenStack Identity (Keystone):
Invalid
Bug description:
http_log
Wed Dec 03 16:35:00 CST 2014:DEBUG:>> "POST /v3/regions HTTP/1.1[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:>> "Accept-Encoding: gzip,deflate[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:>> "X-Auth-Token:
13b2e551af074494ac3d5440e406e1ac[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:>> "Content-Type: application/json[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:>> "Content-Length: 25[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:>> "Host: localhost:[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:>> "Connection: Keep-Alive[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:>> "User-Agent: Apache-HttpClient/4.1.1
(java 1.5)[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:>> "[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:>> "{[\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:>> " "region":
{[\n]" Wed Dec 03 16:35:00 CST 2014:DEBUG:>> " }
[\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:>> "}"
Wed Dec 03 16:35:00 CST 2014:DEBUG:<< "HTTP/1.1 201 Created[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:<< "Date: Wed, 03 Dec 2014 08:35:00
GMT[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:<< "Server: Apache/2.4.9 (Debian)[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:<< "Vary: X-Auth-Token[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:<< "Content-Length: 200[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:<< "Keep-Alive: timeout=5, max=100[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:<< "Connection: Keep-Alive[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:<< "Content-Type: application/json[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:<< "[\r][\n]"
Wed Dec 03 16:35:00 CST 2014:DEBUG:<< "{"region": {"url": null,
"parent_region_id": null, "id": "c59fa38d4f9f49e48879f1e5bb137cda", "links":
{"self": "http://localhost:/v3/regions/c59fa38d4f9f49e48879f1e5bb137cda"}
, "description": ""}}"
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1416953/+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 1424500] [NEW] /OS-FEDERATION/projects does not honor project inherited role assignments
Public bug reported: '/OS-FEDERATION/projects' and '/auth/projects' API endpoints do not honor project inherited group role assignments. ** Affects: keystone Importance: Undecided Assignee: Samuel de Medeiros Queiroz (samueldmq) Status: New ** Summary changed: - Federation does not honor project inherited role assignments + /OS-FEDERATION/projects does not honor project inherited role assignments ** Changed in: keystone Assignee: (unassigned) => Samuel de Medeiros Queiroz (samueldmq) ** Description changed: - API endpoints '/OS-FEDERATION/projects' and '/auth/projects' do not + '/OS-FEDERATION/projects' and '/auth/projects' API endpoints do not honor project inherited group role assignments. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1424500 Title: /OS-FEDERATION/projects does not honor project inherited role assignments Status in OpenStack Identity (Keystone): New Bug description: '/OS-FEDERATION/projects' and '/auth/projects' API endpoints do not honor project inherited group role assignments. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1424500/+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 1424269] Re: No [database] section on nova.conf
** Also affects: openstack-manuals 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/1424269 Title: No [database] section on nova.conf Status in OpenStack Compute (Nova): New Status in OpenStack Manuals: New Bug description: While following the http://docs.openstack.org/juno/install- guide/install/yum/content/ch_nova.html documentation, on the step to populate the Database I've faced an error with DB access. After verifying again, I've realized that the following area didn't even exist on nova.conf file (even commented out): "[database] ... connection = mysql://nova:NOVA_DBPASS@controller/nova" This is strange, because on "To install and configure Compute controller components" section / item 2, they say to edit the '[database]' section, but this section doesn't exist on nova.conf file. So, what's wrong? The documentation that should say to 'add' a section called 'database' on nova.conf file, or the 'nova.conf' file that does not contain this section with the example config directives? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1424269/+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 1424496] [NEW] Documentation lacking for mapping of operation policy target
Public bug reported:
There's no documentation that says what the mapping is of target in the
policy.json file to the operation.
For example, the policy.json has a target for "identity:get_region".
This is the rule for the operation of GET /v3/regions/{region_id} . But
there's no way to tell this without reading the code because there's no
documentation for it.
** Affects: keystone
Importance: Undecided
Assignee: Brant Knudson (blk-u)
Status: In Progress
** Changed in: keystone
Assignee: (unassigned) => Brant Knudson (blk-u)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1424496
Title:
Documentation lacking for mapping of operation policy target
Status in OpenStack Identity (Keystone):
In Progress
Bug description:
There's no documentation that says what the mapping is of target in the
policy.json file to the operation.
For example, the policy.json has a target for "identity:get_region".
This is the rule for the operation of GET /v3/regions/{region_id} .
But there's no way to tell this without reading the code because
there's no documentation for it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1424496/+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 1424474] Re: agent-update: wrong help message for AGENT arg "ID or name of agent to update"
https://review.openstack.org/#/c/158152/
** Project changed: neutron => python-neutronclient
** Changed in: python-neutronclient
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/1424474
Title:
agent-update: wrong help message for AGENT arg "ID or name of agent to
update"
Status in Python client library for Neutron:
In Progress
Bug description:
agent-update command takes only ID to specify an agent, but the help
message says "ID or name".
(.venv)ubuntu@dev07:~/python-neutronclient (master)$ neutron help agent-update
usage: neutron agent-update [-h] [--request-format {json,xml}]
[--admin-state-down] [--description DESCRIPTION]
AGENT
Updates the admin status and description for a specified agent.
positional arguments:
AGENT ID or name of agent to update.
optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
The XML or JSON request format.
--admin-state-downSet admin state up of the agent to false.
--description DESCRIPTION
Description for the agent.
To manage notifications about this bug go to:
https://bugs.launchpad.net/python-neutronclient/+bug/1424474/+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 1424474] [NEW] agent-update: wrong help message for AGENT arg "ID or name of agent to update"
Public bug reported:
agent-update command takes only ID to specify an agent, but the help
message says "ID or name".
(.venv)ubuntu@dev07:~/python-neutronclient (master)$ neutron help agent-update
usage: neutron agent-update [-h] [--request-format {json,xml}]
[--admin-state-down] [--description DESCRIPTION]
AGENT
Updates the admin status and description for a specified agent.
positional arguments:
AGENT ID or name of agent to update.
optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
The XML or JSON request format.
--admin-state-downSet admin state up of the agent to false.
--description DESCRIPTION
Description for the agent.
** Affects: python-neutronclient
Importance: Medium
Assignee: Akihiro Motoki (amotoki)
Status: 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/1424474
Title:
agent-update: wrong help message for AGENT arg "ID or name of agent to
update"
Status in Python client library for Neutron:
In Progress
Bug description:
agent-update command takes only ID to specify an agent, but the help
message says "ID or name".
(.venv)ubuntu@dev07:~/python-neutronclient (master)$ neutron help agent-update
usage: neutron agent-update [-h] [--request-format {json,xml}]
[--admin-state-down] [--description DESCRIPTION]
AGENT
Updates the admin status and description for a specified agent.
positional arguments:
AGENT ID or name of agent to update.
optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
The XML or JSON request format.
--admin-state-downSet admin state up of the agent to false.
--description DESCRIPTION
Description for the agent.
To manage notifications about this bug go to:
https://bugs.launchpad.net/python-neutronclient/+bug/1424474/+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 1424462] [NEW] Nova/Neutron v3 authentication
Public bug reported: It is currently only possible for the service user that enables nova to talk to neutron to authenticate via the standard keystone v2 auth mechanisms. As we progress we should support v3 auth and any new formats that come along. Adopting keystoneclient's session work will give us forward compatibility with any authentication mechanisms they allow. ** 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/1424462 Title: Nova/Neutron v3 authentication Status in OpenStack Compute (Nova): New Bug description: It is currently only possible for the service user that enables nova to talk to neutron to authenticate via the standard keystone v2 auth mechanisms. As we progress we should support v3 auth and any new formats that come along. Adopting keystoneclient's session work will give us forward compatibility with any authentication mechanisms they allow. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1424462/+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 1357751] Re: nova.tests.network.test_manager.AllocateTestCase should use mock
** Changed in: nova Status: Triaged => Opinion ** Changed in: nova Status: Opinion => 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/1357751 Title: nova.tests.network.test_manager.AllocateTestCase should use mock Status in OpenStack Compute (Nova): In Progress Bug description: Unit tests should not need to start services. Instead, they should simply mock out the specific calls out of the unit of code that is being tested. nova.tests.network.test_manager.AllocateTestCase calls self.start_service() for the conductor, network, and compute service, and it does so unnecessarily. This results in long test run times and tests that are affected by side effects. Remove the calls to self.start_service() and replace with proper use of mock. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1357751/+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 1424378] [NEW] OVS to ml2 migration doesn't handle ports with no value for binding:host_id
Public bug reported: While working on the upgrade process from Havana to Icehouse we noticed that the ml2 migration doesn't handle ports with no value for binding:host_id. I first came across this issue when I had issues with DHCP ports which I was able to work around by deleting them and recreating them by restarting the dhcp agent. The bigger issue came when we moved on to production where we had instances that were created back in Folsom and undergone the Folsom->Grizzly->Havana->Icehouse upgrades. The network for these instances wasn't restored after the upgrade + there were a lot of nova-compute exceptions when trying to reboot those instances. ** 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/1424378 Title: OVS to ml2 migration doesn't handle ports with no value for binding:host_id Status in OpenStack Neutron (virtual network service): New Bug description: While working on the upgrade process from Havana to Icehouse we noticed that the ml2 migration doesn't handle ports with no value for binding:host_id. I first came across this issue when I had issues with DHCP ports which I was able to work around by deleting them and recreating them by restarting the dhcp agent. The bigger issue came when we moved on to production where we had instances that were created back in Folsom and undergone the Folsom->Grizzly->Havana->Icehouse upgrades. The network for these instances wasn't restored after the upgrade + there were a lot of nova-compute exceptions when trying to reboot those instances. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1424378/+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 1424373] [NEW] Service CRUD is allowed in templated catalog
Public bug reported: Keystone is setup with templated catalog. Steps: 1. setup keystone to use templated catalog driver 2. use keystoneclient to create a service: keystone service-create --type test Result: service created successfully expected result: service should not have been created ** Affects: keystone Importance: Undecided Assignee: Lin Hua Cheng (lin-hua-cheng) Status: New ** Changed in: keystone Assignee: (unassigned) => Lin Hua Cheng (lin-hua-cheng) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1424373 Title: Service CRUD is allowed in templated catalog Status in OpenStack Identity (Keystone): New Bug description: Keystone is setup with templated catalog. Steps: 1. setup keystone to use templated catalog driver 2. use keystoneclient to create a service: keystone service-create --type test Result: service created successfully expected result: service should not have been created To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1424373/+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 1424099] Re: Unable to pass additional parameters to update_router tesmpest test case
Removing Neutron project. ** Also affects: tempest Importance: Undecided Status: New ** No longer affects: neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1424099 Title: Unable to pass additional parameters to update_router tesmpest test case Status in Tempest: New Bug description: While writing tempest test case, I encountered the following: Consider the following scenario: Suppose a third-party plugin has additinal attributes that can be passed during router-creation and router-update. Now, the _update_router method in our json network client does not consider these additional parameter. See the method _update_router in json network client. ( tempest/services/network/json/network_client.py ) To manage notifications about this bug go to: https://bugs.launchpad.net/tempest/+bug/1424099/+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 1417267] Re: neutron-ovs-agent on compute couldn't create interface
So apparently this issue along with some others were caused by unstable work of rabbitmq in certain conditions in certain environment. I don't see an issue on neutron side for now. ** Changed in: neutron Status: New => Invalid ** Changed in: neutron Assignee: Eugene Nikanorov (enikanorov) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1417267 Title: neutron-ovs-agent on compute couldn't create interface Status in OpenStack Neutron (virtual network service): Invalid Bug description: Steps to reproduce: 1. Create env with two powerful compute nodes and start to provision instances. 2. After 130 instance one of the compute nodes starting failing provision because of unable to create interfaces. Here is trace from logs. http://paste.openstack.org/show/164308/ 3. Restarting of agent restore functionality of compute node. 4. After some more VMs provisioned ovs-agent on another node stop working with the same symptoms. 5. Restarting of agent restore functionality of compute node. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1417267/+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 1412325] Re: test_subnet_details failed due to MismatchError
Reviewed: https://review.openstack.org/148815 Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=bb0ea39fd19d2675dae738620f5dcc44498633e4 Submitter: Jenkins Branch:master commit bb0ea39fd19d2675dae738620f5dcc44498633e4 Author: Yair Fried Date: Mon Jan 19 07:26:08 2015 + Unskip and Add timeout method to dns check scenario In test_subnet_details, Tempest checks the effect of alternative dns server which is updated just before the check. However, sometimes the check failed because the update could not make it before the check. This reason is not concrete yet, but this problem happens three times in 60 minutes now. So we need to solve this problem soon for smooth development, and this patch adds timeout method for alternative dns part. Change-Id: I0cb98ff401b526c24388ea440e5629a8ebc925eb Closes-Bug: #1412325 ** Changed in: tempest Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1412325 Title: test_subnet_details failed due to MismatchError Status in OpenStack Neutron (virtual network service): New Status in Tempest: Fix Released Bug description: A new test test_subnet_details failed on the gate for Nova like the following: http://logs.openstack.org/92/144092/3/check/check-tempest-dsvm- neutron-full/6bcefe8/logs/testr_results.html.gz Traceback (most recent call last): File "tempest/test.py", line 112, in wrapper return f(self, *func_args, **func_kwargs) File "tempest/scenario/test_network_basic_ops.py", line 486, in test_subnet_details self._check_dns_server(ssh_client, [alt_dns_server]) File "tempest/scenario/test_network_basic_ops.py", line 437, in _check_dns_server trgt_serv=dns_servers)) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 348, in assertEqual self.assertThat(observed, matcher, message) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 433, in assertThat raise mismatch_error MismatchError: set(['9.8.7.6']) != set(['1.2.3.4']): Looking for servers: ['9.8.7.6']. Retrieved DNS nameservers: ['1.2.3.4'] From host: 172.24.4.98. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1412325/+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 1424344] [NEW] Integration tests - add option to change number of log lines
Public bug reported: The option to change the number of log lines to be shown per instance was added to the settings page. Therefore, the same option should be added to the integration tests's page and change user settings test. ** Affects: horizon Importance: Undecided Assignee: Daniel Korn (dkorn) Status: In Progress ** Tags: integration-tests log-lines ** Description changed: The option to change the number of log lines to be shown per instance was added to the settings page. - Therefore, the same option should be added to the integration tests's page and test. + Therefore, the same option should be added to the integration tests's page and change user settings test. ** Changed in: horizon Assignee: (unassigned) => Daniel Korn (dkorn) -- 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/1424344 Title: Integration tests - add option to change number of log lines Status in OpenStack Dashboard (Horizon): In Progress Bug description: The option to change the number of log lines to be shown per instance was added to the settings page. Therefore, the same option should be added to the integration tests's page and change user settings test. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1424344/+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
