New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add acm cert bundle #130
add acm cert bundle #130
Conversation
I'll pull this down and run tests against the cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to update the manifest etc
Updated. |
I'm seeing errors when running the tests against Redshift which look entirely unrelated:
Could this be a regression from a recent change in this repo, or does this look like a change in Redshift's behavior? It looks like constraints are being returned differently. |
Travis is showing InterpreterNotFound errors, which I've also not seen. |
Looking at the travis logs, I'm seeing: E: Failed to fetch http://dl.hhvm.com/ubuntu/dists/trusty/main/binary-i386/Packages 503 Service Unavailable [IP: 140.211.166.134 80] |
Looks like the travis failures are recovering. I kicked off restarts of the last 2 failing test scenarios. |
I'm getting the errors discussed in #130 (comment) when running master branch tests against Redshift, so I think something changed with Redshift itself that will need to be fixed separately from this issue. |
It would be nice to verify the new bundle against the new certs AWS will be using prior to them actually forcing everyone to changeover. From the email and page when I read it that doesn't seem possible right now (which scares me). I can open a support issue inquiring about that ability unless you have that ability? |
I'd love if you go ahead and open the support case, @mjschultz |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To my knowledge, all test failures actually related to this change are now resolved.
I've filed an alternative pr in #132 which cleans up the issues here and some other things. |
closing in favor of #132 |
Todos