-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deleting account returns error, after receiving status code 204 #18
Comments
It needs to change the way to match the ID by the redfish API first and then delete the account. This test case needs to change in this way to do it. |
The HTTP status code 204 means "No Content". Did you make sure you created an account before you delete it? Otherwise, you will see the 204 status code returned. |
In this case, after deleting an account, BMC simulator returns 204 No Content (according to Redfish Specification the status coded 204 should be accepted for deletion). DeviceMgr accepts only code 200 for the deletion (as in the following code from accountService.go):
|
@ehaligow Yes, you could add those conditions of the HTTP status code (202 and 204) to this function. |
Added status No content as accepted response for deleting Account (fix for Issue #18)
Deleting account returns error, after receiving status code 204 from BMC Simulator.
intel@ubuntu:functional_test$ ./dm deleteaccount 192.168.40.247:8888:admin:admin_1 Failed to delete device account admin_1, status code 204
According to code, receiving status codes other than 200 returns error.
The text was updated successfully, but these errors were encountered: