[Yahoo-eng-team] [Bug 1426248] [NEW] lbaas v2 member create should not require subnet_id
Public bug reported: subnet_id on a member is currently required. It should be optional and if not provided, it can be assumed the member can be reached by the load balancer (through the loadbalancer's vip subnet) ** Affects: neutron Importance: Undecided Status: New ** Tags: lbaas -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1426248 Title: lbaas v2 member create should not require subnet_id Status in OpenStack Neutron (virtual network service): New Bug description: subnet_id on a member is currently required. It should be optional and if not provided, it can be assumed the member can be reached by the load balancer (through the loadbalancer's vip subnet) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1426248/+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 1370934] Re: Add details on dhcp_agents_per_network option for DHCP agent HA
** No longer affects: openstack-manuals -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1370934 Title: Add details on dhcp_agents_per_network option for DHCP agent HA Status in OpenStack Neutron (virtual network service): Confirmed Bug description: The current documentation does not specify any information about the dhcp_agents_per_network configuration option in /etc/neutron/neutron.conf. Using this option, it is possible to have the scheduler automatically assign multiple DHCP agents to a tenant network, which provides high availability. If that option is not set, you have to manually assign multiple DHCP agents to each network, which does not scale in terms of management. Would it be possible to document this option here? --- Built: 2014-04-17T10:27:55 00:00 git SHA: 1842612f99f1fe87149db9a3cb0bd43e7892e22b URL: http://docs.openstack.org/trunk/config-reference/content/multi_agent_demo_configuration.html source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/config-reference/networking/section_networking-multi-dhcp-agents.xml xml:id: multi_agent_demo_configuration To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1370934/+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 1426241] [NEW] pci plugin needs to be re-enabled for V2 microversions
Public bug reported: The PCI API support was enabled for v3 but never for V2. However V2.1 is built on v3 and it includes everything in v3. So we are disabling pci support in v3. and then will renable in the v2 microversions as one of the early microversion changes. This bug is to keep track of this work. ** 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/1426241 Title: pci plugin needs to be re-enabled for V2 microversions Status in OpenStack Compute (Nova): New Bug description: The PCI API support was enabled for v3 but never for V2. However V2.1 is built on v3 and it includes everything in v3. So we are disabling pci support in v3. and then will renable in the v2 microversions as one of the early microversion changes. This bug is to keep track of this work. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1426241/+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 1364463] Re: Incorrect key in endpoint dictionary
** Changed in: python-keystoneclient Milestone: None = 1.2.0 ** Changed in: python-keystoneclient Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1364463 Title: Incorrect key in endpoint dictionary Status in OpenStack Identity (Keystone): Fix Released Status in Python client library for Keystone: Fix Released Bug description: Keystone v3 has keyword 'region_id' in endpoint dictionary instead 'region'. It leads to bug in when you try to get endpoint with specific region. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1364463/+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 1425946] [NEW] Correct Uptime field in CSV report
Public bug reported: This patch changed the Uptime column on overview panel to Time since created: https://review.openstack.org/#/c/125332/ But Uptime still appears in the CSV report as Uptime (seconds). ** Affects: horizon Importance: Undecided Assignee: Ambroise CHRISTEA (ambroise-christea) Status: New ** Changed in: horizon Assignee: (unassigned) = Ambroise CHRISTEA (ambroise-christea) -- 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/1425946 Title: Correct Uptime field in CSV report Status in OpenStack Dashboard (Horizon): New Bug description: This patch changed the Uptime column on overview panel to Time since created: https://review.openstack.org/#/c/125332/ But Uptime still appears in the CSV report as Uptime (seconds). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1425946/+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 1425988] [NEW] in some tests in L3SchedulerTestBaseMixin plugin is mocked without any reason
Public bug reported: Plugin shouldn't be mocked since it's defined by the classes that inherits from L3SchedulerTestBaseMixin ** Affects: neutron Importance: Undecided Assignee: Rossella Sblendido (rossella-o) Status: New ** Changed in: neutron Assignee: (unassigned) = Rossella Sblendido (rossella-o) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1425988 Title: in some tests in L3SchedulerTestBaseMixin plugin is mocked without any reason Status in OpenStack Neutron (virtual network service): New Bug description: Plugin shouldn't be mocked since it's defined by the classes that inherits from L3SchedulerTestBaseMixin To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1425988/+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 1425974] [NEW] SSH on instance does'nt return the shell
Public bug reported: I've installed Openstack Juno (fresh install, two weeks ago). The ping from any network to instances works, but I have an issue with SSH (from any host). I tried with and without SSH keys, and that's the same problem. I tried with Cirros and Ubuntu14.04 instances. The ssh command seems working, but the host never returns the shell prompt... : root@networkc:~# ssh -vvv user@192.168.60.X OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 192.168.60.X [192.168.60.X] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: identity file /root/.ssh/id_ed25519 type -1 debug1: identity file /root/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 pat OpenSSH_6.6.1* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent On the instance, 'netstat -laputen' notifies that a new connection is established, and then : Proto Recv-Q Sens-QAdresse locale Adresse distante Etat User tcp 01648 192.168.60.X:22 10.X.X.X 0777/sshd [accepted] At the end, my host displays Connection timed out. I suppose it's a Neutron problem (connection speed or other...). I tried to use the Network Namespace of the concerned instance, but I had the same problem. ** 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/1425974 Title: SSH on instance does'nt return the shell Status in OpenStack Neutron (virtual network service): New Bug description: I've installed Openstack Juno (fresh install, two weeks ago). The ping from any network to instances works, but I have an issue with SSH (from any host). I tried with and without SSH keys, and that's the same problem. I tried with Cirros and Ubuntu14.04 instances. The ssh command seems working, but the host never returns the shell prompt... : root@networkc:~# ssh -vvv user@192.168.60.X OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 192.168.60.X [192.168.60.X] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: identity file /root/.ssh/id_ed25519 type -1 debug1: identity file /root/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 pat OpenSSH_6.6.1* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent On the instance, 'netstat -laputen' notifies that a new connection is established, and then : Proto Recv-Q Sens-QAdresse locale Adresse distante Etat User tcp 01648 192.168.60.X:22 10.X.X.X 0777/sshd [accepted] At the end, my host displays Connection timed out. I suppose it's a Neutron problem (connection speed or other...). I tried to use the Network Namespace of the concerned instance, but I had the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1425974/+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 1394043] Re: KeyError: 'gw_port_host' seen for DVR router removal
Kilo is not released yet. ** Changed in: neutron Status: Fix Released = Fix Committed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1394043 Title: KeyError: 'gw_port_host' seen for DVR router removal Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron juno series: Fix Released Bug description: In some multi-node setups, a qrouter namespace might be hosted on a node where only a dhcp port is hosted (no VMs, no SNAT). When the router is removed from the db, the host with only the qrouter and dhcp namespace will have the qrouter namespace remain. Other hosts with the same qrouter will remove the namespace. The following KeyError is seen on the host with the remaining namespace - 2014-11-18 17:18:43.334 ERROR neutron.agent.l3_agent [-] 'gw_port_host' 2014-11-18 17:18:43.334 TRACE neutron.agent.l3_agent Traceback (most recent call last): 2014-11-18 17:18:43.334 TRACE neutron.agent.l3_agent File /opt/stack/neutron/neutron/common/utils.py, line 341, in call 2014-11-18 17:18:43.334 TRACE neutron.agent.l3_agent return func(*args, **kwargs) 2014-11-18 17:18:43.334 TRACE neutron.agent.l3_agent File /opt/stack/neutron/neutron/agent/l3_agent.py, line 958, in process_router 2014-11-18 17:18:43.334 TRACE neutron.agent.l3_agent self.external_gateway_removed(ri, ri.ex_gw_port, interface_name) 2014-11-18 17:18:43.334 TRACE neutron.agent.l3_agent File /opt/stack/neutron/neutron/agent/l3_agent.py, line 1429, in external_gateway_removed 2014-11-18 17:18:43.334 TRACE neutron.agent.l3_agent ri.router['gw_port_host'] == self.host): 2014-11-18 17:18:43.334 TRACE neutron.agent.l3_agent KeyError: 'gw_port_host' 2014-11-18 17:18:43.334 TRACE neutron.agent.l3_agent Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/eventlet/greenpool.py, line 82, in _spawn_n_impl func(*args, **kwargs) File /opt/stack/neutron/neutron/agent/l3_agent.py, line 1842, in _process_router_update self._process_router_if_compatible(router) File /opt/stack/neutron/neutron/agent/l3_agent.py, line 1817, in _process_router_if_compatible self.process_router(ri) File /opt/stack/neutron/neutron/common/utils.py, line 344, in call self.logger(e) File /opt/stack/neutron/neutron/openstack/common/excutils.py, line 82, in __exit__ six.reraise(self.type_, self.value, self.tb) File /opt/stack/neutron/neutron/common/utils.py, line 341, in call return func(*args, **kwargs) File /opt/stack/neutron/neutron/agent/l3_agent.py, line 958, in process_router self.external_gateway_removed(ri, ri.ex_gw_port, interface_name) File /opt/stack/neutron/neutron/agent/l3_agent.py, line 1429, in external_gateway_removed ri.router['gw_port_host'] == self.host): KeyError: 'gw_port_host' For the issue to be seen, the router in question needs to have the router-gateway-set previously. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1394043/+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 1422388] Re: Fetch passwords from CloudStack virtual router
This bug was fixed in the package cloud-init - 0.7.7~bzr1067-0ubuntu1 --- cloud-init (0.7.7~bzr1067-0ubuntu1) vivid; urgency=medium * New upstream snapshot. * fix broken consumption of gzipped user-data (LP: #1424900) * functional user-data on Azure again (LP: #1423972) * CloudStack: support fetching password from virtual router (LP: #1422388) -- Scott Moser smo...@ubuntu.com Thu, 26 Feb 2015 14:19:16 -0500 ** Changed in: cloud-init (Ubuntu) Status: In Progress = Fix Released -- 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/1422388 Title: Fetch passwords from CloudStack virtual router Status in Init scripts for use on cloud images: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Bug description: CloudStack supports setting passwords in instances, which it would be helpful to support. See [0] for the documentation of this functionality, and [1] for their implementation of it. [0] https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.2/html/Admin_Guide/add-password-management-to-templates.html [1] https://github.com/shankerbalan/cloudstack-scripts/blob/master/cloud-set-guest-password-ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1422388/+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 1425887] Re: Setting 'enable_snat' be false does not work in DVR
Presence of the SNAT namespace is not a bug because the port that
provides connectivity to the external network resides in the SNAT
namespace. If you check, even for a legacy router with enable_snat:
false a qg interface is created on the external network. Similarly for
the DVR such a port is to be created in the SNAT namespace. So presence
of the SNAT namespace is not a defect.
I will mark it as invalid if permitted.
** Changed in: neutron
Status: Confirmed = 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/1425887
Title:
Setting 'enable_snat' be false does not work in DVR
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
I create a DVR with 'enable_snat' false, but the snat namespace also
is create on 'dvr_snat' node:
root@shz-vpn02:/var/log/neutron# neutron router-list
+--+--+--+-+---+
| id | name | external_gateway_info
|
distributed | ha|
+--+--+--+-+---+
| 2a3b6825-0bff-46d9-aea9-535176e78387 | dvr | {network_id:
dbed9af5-528b-4aec-b22f-d0ad8c346e02, enable_snat: false,
external_fixed_ips: [{subnet_id: 63705be9-d3db-4159-9e49-fd7e35b9c893,
ip_address: 172.24.4.99}]} | True| False |
in 'dvr_snat' node, the snat-xxx is created, but the snat rule does
not add, so I think the snat namespace does not be created:
root@shz-vpn01:/var/log/neutron# ip netns list
snat-2a3b6825-0bff-46d9-aea9-535176e78387
qrouter-2a3b6825-0bff-46d9-aea9-535176e78387
root@shz-vpn01:/var/log/neutron# ip netns exec
qrouter-2a3b6825-0bff-46d9-aea9-535176e78387 iptables-save -t nat
# Generated by iptables-save v1.4.21 on Thu Feb 26 10:30:32 2015
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:neutron-l3-agent-OUTPUT - [0:0]
:neutron-l3-agent-POSTROUTING - [0:0]
:neutron-l3-agent-PREROUTING - [0:0]
:neutron-l3-agent-float-snat - [0:0]
:neutron-l3-agent-snat - [0:0]
:neutron-postrouting-bottom - [0:0]
-A PREROUTING -j neutron-l3-agent-PREROUTING
-A OUTPUT -j neutron-l3-agent-OUTPUT
-A POSTROUTING -j neutron-l3-agent-POSTROUTING
-A POSTROUTING -j neutron-postrouting-bottom
-A neutron-l3-agent-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80
-j REDIRECT --to-ports 9697
-A neutron-l3-agent-snat -j neutron-l3-agent-float-snat
-A neutron-postrouting-bottom -m comment --comment Perform source NAT on
outgoing traffic. -j neutron-l3-agent-snat
COMMIT
# Completed on Thu Feb 26 10:30:32 2015
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1425887/+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 1426071] [NEW] horizon integration tests are currently broken in Firefox 36
Public bug reported: The recent update of Firefox 36, available now on Ubuntu Trusty used on the gate, broke selenium and all gate-horizon-dsvm-integration are failing with errors like: WebDriverException: Message: Can't load the profile. Profile Dir: %s If you specified a log_file in the FirefoxBinary constructor, check it for details. See for example: http://logs.openstack.org/60/157760/4/check/gate- horizon-dsvm-integration/fd3c268/console.html A new version of Selenium has not been released yet. See the Selenium bug: https://code.google.com/p/selenium/issues/detail?id=8399). I think this should be solved on infrastructural level (pinning firefox version, for example). After some IRC discussion it seems it's not the solution which is going to be implemented, and the job will be non-voting instead. This means that people can't rely on at all on results from that test (they are not even starting) until the new selenium pip packages are available, and we could suffer from unexpected issues when the tests are reenabled because of some patch which seemed to work locally but not on the gate. That said, who codes decides. ** 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/1426071 Title: horizon integration tests are currently broken in Firefox 36 Status in OpenStack Dashboard (Horizon): New Bug description: The recent update of Firefox 36, available now on Ubuntu Trusty used on the gate, broke selenium and all gate-horizon-dsvm-integration are failing with errors like: WebDriverException: Message: Can't load the profile. Profile Dir: %s If you specified a log_file in the FirefoxBinary constructor, check it for details. See for example: http://logs.openstack.org/60/157760/4/check/gate- horizon-dsvm-integration/fd3c268/console.html A new version of Selenium has not been released yet. See the Selenium bug: https://code.google.com/p/selenium/issues/detail?id=8399). I think this should be solved on infrastructural level (pinning firefox version, for example). After some IRC discussion it seems it's not the solution which is going to be implemented, and the job will be non-voting instead. This means that people can't rely on at all on results from that test (they are not even starting) until the new selenium pip packages are available, and we could suffer from unexpected issues when the tests are reenabled because of some patch which seemed to work locally but not on the gate. That said, who codes decides. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1426071/+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 1426002] [NEW] update mac address feature needs tests
Public bug reported: Need to add api and scenario tempest tests, and possibly neutron functional tests. ** Affects: neutron Importance: Undecided Assignee: Chuck Carlino (ccarlino) Status: In Progress ** Changed in: neutron Assignee: (unassigned) = Chuck Carlino (ccarlino) ** Changed in: neutron Status: New = Incomplete ** Changed in: neutron Status: Incomplete = 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/1426002 Title: update mac address feature needs tests Status in OpenStack Neutron (virtual network service): In Progress Bug description: Need to add api and scenario tempest tests, and possibly neutron functional tests. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1426002/+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 1426082] [NEW] neutron should consume oslo.policy
Public bug reported: The library supersedes policy module from oslo-incubator. Note that consumption is not trivial in this case since the library misses sub-attribute checks. We need to move the code from neutron to oslo.policy, and probably other custom checks. ** Affects: neutron Importance: Undecided Assignee: Ihar Hrachyshka (ihar-hrachyshka) Status: New ** Changed in: neutron Assignee: (unassigned) = Ihar Hrachyshka (ihar-hrachyshka) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1426082 Title: neutron should consume oslo.policy Status in OpenStack Neutron (virtual network service): New Bug description: The library supersedes policy module from oslo-incubator. Note that consumption is not trivial in this case since the library misses sub-attribute checks. We need to move the code from neutron to oslo.policy, and probably other custom checks. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1426082/+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 1426093] [NEW] nova logging error
Public bug reported: I receie weird exception when I try to perform any action with nova ( nova list for example ). I checked, error that should have been logged is Authorization failed for token. Logged from file auth_token.py, line 825 Traceback (most recent call last): File /usr/lib/python2.7/logging/__init__.py, line 859, in emit msg = self.format(record) File /home/xentime/.virtualenvs/xentime/local/lib/python2.7/site-packages/nova/openstack/common/log.py, line 706, in format return logging.StreamHandler.format(self, record) File /usr/lib/python2.7/logging/__init__.py, line 732, in format return fmt.format(record) File /home/xentime/.virtualenvs/xentime/local/lib/python2.7/site-packages/nova/openstack/common/log.py, line 670, in format return logging.Formatter.format(self, record) File /usr/lib/python2.7/logging/__init__.py, line 471, in format record.message = record.getMessage() File /usr/lib/python2.7/logging/__init__.py, line 335, in getMessage msg = msg % self.args TypeError: __str__ returned non-string (type Error) ** 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/1426093 Title: nova logging error Status in OpenStack Compute (Nova): New Bug description: I receie weird exception when I try to perform any action with nova ( nova list for example ). I checked, error that should have been logged is Authorization failed for token. Logged from file auth_token.py, line 825 Traceback (most recent call last): File /usr/lib/python2.7/logging/__init__.py, line 859, in emit msg = self.format(record) File /home/xentime/.virtualenvs/xentime/local/lib/python2.7/site-packages/nova/openstack/common/log.py, line 706, in format return logging.StreamHandler.format(self, record) File /usr/lib/python2.7/logging/__init__.py, line 732, in format return fmt.format(record) File /home/xentime/.virtualenvs/xentime/local/lib/python2.7/site-packages/nova/openstack/common/log.py, line 670, in format return logging.Formatter.format(self, record) File /usr/lib/python2.7/logging/__init__.py, line 471, in format record.message = record.getMessage() File /usr/lib/python2.7/logging/__init__.py, line 335, in getMessage msg = msg % self.args TypeError: __str__ returned non-string (type Error) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1426093/+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 1426076] [NEW] Paging to the next page doesn't work after all the items in the current page are deleted
Public bug reported: I was not able to page to the next page after I delete all the instance of the current page. Steps to reproduce: 1. In the user settings, set the Item per page as 3. 2. On the project - Instance page, launch 6 instances. 3. You should see 3 instances per page in the instance table. 4. On the first page, delete all the instance at once. 5. After all the instances are deleted, click the Next link. 6. You should see an error saying that it cannot page to the next page. ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Changed in: horizon Assignee: (unassigned) = Kahou Lei (kahou82) ** Summary changed: - Paging to the next page doesn't work if all the items in the current page are deleted + Paging to the next page doesn't work after all the items in the current page are deleted -- 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/1426076 Title: Paging to the next page doesn't work after all the items in the current page are deleted Status in OpenStack Dashboard (Horizon): New Bug description: I was not able to page to the next page after I delete all the instance of the current page. Steps to reproduce: 1. In the user settings, set the Item per page as 3. 2. On the project - Instance page, launch 6 instances. 3. You should see 3 instances per page in the instance table. 4. On the first page, delete all the instance at once. 5. After all the instances are deleted, click the Next link. 6. You should see an error saying that it cannot page to the next page. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1426076/+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 1417515] Re: Horizon Input fields swapped when tried to Launch Stack with invalid name
Verified on devstack
/opt/stack/horizon$ git show HEAD
commit 56c6677d61e89b6535dd7dae6fabda2f77063a96
Merge: dfb7c76 243d2a5
Author: Jenkins jenk...@review.openstack.org
Date: Thu Feb 26 08:20:50 2015 +
** Changed in: horizon
Status: Fix Committed = Fix Released
--
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/1417515
Title:
Horizon Input fields swapped when tried to Launch Stack with invalid
name
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
Steps:
1.Open Horizon Dashboard
2.Open Project-Orchestration-Stack
3.Click Launch Stack
4.Template Source - Direct Input
Use template:
[heat_template_version: 2013-05-23
description: Simple template to deploy a single compute instance
parameters:
key_name:
type: string
label: Key Name
description: Name of key-pair to be used for compute instance
image_id:
type: string
label: Image ID
description: Image to be used for compute instance
instance_type:
type: string
label: Instance Type
description: Type of instance (flavor) to be used
resources:
my_instance:
type: OS::Nova::Server
properties:
key_name: { get_param: key_name }
image: { get_param: image_id }
flavor: { get_param: instance_type }]
5.Click Next
6.Fill in the fields:
Stack Name: [111] - invalid value
Password for user admin - your admin pass
Image ID: [25e3e805-1c42-4eb0-abf2-afdc9e96c62e] or any valid id
Instance Type: [m1.small] or any valid type
Key Name:[heat_key] - your Key Pair
7.Click Launch
Stack don't launch(invalid Stack Name), but fields Instance Type and
Key Name swapped
devstack$ git show HEAD
commit e256022a1686eb447da1bbd318c44b58f72f3e0e
Merge: b9a7d3b ff72c50
Author: Jenkins jenk...@review.openstack.org
Date: Sat Jan 31 00:08:29 2015 +
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1417515/+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 1425974] Re: SSH on instance does'nt return the shell
** Also affects: ubuntu Importance: Undecided Status: New ** Description changed: I've installed Openstack Juno (fresh install, two weeks ago). - The ping from any network to instances works, but I have an issue with SSH (from any host). - I tried with and without SSH keys, and that's the same problem. - I tried with Cirros and Ubuntu14.04 instances. + The ping from any network to instances works, but I have an issue with SSH (from any host). + I tried with and without SSH keys, and that's the same problem. + I tried with Cirros and Ubuntu14.04 instances. The ssh command seems working, but the host never returns the shell prompt... : root@networkc:~# ssh -vvv user@192.168.60.X OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 192.168.60.X [192.168.60.X] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: identity file /root/.ssh/id_ed25519 type -1 debug1: identity file /root/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 pat OpenSSH_6.6.1* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent - On the instance, 'netstat -laputen' notifies that a new connection is established, and then : - Proto Recv-Q Sens-QAdresse locale Adresse distante Etat User + Proto Recv-Q Sens-QAdresse locale Adresse distante Etat User tcp 01648 192.168.60.X:22 10.X.X.X 0777/sshd [accepted] At the end, my host displays Connection timed out. - I suppose it's a Neutron problem (connection speed or other...). + I suppose it's a Neutron problem (connection speed or other...). I tried to use the Network Namespace of the concerned instance, but I had the same problem. + + EDIT : With KVM (and default network), the same Qcow2 image has not this + problem. I think, it's not a SSH program issue. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1425974 Title: SSH on instance does'nt return the shell Status in OpenStack Neutron (virtual network service): New Status in Ubuntu: New Bug description: I've installed Openstack Juno (fresh install, two weeks ago). The ping from any network to instances works, but I have an issue with SSH (from any host). I tried with and without SSH keys, and that's the same problem. I tried with Cirros and Ubuntu14.04 instances. The ssh command seems working, but the host never returns the shell prompt... : root@networkc:~# ssh -vvv user@192.168.60.X OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 192.168.60.X [192.168.60.X] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: identity file /root/.ssh/id_ed25519 type -1 debug1: identity file /root/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 pat OpenSSH_6.6.1* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent On the instance, 'netstat -laputen' notifies that a new connection is established, and then : Proto Recv-Q Sens-QAdresse locale Adresse distante Etat User tcp 01648 192.168.60.X:22 10.X.X.X 0777/sshd [accepted] At the end, my host displays Connection timed out. I suppose it's a Neutron problem (connection speed or
[Yahoo-eng-team] [Bug 1404311] Re: [SRU] gce metadata api doesn't properly stream binary data
Hello Wayne, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: cloud-init (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Precise) Status: New = Fix Committed -- 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/1404311 Title: [SRU] gce metadata api doesn't properly stream binary data Status in Init scripts for use on cloud images: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Precise: Fix Committed Status in cloud-init source package in Trusty: Fix Committed Status in cloud-init source package in Utopic: Fix Committed Status in cloud-init source package in Vivid: Fix Released Bug description: [IMPACT] Due to limitations in GCE, binary user-data is mangled when sent as user-data. [FIX] Allow user to declare binary encoding on user-data. [VERIFICATION] 1. Create pristine image from -proposed 2. For step 6 3. Boot GCE instance w/ normal user-data, i.e.: $ cat user-data #cloud-config ssh_import_id: [utlemming] $ gcloud compute instances create image from step 1 \ --metadata-from-file user-data=user-data 4. Confirm that user-data was parsed properly 5. GZIP user-data, and encode using base64: gzip -c user-data.txt | base64 user-data.b64 6. Boot GCE instance w/ user-data.b64 and character encoding meta-data set: $ gcloud compute instances create image from step 1 \ --metadata-from-file user-data=user-data.b64 \ --metadata user-data-encoding=base64 7. Confirm that user-data was consumed; attach /var/log/cloud-init.log to report. [RISK] If a user sets the user-data-encoding to base64, but does not provide base64 data the instance will fail to provision. However, since the user has to explicitly setup the circumstances, it is low risk. [ORIGINAL REPORT] The GCE datasource uses the long hostname. Hostnames longer than 64 characters can break several tools. While implementing the GCE provider for Juju we found that the metadata API breaks when trying to retrieve certain binary formats. In our case the gz of user-data. The API only streams out the first 5 bytes, encounters what it preceives as a EOF/nil character and truncates the rest of the request. We've opened an issue with Google directly, but in the meantime a work around is to allow an explicit encoding to be set for the user-data field of the GCE metadata. This will allow use to base64 encode the binary blob, which the API returns the entire contents of without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1404311/+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 1426121] [NEW] vmw nsx: add/remove interface on dvr is broken
Public bug reported: When the NSX specific extension was dropped in favour of the community one, there was a side effect that unfortunately caused add/remove interface operations to fail when executed passing a subnet id. This should be fixed soon and backported to Juno. Icehouse is not affected. ** Affects: neutron Importance: Undecided Status: New ** Affects: neutron/juno Importance: High Assignee: Salvatore Orlando (salvatore-orlando) Status: New ** Affects: vmware-nsx Importance: High Assignee: Salvatore Orlando (salvatore-orlando) Status: New ** Also affects: neutron Importance: Undecided Status: New ** Summary changed: - add/remove interface on dist router is broken + vmw nsx: add/remove interface on dvr is broken ** Also affects: neutron/juno Importance: Undecided Status: New ** Changed in: neutron/juno Importance: Undecided = High ** Changed in: neutron/juno Assignee: (unassigned) = Salvatore Orlando (salvatore-orlando) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1426121 Title: vmw nsx: add/remove interface on dvr is broken Status in OpenStack Neutron (virtual network service): New Status in neutron juno series: New Status in VMware NSX: New Bug description: When the NSX specific extension was dropped in favour of the community one, there was a side effect that unfortunately caused add/remove interface operations to fail when executed passing a subnet id. This should be fixed soon and backported to Juno. Icehouse is not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1426121/+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 1426128] [NEW] Add ECP related bits to saml generation code
Public bug reported: If an app want to use k2k, then the keystone SP is probably setup to leverage ECP SAML assertions. Currently, the SAML assertion that is generated by the IdP keystone does not contain the ECP related bits, such as: soap11:Envelope xmlns:soap11=http://schemas.xmlsoap.org/soap/envelope/;soap11:Headerecp:Relay State xmlns:ecp=urn:oasis:names:tc:SAML:2.0:profiles:SSO:ecp soap11:actor=http://schemas.xmlsoap.org/soap/actor/next; soap11:mustUnderstand=1ss:mem:f88cd8ad5aeee3456e74900b306b5ed54ec9fb23c614f9fa7 3ece1c97ec004ed/ecp:RelayStatesamlec:GeneratedKey xmlns:samlec=urn:ietf:params:xml:ns:samlec soap11:actor=http://schemas.xmlsoap.org/soap/actor/next;yvYbdh49qSJ7LqjFv+rfB8SR 97hPWMwQkL0KKOgSkhY=/samlec:GeneratedKey/soap11:Header soap11:Body%(response)s/soap11:Body/soap11:Envelope we should add these into the saml generator code so that a client can simply get a SAML assertion from his token, and pass that assertion directly to a remote keystone. ** 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/1426128 Title: Add ECP related bits to saml generation code Status in OpenStack Identity (Keystone): New Bug description: If an app want to use k2k, then the keystone SP is probably setup to leverage ECP SAML assertions. Currently, the SAML assertion that is generated by the IdP keystone does not contain the ECP related bits, such as: soap11:Envelope xmlns:soap11=http://schemas.xmlsoap.org/soap/envelope/;soap11:Headerecp:Relay State xmlns:ecp=urn:oasis:names:tc:SAML:2.0:profiles:SSO:ecp soap11:actor=http://schemas.xmlsoap.org/soap/actor/next; soap11:mustUnderstand=1ss:mem:f88cd8ad5aeee3456e74900b306b5ed54ec9fb23c614f9fa7 3ece1c97ec004ed/ecp:RelayStatesamlec:GeneratedKey xmlns:samlec=urn:ietf:params:xml:ns:samlec soap11:actor=http://schemas.xmlsoap.org/soap/actor/next;yvYbdh49qSJ7LqjFv+rfB8SR 97hPWMwQkL0KKOgSkhY=/samlec:GeneratedKey/soap11:Header soap11:Body%(response)s/soap11:Body/soap11:Envelope we should add these into the saml generator code so that a client can simply get a SAML assertion from his token, and pass that assertion directly to a remote keystone. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1426128/+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 1425859] [NEW] resize-revert broken anti-affinity policy of server group
Public bug reported: Reproduce steps: 1. boot instanceA with anti-affinity policy server group, instanceA start on hostA. 2. resize instanceA, instanceA was migrated to hostB, wait for verify resize. 3. boot instanceB with the same server group, the instanceB was scheduled to hostA because of anti-affinity policy. 4. resize-revert instanceA, the instanceA restart on the source host(hostA). 5. the instanceA and instanceB run on same host (hostA), the anti-affinity policy is broken. When we setup the server group in booting instance logic, the source and destination hosts of resizing/migrating instance should been add into server group hosts in order to impact on the schedule of other instance with same server group. ** Affects: nova Importance: Undecided Assignee: Rui Chen (kiwik-chenrui) Status: New ** Tags: compute ** Changed in: nova Assignee: (unassigned) = Rui Chen (kiwik-chenrui) -- 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/1425859 Title: resize-revert broken anti-affinity policy of server group Status in OpenStack Compute (Nova): New Bug description: Reproduce steps: 1. boot instanceA with anti-affinity policy server group, instanceA start on hostA. 2. resize instanceA, instanceA was migrated to hostB, wait for verify resize. 3. boot instanceB with the same server group, the instanceB was scheduled to hostA because of anti-affinity policy. 4. resize-revert instanceA, the instanceA restart on the source host(hostA). 5. the instanceA and instanceB run on same host (hostA), the anti-affinity policy is broken. When we setup the server group in booting instance logic, the source and destination hosts of resizing/migrating instance should been add into server group hosts in order to impact on the schedule of other instance with same server group. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1425859/+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 1425887] [NEW] Setting 'enable_snat' be false does not work in DVR
Public bug reported:
I create a DVR with 'enable_snat' false, but the snat namespace also is
create on 'dvr_snat' node:
root@shz-vpn02:/var/log/neutron# neutron router-list
+--+--+--+-+---+
| id | name | external_gateway_info
|
distributed | ha|
+--+--+--+-+---+
| 2a3b6825-0bff-46d9-aea9-535176e78387 | dvr | {network_id:
dbed9af5-528b-4aec-b22f-d0ad8c346e02, enable_snat: false,
external_fixed_ips: [{subnet_id: 63705be9-d3db-4159-9e49-fd7e35b9c893,
ip_address: 172.24.4.99}]} | True| False |
in 'dvr_snat' node, the snat-xxx is created, but the snat rule does not
add, so I think the snat namespace does not be created:
root@shz-vpn01:/var/log/neutron# ip netns list
snat-2a3b6825-0bff-46d9-aea9-535176e78387
qrouter-2a3b6825-0bff-46d9-aea9-535176e78387
root@shz-vpn01:/var/log/neutron# ip netns exec
qrouter-2a3b6825-0bff-46d9-aea9-535176e78387 iptables-save -t nat
# Generated by iptables-save v1.4.21 on Thu Feb 26 10:30:32 2015
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:neutron-l3-agent-OUTPUT - [0:0]
:neutron-l3-agent-POSTROUTING - [0:0]
:neutron-l3-agent-PREROUTING - [0:0]
:neutron-l3-agent-float-snat - [0:0]
:neutron-l3-agent-snat - [0:0]
:neutron-postrouting-bottom - [0:0]
-A PREROUTING -j neutron-l3-agent-PREROUTING
-A OUTPUT -j neutron-l3-agent-OUTPUT
-A POSTROUTING -j neutron-l3-agent-POSTROUTING
-A POSTROUTING -j neutron-postrouting-bottom
-A neutron-l3-agent-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80
-j REDIRECT --to-ports 9697
-A neutron-l3-agent-snat -j neutron-l3-agent-float-snat
-A neutron-postrouting-bottom -m comment --comment Perform source NAT on
outgoing traffic. -j neutron-l3-agent-snat
COMMIT
# Completed on Thu Feb 26 10:30:32 2015
** Affects: neutron
Importance: Undecided
Assignee: shihanzhang (shihanzhang)
Status: New
** Changed in: neutron
Assignee: (unassigned) = shihanzhang (shihanzhang)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1425887
Title:
Setting 'enable_snat' be false does not work in DVR
Status in OpenStack Neutron (virtual network service):
New
Bug description:
I create a DVR with 'enable_snat' false, but the snat namespace also
is create on 'dvr_snat' node:
root@shz-vpn02:/var/log/neutron# neutron router-list
+--+--+--+-+---+
| id | name | external_gateway_info
|
distributed | ha|
+--+--+--+-+---+
| 2a3b6825-0bff-46d9-aea9-535176e78387 | dvr | {network_id:
dbed9af5-528b-4aec-b22f-d0ad8c346e02, enable_snat: false,
external_fixed_ips: [{subnet_id: 63705be9-d3db-4159-9e49-fd7e35b9c893,
ip_address: 172.24.4.99}]} | True| False |
in 'dvr_snat' node, the snat-xxx is created, but the snat rule does
not add, so I think the snat namespace does not be created:
root@shz-vpn01:/var/log/neutron# ip netns list
snat-2a3b6825-0bff-46d9-aea9-535176e78387
qrouter-2a3b6825-0bff-46d9-aea9-535176e78387
root@shz-vpn01:/var/log/neutron# ip netns exec
qrouter-2a3b6825-0bff-46d9-aea9-535176e78387 iptables-save -t nat
# Generated by iptables-save v1.4.21 on Thu Feb 26 10:30:32 2015
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:neutron-l3-agent-OUTPUT - [0:0]
:neutron-l3-agent-POSTROUTING - [0:0]
:neutron-l3-agent-PREROUTING - [0:0]
:neutron-l3-agent-float-snat - [0:0]
:neutron-l3-agent-snat - [0:0]
:neutron-postrouting-bottom - [0:0]
-A PREROUTING -j neutron-l3-agent-PREROUTING
-A OUTPUT -j
[Yahoo-eng-team] [Bug 1425882] [NEW] Use Neutron in Horizon integration tests job
Public bug reported: Currently, gate-horizon-dsvm-integration job uses Nova Network instead of Neutron, causing network-related patches to fail. Since the integration tests are also planned to test Neutron's networking features within Horizon it only makes sense that Neutron will be deployed. ** Affects: horizon Importance: Undecided Status: New ** Tags: integration-tests ** Description changed: - Currently, gate-horizon-dsvm-integration job uses Nova Network instead of Neutron. - Since the integration tests are also planned to test Neutron's networking features within Horizon it only makes sense that Neutron will be deployed. + Currently, gate-horizon-dsvm-integration job uses Nova Network instead of Neutron. + Since the integration tests are also planned to test Neutron's networking features within Horizon it only makes sense that Neutron will be deployed. ** Description changed: - Currently, gate-horizon-dsvm-integration job uses Nova Network instead of Neutron. + Currently, gate-horizon-dsvm-integration job uses Nova Network instead of Neutron, causing network-related patches to fail. Since the integration tests are also planned to test Neutron's networking features within Horizon it only makes sense that Neutron will be deployed. -- 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/1425882 Title: Use Neutron in Horizon integration tests job Status in OpenStack Dashboard (Horizon): New Bug description: Currently, gate-horizon-dsvm-integration job uses Nova Network instead of Neutron, causing network-related patches to fail. Since the integration tests are also planned to test Neutron's networking features within Horizon it only makes sense that Neutron will be deployed. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1425882/+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 1425890] [NEW] Neutron functional tests use an oslo.db private method removed in 1.5.0
Public bug reported: neutron/tests/functional/db/test_migrations.py uses _cleanup private method defined in oslo_db/sqlalchemy/test_migrations.py which has been removed in oslo.db 1.5.0 https://jenkins02.openstack.org/job/check-neutron-dsvm- functional/3593/console ** Affects: neutron Importance: Undecided Assignee: Cedric Brandily (cbrandily) Status: In Progress ** Changed in: neutron Assignee: (unassigned) = Cedric Brandily (cbrandily) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1425890 Title: Neutron functional tests use an oslo.db private method removed in 1.5.0 Status in OpenStack Neutron (virtual network service): In Progress Bug description: neutron/tests/functional/db/test_migrations.py uses _cleanup private method defined in oslo_db/sqlalchemy/test_migrations.py which has been removed in oslo.db 1.5.0 https://jenkins02.openstack.org/job/check-neutron-dsvm- functional/3593/console To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1425890/+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 1425892] [NEW] TypeError with django-1.8
Public bug reported: [root@turing openstack-dashboard]# ./manage.py runserver Traceback (most recent call last): File ./manage.py, line 23, in module execute_from_command_line(sys.argv) File /usr/lib/python2.7/site-packages/django/core/management/__init__.py, line 338, in execute_from_command_line utility.execute() File /usr/lib/python2.7/site-packages/django/core/management/__init__.py, line 303, in execute settings.INSTALLED_APPS File /usr/lib/python2.7/site-packages/django/conf/__init__.py, line 48, in __getattr__ self._setup(name) File /usr/lib/python2.7/site-packages/django/conf/__init__.py, line 44, in _setup self._wrapped = Settings(settings_module) File /usr/lib/python2.7/site-packages/django/conf/__init__.py, line 92, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File /usr/lib64/python2.7/importlib/__init__.py, line 37, in import_module __import__(name) File /usr/share/openstack-dashboard/openstack_dashboard/settings.py, line 255, in module from local.local_settings import * # noqa File /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py, line 99, in module from horizon.utils import secret_key File /usr/lib/python2.7/site-packages/horizon/__init__.py, line 27, in module from horizon.base import Dashboard # noqa File /usr/lib/python2.7/site-packages/horizon/base.py, line 45, in module from horizon import loaders File /usr/lib/python2.7/site-packages/horizon/loaders.py, line 57, in module _loader = TemplateLoader() File /usr/lib/python2.7/site-packages/django/template/loader.py, line 155, in __init__ super(BaseLoader, self).__init__(*args, **kwargs) TypeError: __init__() takes exactly 2 arguments (1 given) ** 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/1425892 Title: TypeError with django-1.8 Status in OpenStack Dashboard (Horizon): New Bug description: [root@turing openstack-dashboard]# ./manage.py runserver Traceback (most recent call last): File ./manage.py, line 23, in module execute_from_command_line(sys.argv) File /usr/lib/python2.7/site-packages/django/core/management/__init__.py, line 338, in execute_from_command_line utility.execute() File /usr/lib/python2.7/site-packages/django/core/management/__init__.py, line 303, in execute settings.INSTALLED_APPS File /usr/lib/python2.7/site-packages/django/conf/__init__.py, line 48, in __getattr__ self._setup(name) File /usr/lib/python2.7/site-packages/django/conf/__init__.py, line 44, in _setup self._wrapped = Settings(settings_module) File /usr/lib/python2.7/site-packages/django/conf/__init__.py, line 92, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File /usr/lib64/python2.7/importlib/__init__.py, line 37, in import_module __import__(name) File /usr/share/openstack-dashboard/openstack_dashboard/settings.py, line 255, in module from local.local_settings import * # noqa File /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py, line 99, in module from horizon.utils import secret_key File /usr/lib/python2.7/site-packages/horizon/__init__.py, line 27, in module from horizon.base import Dashboard # noqa File /usr/lib/python2.7/site-packages/horizon/base.py, line 45, in module from horizon import loaders File /usr/lib/python2.7/site-packages/horizon/loaders.py, line 57, in module _loader = TemplateLoader() File /usr/lib/python2.7/site-packages/django/template/loader.py, line 155, in __init__ super(BaseLoader, self).__init__(*args, **kwargs) TypeError: __init__() takes exactly 2 arguments (1 given) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1425892/+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 1425895] [NEW] Tests on DomainSpecificLDAPandSQLIdentity cannot create and use new domains
Public bug reported: Tests in this class (or in subclasses) can create domains, but cannot use them for any identity operation, such as list_users. When domain-specific backends functionality is used, the created domains (that do not have an explicit configuration) are mapped in the default driver. It works pretty well when the default driver is SQL, but not for LDAP, which is read-only. LDAP is configured as default driver for that test class. An exception is thrown when trying to use identity operations on that domain, since the manager cannot find a driver to use: Found multiple domains being mapped to a driver that does not support that (e.g. LDAP) - Domain ID: fcda5a65a54e43618b1c5acfaefa8d00, Default Driver: True ** 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/1425895 Title: Tests on DomainSpecificLDAPandSQLIdentity cannot create and use new domains Status in OpenStack Identity (Keystone): New Bug description: Tests in this class (or in subclasses) can create domains, but cannot use them for any identity operation, such as list_users. When domain-specific backends functionality is used, the created domains (that do not have an explicit configuration) are mapped in the default driver. It works pretty well when the default driver is SQL, but not for LDAP, which is read-only. LDAP is configured as default driver for that test class. An exception is thrown when trying to use identity operations on that domain, since the manager cannot find a driver to use: Found multiple domains being mapped to a driver that does not support that (e.g. LDAP) - Domain ID: fcda5a65a54e43618b1c5acfaefa8d00, Default Driver: True To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1425895/+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 1425845] [NEW] Image list multiselection buttons allowed
Public bug reported: In Horizon Juno Name: openstack-dashboard Arch: noarch Version : 2014.2.1 Release : 2.el7.centos DESCRIPTION: In Project dashboard - Image list there is a problem with the CSS behavior in the buttons grouped (Project, Shared with me, Public). The problem is that you can active more than one button at same time. HOW TO REPRODUCE 1 - The start status is all with background color white. 2 - Click in one button, for example, Public. Now, public is active (it has active css class) 3 - Click in other button, for example, Shared with me. Now, Shared with me is active (it has active css class) as well. (see attachment horizon_images_multiselection_status.png) The miss-behavior is: only one button (that belongs to that group) can be active at the same time. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: horizon_images_multiselection_status.png https://bugs.launchpad.net/bugs/1425845/+attachment/4328085/+files/horizon_images_multiselection_status.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/1425845 Title: Image list multiselection buttons allowed Status in OpenStack Dashboard (Horizon): New Bug description: In Horizon Juno Name: openstack-dashboard Arch: noarch Version : 2014.2.1 Release : 2.el7.centos DESCRIPTION: In Project dashboard - Image list there is a problem with the CSS behavior in the buttons grouped (Project, Shared with me, Public). The problem is that you can active more than one button at same time. HOW TO REPRODUCE 1 - The start status is all with background color white. 2 - Click in one button, for example, Public. Now, public is active (it has active css class) 3 - Click in other button, for example, Shared with me. Now, Shared with me is active (it has active css class) as well. (see attachment horizon_images_multiselection_status.png) The miss-behavior is: only one button (that belongs to that group) can be active at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1425845/+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 1425844] [NEW] metadata start with db connections
Public bug reported: metadata agent should not try to connect db since it does not need db connections at all $ neutron-metadata-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/metadata_agent.ini 2015-02-26 17:06:09.768 3045 WARNING oslo_db.sqlalchemy.session [-] SQL connection failed. 10 attempts left. 10.16.91.1:5672 ** Affects: neutron Importance: Undecided Assignee: yong sheng gong (gongysh) 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/1425844 Title: metadata start with db connections Status in OpenStack Neutron (virtual network service): In Progress Bug description: metadata agent should not try to connect db since it does not need db connections at all $ neutron-metadata-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/metadata_agent.ini 2015-02-26 17:06:09.768 3045 WARNING oslo_db.sqlalchemy.session [-] SQL connection failed. 10 attempts left. 10.16.91.1:5672 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1425844/+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 1425849] [NEW] remove the redundant policy check for SecurityGroupsOutputController
Public bug reported: The normal authorize and soft authorize has the same rule. All actions of SecurityGroupsOutputController need soft authorize. If soft authorize fails, no chance to do normal authorize, also if soft authorize passes, the normal authorize is redundant. ** Affects: nova Importance: Undecided Assignee: lvmxh (shaohef) Status: In Progress ** Changed in: nova Assignee: (unassigned) = lvmxh (shaohef) -- 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/1425849 Title: remove the redundant policy check for SecurityGroupsOutputController Status in OpenStack Compute (Nova): In Progress Bug description: The normal authorize and soft authorize has the same rule. All actions of SecurityGroupsOutputController need soft authorize. If soft authorize fails, no chance to do normal authorize, also if soft authorize passes, the normal authorize is redundant. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1425849/+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 1426151] [NEW] PING health-monitor in LBaaS Haproxy sends a TCP request to members
You have been subscribed to a public bug:
There are different health-monitors in LBaaS:
1) PING 2) TCP 3) HTTP and 4) HTTPS
I was trying PING health-monitor with Haproxy, but it seem to be sending
TCP requests to the members instead of PING requests.
varunlodaya@ubuntu:~$ neutron lb-healthmonitor-show
fb5d0e4b-5763-4f38-bf2c-09f9f7ab2e49
++-+
| Field | Value
|
++-+
| admin_state_up | True
|
| delay | 30
|
| id | fb5d0e4b-5763-4f38-bf2c-09f9f7ab2e49
|
| max_retries| 2
|
| pools | {status: ACTIVE, status_description: null, pool_id:
93d03b4e-05a5-4691-b36f-1416b96c3751} |
| tenant_id | 6d560cf5767d4f17a61ebc11c14bc1cc
|
| timeout| 5
|
| type | PING
|
++-+
The Haproxy config it generates for backend is:
*
backend 93d03b4e-05a5-4691-b36f-1416b96c3751
mode http
balance roundrobin
option forwardfor
timeout check 5s
server 07285f2e-9e9f-41ad-a343-2f1d7296f2d9 10.0.0.4:80 weight 1 check
inter 30s fall 2
On the member, I opened tcpdump to check whats being received:
sudo tcpdump -i eth0 -v icmp
sudo: unable to resolve host ubuntu-vm
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535
bytes
^C
0 packets captured
0 packets received by filter
0 packets dropped by kernel
ubuntu@ubuntu-vm:~$ sudo tcpdump -i eth0 -n src host 10.0.0.5 -vv
sudo: unable to resolve host ubuntu-vm
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535
bytes
23:03:53.434592 IP (tos 0x0, ttl 64, id 4614, offset 0, flags [DF], proto TCP
(6), length 60)
10.0.0.5.55697 10.0.0.4.80: Flags [S], cksum 0xc228 (correct), seq
3491668946, win 29200, options [mss 1460,sackOK,TS val 1552852 ecr 0,nop,wscale
7], length 0
23:03:58.441968 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.0.0.4
tell 10.0.0.5, length 28
23:04:23.439097 IP (tos 0x0, ttl 64, id 30112, offset 0, flags [DF], proto TCP
(6), length 60)
10.0.0.5.55704 10.0.0.4.80: Flags [S], cksum 0x3862 (correct), seq
635615873, win 29200, options [mss 1460,sackOK,TS val 1560353 ecr 0,nop,wscale
7], length 0
^C
3 packets captured
3 packets received by filter
0 packets dropped by kernel
** Affects: neutron
Importance: Undecided
Status: New
** Tags: lbaas
--
PING health-monitor in LBaaS Haproxy sends a TCP request to members
https://bugs.launchpad.net/bugs/1426151
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
--
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 1424576] Re: RuntimeError: Unable to find group for option fatal_deprecations, maybe it's defined twice in the same group?
This problem was introduced with this change https://review.openstack.org/#/c/123868/ ** Also affects: oslo-incubator 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/1424576 Title: RuntimeError: Unable to find group for option fatal_deprecations, maybe it's defined twice in the same group? Status in OpenStack Compute (Nova): New Status in The Oslo library incubator: New Bug description: I tried to generate a nova.conf configuration file with the current state of the Nova repository (master) and got the following exception message: % tox -e genconfig genconfig create: /home/berendt/Repositories/nova/.tox/genconfig genconfig installdeps: -r/home/berendt/Repositories/nova/requirements.txt, -r/home/berendt/Repositories/nova/test-requirements.txt genconfig develop-inst: /home/berendt/Repositories/nova genconfig runtests: PYTHONHASHSEED='0' genconfig runtests: commands[0] | bash tools/config/generate_sample.sh -b . -p nova -o etc/nova Traceback (most recent call last): File /usr/lib64/python2.7/runpy.py, line 162, in _run_module_as_main __main__, fname, loader, pkg_name) File /usr/lib64/python2.7/runpy.py, line 72, in _run_code exec code in run_globals File /home/berendt/Repositories/nova/nova/openstack/common/config/generator.py, line 303, in module main() File /home/berendt/Repositories/nova/nova/openstack/common/config/generator.py, line 300, in main generate(sys.argv[1:]) File /home/berendt/Repositories/nova/nova/openstack/common/config/generator.py, line 128, in generate for group, opts in _list_opts(mod_obj): File /home/berendt/Repositories/nova/nova/openstack/common/config/generator.py, line 192, in _list_opts ret.setdefault(_guess_groups(opt, obj), []).append(opt) File /home/berendt/Repositories/nova/nova/openstack/common/config/generator.py, line 172, in _guess_groups % opt.name RuntimeError: Unable to find group for option fatal_deprecations, maybe it's defined twice in the same group? To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1424576/+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
