[Yahoo-eng-team] [Bug 2089252] [NEW] neutron-vpnaas: LibreSwan 4 connections not listed as ACTIVE

2024-11-21 Thread Trygve Vea
Public bug reported: The regex that are used to check IPSec connection status is incorrect for LibreSwan 4: >From neutron_vpnaas/services/vpn/device_drivers/ipsec.py ```python STATUS_IPSEC_SA_ESTABLISHED_RE = ( r'\d{3} #\d+: "([a-f0-9\-]+).*established.*newest IPSEC') STATUS_IPSEC

[Yahoo-eng-team] [Bug 2089250] [NEW] neutron-vpnaas: Automatic VPN Agent failover not working with OVN driver

2024-11-21 Thread Trygve Vea
Public bug reported: This issue has been observed in RDO 2024.1/OVN 23.03/AlmaLinux 9. This has also been reproduced in Devstack. 1. Ensure that allow_automatic_vpnagent_failover is set to True 2. Have two VPN agents 3. Set up a VPN connection successfully 4. Disable the agent running the VPN co

[Yahoo-eng-team] [Bug 2028142] [NEW] VM can't get IP without default egress rules on OVN

2023-07-19 Thread Trygve Vea
Public bug reported: Confirmed on: - RDO stable/2023.1 (antelope) - Almalinux 9, kernel 5.14.0-284.18.1.el9_2.x86_64 - Neutron 22.0.2 (RDO) - OVN 22.12 (from CentOS SIG) How to reproduce: - Have a functioning instance which gets its IP address from DHCP - Ensure that you have a user that can lo

[Yahoo-eng-team] [Bug 1778305] [NEW] Nova may erronously look up service version of a deleted service, when hostname have been reused

2018-06-22 Thread Trygve Vea
Public bug reported: Prerequisites: - A compute node running an old version of nova has been deleted. (In our case, version 9) - The hostname of said compute node has been reused, and has been upgraded as per normal. (To version 16) - The services table in the nova database contains both the ol

[Yahoo-eng-team] [Bug 1738625] [NEW] Floating IP description field should be available in Horizon

2017-12-17 Thread Trygve Vea
Public bug reported: The Network v2.0 API has a description field for floating ip addresses. It should be possible to set this value when allocating, and to read this value when displaying a list. ** Affects: horizon Importance: Undecided Assignee: Trygve Vea (trygve-vea-gmail

[Yahoo-eng-team] [Bug 1738501] [NEW] Nova scheduler randomly fails to schedule CPU-pinned instance-flavors with hugepages - fails increases as running instance count grows

2017-12-15 Thread Trygve Vea
Public bug reported: Description === Isolated to single hypervisor. Nova scheduler randomly fails to schedule CPU-pinned instance-flavors with hugepages - fails increases as running instance count grows. Steps to reproduce == 1) Hypervisor with two numa-nodes, 2x Intel G

[Yahoo-eng-team] [Bug 1727845] [NEW] Database and compute nodes can fall out of sync after live migration

2017-10-26 Thread Trygve Vea
Public bug reported: Description === When performing a rolling live-migrate-and-reboot of a series of compute hosts, we have seen some (rare) occurrances where the instance-record in the database have not been updated with the new host. Another symptom is that the affected instance wil

[Yahoo-eng-team] [Bug 1725617] [NEW] Neutron extension 'network_availability_zone' not supported

2017-10-21 Thread Trygve Vea
- The network create form gets a new field 'Availability Zone Hints', which forwards this to the neutron client on submission. ** Affects: horizon Importance: Undecided Assignee: Trygve Vea (trygve-vea-gmail) Status: In Progress ** Changed in: horizon Status:

[Yahoo-eng-team] [Bug 1724393] [NEW] Poor ipv6 test coverage for networks and subnetworks

2017-10-17 Thread Trygve Vea
: horizon Importance: Undecided Assignee: Trygve Vea (trygve-vea-gmail) Status: New ** Changed in: horizon Assignee: (unassigned) => Trygve Vea (trygve-vea-gmail) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscri

[Yahoo-eng-team] [Bug 1722584] [NEW] Return traffic from metadata service may get dropped by hypervisor due to wrong checksum

2017-10-10 Thread Trygve Vea
Public bug reported: We have a problem with the metadata service not being responsive, when the proxied in the router namespace on some of our networking nodes after upgrading to Ocata (Running on CentOS 7.4, with the RDO packages). Instance routes traffic to 169.254.169.254 to it's default gate

[Yahoo-eng-team] [Bug 1696417] [NEW] nova-manage db online_data_migrations can fail when upgrading to newton under certain conditions

2017-06-07 Thread Trygve Vea
Public bug reported: Reproduceable under conditions: * Mitaka upgraded to Newton * online_data_migrations have not yet migrated flavors and/or aggregates from the nova database, to the nova-api database * One or more of the datetime-fields (created_at, updated_at, deleted_at) are set. ** Becaus