Skip to content
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.

Admiral UI does not set limit when accessing xenon services #96

Closed
martin-borisov opened this issue May 17, 2017 · 1 comment
Closed

Comments

@martin-borisov
Copy link
Contributor

This issue was reported by Laksmi in #admiral slack channel. Simply said he had added 50 VCH to Admiral and some time after that they are gone.

Trying to open Placements view results in similar error.

On the environment there's 51 placement zones - attached resources-pools.json
The problem is that each pool has many versions and including the old versions in total count is over 10k and xenon throws exception because Admiral UI is not limiting the query.

@martin-borisov martin-borisov added this to the VIC 1.2 milestone May 17, 2017
@lazarin
Copy link
Contributor

lazarin commented May 17, 2017

Fixed in vmware/admiral:vic_v1.1.1

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

No branches or pull requests

2 participants