PATCH - Adding a second rule to an origin causes the service to go to failed state

Bug #1421183 reported by Malini Kamalambal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Poppy
Invalid
High
Unassigned

Bug Description

PATCH service endpoint - Adding a second rule to an origin causes the service to go to failed state

request body,

[
        {"op": "replace",
            "path": "/origins/1",
            "value": {"origin": "1.2.3.4", "port": 80, "ssl": false,
                "rules": [{"name" : "origin", "request_url" : "/replaced"},{"name" : "origin2", "request_url" : "/replaced2"}]}
        }
    ]

Changed in poppy:
milestone: none → kilo-3
importance: Undecided → High
Changed in poppy:
milestone: kilo-3 → liberty-1
Changed in poppy:
milestone: liberty-1 → none
Changed in poppy:
milestone: none → liberty-2
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.