Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2151335

Summary: openstack port delete is failing with httpException: 504 Gateway Time-out
Product: Red Hat OpenStack Reporter: Jason Paroly <jparoly>
Component: openstack-ironicAssignee: Luca Miccini <lmiccini>
Status: CLOSED DUPLICATE QA Contact: Jason Paroly <jparoly>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17.1 (Wallaby)CC: lmiccini, sbaker
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-19 20:50:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jason Paroly 2022-12-06 18:57:19 UTC
Description of problem:
Network attach detach script is failing during regression testing with "Failed to delete port with name or ID 'edd7e958-9b51-44f2-b6eb-facc985b5d15': HttpException: 504: Server Error for url: https://10.0.0.135:13696/v2.0/ports/edd7e958-9b51-44f2-b6eb-facc985b5d15, The server didn't respond in time.: 504 Gateway Time-out"

Version-Release number of selected component (if applicable):


How reproducible:
everytime with script posted below

Steps to Reproduce:
1. run ironic-network-attach-detach job and/or script which includes running 'openstack port delete ...'
2.
3.

Actual results:
port delete failed

Expected results:
port delete succeeds

Additional info:

script: 

#!/bin/bash

# There should be only one running nova istance at this point
source /home/stack/overcloudrc
IRONIC_NODE=`openstack baremetal node list -f value|awk '/active/ {print $1}'`
NEWIP=192.168.24.24
# Display list
openstack baremetal node list
IRONIC_NODE_VIF_ID=$(openstack baremetal node vif list $IRONIC_NODE -f value|head -1)
NOVA_INSTANCE_NAME=$(openstack server list -f value |awk '/ACTIVE/ {print $1}')
openstack port delete $IRONIC_NODE_VIF_ID
sleep 30
openstack port create --network baremetal --fixed-ip ip-address=$NEWIP $IRONIC_NODE-extra
sleep 300
openstack server add port $NOVA_INSTANCE_NAME "$IRONIC_NODE-extra"
sleep 120

# reboot instance to get network refresh
openstack server reboot $NOVA_INSTANCE_NAME
sleep 300
openstack server list -c Name -c Status | grep $NOVA_INSTANCE_NAME

ssh -q -o strictHostKeyChecking=no cloud-user@$NEWIP "echo success"

if [ "$?" = "0" ]; then
    echo -e "\tSSH cloud-user@$NEWIP is successful"
else
    echo -e "\tSSH cloud-user@$NEWIP FAILED!"
    sleep 2
    exit 1
fi

log and job to follow

blocks a regression job

Comment 10 Steve Baker 2022-12-19 20:50:59 UTC
Considering the logs have disk IO errors, this is likely caused by the thin pool metadata volume filling up, which is being tracked by bug #2149586

*** This bug has been marked as a duplicate of bug 2149586 ***