Skip to content
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

[UI - Telegrafs] Update NGINX values popup fails to close when clicking done #15500

Closed
karel-rehor opened this issue Oct 18, 2019 · 0 comments · Fixed by #15710
Closed

[UI - Telegrafs] Update NGINX values popup fails to close when clicking done #15500

karel-rehor opened this issue Oct 18, 2019 · 0 comments · Fixed by #15710

Comments

@karel-rehor
Copy link
Contributor

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

  1. Open Load Data telegrafs.
  2. Click create configuration. The wizard loads
  3. Choose NGINX
  4. Click continue
  5. In the plugins list click NGINX. A panel to configure NGinx URLs loads.
  6. Add a URL.
  7. Click done. NOTHING HAPPENS

Expected behavior:
That the value in the URLs field will be validated and if valid, the wizard will return to the review step. If invalid an error message would be supplied.

Previously it returned to the review step and the plugin was red, green or grey depending on the validity or existence of the plugin URLs value.

Actual behavior:
Clicking the "Done" button did nothing. Had to dismiss the wizard.

Screencast
TelegrafNginxPluginDetails01

Environment info:

  • System info: Run uname -srm and copy the output here
  • InfluxDB version: Run influxd version and copy the output here
    Discovered in nightly build docker image
ts=2019-10-18T08:29:40.849811Z lvl=info msg="Welcome to InfluxDB" log_id=0IZVctSG000 version=nightly commit=552168d3a build_date=2019-10-18T07:25:22Z
  • Other relevant environment details: Container runtime, disk info, etc
    browser: Chrome 77
    Config:
    Copy any non-default config values here or attach the full config as a gist or file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment