WRONG_AMI violation on a compliant ami
drummerwolli opened this issue · 2 comments
please have a look at our internal zalando violations 2366790 and 2349361 ... both of them say that we are running a non-conforming taupage ami (WRONG_AMI violation). but we didn't, this is a false violation. @linki can confirm this.
amis exist in stups-build and are shared with other accounts. violation data misses an image owner which could indicate a problem accessing the information from the aws api.
On 07.06.2016, at 14:11, Fabian Wollert notifications@github.com wrote:
please have a look at our internal zalando violations 2366790 and 2349361 ... both of them say that we are running a non-conforming taupage ami (WRONG_AMI violation). but we didn't, this is a false violation. @linki can confirm this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
The problem is that fullstop exeeds request limit while invoking a describe-images on the AWS API for that image id to inspect. Afterwards it marks the image as WRONG because it got no info about.
There should be some retry mechanism for that to make sure to get the image info.
WARN [pool-3-thread-1] o.z.s.f.p.p.i.AmiProviderImpl - Could not get AMI of: ami-75138006
14:40:41.647 fullstop /var/log/application.log Jul 28 12:40:40 ip-172-31-160-79 docker/10833d31ede4[882]: com.amazonaws.AmazonServiceException: Request limit exceeded. (Service: AmazonEC2; Status Code: 503; Error Code: RequestLimitExceeded;