You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The logs were a little unclear to me but it looks like AFI creation failed. Describing an image seems to confirm it, with the error SHELL_VERSION_DEPRECATED.
Interestingly, the one which succeeded happens to have completed only 40 minutes earlier. I assume they're all using the same version in which case it looks like AWS deprecated it while we were in the middle of using it!
That seems quite unfortunate - I guess it means we have to keep our tooling uptodate otherwise we risk the platform ceasing to work. How out of date is our current choice of shell version?
It seems a bit surprising to me that this would break in this manner. You'd hope that they would support such things for a long time. I can imagine that they'd need to do it for security reasons, etc, though.
The text was updated successfully, but these errors were encountered:
During a hardware test, 2 out of 3 builds failed:
http://jenkins.nerabus-infra.com:8080/blue/organizations/jenkins/reconfigureio%2Freco-sdaccel/detail/master/721/pipeline/75/
The logs were a little unclear to me but it looks like AFI creation failed. Describing an image seems to confirm it, with the error
SHELL_VERSION_DEPRECATED
.Interestingly, the one which succeeded happens to have completed only 40 minutes earlier. I assume they're all using the same version in which case it looks like AWS deprecated it while we were in the middle of using it!
That seems quite unfortunate - I guess it means we have to keep our tooling uptodate otherwise we risk the platform ceasing to work. How out of date is our current choice of shell version?
It seems a bit surprising to me that this would break in this manner. You'd hope that they would support such things for a long time. I can imagine that they'd need to do it for security reasons, etc, though.
The text was updated successfully, but these errors were encountered: