[PACKTCABLE-17] Failing CSIT tests for Packetcable Boron (and master) due to HTTP Put 201 return Created: 29/Aug/16 Updated: 19/Oct/17 Resolved: 09/Sep/16 |
|
| Status: | Resolved |
| Project: | packetcable |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Kevin Kershaw | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6572 |
| Description |
|
Packetcable CSIT test failure due to change in HTTP put return code for creating resources. Per IETF spec, return code should be 201, not 200. See https://bugs.opendaylight.org/show_bug.cgi?id=2594 |
| Comments |
| Comment by Kevin Kershaw [ 30/Aug/16 ] |
|
This problem resolved by applying change: https://git.opendaylight.org/gerrit/#/c/44817 Jenkins run of CSIT now giving 6 of 6 tests passing: https://jenkins.opendaylight.org/releng/view/packetcable/job/packetcable-csit-1node-pcmm-all-boron/ https://jenkins.opendaylight.org/releng/view/packetcable/job/packetcable-csit-1node-pcmm-only-boron/ |
| Comment by Vratko Polak [ 09/Sep/16 ] |
|
Expecting wrong http code is a fault of test. Faulty tests can cause the feature under test being marked as experimental, but I do not think that should block release; so severity should not have been "blocker". |