Unless I'm misreading the packet dump, the events are clearly posted to maas and being decoded as a curtin event with curtin details. Why maas isn't reading/storing/displaying them is not something that curtin controls.
I don't want to bat this back and forth but the very fact that maas accepts the POSTed data and it returns OK clearly means the data is arriving at the owner of the reporting URL. It *cannot* be curtin at fault; it's sending the data; full-stop.
Unless I'm misreading the packet dump, the events are clearly posted to maas and being decoded as a curtin event with curtin details. Why maas isn't reading/ storing/ displaying them is not something that curtin controls.
I don't want to bat this back and forth but the very fact that maas accepts the POSTed data and it returns OK clearly means the data is arriving at the owner of the reporting URL. It *cannot* be curtin at fault; it's sending the data; full-stop.