[Yahoo-eng-team] [Bug 1609097] [NEW] vif_port_id of ironic port is not updating after neutron port-delete

2016-08-02 Thread Andrey Shestakov 
Public bug reported:

Steps to reproduce
==
1. Get list of attached ports of instance:
nova interface-list 42dd8b8b-b2bc-420e-96b6-958e9295b2d4
++--+--+---+---+
| Port State | Port ID | Net ID | IP addresses | MAC Addr |
++--+--+---+---+
| ACTIVE | 512e6c8e-3829-4bbd-8731-c03e5d7f7639 | 
ccd0fd43-9cc3-4544-b17c-dfacd8fa4d14 | 
10.1.0.6,fdea:fd32:11ff:0:f816:3eff:fed1:8a7c | 52:54:00:85:19:89 |
++--+--+---+---+
2. Show ironic port. it has vif_port_id in extra with id of neutron port:
ironic port-show 735fcaf5-145d-4125-8701-365c58c6b796
+---+---+
| Property | Value |
+---+---+
| address | 52:54:00:85:19:89 |
| created_at | 2016-07-20T13:15:23+00:00 |
| extra | {u'vif_port_id': u'512e6c8e-3829-4bbd-8731-c03e5d7f7639'} |
| local_link_connection | |
| node_uuid | 679fa8a9-066e-4166-ac1e-6e77af83e741 |
| pxe_enabled | |
| updated_at | 2016-07-22T13:31:29+00:00 |
| uuid | 735fcaf5-145d-4125-8701-365c58c6b796 |
+---+---+
3. Delete neutron port:
neutron port-delete 512e6c8e-3829-4bbd-8731-c03e5d7f7639
Deleted port: 512e6c8e-3829-4bbd-8731-c03e5d7f7639
4. It is done from interface list:
nova interface-list 42dd8b8b-b2bc-420e-96b6-958e9295b2d4
++-++--+--+
| Port State | Port ID | Net ID | IP addresses | MAC Addr |
++-++--+--+
++-++--+--+
5. ironic port still has vif_port_id with neutron's port id:
ironic port-show 735fcaf5-145d-4125-8701-365c58c6b796
+---+---+
| Property | Value |
+---+---+
| address | 52:54:00:85:19:89 |
| created_at | 2016-07-20T13:15:23+00:00 |
| extra | {u'vif_port_id': u'512e6c8e-3829-4bbd-8731-c03e5d7f7639'} |
| local_link_connection | |
| node_uuid | 679fa8a9-066e-4166-ac1e-6e77af83e741 |
| pxe_enabled | |
| updated_at | 2016-07-22T13:31:29+00:00 |
| uuid | 735fcaf5-145d-4125-8701-365c58c6b796 |
+---+---+

Expected result
===
ironic port should not have vif_port_id in extra field.

Actual result
=
ironic port has vif_port_id with id of deleted neutron port.

This can confuse when user wants to get list of unused ports of ironic node.
vif_port_id should be removed after neutron port-delete.
Corresponding bug filed on neutron side 
https://bugs.launchpad.net/neutron/+bug/1606229

** Affects: nova
 Importance: Undecided
 Assignee: Andrey Shestakov (ashestakov)
 Status: In Progress

** Changed in: nova
 Assignee: (unassigned) => Andrey Shestakov (ashestakov)

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

Title:
  vif_port_id of ironic port is not updating after neutron port-delete

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Steps to reproduce
  ==
  1. Get list of attached ports of instance:
  nova interface-list 42dd8b8b-b2bc-420e-96b6-958e9295b2d4
  
++--+--+---+---+
  | Port State | Port ID | Net ID | IP addresses | MAC Addr |
  
++--+--+---+---+
  | ACTIVE | 512e6c8e-3829-4bbd-8731-c03e5d7f7639 | 
ccd0fd43-9cc3-4544-b17c-dfacd8fa4d14 | 
10.1.0.6,fdea:fd32:11ff:0:f816:3eff:fed1:8a7c | 52:54:00:85:19:89 |
  
++--+--+---+---+
  2. Show ironic port. it has vif_port_id in extra with id of neutron port:
  ironic port-show 735fcaf5-145d-4125-8701-365c58c6b796
  
+---+---+
  | Property | Value |
  
+---+---+
  | address | 52:54:00:85:19:89 |
  | created_at | 2016-07-20T13:15:23

[Yahoo-eng-team] [Bug 1606229] [NEW] vif_port_id of ironic port is not updating after neutron port-delete

2016-07-25 Thread Andrey Shestakov 
Public bug reported:

Steps to reproduce:
1. Get list of attached ports of instance:
nova interface-list 42dd8b8b-b2bc-420e-96b6-958e9295b2d4
++--+--+---+---+
| Port State | Port ID  | Net ID
   | IP addresses  | MAC Addr  |
++--+--+---+---+
| ACTIVE | 512e6c8e-3829-4bbd-8731-c03e5d7f7639 | 
ccd0fd43-9cc3-4544-b17c-dfacd8fa4d14 | 
10.1.0.6,fdea:fd32:11ff:0:f816:3eff:fed1:8a7c | 52:54:00:85:19:89 |
++--+--+---+---+
2. Show ironic port. it has vif_port_id in extra with id of neutron port:
ironic port-show 735fcaf5-145d-4125-8701-365c58c6b796
+---+---+
| Property  | Value 
|
+---+---+
| address   | 52:54:00:85:19:89 
|
| created_at| 2016-07-20T13:15:23+00:00 
|
| extra | {u'vif_port_id': 
u'512e6c8e-3829-4bbd-8731-c03e5d7f7639'} |
| local_link_connection |   
|
| node_uuid | 679fa8a9-066e-4166-ac1e-6e77af83e741  
|
| pxe_enabled   |   
|
| updated_at| 2016-07-22T13:31:29+00:00 
|
| uuid  | 735fcaf5-145d-4125-8701-365c58c6b796  
|
+---+---+
3. Delete neutron port:
neutron port-delete 512e6c8e-3829-4bbd-8731-c03e5d7f7639
Deleted port: 512e6c8e-3829-4bbd-8731-c03e5d7f7639
4. It is done from interface list:
nova interface-list 42dd8b8b-b2bc-420e-96b6-958e9295b2d4
++-++--+--+
| Port State | Port ID | Net ID | IP addresses | MAC Addr |
++-++--+--+
++-++--+--+
5. ironic port still has vif_port_id with neutron's port id:
ironic port-show 735fcaf5-145d-4125-8701-365c58c6b796
+---+---+
| Property  | Value 
|
+---+---+
| address   | 52:54:00:85:19:89 
|
| created_at| 2016-07-20T13:15:23+00:00 
|
| extra | {u'vif_port_id': 
u'512e6c8e-3829-4bbd-8731-c03e5d7f7639'} |
| local_link_connection |   
|
| node_uuid | 679fa8a9-066e-4166-ac1e-6e77af83e741  
|
| pxe_enabled   |   
|
| updated_at| 2016-07-22T13:31:29+00:00 
|
| uuid  | 735fcaf5-145d-4125-8701-365c58c6b796  
|
+---+---+

This can confuse when user wants to get list of unused ports of ironic node.
vif_port_id should be removed after neutron port-delete.

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

Title:
  vif_port_id of ironic port is not updating after neutron port-delete

Status in neutron:
  New

Bug description:
  Steps to reproduce:
  1. Get list of attached ports of instance:
  nova interface-list 42dd8b8b-b2bc-420e-96b6-958e9295b2d4
  
++--+--+---+---+
  | Port State | Port ID  | Net ID  
 | IP addresses  | MAC Addr 
 |
  
++--+--+---+---+
  | ACTIVE | 512e6c8e-3829-4bbd-8731-c03e5d7f7639 | 
ccd0fd43-9cc3-4544-b17c-dfacd8fa4d14 | 
10.1.0.6,fdea:fd32:11ff:0:f816:3eff:fed1:8a7c |

[Yahoo-eng-team] [Bug 1598078] [NEW] dnsmasq replies are incorrect after multiple simultaneously reloads

2016-07-01 Thread Andrey Shestakov 
Public bug reported:

When boot lot of instances by single request (nova boot --min-count 90), some 
instances do not receive DHCP reply.
After investigation found that DHCP server for some requests answers to correct 
address and for some requests answers to broadcast.

Packages captured by tcpdump:
13:37:44.298533 3c:fd:fe:9c:62:c4 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), 
length 590: (tos 0x0, ttl 20, id 0, offset 0, flags [none], proto UDP (17), 
length 576)
   0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 
3c:fd:fe:9c:62:c4, length 548, xid 0xfe9c62c4, Flags [Broadcast] (0x8000)
  Client-Ethernet-Address 3c:fd:fe:9c:62:c4
  Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
Parameter-Request Option 55, length 36:
  Subnet-Mask, Time-Zone, Default-Gateway, Time-Server
  IEN-Name-Server, Domain-Name-Server, RL, Hostname
  BS, Domain-Name, SS, RP
  EP, RSZ, TTL, BR
  YD, YS, NTP, Vendor-Option
  Requested-IP, Lease-Time, Server-ID, RN
  RB, Vendor-Class, TFTP, BF
  Option 128, Option 129, Option 130, Option 131
  Option 132, Option 133, Option 134, Option 135
MSZ Option 57, length 2: 1260
GUID Option 97, length 17: 
0.55.49.57.48.54.49.85.83.69.53.51.55.87.78.89.54
ARCH Option 93, length 2: 0
NDI Option 94, length 3: 1.2.1
Vendor-Class Option 60, length 32: "PXEClient:Arch:0:UNDI:002001"
END Option 255, length 0
PAD Option 0, length 0, occurs 200
13:37:44.298819 fa:16:3e:f0:b1:23 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), 
length 401: (tos 0xc0, ttl 64, id 30122, offset 0, flags [none], proto UDP 
(17), length 387)
   10.51.1.1.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP, Reply, length 
359, xid 0xfe9c62c4, Flags [Broadcast] (0x8000)
  Your-IP 10.51.5.125
  Server-IP 10.51.0.4
  Client-Ethernet-Address 3c:fd:fe:9c:62:c4
  Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Offer
Server-ID Option 54, length 4: 10.51.1.1
Lease-Time Option 51, length 4: 600
RN Option 58, length 4: 300
RB Option 59, length 4: 525
Subnet-Mask Option 1, length 4: 255.255.0.0
BR Option 28, length 4: 10.51.255.255
Domain-Name Option 15, length 14: "openstacklocal"
Hostname Option 12, length 16: "host-10-51-5-125"
TFTP Option 66, length 10: "10.51.0.4^@"
BF Option 67, length 11: "pxelinux.0^@"
Default-Gateway Option 3, length

After restart of neutron-dhcp-agent this issue gone.
Looks like on bunch of port-create and port-update operations 
neutron-dhcp-agent sends HUP signal to dnsmasq for reload to frequently.
dnsmasq do clear cache and read files by signal event asynchronously which 
causes errors in loaded data.

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

Title:
  dnsmasq replies are incorrect after multiple simultaneously reloads

Status in neutron:
  New

Bug description:
  When boot lot of instances by single request (nova boot --min-count 90), some 
instances do not receive DHCP reply.
  After investigation found that DHCP server for some requests answers to 
correct address and for some requests answers to broadcast.

  Packages captured by tcpdump:
  13:37:44.298533 3c:fd:fe:9c:62:c4 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 590: (tos 0x0, ttl 20, id 0, offset 0, flags [none], proto UDP 
(17), length 576)
 0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 
3c:fd:fe:9c:62:c4, length 548, xid 0xfe9c62c4, Flags [Broadcast] (0x8000)
Client-Ethernet-Address 3c:fd:fe:9c:62:c4
Vendor-rfc1048 Extensions
  Magic Cookie 0x63825363
  DHCP-Message Option 53, length 1: Discover
  Parameter-Request Option 55, length 36:
Subnet-Mask, Time-Zone, Default-Gateway, Time-Server
IEN-Name-Server, Domain-Name-Server, RL, Hostname
BS, Domain-Name, SS, RP
EP, RSZ, TTL, BR
YD, YS, NTP, Vendor-Option
Requested-IP, Lease-Time, Server-ID, RN
RB, Vendor-Class, TFTP, BF
Option 128, Option 129, Option 130, Option 131
Option 132, Option 133, Option 134, Option 135
  MSZ Option 57, length 2: 1260
  GUID Option 97, length 17: 
0.55.49.57.48.54.49.85.83.69.53.51.55.87.78.89.54
  ARCH Option 93, length 2: 0
  NDI Option 94, length 3: 1.2.1
  Vendor-Class Option 60, length 32: "PXEClient:Arch:0:UNDI:002001"
  END Option 255, length 0
  PAD Option 0, length 0, occurs 200
  13:37:44.298819 fa:16:3e:f0:b1:23 > ff:ff:ff:ff:ff:ff, ethertype IPv4

[Yahoo-eng-team] [Bug 1537721] [NEW] Image corrupts when upload

2016-01-25 Thread Andrey Shestakov 
Public bug reported:

After this commit 
https://github.com/openstack/glance_store/commit/a0572ef672512a8ed7ef203816ec256eafd5f9de
image uploads works incorrect.

Steps to reproduce:

1. Upload image (1.47GB)
md5sum virtual_ubuntu_trasty_ext4_demo 
fa9ec35d64d43aefd6356150d361ec24  virtual_ubuntu_trasty_ext4_demo

glance image-create --disk-format raw --container-format bare --file 
virtual_ubuntu_trasty_ext4_demo --progress --name ubuntu_upload_with_fix 
[=>] 100%
+--+--+
| Property | Value|
+--+--+
| checksum | fa9ec35d64d43aefd6356150d361ec24 |
| container_format | bare |
| created_at   | 2016-01-25T11:06:15Z |
| disk_format  | raw  |
| id   | 5b955bce-61ab-4c55-afd9-8bd6012cf1ab |
| min_disk | 0|
| min_ram  | 0|
| name | ubuntu_upload_with_fix   |
| owner| e885a6c5e87c45d38a274de4388241e6 |
| protected| False|
| size | 1476395008   |
| status   | active   |
| tags | []   |
| updated_at   | 2016-01-25T11:10:49Z |
| virtual_size | None |
| visibility   | private  |
+--+--+

2. It has 10 obects in Swift, but should has only one (size is less than 5G)
swift list glance
5b955bce-61ab-4c55-afd9-8bd6012cf1ab
5b955bce-61ab-4c55-afd9-8bd6012cf1ab-1
5b955bce-61ab-4c55-afd9-8bd6012cf1ab-2
5b955bce-61ab-4c55-afd9-8bd6012cf1ab-3
5b955bce-61ab-4c55-afd9-8bd6012cf1ab-4
5b955bce-61ab-4c55-afd9-8bd6012cf1ab-5
5b955bce-61ab-4c55-afd9-8bd6012cf1ab-6
5b955bce-61ab-4c55-afd9-8bd6012cf1ab-7
5b955bce-61ab-4c55-afd9-8bd6012cf1ab-8
5b955bce-61ab-4c55-afd9-8bd6012cf1ab-9

Image splitted by 7 chunks of 200MB + 1*47MB + 1 zero length chunk.
swift stat glance 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-7
   Account: v1
 Container: glance
Object: 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-7
  Content Type: binary/octet-stream
Content Length: 20480
 Last Modified: Mon, 25 Jan 2016 11:10:42 GMT
  ETag: eda9a9889837ac4bc81d6387d92c1bec
 Accept-Ranges: bytes
Server: Apache
   X-Timestamp: 1453720242.0
X-Trans-Id: txda5cc-0056a6064c-5e81-default
swift stat glance 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-8
   Account: v1
 Container: glance
Object: 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-8
  Content Type: binary/octet-stream
Content Length: 42795008
 Last Modified: Mon, 25 Jan 2016 11:10:49 GMT
  ETag: f3c9b36eceea8d2192996ca931f1fa55
 Accept-Ranges: bytes
Server: Apache
   X-Timestamp: 1453720249.0
X-Trans-Id: txd8c0e-0056a60655-377d-default
swift stat glance 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-9
   Account: v1
 Container: glance
Object: 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-9
  Content Type: binary/octet-stream
Content Length: 0
 Last Modified: Mon, 25 Jan 2016 11:10:49 GMT
  ETag: d41d8cd98f00b204e9800998ecf8427e
 Accept-Ranges: bytes
Server: Apache
   X-Timestamp: 1453720249.0
X-Trans-Id: txda39b-0056a60660-85c1-default

3. Download image 
glance image-download 5b955bce-61ab-4c55-afd9-8bd6012cf1ab --file 
ubuntu_download_with_fix --progress
[=>] 100%[Errno 32] Corrupt image download. 
Checksum was 9253e738cabf6a3c0beace1a3b07e623 expected 
fa9ec35d64d43aefd6356150d361ec24

Image is corrupted, and original and result files has difference in lenght 
(1754 bytes)
ls -l virtual_ubuntu_trasty_ext4_demo 
-rw-r--r-- 1 root root 1476395008 Jan 25 11:04 virtual_ubuntu_trasty_ext4_demo
ls -l ubuntu_download_with_fix 
-rw-r--r-- 1 root root 1476393254 Jan 25 11:17 ubuntu_download_with_fix

** Affects: glance
 Importance: Undecided
 Status: New

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

Title:
  Image corrupts when upload

Status in Glance:
  New

Bug description:
  After this commit 
https://github.com/openstack/glance_store/commit/a0572ef672512a8ed7ef203816ec256eafd5f9de
  image uploads works incorrect.

  Steps to reproduce:

  1. Upload image (1.47GB)
  md5sum virtual_ubuntu_trasty_ext4_demo 
  fa9ec35d64d43aefd6356150d361ec24  virtual_ubuntu_trasty_ext4_demo

  glance image-create --disk-format raw --container-format bare --file 
virtual_ubuntu_trasty_ext4_demo --progress --name

[Yahoo-eng-team] [Bug 1518431] Re: Glance failed to upload image to swift storage

2015-12-01 Thread Andrey Shestakov 
** Also affects: mos
   Importance: Undecided
   Status: New

** Changed in: mos
   Status: New => Confirmed

** Changed in: mos
 Assignee: (unassigned) => MOS Glance (mos-glance)

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

Title:
  Glance failed to upload image to swift storage

Status in Glance:
  Confirmed
Status in Mirantis OpenStack:
  Confirmed

Bug description:
  When glance configured with swift backend, and swift API provides via
  RadosGW is unable to upload image.

  Command:
  glance --debug image-create --name trusty_ext4 --disk-format raw 
--container-format bare --file trusty-server-cloudimg-amd64.img --visibility 
public --progress
  Logs:
  http://paste.openstack.org/show/479621/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1518431/+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 1518431] [NEW] Glance failed to upload image to swift storage via RadosGW

2015-11-20 Thread Andrey Shestakov 
Public bug reported:

When glance configured with swift backend, and swift API provides via
RadosGW is unable to upload image.

Command:
glance --debug image-create --name trusty_ext4 --disk-format raw 
--container-format bare --file trusty-server-cloudimg-amd64.img --visibility 
public --progress
Logs:
http://paste.openstack.org/show/479621/

** Affects: glance
 Importance: Undecided
 Status: New

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

Title:
  Glance failed to upload image to swift storage via RadosGW

Status in Glance:
  New

Bug description:
  When glance configured with swift backend, and swift API provides via
  RadosGW is unable to upload image.

  Command:
  glance --debug image-create --name trusty_ext4 --disk-format raw 
--container-format bare --file trusty-server-cloudimg-amd64.img --visibility 
public --progress
  Logs:
  http://paste.openstack.org/show/479621/

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