Hello guys.
I’ve tried to invite a new user in our organization and he gets an error saying that
"There was a problem processing one or more invitations. Please try again later."
I’ve run chef-server-ctl reconfigure and then chef-server-ctl test and the results of the test is as follow:
Pending: (Failures listed here are expected and do not affect your suite's status)
1) opscode-account user association user not in org can be invited to the org by an admin when the inviting admin is removed from the org, invites issued by that admin cannot be accepted
# Known failure: passes w/ 200 b/c no USAG cleanup performed for deleted user
# ./spec/api/account/account_association_spec.rb:661
2) opscode-account user association user not in org can be invited to the org by an admin when the inviting admin is removed from the system, invites issued by that admin can't by accepted
# Known failure: passes w/ 200 b/c no USAG or other group cleanup performed for deleted user
# ./spec/api/account/account_association_spec.rb:670
Failures:
1) authenticate_user POST /authenticate_user with correct credentials superuser user returns 200 ("OK")
Failure/Error:
post(request_url, superuser, :payload => body).should look_like({
:status => 200,
:body_exact => response_body
})
Response should have HTTP status code 200 ('OK'), but it was actually 401 ('Unauthorized')
Reponse Body: {"error":["Failed to authenticate: Username and password incorrect"]}
# ./spec/api/authenticate_user_spec.rb:129:in `block (4 levels) in <top (required)>'
2) users /users/<name> endpoint PUT /users/<name> superuser authenticating after updates when password is unchanged can authenticate as the modified user when password has not been changed.
Failure/Error:
post(auth_url, superuser, :payload => { 'username' => username,
'password' => password }).should look_like({
:status => 200
})
Response should have HTTP status code 200 ('OK'), but it was actually 401 ('Unauthorized')
Reponse Body: {"error":["Failed to authenticate: Username and password incorrect"]}
# ./spec/api/user_spec.rb:873:in `block (7 levels) in <top (required)>'
Finished in 2 minutes 17.3 seconds (files took 13.97 seconds to load)
154 examples, 2 failures, 2 pending
Failed examples:
rspec ./spec/api/authenticate_user_spec.rb:128 # authenticate_user POST /authenticate_user with correct credentials superuser user returns 200 ("OK")
rspec ./spec/api/user_spec.rb:871 # users /users/<name> endpoint PUT /users/<name> superuser authenticating after updates when password is unchanged can authenticate as the modified user when password has not been changed.
My colleague still have no access receiving the same error.
I’ve also tried to run add manually the user in the organization and the result says that user is already associated with the organization.
What else can I do?
Thank you,
Gabriel