date:20161201

[Yahoo-eng-team] [Bug 1505776] Re: Validate src_ip_adress, dest_ip_address and ip_version

2016-12-01 Thread Reedip

** 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/1505776

Title:
  Validate src_ip_adress, dest_ip_address and ip_version

Status in neutron:
  Invalid
Status in openstack-manuals:
  Fix Released

Bug description:
  https://review.openstack.org/215768
  commit 29c51879683087e8ea486aaa9866bbce1f47a15c
  Author: Sean M. Collins 
  Date:   Mon Aug 10 15:24:52 2015 -0400

  Validate src_ip_adress, dest_ip_address and ip_version
  
  The FwaaS API should not allow the creation of firewall rules where
  the ip_version is set to 4, but the source or destination IPs are IPv6
  addresses
  
  APIImpact
  DocImpact
  
  Closes-Bug: #1487599
  
  Change-Id: Iad680996a47adcf27f9dc7e0bc0fea924fff4f9f

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1505776/+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 1621076] Re: Can't detach interface from VM (if VM has two interface with same mac addresses)

2016-12-01 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/372243
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=a5c38cc861f052b89bc1ce182f68784c493c723e
Submitter: Jenkins
Branch:master

commit a5c38cc861f052b89bc1ce182f68784c493c723e
Author: Leehom Li (feli5) 
Date:   Mon Sep 19 13:43:46 2016 +0800

Support detach interface with same MAC from instance

When detach_interface nova uses  XML generated
from scatch, which is missing the PCI device information that
libvirt would use to uniquely identify devices.

In case instance has mutiple interfaces with same MAC address.
Libvirt will failed with below error message:
libvirtError: operation failed: multiple devices matching
mac address fa:16:3e:60:46:1f found

This patch fixes this problem by provide a new function
get_interface_by_cfg, this function uses cfg generated by
nova.virt.libvirt.vif.get_config  as parameter,
return a LibvirtConfigGuestInterface object.

Also added function format_dom for
LibvirtConfigGuestDeviceAddressPCI, which will be used to
generate pci address for LibvirtConfigGuestInterface.

Change-Id: I8acae90c9d2111ed35f58f374f321d64f01ba563
Closes-Bug: #1621076


** Changed in: nova
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1621076

Title:
  Can't detach interface from VM (if VM has two interface with same mac
  addresses)

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  How to reproduce:

  1. Run any VM.
  2. Create two networks.
  3. Create two ports for each network with same mac addresses
  4. Attach those ports to VM
  5. Try to detach any interface.

  Expected result:
  The interface should be detached from VM.

  Actual result:
  We don't get any errors (via API) on previous steps but an interface still 
attached to VM

  Environment:
  * fuel_release: 9.0
  * fuel_openstack_version: mitaka-9.0
  * libvirt0: 1.2.9.3-9~u14.04+mos10
  * hypervisor: Libvirt + KVM


  Example:

  (OpenStack-venv)agent@laptop ~/projects $ nova interface-list 
c5ae5a9a-54a2-47b8-800e-619b8bc286f5
  
++--+--++---+
  | Port State | Port ID  | Net ID  
 | IP addresses   | MAC Addr  |
  
++--+--++---+
  | ACTIVE | 0d9377b4-4f8f-467a-bae7-54d0d70e5262 | 
3f5adcaa-d3e5-4caf-be8f-474751de5589 | 192.168.0.1| fa:16:3e:60:46:1f |
  | ACTIVE | 13cac036-7b6d-4188-879f-650c8d9e1f63 | 
28939866-7379-4279-800c-b64c2776e1e0 | 192.168.111.82 | fa:16:3e:24:0d:a4 |
  | ACTIVE | 310b9883-806d-4038-a095-1625abecbcb1 | 
311c5a7e-5cb0-47e2-8aa0-20d74c4ee8c2 | 192.168.0.1| fa:16:3e:60:46:1f |
  
++--+--++---+
  (OpenStack-venv)agent@laptop ~/projects $ nova interface-detach 
c5ae5a9a-54a2-47b8-800e-619b8bc286f5 0d9377b4-4f8f-467a-bae7-54d0d70e5262
  (OpenStack-venv)agent@laptop ~/projects $ nova interface-list 
c5ae5a9a-54a2-47b8-800e-619b8bc286f5
  
++--+--++---+
  | Port State | Port ID  | Net ID  
 | IP addresses   | MAC Addr  |
  
++--+--++---+
  | ACTIVE | 0d9377b4-4f8f-467a-bae7-54d0d70e5262 | 
3f5adcaa-d3e5-4caf-be8f-474751de5589 | 192.168.0.1| fa:16:3e:60:46:1f |
  | ACTIVE | 13cac036-7b6d-4188-879f-650c8d9e1f63 | 
28939866-7379-4279-800c-b64c2776e1e0 | 192.168.111.82 | fa:16:3e:24:0d:a4 |
  | ACTIVE | 310b9883-806d-4038-a095-1625abecbcb1 | 
311c5a7e-5cb0-47e2-8aa0-20d74c4ee8c2 | 192.168.0.1| fa:16:3e:60:46:1f |
  
++--+--++---+

  logs from compute:

  libvirt:
  <11>Sep  7 12:18:00 node-9 libvirtd: 11320: error : virDomainNetFindIdx:11005 
: operation failed: multiple devices matching mac address fa:16:3e:60:46:1f 
found

  nova compute:
  <183>Sep  6 17:58:04 node-7 nova-compute: 2016-09-06 17:58:04.348 7652 DEBUG 
nova.objects.instance [req-db381757-3fbf-4bb8-a4df-160e1422a005 
2b96e098d62147d8b9a15f635e0dd51a 4b867602d6974059afb2489a71dfaabb - - -] 
Lazy-loading 'flavor' on Instance uuid d95ab3d6-6b8f-42f0-8bf8-a553e99ee41a 
obj_load_attr /usr/lib/python2.7/dist-packages/nova/objects/instance.py:895

[Yahoo-eng-team] [Bug 1645554] Re: [api-ref] incorrect title for role-assignment

2016-12-01 Thread Steve Martinelli

** Summary changed:

- un appropriate title for role-assignment identity v3 api-ref
+ [api-ref] incorrect title for role-assignment

** Changed in: openstack-api-site
   Status: New => Invalid

** Also affects: keystone
   Importance: Undecided
   Status: New

** Tags added: api-ref

** Changed in: keystone
   Status: New => In Progress

** Changed in: keystone
   Importance: Undecided => Low

** Changed in: keystone
 Assignee: (unassigned) => Rodrigo Duarte (rodrigodsousa)

** Changed in: keystone
Milestone: None => ocata-2

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1645554

Title:
  [api-ref] incorrect title for role-assignment

Status in OpenStack Identity (keystone):
  In Progress
Status in openstack-api-site:
  Invalid

Bug description:
  Title for role-assignment identity v3 api-ref is not appropriate, as
  this API is to list all role assignment and depends on query
  (effective), it will return filter role assignments.

  So title should be "List role assignments" instead of "List effective
  role assignments"

  http://developer.openstack.org/api-ref/identity/v3/?expanded=list-
  effective-role-assignments-detail

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1645554/+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 1632054] Re: Heat engine doesn't detect lbaas listener failures

2016-12-01 Thread Zhixin Li

Doesn't it need to add an affected project for neutron-lbaas? We need to
expose provisioning_status for all top level objects of lbaas.

** Also affects: neutron
Importance: Undecided
Status: New

--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1632054

Title:
Heat engine doesn't detect lbaas listener failures

Status in heat:
Triaged
Status in neutron:
New
Status in octavia:
Triaged

Bug description:
Please refer to the mail-list for comments from other developers,
https://openstack.nimeyo.com/97427/openstack-neutron-octavia-doesnt-
detect-listener-failures

I am trying to use heat to launch lb resources with Octavia as backend. The
template I used is from

https://github.com/openstack/heat-templates/blob/master/hot/lbaasv2/lb_group.yaml
.

Following are a few observations:

1. Even though Listener was created with ERROR status, heat will still go
ahead and mark it Creation Complete. As in the heat code, it only check
whether root Loadbalancer status is change from PENDING_UPDATE to ACTIVE.
And Loadbalancer status will be changed to ACTIVE anyway no matter
Listener's status.

2. As heat engine wouldn't know the Listener's creation failure, it will
continue to create Pool\Member\Heatthmonitor on top of an Listener which
actually doesn't exist. It causes a few undefined behaviors. As a result,
those LBaaS resources in ERROR state are unable to be cleaned up
with either normal neutron or heat api.

3. The bug is introduce from here,

https://github.com/openstack/heat/blob/master/heat/engine/resources/openstack/neutron/lbaas/listener.py#L188.
It only checks the provisioning status of the root loadbalancer.
However the listener itself has its own provisioning status which may
go into ERROR.

4. The same scenario applies for not only listener but also pool,
member, healthmonitor, etc., basically every resources except
loadbalancer from lbaas.

To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1632054/+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 1646672] Re: It's recommended to use keystoneauth1

2016-12-01 Thread Xu Ao

** Changed in: glance
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1646672

Title:
  It's recommended to use keystoneauth1

Status in Glance:
  Invalid

Bug description:
  While use cinder as glance-store, there being a warning in the log:

  2016-12-02 10:40:30.935 DEBUG
  glance.api.middleware.version_negotiation [-] new path
  /v2/images/59183025-2163-4022-93b6-928e9385359c from (pid=30487)
  process_request
  /opt/stack/glance/glance/api/middleware/version_negotiation.py:71

  /usr/local/lib/python2.7/dist-packages/keystoneauth1/adapter.py:135: 
UserWarning: Using keystoneclient sessions has been deprecated. Please update 
your software to use keystoneauth1.
warnings.warn('Using keystoneclient sessions has been deprecated. '

  If the auth_plugin should be convert to keystoneauth1 here?

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1646672/+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 1646672] [NEW] It's recommended to use keystoneauth1

2016-12-01 Thread Xu Ao

Public bug reported:

While use cinder as glance-store, there being a warning in the log:

2016-12-02 10:40:30.935 DEBUG glance.api.middleware.version_negotiation
[-] new path /v2/images/59183025-2163-4022-93b6-928e9385359c from
(pid=30487) process_request
/opt/stack/glance/glance/api/middleware/version_negotiation.py:71

/usr/local/lib/python2.7/dist-packages/keystoneauth1/adapter.py:135: 
UserWarning: Using keystoneclient sessions has been deprecated. Please update 
your software to use keystoneauth1.
  warnings.warn('Using keystoneclient sessions has been deprecated. '

If the auth_plugin should be convert to keystoneauth1 here?

** Affects: glance
 Importance: Undecided
 Assignee: Xu Ao (xuao)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Xu Ao (xuao)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1646672

Title:
  It's recommended to use keystoneauth1

Status in Glance:
  New

Bug description:
  While use cinder as glance-store, there being a warning in the log:

  2016-12-02 10:40:30.935 DEBUG
  glance.api.middleware.version_negotiation [-] new path
  /v2/images/59183025-2163-4022-93b6-928e9385359c from (pid=30487)
  process_request
  /opt/stack/glance/glance/api/middleware/version_negotiation.py:71

  /usr/local/lib/python2.7/dist-packages/keystoneauth1/adapter.py:135: 
UserWarning: Using keystoneclient sessions has been deprecated. Please update 
your software to use keystoneauth1.
warnings.warn('Using keystoneclient sessions has been deprecated. '

  If the auth_plugin should be convert to keystoneauth1 here?

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1646672/+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 1642679] Re: The OpenStack network_config.json implementation fails on Hyper-V compute nodes

2016-12-01 Thread Scott Moser

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu)
   Status: New => Fix Released

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Confirmed => In Progress

** Changed in: cloud-init (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

** Changed in: cloud-init (Ubuntu Yakkety)
   Importance: Undecided => Medium

-- 
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/1642679

Title:
  The OpenStack network_config.json implementation fails on Hyper-V
  compute nodes

Status in cloud-init:
  Confirmed
Status in OpenStack Compute (nova):
  In Progress
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  We have discovered an issue when booting Xenial instances on OpenStack
  environments (Liberty or newer) and Hyper-V compute nodes using config
  drive as metadata source.

  When applying the network_config.json, cloud-init fails with this error:
  http://paste.openstack.org/show/RvHZJqn48JBb0TO9QznL/

  The fix would be to add 'hyperv' as a link type here:
  /usr/lib/python3/dist-packages/cloudinit/sources/helpers/openstack.py, line 
587

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1642679/+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 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line

2016-12-01 Thread Scott Moser

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

-- 
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/1639930

Title:
  initramfs network configuration ignored if only ip6= on kernel command
  line

Status in cloud-init:
  Confirmed
Status in MAAS:
  New
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  In changes made under bug 1621615 (specifically a1cdebdea), we now
  expect that there may be a 'ip6=' argument on the kernel command line.
  The changes made did not test the case where there is 'ip6=' and no
  'ip='.

  The code currently will return with no network configuration found if
  there is only ip6=...


  Related bugs:
   * bug 1621615: network not configured when ipv6 netbooted into cloud-init 
   * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 
addresses
   * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1639930/+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 1644043] Re: Read Kernel Config tests missing MAC Address

2016-12-01 Thread Scott Moser

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu)
   Status: New => Fix Released

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

-- 
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/1644043

Title:
  Read Kernel Config tests missing MAC Address

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  Unittests are broken [1] preventing cloud-init from building
  currently. The issue is the kernel config tests are looking for a MAC
  address that is not there.

  [1] https://jenkins.ubuntu.com/server/job/cloud-init-integration-
  lts/35/console

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1644043/+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 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit

2016-12-01 Thread Scott Moser

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu)
   Status: New => Fix Released

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Confirmed => In Progress

** Changed in: cloud-init (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

-- 
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/1460715

Title:
  MBR disk setup fails because sfdisk no longer accepts M as a valid
  unit

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  Specifically, we get the following output in
  cc_disk_setup.exec_mkpart_mbr:

  sfdisk: --Linux option is unnecessary and deprecated
  sfdisk: unsupported unit 'M'

  and the manpage says:

     -u, --unit S
    Deprecated option.  Only the sector unit is supported.

  So we'll need to shift to using sectors.

  Related bugs:
   * bug 1642383: Unable to configure swap space on ephemeral disk in Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1460715/+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

60 matches

Mail list logo