Thursday, 2023-01-05

abdiis anyone running into 404 resource not found errors for various tempest tests?  I am using the master branch.  For example, the following test: tempest.scenario.test_stamp_pattern.TestStampPattern.test_stamp_pattern invokes "POST http://15.113.218.73:9696/networking/v2.0/security-groups" to create a security group but fails with a 404 error:  {"NeutronError": {"type": "HTTPNotFound", "message": "The resource could not be 00:24
abdifound.", "detail": ""}}00:24
abdiI’ve root caused the issue above.  You can ignore the question.  Thanks.03:02
gmannk04:02
*** pojadhav is now known as pojadhav|ruck04:36
*** tkajinam is now known as Guest29904:46
*** soniya29 is now known as soniya29|lunch07:30
*** soniya29|lunch is now known as soniya2908:14
opendevreviewMerged openstack/tempest master: Add release notes page for version 33.0.0  https://review.opendev.org/c/openstack/tempest/+/86854309:24
opendevreviewMerged openstack/tempest master: Remove references to 'all-plugin' tox environment  https://review.opendev.org/c/openstack/tempest/+/86071910:33
opendevreviewMerged openstack/tempest master: zuul: Increase timeout for c9s-fips job  https://review.opendev.org/c/openstack/tempest/+/86604913:44
*** soniya29 is now known as soniya29|out16:08
*** pojadhav|ruck is now known as pojadhav|out16:13
opendevreviewGhanshyam Mann proposed openstack/tempest master: DNM: tetsing tox  https://review.opendev.org/c/openstack/tempest/+/86940420:34
abdiI am consistently seeing this AMQP server unreachable error right after a volume attachment request during the tempest test: cinder_tempest_plugin.scenario.test_volume_multiattach.VolumeMultiattachTests.test_multiattach_data_integrity.  23:18
abdiJan 05 02:22:43 devstack@n-api.service[2190307]: POST /compute/v2.1/servers/53da3852-4a03-42cb-937e-10929b6892d5/os-volume_attachments => generated 194 bytes in 391 msecs23:18
abdiJan 05 02:40:36 devstack@n-api.service[2190308]: ERROR oslo.messaging._drivers.impl_rabbit [-] [1849e160-fcc5-4c72-a8e0-664530f0e6c0] AMQP server on 15.113.218.73:5672 is unreachable: [Errno 104] Connection reset by peer. Trying again in 1 seconds.: ConnectionResetError.23:18
abdiThe resulting failure is that the volume never attaches (transition from "Reserved" to "In Use" and goes back to "Available" status), which causes the test failure.  I am investigating whether the oslo AMQP error is the culprit of or resulting from the volume attachment issue.  The 18mins gap in the timestamp is leading me to believe the events are related.23:18
abdiI have combed nova, tempest, and cinder logs.  I am looking for guidance as to what other logs could provide insights.  Thanks ahead.23:18
abdiI should note that I am using the master devstack branch23:25
clarkbconnection reset by peer implicates the other side of the connection (the amqp server) I would look at the logs for rabbit23:28
abdiThank you clarkb.  23:33

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!