Bug 2151335 - openstack port delete is failing with httpException: 504 Gateway Time-out
Summary: openstack port delete is failing with httpException: 504 Gateway Time-out
Keywords:
Status: CLOSED DUPLICATE of bug 2149586
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Luca Miccini
QA Contact: Jason Paroly
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-06 18:57 UTC by Jason Paroly
Modified: 2022-12-19 20:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-19 20:50:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-20746 0 None None None 2022-12-06 18:58:45 UTC

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 ***


Note You need to log in before you can comment on or make changes to this bug.