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

1.0.0 Web UI cli fullscreen not working #5901

Closed
yura-shutkin opened this issue Dec 5, 2018 · 3 comments
Closed

1.0.0 Web UI cli fullscreen not working #5901

yura-shutkin opened this issue Dec 5, 2018 · 3 comments
Labels

Comments

@yura-shutkin
Copy link
Contributor

yura-shutkin commented Dec 5, 2018

Describe the bug
A clear and concise description of what the bug is.
Web UI cli full screen not working. Cli disapears after command fullscreen. Tested on both Chrome Version 70.0.3538.110 (Official Build) (64-bit) and FireFox 63.0.3 (64-bit)

To Reproduce
Steps to reproduce the behavior:

  1. Login to vault
  2. Open web UI cli
  3. write fullscreen
  4. See error

Expected behavior
Web UI cli shoud fill whole web page.

Environment:

  • Vault Server Version (retrieve with vault status):
Key             Value
---             -----
Seal Type       shamir
Initialized     true
Sealed          false
Total Shares    1
Threshold       1
Version         1.0.0
Cluster Name    vault-cluster-f74a4390
Cluster ID      c34424f6-72eb-14d2-2c52-b4071cb65ba2
HA Enabled      true
HA Cluster      https://vault-client-1:8201
HA Mode         active
  • Vault CLI Version (retrieve with vault version):
Vault v1.0.0 ('c19cef14891751a23eaa9b41fd456d1f99e7e856')
  • Server Operating System/Architecture:
ubuntu 16.04 x64

Vault server configuration file(s):

storage "consul" {
  address = "127.0.0.1:8500"
  path = "vault/"
  scheme = "http"
  token = "d565f7b1-a1ac-f91a-eaa5-820ca3f03124"
  service_tags = "vault-dev"
  service_address = "vault-client-1"
}

listener "tcp" {
  address     = "192.168.4.6:8200"
  tls_disable = "true"
  cluster_address = "192.168.4.6:8201"
  proxy_protocol_behavior = "allow_authorized"
  proxy_protocol_authorized_addrs = "192.168.4.5"
  x_forwarded_for_authorized_addrs = "192.168.4.5/32"
  x_forwarded_for_reject_not_authorized = "true"
  x_forwarded_for_reject_not_present = "true"
}

listener "tcp" {
  address     = "127.0.0.1:8200"
  tls_disable = "true"
}

telemetry {
  statsite_address = "statsd-exporter:9125"
  disable_hostname = true
}

ui = "true"

api_addr = "http://vault-client-1:8200"
cluster_addr = "https://vault-client-1:8201"

Additional context
On local single node with -dev at docker all works fine, but ha with consul storage have this issue.
You can see docker-compose file at https://github.com/yura-shutkin/docker-lab/tree/master/vault-cluster

@meirish
Copy link
Contributor

meirish commented Dec 5, 2018

Hi - thanks for filling an issue!

What error are you seeing? On https://demo.vaultproject.io I do see that there's a rendering issue - the whole cli moves off the top of the viewport - is that what you're seeing? I'm working to get that fixed, but I want to make sure we get everything and I'm not seeing other errors. Could you screenshot them or paste the text of errors you're seeing?

Thanks!

@yura-shutkin
Copy link
Contributor Author

yura-shutkin commented Dec 5, 2018

Thank you for answer. Yes, cli moves off the top.

screenshot from 2018-12-06 03-46-58
Nothing at console log and no failed queries at network tab

@meirish
Copy link
Contributor

meirish commented Dec 5, 2018

@yura-shutkin great - the linked PR fixes this then. Sorry we missed that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants