Hi,

It seems that if i ask the CS API information on a disk which has been uploaded
or created
from template a disk offering id is returned. This disk offering id links to a
service offering not a disk offering, which differs per CS setup. I tested this
on 4.1 and 4.2.

What should the normal behavior be? I can understand that CS cannot return a
disk offering cause it's a custom disk, but returning id which maps to a service
(compute) offering causes some issues cause our system will calculate the wrong
price.

Shouldn't the disk offering be empty ( or null) for template/uploaded
disks/volumes?

Maybe somebody can verify they have the same issue? Looking up the offering id
in the db should be enough.

Thanks!

Met vriendelijke groet / Kind regards,

Lennert den Teuling
Tel direct: +31 (0)118 700 210

Reply via email to