[Yahoo-eng-team] [Bug 1761140] Re: dpkg eror processing package nova-compute
Hi, Corey! Thank you for respond. I'd replaced local repositories with official cloud-archive you provided, but the result is still the same... Log is attached. ** Attachment added: "apt_install_nova-compute.log" https://bugs.launchpad.net/nova/+bug/1761140/+attachment/5157041/+files/apt_install_nova-compute.log ** Changed in: nova (Ubuntu) Status: Invalid => 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/1761140 Title: dpkg eror processing package nova-compute Status in OpenStack Compute (nova): Invalid Status in nova package in Ubuntu: New Bug description: Hello! I've encountered the bug while installing Nova on compute nodes: ... Setting up qemu-system-x86 (1:2.11+dfsg-1ubuntu5~cloud0) ... Setting up qemu-kvm (1:2.11+dfsg-1ubuntu5~cloud0) ... Setting up qemu-utils (1:2.11+dfsg-1ubuntu5~cloud0) ... Setting up python-keystone (2:13.0.0-0ubuntu1~cloud0) ... Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-116-generic Setting up nova-compute-libvirt (2:17.0.1-0ubuntu1~cloud0) ... adduser: The user `nova' does not exist. dpkg: error processing package nova-compute-libvirt (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of nova-compute-kvm: nova-compute-kvm depends on nova-compute-libvirt (= 2:17.0.1-0ubuntu1~cloud0); however: Package nova-compute-libvirt is not configured yet. dpkg: error processing package nova-compute-kvm (--configure): dependency problems - leaving unconfigured Setting up python-os-brick (2.3.0-0ubuntu1~cloud0) ... No apport report written because the error message indicates its a followup error from a previous failure. Setting up python-nova (2:17.0.1-0ubuntu1~cloud0) ... Setting up nova-common (2:17.0.1-0ubuntu1~cloud0) ... Setting up nova-compute (2:17.0.1-0ubuntu1~cloud0) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for systemd (229-4ubuntu21.2) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Errors were encountered while processing: nova-compute-libvirt nova-compute-kvm ... Installation failed when executing 'post-installation script'. After some investigation I've found out that if I've create 'nova' user BEFORE running package installation, it's will be succeded. Steps to reproduce -- 1. Prepare the node for installing nova-compute packages 2. Run 'apt-get install nova-compute' Expected result -- Nova-compute installed successfully without errors Actual result -- Installation failed with dpkg error Workaround -- 1. Create system user: add to /etc/passwd nova:x:64060:64060::/var/lib/nova:/bin/false 2. Create system group: add to /etc/group nova:x:64060: 3. Run 'apt-get install nova-compute' My Environment -- Ubuntu 16.04.4 LTS, 4.4.0-116-generic Openstack Queens Release Nova 17.0.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1761140/+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 1761140] Re: dpkg eror processing package nova-compute
** Also affects: nova (Ubuntu) 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/1761140 Title: dpkg eror processing package nova-compute Status in OpenStack Compute (nova): Invalid Status in nova package in Ubuntu: New Bug description: Hello! I've encountered the bug while installing Nova on compute nodes: ... Setting up qemu-system-x86 (1:2.11+dfsg-1ubuntu5~cloud0) ... Setting up qemu-kvm (1:2.11+dfsg-1ubuntu5~cloud0) ... Setting up qemu-utils (1:2.11+dfsg-1ubuntu5~cloud0) ... Setting up python-keystone (2:13.0.0-0ubuntu1~cloud0) ... Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-116-generic Setting up nova-compute-libvirt (2:17.0.1-0ubuntu1~cloud0) ... adduser: The user `nova' does not exist. dpkg: error processing package nova-compute-libvirt (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of nova-compute-kvm: nova-compute-kvm depends on nova-compute-libvirt (= 2:17.0.1-0ubuntu1~cloud0); however: Package nova-compute-libvirt is not configured yet. dpkg: error processing package nova-compute-kvm (--configure): dependency problems - leaving unconfigured Setting up python-os-brick (2.3.0-0ubuntu1~cloud0) ... No apport report written because the error message indicates its a followup error from a previous failure. Setting up python-nova (2:17.0.1-0ubuntu1~cloud0) ... Setting up nova-common (2:17.0.1-0ubuntu1~cloud0) ... Setting up nova-compute (2:17.0.1-0ubuntu1~cloud0) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for systemd (229-4ubuntu21.2) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Errors were encountered while processing: nova-compute-libvirt nova-compute-kvm ... Installation failed when executing 'post-installation script'. After some investigation I've found out that if I've create 'nova' user BEFORE running package installation, it's will be succeded. Steps to reproduce -- 1. Prepare the node for installing nova-compute packages 2. Run 'apt-get install nova-compute' Expected result -- Nova-compute installed successfully without errors Actual result -- Installation failed with dpkg error Workaround -- 1. Create system user: add to /etc/passwd nova:x:64060:64060::/var/lib/nova:/bin/false 2. Create system group: add to /etc/group nova:x:64060: 3. Run 'apt-get install nova-compute' My Environment -- Ubuntu 16.04.4 LTS, 4.4.0-116-generic Openstack Queens Release Nova 17.0.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1761140/+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 1761140] [NEW] dpkg eror processing package nova-compute
Public bug reported: Hello! I've encountered the bug while installing Nova on compute nodes: ... Setting up qemu-system-x86 (1:2.11+dfsg-1ubuntu5~cloud0) ... Setting up qemu-kvm (1:2.11+dfsg-1ubuntu5~cloud0) ... Setting up qemu-utils (1:2.11+dfsg-1ubuntu5~cloud0) ... Setting up python-keystone (2:13.0.0-0ubuntu1~cloud0) ... Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-116-generic Setting up nova-compute-libvirt (2:17.0.1-0ubuntu1~cloud0) ... adduser: The user `nova' does not exist. dpkg: error processing package nova-compute-libvirt (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of nova-compute-kvm: nova-compute-kvm depends on nova-compute-libvirt (= 2:17.0.1-0ubuntu1~cloud0); however: Package nova-compute-libvirt is not configured yet. dpkg: error processing package nova-compute-kvm (--configure): dependency problems - leaving unconfigured Setting up python-os-brick (2.3.0-0ubuntu1~cloud0) ... No apport report written because the error message indicates its a followup error from a previous failure. Setting up python-nova (2:17.0.1-0ubuntu1~cloud0) ... Setting up nova-common (2:17.0.1-0ubuntu1~cloud0) ... Setting up nova-compute (2:17.0.1-0ubuntu1~cloud0) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for systemd (229-4ubuntu21.2) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Errors were encountered while processing: nova-compute-libvirt nova-compute-kvm ... Installation failed when executing 'post-installation script'. After some investigation I've found out that if I've create 'nova' user BEFORE running package installation, it's will be succeded. Steps to reproduce -- 1. Prepare the node for installing nova-compute packages 2. Run 'apt-get install nova-compute' Expected result -- Nova-compute installed successfully without errors Actual result -- Installation failed with dpkg error Workaround -- 1. Create system user: add to /etc/passwd nova:x:64060:64060::/var/lib/nova:/bin/false 2. Create system group: add to /etc/group nova:x:64060: 3. Run 'apt-get install nova-compute' My Environment -- Ubuntu 16.04.4 LTS, 4.4.0-116-generic Openstack Queens Release Nova 17.0.1-0ubuntu1 ** Affects: nova 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/1761140 Title: dpkg eror processing package nova-compute Status in OpenStack Compute (nova): New Bug description: Hello! I've encountered the bug while installing Nova on compute nodes: ... Setting up qemu-system-x86 (1:2.11+dfsg-1ubuntu5~cloud0) ... Setting up qemu-kvm (1:2.11+dfsg-1ubuntu5~cloud0) ... Setting up qemu-utils (1:2.11+dfsg-1ubuntu5~cloud0) ... Setting up python-keystone (2:13.0.0-0ubuntu1~cloud0) ... Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-116-generic Setting up nova-compute-libvirt (2:17.0.1-0ubuntu1~cloud0) ... adduser: The user `nova' does not exist. dpkg: error processing package nova-compute-libvirt (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of nova-compute-kvm: nova-compute-kvm depends on nova-compute-libvirt (= 2:17.0.1-0ubuntu1~cloud0); however: Package nova-compute-libvirt is not configured yet. dpkg: error processing package nova-compute-kvm (--configure): dependency problems - leaving unconfigured Setting up python-os-brick (2.3.0-0ubuntu1~cloud0) ... No apport report written because the error message indicates its a followup error from a previous failure. Setting up python-nova (2:17.0.1-0ubuntu1~cloud0) ... Setting up nova-common (2:17.0.1-0ubuntu1~cloud0) ... Setting up nova-compute (2:17.0.1-0ubuntu1~cloud0) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for systemd (229-4ubuntu21.2) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Errors were encountered while processing: nova-compute-libvirt nova-compute-kvm ... Installation failed when executing 'post-installation script'. After some investigation I've found out that if I've create 'nova' user BEFORE running package installation, it's will be succeded. Steps to reproduce -- 1. Prepare the node for installing nova-compute packages 2. Run 'apt-get install nova-compute' Expected result -- Nova-compute installed successfully without errors Actual result
[Yahoo-eng-team] [Bug 1761150] [NEW] service fails when deprecated 'os_region_name' is not configured in [placement]
Public bug reported: Hello! I've encountered the bug when configuring nova-compute service on new node: ... 2018-04-04 14:55:42.082 41113 INFO nova.service [req-be886a45-032a-441b-8934-0d586d159edb - - - - -] Starting compute node (version 17.0.1) 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service [req-be886a45-032a-441b-8934-0d586d159edb - - - - -] Error starting thread.: PlacementNotConfigured: This compute is not configured to talk to the placement service. Configure the [placement] section of nova.conf and restart the service. 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service Traceback (most recent call last): 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 729, in run_service 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service service.start() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/nova/service.py", line 161, in start 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service self.manager.init_host() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1137, in init_host 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service raise exception.PlacementNotConfigured() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service PlacementNotConfigured: This compute is not configured to talk to the placement service. Configure the [placement] section of nova.conf and restart the service. ... Steps to reproduce -- 1. Install and configure nova on controller node, make sure that all nova services are running correctly 2. Configure nova on compute node: follow Queens Series Release Notes (https://docs.openstack.org/releasenotes/nova/queens.html), in [placement] comment out deprecated 'os_region_name' and configure 'region_name' 3. Restart nova-compute service Expected result -- Nova-compute service started and running without errors Actual result -- Nova-compute service failed with PlacementNotConfigured error Workaround -- 1. Comment out 'region_name' in [placement] and configure deprecated 'os_region_name': [placement] os_region_name = RegionOne auth_type = password auth_url = project_name = service project_domain_name = default username = placement user_domain_name = default password = #region_name = RegionOne 2. Restart nova-compute service, сheck your log ... 2018-04-04 15:08:59.684 41544 INFO nova.compute.resource_tracker [req-58502787-deca-4c5a-b4b9-8c9f59531720 - - - - -] Compute node record created for compute01-api:compute01.demo.infra.cloud.loc with uuid: d2d36c03-e597-4831-84f6-03c78f331354 2018-04-04 15:09:07.380 41544 INFO nova.scheduler.client.report [req-58502787-deca-4c5a-b4b9-8c9f59531720 - - - - -] [req-9a468e08-7eaa-4f91-a8d9-dca8bbad3b8f] Created resource provider record via placement API for resource provider with UUID d2d36c03-e597-4831-84f6-03c78f331354 and name compute01.demo.infra.cloud.loc. 2018-04-04 15:09:15.774 41544 INFO nova.compute.resource_tracker [req-58502787-deca-4c5a-b4b9-8c9f59531720 - - - - -] Final resource view: name=compute01.demo.infra.cloud.loc phys_ram=257004MB used_ram=512MB phys_disk=243174GB used_disk=0GB total_vcpus=48 used_vcpus=0 pci_stats=[] ... My Environment -- Ubuntu 16.04.4 LTS, 4.4.0-116-generic Openstack Queens Release Nova 17.0.1-0ubuntu1 ** Affects: nova Importance: Undecided Status: New ** Attachment added: "nova-compute_ERROR.conf" https://bugs.launchpad.net/bugs/1761150/+attachment/5101246/+files/nova-compute_ERROR.conf ** Attachment removed: "nova-compute_ERROR.conf" https://bugs.launchpad.net/nova/+bug/1761150/+attachment/5101246/+files/nova-compute_ERROR.conf ** Description changed: Hello! I've encountered the bug when configuring nova-compute service on new node: ... 2018-04-04 14:55:42.082 41113 INFO nova.service [req-be886a45-032a-441b-8934-0d586d159edb - - - - -] Starting compute node (version 17.0.1) 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service [req-be886a45-032a-441b-8934-0d586d159edb - - - - -] Error starting thread.: PlacementNotConfigured: This compute is not configured to talk to the placement service. Configure the [placement] section of nova.conf and restart the service. 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service Traceback (most recent call last): 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 729, in run_service 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service service.start() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/nova/service.py", line 161, in start 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service
[Yahoo-eng-team] [Bug 1761185] [NEW] Value errors when configuring 'enabled_import_methods' option
Public bug reported: Hello! I've encountered the bug when configuring glance-api on controller node: ... 2018-04-04 15:51:07.773 21186 CRITICAL glance [-] Unhandled error: ValueError: tuple.index(x): x not in tuple 2018-04-04 15:51:07.773 21186 ERROR glance Traceback (most recent call last): 2018-04-04 15:51:07.773 21186 ERROR glance File "/usr/bin/glance-api", line 10, in 2018-04-04 15:51:07.773 21186 ERROR glance sys.exit(main()) 2018-04-04 15:51:07.773 21186 ERROR glance File "/usr/lib/python2.7/dist-packages/glance/cmd/api.py", line 97, in main 2018-04-04 15:51:07.773 21186 ERROR glance fail(e) 2018-04-04 15:51:07.773 21186 ERROR glance File "/usr/lib/python2.7/dist-packages/glance/cmd/api.py", line 71, in fail 2018-04-04 15:51:07.773 21186 ERROR glance return_code = KNOWN_EXCEPTIONS.index(type(e)) + 1 2018-04-04 15:51:07.773 21186 ERROR glance ValueError: tuple.index(x): x not in tuple ... Imagine, I don't need to enable web-download method by default, so I've try to configure 'enabled_import_methods' option in [DEFAULT] section. Steps to reproduce -- 1. Install glance-api on controller node 2. Configure glance-api: [DEFAULT] enabled_import_methods = glance-direct 3. Restart glance-api service Expected result -- Glance-api service started and running without errors Actual result -- Glance-api service failed with 'Unhandled error: ValueError' Workaround -- 1. Patching glance/cmd/api.py as described here: https://review.openstack.org/#/c/514114/1/glance/cmd/api.py 2. Restart glance-api, check service status: ... glance-api[26538]: ERROR: Value for option enabled_import_methods is not valid: Value should start with "[" systemd[1]: glance-api.service: Main process exited, code=exited, status=4/NOPERMISSION systemd[1]: glance-api.service: Unit entered failed state. systemd[1]: glance-api.service: Failed with result 'exit-code'. ... 3. Configure glance-api as follows: [DEFAULT] enabled_import_methods = [glance-direct] 4. Restart glance-api again. It's finally working My Environment -- Ubuntu 16.04.4 LTS, 4.4.0-116-generic Openstack Queens Release Glance 16.0.0-0ubuntu1 ** 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/1761185 Title: Value errors when configuring 'enabled_import_methods' option Status in Glance: New Bug description: Hello! I've encountered the bug when configuring glance-api on controller node: ... 2018-04-04 15:51:07.773 21186 CRITICAL glance [-] Unhandled error: ValueError: tuple.index(x): x not in tuple 2018-04-04 15:51:07.773 21186 ERROR glance Traceback (most recent call last): 2018-04-04 15:51:07.773 21186 ERROR glance File "/usr/bin/glance-api", line 10, in 2018-04-04 15:51:07.773 21186 ERROR glance sys.exit(main()) 2018-04-04 15:51:07.773 21186 ERROR glance File "/usr/lib/python2.7/dist-packages/glance/cmd/api.py", line 97, in main 2018-04-04 15:51:07.773 21186 ERROR glance fail(e) 2018-04-04 15:51:07.773 21186 ERROR glance File "/usr/lib/python2.7/dist-packages/glance/cmd/api.py", line 71, in fail 2018-04-04 15:51:07.773 21186 ERROR glance return_code = KNOWN_EXCEPTIONS.index(type(e)) + 1 2018-04-04 15:51:07.773 21186 ERROR glance ValueError: tuple.index(x): x not in tuple ... Imagine, I don't need to enable web-download method by default, so I've try to configure 'enabled_import_methods' option in [DEFAULT] section. Steps to reproduce -- 1. Install glance-api on controller node 2. Configure glance-api: [DEFAULT] enabled_import_methods = glance-direct 3. Restart glance-api service Expected result -- Glance-api service started and running without errors Actual result -- Glance-api service failed with 'Unhandled error: ValueError' Workaround -- 1. Patching glance/cmd/api.py as described here: https://review.openstack.org/#/c/514114/1/glance/cmd/api.py 2. Restart glance-api, check service status: ... glance-api[26538]: ERROR: Value for option enabled_import_methods is not valid: Value should start with "[" systemd[1]: glance-api.service: Main process exited, code=exited, status=4/NOPERMISSION systemd[1]: glance-api.service: Unit entered failed state. systemd[1]: glance-api.service: Failed with result 'exit-code'. ... 3. Configure glance-api as follows: [DEFAULT] enabled_import_methods = [glance-direct] 4. Restart glance-api again. It's finally working My Environment -- Ubuntu 16.04.4 LTS, 4.4.0-116-generic Openstack Queens Release Glance 16.0.0-0ubuntu1 To manage notifications about this bug go to:
[Yahoo-eng-team] [Bug 1763146] [NEW] [ovs] Binding failed for port
Public bug reported: Hello! I've already had successful deployment on Pike (3 control node + several compute nodes): - ML2 plugin - openvswitch - default tunnel type - vxlan - dvr is enabled Instances were started, running, migrating without errors. Everything was fine until I've upgraded to Queens... I've use same neutron configuration files and encountered the following error: ... 2018-04-11 12:21:19.128 36774 INFO neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_bridge [-] Bridge br-int has datapath-ID 5618b7026f46 2018-04-11 12:21:23.460 36774 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-ac08fa6c-7257-4296-aede-67a051568440 - - - - -] Mapping physical network external to bridge br0 2018-04-11 12:21:23.948 36774 INFO neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_bridge [req-ac08fa6c-7257-4296-aede-67a051568440 - - - - -] Bridge br0 has datapath-ID ec0d9a7abceb 2018-04-11 12:21:24.206 36774 INFO neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_bridge [req-ac08fa6c-7257-4296-aede-67a051568440 - - - - -] Bridge br-tun has datapath-ID d2588392e746 2018-04-11 12:21:24.220 36774 INFO neutron.agent.agent_extensions_manager [req-ac08fa6c-7257-4296-aede-67a051568440 - - - - -] Initializing agent extension 'qos' 2018-04-11 12:21:24.323 36774 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_dvr_neutron_agent [req-ac08fa6c-7257-4296-aede-67a051568440 - - - - -] L2 Agent operating in DVR Mode with MAC FA-16-3F-7C-00-B2 2018-04-11 12:21:24.375 36774 INFO neutron.common.ipv6_utils [req-ac08fa6c-7257-4296-aede-67a051568440 - - - - -] IPv6 not present or configured not to bind to new interfaces on this system. Please ensure IPv6 is enabled and /proc/sys/net/ipv6/conf/default/disable_ipv6 is set to 0 to enable IPv6. 2018-04-11 12:21:25.275 36774 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-1c05ff93-84cb-45ed-937c-95f048b553f1 - - - - -] Agent initialized successfully, now running... ... 2018-04-11 21:24:10.248 3953 INFO neutron.agent.common.ovs_lib [req-64bf5e4c-32a9-4936-93cd-2658095b2d35 - - - - -] Port b8b42046-14ba-4b43-a24c-3a0a1b350aea not present in bridge br-int 2018-04-11 21:24:10.249 3953 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-64bf5e4c-32a9-4936-93cd-2658095b2d35 - - - - -] port_unbound(): net_uuid None not managed by VLAN manager 2018-04-11 21:24:10.249 3953 INFO neutron.agent.securitygroups_rpc [req-64bf5e4c-32a9-4936-93cd-2658095b2d35 - - - - -] Remove device filter for ['b8b42046-14ba-4b43-a24c-3a0a1b350aea'] ... It happens every time I try to launch instance. No matter, internal or external (vlan provider) network, result is the same. So my question is 'What I'm doing wrong?' May be I missed something in Queens config samples, or encountered the huge bug, or what?.. Pike Environment -- Ubuntu 16.04.4 LTS, 4.4.0-119-generic Neutron 11.0.3-0ubuntu1.1~cloud0 openvswitch-switch 2.8.1 Queens Environment -- Ubuntu 16.04.4 LTS, 4.4.0-119-generic Neutron 12.0.0-0ubuntu2~cloud0 openvswitch-switch 2.9.0 ** 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/1763146 Title: [ovs] Binding failed for port Status in neutron: New Bug description: Hello! I've already had successful deployment on Pike (3 control node + several compute nodes): - ML2 plugin - openvswitch - default tunnel type - vxlan - dvr is enabled Instances were started, running, migrating without errors. Everything was fine until I've upgraded to Queens... I've use same neutron configuration files and encountered the following error: ... 2018-04-11 12:21:19.128 36774 INFO neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_bridge [-] Bridge br-int has datapath-ID 5618b7026f46 2018-04-11 12:21:23.460 36774 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-ac08fa6c-7257-4296-aede-67a051568440 - - - - -] Mapping physical network external to bridge br0 2018-04-11 12:21:23.948 36774 INFO neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_bridge [req-ac08fa6c-7257-4296-aede-67a051568440 - - - - -] Bridge br0 has datapath-ID ec0d9a7abceb 2018-04-11 12:21:24.206 36774 INFO neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_bridge [req-ac08fa6c-7257-4296-aede-67a051568440 - - - - -] Bridge br-tun has datapath-ID d2588392e746 2018-04-11 12:21:24.220 36774 INFO neutron.agent.agent_extensions_manager [req-ac08fa6c-7257-4296-aede-67a051568440 - - - - -] Initializing agent extension 'qos' 2018-04-11 12:21:24.323 36774 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_dvr_neutron_agent
[Yahoo-eng-team] [Bug 1793244] [NEW] Egress UDP traffic is dropped
Public bug reported: Hello! I've encountered the error while becnhmarking UDP traffic between two instances. Any help would be apreciated. I've got two instances (test1: 172.31.200.232, test2: 172.31.200.234) located in one external network on separate compute nodes. Testing via iperf3 brought me to fail: root@test1:~# iperf3 -s root@test2:~# iperf3 -c 172.31.200.234 -u Connecting to host 172.31.200.234, port 5201 iperf3: error - unable to read from stream socket: Resource temporarily unavailable While, when I put together these instances on the same compute node, everything is fine: root@test1:~# iperf3 -s root@test2:~# iperf3 -c 172.31.200.234 -u Connecting to host 172.31.200.234, port 5201 [ 4] local 172.31.200.232 port 57176 connected to 172.31.200.234 port 5201 [ ID] Interval Transfer Bandwidth Total Datagrams [ 4] 0.00-1.00 sec 120 KBytes 983 Kbits/sec 15 [ 4] 1.00-2.00 sec 128 KBytes 1.05 Mbits/sec 16 [ 4] 2.00-3.00 sec 128 KBytes 1.05 Mbits/sec 16 [ 4] 3.00-3.22 sec 40.0 KBytes 1.46 Mbits/sec 5 My security groups allow UDP and TCP traffic. Openstack Queens, openvswitch v.2.9 Firewall_driver is 'openvswitch', can it be the cause? Thanks, Annie ** 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/1793244 Title: Egress UDP traffic is dropped Status in neutron: New Bug description: Hello! I've encountered the error while becnhmarking UDP traffic between two instances. Any help would be apreciated. I've got two instances (test1: 172.31.200.232, test2: 172.31.200.234) located in one external network on separate compute nodes. Testing via iperf3 brought me to fail: root@test1:~# iperf3 -s root@test2:~# iperf3 -c 172.31.200.234 -u Connecting to host 172.31.200.234, port 5201 iperf3: error - unable to read from stream socket: Resource temporarily unavailable While, when I put together these instances on the same compute node, everything is fine: root@test1:~# iperf3 -s root@test2:~# iperf3 -c 172.31.200.234 -u Connecting to host 172.31.200.234, port 5201 [ 4] local 172.31.200.232 port 57176 connected to 172.31.200.234 port 5201 [ ID] Interval Transfer Bandwidth Total Datagrams [ 4] 0.00-1.00 sec 120 KBytes 983 Kbits/sec 15 [ 4] 1.00-2.00 sec 128 KBytes 1.05 Mbits/sec 16 [ 4] 2.00-3.00 sec 128 KBytes 1.05 Mbits/sec 16 [ 4] 3.00-3.22 sec 40.0 KBytes 1.46 Mbits/sec 5 My security groups allow UDP and TCP traffic. Openstack Queens, openvswitch v.2.9 Firewall_driver is 'openvswitch', can it be the cause? Thanks, Annie To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1793244/+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
