Is there any reason the method in ec2_utils wouldn't work, that allows it to be 
a case-specific skipping of 404, instead of always skipping on 404. It seems 
like something like that which allows could be used to preemptively abort the 
retry (instead of the code below, which makes it very specific to 404). Maybe 
provide a should_retry_cb (callback) that gets called to see if retrying should 
be aborted (and then in cloudstack provide a callback that says 'no' should not 
retry on 404).
-- 
https://code.launchpad.net/~juergh/cloud-init/lp1298921/+merge/213234
Your team cloud init development team is requested to review the proposed merge 
of lp:~juergh/cloud-init/lp1298921 into lp:cloud-init.

_______________________________________________
Mailing list: https://launchpad.net/~cloud-init-dev
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~cloud-init-dev
More help   : https://help.launchpad.net/ListHelp

Reply via email to