Skip to content

EKS credentials form doesn't "reset" after error

Summary

I tried to add a Provision Role to authenticate to EKS to create a cluster but the request failed and I got an error. When I removed the value from the role field and entered a different value, the button did not turn green as I expected but remained in a disabled state (visually). However, I think functionally it worked.

Steps to reproduce

  • Go to Operations -> Kubernetes-> Create Cluster
  • Select EKS
  • Add an invalid Provision role value
  • Click Authenticate with AWS
  • System returns error (not very informative btw)
  • Remove value from provision role field
  • Add a different value

What is the current bug behavior?

  • Add an invalid Provision role value
  • Click Authenticate with AWS
  • Remove value from provision role field (the error banner remains on the screen)
  • Add a different value (the Authenticate button remains in a disabled state)

What is the expected correct behavior?

  • Add an invalid Provision role value
  • Click Authenticate with AWS
  • System returns error (that helps the user understand what went wrong)
  • Remove value from provision role field (the error banner disappears/is hidden)
  • Add a different value (the Authenticate button gets enabled/turns green)

Relevant logs and/or screenshots

Screenshot_2019-11-27_at_14.35.30

Screenshot_2019-11-27_at_14.35.47

Screenshot_2019-11-27_at_14.35.58

Screenshot_2019-11-27_at_14.36.17

Screenshot_2019-11-27_at_14.36.25 Screenshot_2019-11-27_at_14.36.28__2_

Screenshot_2019-11-27_at_14.36.34__2_

Output of checks

This bug happens on GitLab.com

Edited by Maria Vrachni