Closed pjbreaux closed 7 years ago
Two things fail here, one is that when we do a POST to the virtual to add the policy, it successfully adds the policy but produces a 404. The second is that when we do a GET on the policy that has been added, it also produces a 404, when the policy certainly exists. This is an sdk issue and should be handled properly there.
The fix for this issue is dependent on a fix of sdk issue #968. We should bump the sdk version once this bugfix is in there. We could workaround the issue in the agent, but we have a great deal of precedent of dealing with these types of things in the sdk.
@pjbreaux: confirm this is resolved with the bump to 2.3.1 and close the issue.
Recent test runs show passing in gumballs report. Closing this issue as resolved with changes to SDK.
This issue was found when testing against BIG-IP 11.5.4
Agent Version
9.2.0
OpenStack Release
Mitaka
Description
The test
api/test_l7policy_update.py::L7PolicyRulesTestJSON::test_reorder_policies
fails after the creation of a single policy, when it's checking that the virtual server has the proper wrapper policy. The tempest error is shown below:The first obvious sign of trouble in the agent log is shown in a traceback, which seems to jive with the tempest call failure. A 404 is returned when looking for the policies for the virtual server.