[Yahoo-eng-team] [Bug 1938575] [NEW] Misalignment with extra-dhcp-options between neutronclient & openstackclient
Public bug reported:
The SetPort class from the openstack client does not support
--extra-dhcp-option [1]
(overcloud) $ openstack port set --extra-dhcp-option
name=mtu,value=1700,ip-version=4 port-test-202
usage: openstack port set [-h] [--description ]
[--device ] [--mac-address ]
[--device-owner ]
[--vnic-type ] [--host ]
[--dns-domain dns-domain] [--dns-name ]
[--enable | --disable] [--name ]
[--fixed-ip subnet=,ip-address=]
[--no-fixed-ip]
[--binding-profile ]
[--no-binding-profile] [--qos-policy ]
[--security-group ]
[--no-security-group]
[--enable-port-security | --disable-port-security]
[--allowed-address
ip-address=[,mac-address=]]
[--no-allowed-address]
[--data-plane-status ] [--tag ]
[--no-tag]
openstack port set: error: unrecognized arguments: --extra-dhcp-option
port-test-202
The UpdatePort class from the neutron client supports --extra-dhcp-opt [2]
This is aligned with the neutron API [3]
(overcloud) $ neutron port-update port-test-202 --extra-dhcp-opt
opt_name=mtu,opt_value=1750,ip_version=4
neutron CLI is deprecated and will be removed in the future. Use openstack CLI
instead.
Updated port: port-test-202
(overcloud) $ neutron port-show port-test-202 | grep mtu
neutron CLI is deprecated and will be removed in the future. Use openstack CLI
instead.
| | {"opt_name": "mtu", "opt_value": "1750",
"ip_version": 4}
|
[1]
https://opendev.org/openstack/python-openstackclient/src/commit/ed87f7949ef1ef580ed71b9820e16823c0466472/openstackclient/network/v2/port.py#L703
[2]
https://github.com/openstack/python-neutronclient/blob/2f047b15957308e84dcb72baee3415b8bf5a470a/neutronclient/neutron/v2_0/port.py#L305
[3]
https://docs.openstack.org/api-ref/network/v2/?expanded=update-port-detail#update-port
** Affects: neutron
Importance: Undecided
Status: New
** Description changed:
The SetPort class from the openstack client does not support
--extra-dhcp-option [1]
- (overcloud) [stack@undercloud-0 tempest-dir]$ openstack port set
--extra-dhcp-option name=mtu,value=1700,ip-version=4 port-test-202
+ (overcloud) $ openstack port set --extra-dhcp-option
name=mtu,value=1700,ip-version=4 port-test-202
usage: openstack port set [-h] [--description ]
- [--device ] [--mac-address ]
- [--device-owner ]
- [--vnic-type ] [--host ]
- [--dns-domain dns-domain] [--dns-name ]
- [--enable | --disable] [--name ]
- [--fixed-ip subnet=,ip-address=]
- [--no-fixed-ip]
- [--binding-profile ]
- [--no-binding-profile] [--qos-policy ]
- [--security-group ]
- [--no-security-group]
- [--enable-port-security | --disable-port-security]
- [--allowed-address
ip-address=[,mac-address=]]
- [--no-allowed-address]
- [--data-plane-status ] [--tag ]
- [--no-tag]
-
+ [--device ] [--mac-address ]
+ [--device-owner ]
+ [--vnic-type ] [--host ]
+ [--dns-domain dns-domain] [--dns-name ]
+ [--enable | --disable] [--name ]
+ [--fixed-ip subnet=,ip-address=]
+ [--no-fixed-ip]
+ [--binding-profile ]
+ [--no-binding-profile] [--qos-policy ]
+ [--security-group ]
+ [--no-security-group]
+ [--enable-port-security | --disable-port-security]
+ [--allowed-address
ip-address=[,mac-address=]]
+ [--no-allowed-address]
+ [--data-plane-status ] [--tag ]
+ [--no-tag]
+
openstack port set: error: unrecognized arguments: --extra-dhcp-option
port-test-202
The UpdatePort class from the neutron client supports --extra-dhcp-opt [2]
This is aligned with the neutron API [3]
(overcloud) $ neutron port-update port-test-202 --extra-dhcp-opt
opt_name=mtu,opt_value=1750,ip_version=4
neutron CLI
[Yahoo-eng-team] [Bug 1885825] Re: No implicit user creation with GRANT syntax in MySQL 8.0 Ubuntu Focal
This was fixed in glance with b220030070adbea0bd253dfa390218d30b047154. ** Changed in: glance Status: New => 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/1885825 Title: No implicit user creation with GRANT syntax in MySQL 8.0 Ubuntu Focal Status in coverage2sql: Fix Released Status in Glance: Fix Released Status in Glance ussuri series: New Status in OpenStack Identity (keystone): Fix Released Status in OpenStack Compute (nova): Fix Released Status in tacker: Fix Released Status in zaqar: Fix Released Bug description: Ubuntu Focal (20.04) has mysql 8.0 and with mysql 8.0 there is no implicit user creation with GRANT syntax. In Ubuntu Bionic (18.04) mysql 5.7 version used to create the user implicitly when using using the GRANT. But starting with mysql 8.0, we need to create the user explicitly before using the GRANT command. Nova unit and functional tests job using tools/test-setup.sh script start failing when running on Ubuntu Focal https://zuul.opendev.org/t/openstack/build/8b0f4fcc21854655a638c413b6fe1a91 + sudo -H mysql -u root -pinsecure_slave -h localhost -e ' DELETE FROM mysql.user WHERE User='\'''\''; FLUSH PRIVILEGES; GRANT ALL PRIVILEGES ON *.* TO '\''openstack_citest'\''@'\''%'\'' identified by '\''openstack_citest'\'' WITH GRANT OPTION;' mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 1064 (42000) at line 4: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'identified by 'openstack_citest' WITH GRANT OPTION' at line 2 we need to modify the tools/test-setup.sh to create user first. Below used to work with mysql 5.7 GRANT ALL PRIVILEGES ON *.* TO '$DB_USER'@'%' identified by '$DB_PW' WITH GRANT OPTION;" With mysql 8.0 we need to create user first CREATE USER '$DB_USER'@'%' IDENTIFIED BY '$DB_PW'; GRANT ALL PRIVILEGES ON *.* TO '$DB_USER'@'%' WITH GRANT OPTION;" To manage notifications about this bug go to: https://bugs.launchpad.net/coverage2sql/+bug/1885825/+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 1938571] [NEW] vpnaas problem:ipsec pluto not running centos 8 victoria wallaby
Public bug reported: Hello. I apologize if I don't do things right to explain the bug. I am using Centos 8 and I install openstak with, kolla ansible. Whether it is Ussuri, Victoria or Wallaby, when establishing the connection between the 2 networks(with vpnaas), the error message is as follows: ipsec whack --status" (no "/run/pluto/pluto.ctl") The problem would be present with the Libreswan version 4.X which does not include the option "--use-netkey " used by the ipsec pluto command This option was present in Libreswan 3.X. So the command "ipsec pluto." failed , so no "/run/pluto/pluto.ctl". ** 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/1938571 Title: vpnaas problem:ipsec pluto not running centos 8 victoria wallaby Status in neutron: New Bug description: Hello. I apologize if I don't do things right to explain the bug. I am using Centos 8 and I install openstak with, kolla ansible. Whether it is Ussuri, Victoria or Wallaby, when establishing the connection between the 2 networks(with vpnaas), the error message is as follows: ipsec whack --status" (no "/run/pluto/pluto.ctl") The problem would be present with the Libreswan version 4.X which does not include the option "--use-netkey " used by the ipsec pluto command This option was present in Libreswan 3.X. So the command "ipsec pluto." failed , so no "/run/pluto/pluto.ctl". To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1938571/+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 1938569] [NEW] Typo in OVN SUPPORTED_DHCP_OPTS_MAPPING dictionary
Public bug reported:
SUPPORTED_DHCP_OPTS_MAPPING is a dictionary that maps neutron dhcp-
option names to ovn dhcp-option names. OVN dhcp-option ia_addr
corresponds with neutron dhcp-option names 'ia-addr' or '5'. However,
there is a type here and the corresponding OVN value is defined as
ip_addr instead of ia_addr [1]
Definition of ia_addr from OVN code: [2]
The following openstack command created a wrong entry in the OVN NBDB
DHCP_OPTIONS
$ openstack port create --network tempest-DHCPTest-980691237
--extra-dhcp-option name=ia-addr,value=2001::2001,ip-version=6 port-test-202
# ovn-nbctl list dhcp_options c9b0f6c0-c1bf-4e91-9e66-5e75491ae9e5
_uuid : c9b0f6c0-c1bf-4e91-9e66-5e75491ae9e5
cidr: "2001:db8::/64"
external_ids: {"neutron:revision_number"="0",
port_id="1188bca5-4b75-4810-a9a0-38ecc96d0274",
subnet_id="567272f0-f1b8-423c-a939-9dea6b5e26ab"}
options : {dhcpv6_stateless="true", ip_addr="2001::2001",
server_id="fa:16:3e:ce:f4:67"}
[1]
https://opendev.org/openstack/neutron/src/commit/19372a3cd8b4e6e45f707753b914e133857dd629/neutron/common/ovn/constants.py#L163
[2]
https://github.com/ovn-org/ovn/blob/1c9e46ab5c05043a8cd6c47b5fec2e1ac4c962db/lib/ovn-l7.h#L261
** Affects: neutron
Importance: Undecided
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/1938569
Title:
Typo in OVN SUPPORTED_DHCP_OPTS_MAPPING dictionary
Status in neutron:
In Progress
Bug description:
SUPPORTED_DHCP_OPTS_MAPPING is a dictionary that maps neutron dhcp-
option names to ovn dhcp-option names. OVN dhcp-option ia_addr
corresponds with neutron dhcp-option names 'ia-addr' or '5'. However,
there is a type here and the corresponding OVN value is defined as
ip_addr instead of ia_addr [1]
Definition of ia_addr from OVN code: [2]
The following openstack command created a wrong entry in the OVN NBDB
DHCP_OPTIONS
$ openstack port create --network tempest-DHCPTest-980691237
--extra-dhcp-option name=ia-addr,value=2001::2001,ip-version=6 port-test-202
# ovn-nbctl list dhcp_options c9b0f6c0-c1bf-4e91-9e66-5e75491ae9e5
_uuid : c9b0f6c0-c1bf-4e91-9e66-5e75491ae9e5
cidr: "2001:db8::/64"
external_ids: {"neutron:revision_number"="0",
port_id="1188bca5-4b75-4810-a9a0-38ecc96d0274",
subnet_id="567272f0-f1b8-423c-a939-9dea6b5e26ab"}
options : {dhcpv6_stateless="true", ip_addr="2001::2001",
server_id="fa:16:3e:ce:f4:67"}
[1]
https://opendev.org/openstack/neutron/src/commit/19372a3cd8b4e6e45f707753b914e133857dd629/neutron/common/ovn/constants.py#L163
[2]
https://github.com/ovn-org/ovn/blob/1c9e46ab5c05043a8cd6c47b5fec2e1ac4c962db/lib/ovn-l7.h#L261
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1938569/+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 1936278] Re: nova-manage placement audit command always fails with --resource_provider option
Reviewed: https://review.opendev.org/c/openstack/nova/+/800855 Committed: https://opendev.org/openstack/nova/commit/1d3373dcf0a05d4a2c5b51fc1b74d41ec1bb1175 Submitter: "Zuul (22348)" Branch:master commit 1d3373dcf0a05d4a2c5b51fc1b74d41ec1bb1175 Author: Takashi Kajinami Date: Thu Jul 15 11:25:15 2021 +0900 Fix request path to query a resource provider by uuid To query a resource provider by uuid, request path should look like /resource_providers?uuid= istead of /resource_providers&uuid= This change fixes the wrong path so that "nova-manage placement audit" command can look up the target resource provider properly. Closes-Bug: #1936278 Change-Id: I2ae7e9782316e3662e4e51e3f5ba0ef597bf281b ** 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/1936278 Title: nova-manage placement audit command always fails with --resource_provider option Status in OpenStack Compute (nova): Fix Released Bug description: Description === nova-mange placement audit command always fails if --resource_provider option is used because the target resource provider is not found ~~~ # nova-manage placement audit --resource_provider dbba1bf7-6e97-4dcb-8d4c-37fe36633358 --verbose Resource provider with UUID dbba1bf7-6e97-4dcb-8d4c-37fe36633358 does not exist. Error: non zero exit code: 127: OCI runtime error ~~~ However the resource provider record actually exists in Placement. ~~~ (overcloud) [stack@undercloud-0 ~]$ openstack resource provider list --uuid dbba1bf7-6e97-4dcb-8d4c-37fe36633358 --os-placement-api-version 1.14 +--+++--+--+ | uuid | name | generation | root_provider_uuid | parent_provider_uuid | +--+++--+--+ | dbba1bf7-6e97-4dcb-8d4c-37fe36633358 | compute-0.redhat.local | 28 | dbba1bf7-6e97-4dcb-8d4c-37fe36633358 | None | +--+++--+--+ ~~~ Looking at placement access log, the command is sending request with &uuid= instead of ?uuid= ~~~ 2021-07-15 02:02:28.101 24 INFO placement.requestlog [req-a9d4942e-411a-4901-b05e-98ec1239ef70 31e1d736a759444f92346daf932243ff 91063c94413548b695edc6a0ef1f1252 - default default] 172.17.1.24 "GET /placement/resource_providers&uuid=dbba1bf7-6e97-4dcb-8d4c-37fe36633358" status: 404 len: 162 microversion: 1.14 ~~~ Steps to reproduce == - Look up existing resource provider uuid $ openstack resource provider list - Run audit command with one of the ids specified $ nova-manage placement audit --resource_provider Expected result === The command succeeds without error Actual result = The command fails with the following error Resource provider with UUID does not exist. Environment === This issue was initially found in the following downstream bug. https://bugzilla.redhat.com/show_bug.cgi?id=1982485 Logs & Configs == N/A To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1936278/+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 1938120] Re: keystone-protection-functional is failing because of missing demo project
** No longer affects: keystone -- 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/1938120 Title: keystone-protection-functional is failing because of missing demo project Status in devstack: New Bug description: The keystone-protection-functional job is repeatedly failing because the demo project is not found. ``` + ./stack.sh:main:1294 : echo_summary 'Creating initial neutron network elements' + ./stack.sh:echo_summary:422 : [[ -t 3 ]] + ./stack.sh:echo_summary:428 : echo -e Creating initial neutron network elements + ./stack.sh:main:1297 : type -p neutron_plugin_create_initial_networks + ./stack.sh:main:1300 : create_neutron_initial_network + lib/neutron_plugins/services/l3:create_neutron_initial_network:164 : local project_id ++ lib/neutron_plugins/services/l3:create_neutron_initial_network:165 : grep ' demo ' ++ lib/neutron_plugins/services/l3:create_neutron_initial_network:165 : oscwrap project list ++ lib/neutron_plugins/services/l3:create_neutron_initial_network:165 : get_field 1 ++ functions-common:get_field:726 : local data field ++ functions-common:get_field:727 : read data ++ functions-common:oscwrap:2349: return 0 + lib/neutron_plugins/services/l3:create_neutron_initial_network:165 : project_id= + lib/neutron_plugins/services/l3:create_neutron_initial_network:166 : die_if_not_set 166 project_id 'Failure retrieving project_id for demo' + functions-common:die_if_not_set:216 : local exitcode=0 [Call Trace] ./stack.sh:1300:create_neutron_initial_network /opt/stack/devstack/lib/neutron_plugins/services/l3:166:die_if_not_set /opt/stack/devstack/functions-common:223:die [ERROR] /opt/stack/devstack/functions-common:166 Failure retrieving project_id for demo exit_trap: cleaning up child processes Error on exit *** FINISHED *** ``` Example can be found here; https://zuul.opendev.org/t/openstack/build/90628c08f0f84927a0e547e5c9fc409e To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1938120/+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 1885825] Re: No implicit user creation with GRANT syntax in MySQL 8.0 Ubuntu Focal
** Also affects: glance Importance: Undecided Status: New ** Also affects: glance/ussuri 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/1885825 Title: No implicit user creation with GRANT syntax in MySQL 8.0 Ubuntu Focal Status in coverage2sql: Fix Released Status in Glance: New Status in Glance ussuri series: New Status in OpenStack Identity (keystone): Fix Released Status in OpenStack Compute (nova): Fix Released Status in tacker: Fix Released Status in zaqar: Fix Released Bug description: Ubuntu Focal (20.04) has mysql 8.0 and with mysql 8.0 there is no implicit user creation with GRANT syntax. In Ubuntu Bionic (18.04) mysql 5.7 version used to create the user implicitly when using using the GRANT. But starting with mysql 8.0, we need to create the user explicitly before using the GRANT command. Nova unit and functional tests job using tools/test-setup.sh script start failing when running on Ubuntu Focal https://zuul.opendev.org/t/openstack/build/8b0f4fcc21854655a638c413b6fe1a91 + sudo -H mysql -u root -pinsecure_slave -h localhost -e ' DELETE FROM mysql.user WHERE User='\'''\''; FLUSH PRIVILEGES; GRANT ALL PRIVILEGES ON *.* TO '\''openstack_citest'\''@'\''%'\'' identified by '\''openstack_citest'\'' WITH GRANT OPTION;' mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 1064 (42000) at line 4: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'identified by 'openstack_citest' WITH GRANT OPTION' at line 2 we need to modify the tools/test-setup.sh to create user first. Below used to work with mysql 5.7 GRANT ALL PRIVILEGES ON *.* TO '$DB_USER'@'%' identified by '$DB_PW' WITH GRANT OPTION;" With mysql 8.0 we need to create user first CREATE USER '$DB_USER'@'%' IDENTIFIED BY '$DB_PW'; GRANT ALL PRIVILEGES ON *.* TO '$DB_USER'@'%' WITH GRANT OPTION;" To manage notifications about this bug go to: https://bugs.launchpad.net/coverage2sql/+bug/1885825/+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
