Implement CREATE/UPDATE operation on Placement traits - #3668

coverage: 63.898% (+63.9%) from 0.0%
when pulling 5c4a59a on Etua:add-trait-create-operation
into 8dfa2dc on gophercloud:main.

It looks like we're also getting a 502 for one of the test while we're expecting a 204:

"Expected HTTP response code [201 204] when accessing [PUT http://10.1.1.115/placement/traits/CUSTOM_WY5WWFUO], but got 502 instead: <!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>502 Bad Gateway</title>\n</head><body>\n<h1>Bad Gateway</h1>\n<p>The proxy server received an invalid\r\nresponse from an upstream server.<br />\r\n</p>\n<p>Additionally, a 204 No Content\nerror was encountered while trying to use an ErrorDocument to handle the request.</p>\n<hr>\n<address>Apache/2.4.58 (Ubuntu) Server at 10.1.1.115 Port 80</address>\n</body></html>"

https://github.com/gophercloud/gophercloud/actions/runs/23653607837/job/68904732561?pr=3668#step:7:1234

That test seemed like a fluke not directly related to the implemented functionality. It didn't occur to me on my infrastructure and here the status changed after recheck on committing a change to some comment.

That test seemed like a fluke not directly related to the implemented functionality. It didn't occur to me on my infrastructure and here the status changed after recheck on committing a change to some comment.

The same test, failed in the DELETE PR as well, also against epoxy. I see you rebase and it re-run the tests and this time it worked, but perhaps it would be good to investigate if there's not something weird going on, if we can pin point what the exact issue was.

Failed to backport PR to v2 branch. See logs for details.