[Yahoo-eng-team] [Bug 2037034] [NEW] Neutron tempest plugin zuul job definitions uses deprecated regex syntax
Public bug reported: Details about deprecation are in https://lists.opendev.org/archives/list/service- annou...@lists.opendev.org/thread/C2NADWASR3BFJI3J45ZCNKOZBJETF6NE/ We have issue in the neutron-tempest-plugin jobs: Zuul encountered a deprecated syntax while parsing its configuration in the repo openstack/neutron-tempest-plugin on branch master. The problem was: All regular expressions must conform to RE2 syntax, but an expression using the deprecated Perl-style syntax has been detected. Adjust the configuration to conform to RE2 syntax. The RE2 syntax error is: invalid perl operator: (?! The problem appears in the following job stanza: job: name: neutron-tempest-plugin-base-nested-switch parent: neutron-tempest-plugin-base abstract: true branches: ^(?!stable/(train|ussuri|victoria|wallaby|xena|yoga|zed)).*$ # Comment nodeset and vars to switch back to non nested nodes nodeset: neutron-nested-virt-ubuntu-jammy vars: _virt_vars devstack_localrc: LIBVIRT_TYPE: kvm LIBVIRT_CPU_MODE: host-passthrough CIRROS_VERSION: 0.6.2 DEFAULT_IMAGE_NAME: cirros-0.6.2-x86_64-disk DEFAULT_IMAGE_FILE_NAME: cirros-0.6.2-x86_64-disk.img # Base nested switch job for yoga and zed in "openstack/neutron-tempest-plugin/zuul.d/base-nested- switch.yaml@master", line 22, column 3 ** Affects: neutron Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2037034 Title: Neutron tempest plugin zuul job definitions uses deprecated regex syntax Status in neutron: Confirmed Bug description: Details about deprecation are in https://lists.opendev.org/archives/list/service- annou...@lists.opendev.org/thread/C2NADWASR3BFJI3J45ZCNKOZBJETF6NE/ We have issue in the neutron-tempest-plugin jobs: Zuul encountered a deprecated syntax while parsing its configuration in the repo openstack/neutron-tempest-plugin on branch master. The problem was: All regular expressions must conform to RE2 syntax, but an expression using the deprecated Perl-style syntax has been detected. Adjust the configuration to conform to RE2 syntax. The RE2 syntax error is: invalid perl operator: (?! The problem appears in the following job stanza: job: name: neutron-tempest-plugin-base-nested-switch parent: neutron-tempest-plugin-base abstract: true branches: ^(?!stable/(train|ussuri|victoria|wallaby|xena|yoga|zed)).*$ # Comment nodeset and vars to switch back to non nested nodes nodeset: neutron-nested-virt-ubuntu-jammy vars: _virt_vars devstack_localrc: LIBVIRT_TYPE: kvm LIBVIRT_CPU_MODE: host-passthrough CIRROS_VERSION: 0.6.2 DEFAULT_IMAGE_NAME: cirros-0.6.2-x86_64-disk DEFAULT_IMAGE_FILE_NAME: cirros-0.6.2-x86_64-disk.img # Base nested switch job for yoga and zed in "openstack/neutron-tempest-plugin/zuul.d/base-nested- switch.yaml@master", line 22, column 3 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2037034/+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 2037002] [NEW] Reader can update object tag
Public bug reported: Update of Neutron object tags ignores policies for this object update. So, reader user can update tags for all objects of his project Reproduced on Devstack - Yoga. Newer releases up to master have no changes here, so also should be affected Steps to reproduce: All operations in default alt_demo project, which has all needed users provisioned by default 1. Create network object, i.e. floating ip using alt_demo user - as project admin 2. Re-login as alt_demo_reader and try to update tags for this floating Tags are updated successfully, but reader user has no rights for floating update - "update_floatingip" policy enabled for at least member ** 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/2037002 Title: Reader can update object tag Status in neutron: New Bug description: Update of Neutron object tags ignores policies for this object update. So, reader user can update tags for all objects of his project Reproduced on Devstack - Yoga. Newer releases up to master have no changes here, so also should be affected Steps to reproduce: All operations in default alt_demo project, which has all needed users provisioned by default 1. Create network object, i.e. floating ip using alt_demo user - as project admin 2. Re-login as alt_demo_reader and try to update tags for this floating Tags are updated successfully, but reader user has no rights for floating update - "update_floatingip" policy enabled for at least member To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2037002/+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 2036877] [NEW] radvd seems to crash when ipv4 addresses are supplied as nameservers to ipv6 subnets
Public bug reported:
I'll copy from this report, please notice that I'm NOT the original
reporter!:
https://bugs.launchpad.net/kolla-ansible/+bug/2033980/comments/8
Before cleaning the PID file, I did take a look at the config of radvd:
```
$ cat /var/lib/neutron/ra/aee91f41-1945-40b4-b72f-8be2eb369b44.radvd.conf
interface qr-caa16d7e-26
{
AdvSendAdvert on;
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
AdvLinkMTU 1450;
RDNSS 2a02:74a0:x:0::53 10.40.3.53 2a02:74a0:x:0::54 {};
prefix 2a02:74a0:x:y::/64
{
AdvOnLink on;
AdvAutonomous on;
};
route fe80::a9fe:a9fe/128 {
};
};
```
We've been configuring the router with terraform, assigning the ipv4
resolvers to the IPv4 subnet and the IPv6 resolvers to the IPv6 subnet.
After deleting the router, adjusting the subnets (no resolvers on v4,
only ipv6 resolvers on ipv6), and recreating the router, radvd is now
active and everything's fine.
It seems that due to misconfiguration (and incomplete template parsing),
IPv4 nameservers ended up in the config of radvd, which failed to start.
Neutron was then unable to clean up the pidfile, thus failing to start
radvd again.
** 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/2036877
Title:
radvd seems to crash when ipv4 addresses are supplied as nameservers
to ipv6 subnets
Status in neutron:
New
Bug description:
I'll copy from this report, please notice that I'm NOT the original
reporter!:
https://bugs.launchpad.net/kolla-ansible/+bug/2033980/comments/8
Before cleaning the PID file, I did take a look at the config of
radvd:
```
$ cat /var/lib/neutron/ra/aee91f41-1945-40b4-b72f-8be2eb369b44.radvd.conf
interface qr-caa16d7e-26
{
AdvSendAdvert on;
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
AdvLinkMTU 1450;
RDNSS 2a02:74a0:x:0::53 10.40.3.53 2a02:74a0:x:0::54 {};
prefix 2a02:74a0:x:y::/64
{
AdvOnLink on;
AdvAutonomous on;
};
route fe80::a9fe:a9fe/128 {
};
};
```
We've been configuring the router with terraform, assigning the ipv4
resolvers to the IPv4 subnet and the IPv6 resolvers to the IPv6
subnet.
After deleting the router, adjusting the subnets (no resolvers on v4,
only ipv6 resolvers on ipv6), and recreating the router, radvd is now
active and everything's fine.
It seems that due to misconfiguration (and incomplete template
parsing), IPv4 nameservers ended up in the config of radvd, which
failed to start. Neutron was then unable to clean up the pidfile, thus
failing to start radvd again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2036877/+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
