Closed trickyearlobe closed 4 years ago
Sorry you hit this! This should be resolved by the time of our force-upgrade in a few weeks. We're probably going to port those auth_
generators to the IAM v2 specific diagnostic.
The core issue here is that there are no way to add a node and credentials from the Automate UI. This is where I've noticed it first. While trying to add node or credentials it returns HTTP Code 400.
@pag-r did you mean to add this comment to a different issue?
@susanev no, this is what I noticed when I saw this error in my environment. At least in my case adding creds and nodes is impossible no more. Only way to make it work again is to chef-automate reinstall
@pag-r do you mind opening a new issue that describes how to reproduce the error you're seeing in your environment? It sounds like the error you're describing may be a separate problem we should investigate
We might also be able to help if you post in https://community-slack.chef.io/
@susanev and @bcmdarroch, I was wrong, there is no connection between diagnostics run and HTTP 400. I just checked it when diagnostics failed after switching to v2
but forgot that I've applied policyfile. tl;dr: please ignore my comment from Feb 10th.
work in progress: https://github.com/chef/automate/pull/2842
20200220011437
we confirmed this is fixed in acceptance, closing.
Describe the bug
Reported by customer and verified with A2 build 20200127203438
With a clean install of A2 with IAMv1 enabled A2 diagnostics pass (with 2 skips related to IAMv2) as expected.
After migrating to IAMv2, A2 diagnostics fail.
To Reproduce
chef-automate diagnostics run
and observe tests pass, or are skipped as expected.chef-automate iam upgrade-to-v2
chef-automate diagnostics run
and observe some tests fail (causing whole diagnostic to fail)Versions (please complete the following information):
Diagnostics output with IAMv2 enabled