Device stuck in queued when I request private IPv6 in ip_addresses field in the creating request

[t0mk]

This is connected to provisioning device wihtout public IPv4.

When I create device over the API, and put [{"address_family":6,"public":false}] (obviously a nonsense) to device creating request, device is stuck in queued state.

{ [...] "hostname":"wSFNWecv","plan":"baremetal_0","facility":["ewr1"], "operating_system":"ubuntu_16_04", "ip_addresses":[{"address_family":4,"public":false},{"address_family":6,"public":false}] }

See the stuck device:

curl --silent -X GET -H "X-Auth-Token: $PACKET_AUTH_TOKEN" "https://api.packet.net/devices/91b65b07-fcce-4a9d-b83a-2249424cf7c9" | jq

[amenowanna]

@t0mk thank you for reporting this. We are looking into it.

[mberrueta]

@t0mk sorry I thought that I was answered before, I reviewed and It seems that was a deployment issue. I tested a similar configuration and it works fine

Let me know if this still happens

[jasmingacic]

@t0mk is this still the case?

[t0mk]

Now, if I add {"address_family":6,"public":false}, to the IP addres list when creating device, the device gets stuck in provisioning (not in queued).

[jacobsmith928]

@amenowanna what's the best way to get this into the queue for review?

[jacobsmith928]

@amenowanna added to the existing bugs project, hope this helps!