Bug 1919884 - ping loss during minor update OSP16.1
Summary: ping loss during minor update OSP16.1
Keywords:
Status: CLOSED DUPLICATE of bug 1895220
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Terry Wilson
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-25 11:22 UTC by Eran Kuris
Modified: 2021-01-27 15:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-27 15:54:02 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Eran Kuris 2021-01-25 11:22:39 UTC 
Description of problem:
overcloud minor update is failing due to ping loss  
TASK [tripleo-upgrade : stop l3 agent connectivity check] **********************
task path: /home/rhos-ci/jenkins/workspace/DFG-network-networking-ovn-update-16.1_director-rhel-virthost-3cont_2comp_2net-ipv4-geneve-composable/infrared/plugins/tripleo-upgrade/infrared_plugin/roles/tripleo-upgrade/tasks/common/l3_agent_connectivity_check_stop_script.yml:2
Thursday 21 January 2021  21:20:57 +0000 (0:11:07.119)       1:48:11.214 ****** 
fatal: [undercloud-0]: FAILED! => {
    "changed": true,
    "cmd": "source /home/stack/overcloudrc\n/home/stack/l3_agent_stop_ping.sh 0\n",
    "delta": "0:00:00.068637",
    "end": "2021-01-21 21:20:57.463918",
    "rc": 1,
    "start": "2021-01-21 21:20:57.395281"
}

STDOUT:

656 packets transmitted, 655 received, 0.152439% packet loss, time 1005ms
rtt min/avg/max/mdev = 0.458/1.711/166.534/10.532 ms
Ping loss higher than 0 seconds detected (1 seconds)


MSG:

Version-Release number of selected component (if applicable):
Update from core_puddle: RHOS-16.1-RHEL-8-20201214.n.3  to
core_puddle: RHOS-16.1-RHEL-8-20210120.n.

How reproducible:


Steps to Reproduce:
1. run our CI job
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Jakub Libosvar 2021-01-27 15:54:02 UTC 
This seems to be caused by not updating ovn-controllers on Compute nodes first before running the update as KB article suggests: https://access.redhat.com/solutions/5580961

I'm closing this as a duplicate of bug 1895220 as this is a known limitation of OVN.

*** This bug has been marked as a duplicate of bug 1895220 ***
Note You need to log in before you can comment on or make changes to this bug.