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

storage information in bucket view is inconsistent and wrong #2296

Closed
dannyzaken opened this issue Dec 6, 2016 · 2 comments
Closed

storage information in bucket view is inconsistent and wrong #2296

dannyzaken opened this issue Dec 6, 2016 · 2 comments
Assignees
Labels
Comp-Capacity High system capacity & capacity reporting Severity 2 Product is usable but severely limited. Task is unable to operate or caused other sw to fail
Milestone

Comments

@dannyzaken
Copy link
Member

Environment info

  • Version: 2d500d1
  • Deployment: AZURE|ESX|AWS|GCLOUD|DEV|VBOX
  • Customer: NAME

Actual behavior

  1. a single bucket is using the default pool, but the storage information shows that Used (other buckets) is not 0. it shows different value on each refresh in the range 11-14 GB
  2. This happens on a cluster, but probably relevant for a single server as well.
  3. probably related to cloud policy that was removed (see steps to reproduce)

Expected behavior

  1. Used (other buckets) should be 0

Steps to reproduce

  1. set a bucket with only default_pool in the policy, and cloud pools as backup policy (I used 3 cloud pools)
  2. default_pool should be used only by this bucket.
  3. use the cloud pools for other buckets.
  4. upload files to the bucket.
  5. remove the cloud pools from the policy.
  6. check the storage information in the bucket view. it is not getting better with time

Screenshots or Logs or other output that would be helpful

noobaa_management_console

@dannyzaken
Copy link
Member Author

according to @jeniawhite it should be checked after tiering changes PR that handles storage calculations differently.

@tamireran tamireran added GA-Product Severity 2 Product is usable but severely limited. Task is unable to operate or caused other sw to fail labels Dec 18, 2016
@jeniawhite
Copy link
Contributor

@dannyzaken @nimrod-becker
Seems like you've had storage values in each of the cloud resources, and they aggregated to 13gb (maybe trash values from other tests?)

But I couldn't find an explanation to the changes of the values on each refresh of the page.
I will talk to you when you arrive.

@nimrod-becker nimrod-becker added the Comp-Capacity High system capacity & capacity reporting label Dec 18, 2016
@nimrod-becker nimrod-becker modified the milestone: GA Dec 19, 2016
@nimrod-becker nimrod-becker modified the milestones: GA, 1.1 Jan 31, 2017
@nimrod-becker nimrod-becker modified the milestones: 1.1, 1.2 Feb 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Comp-Capacity High system capacity & capacity reporting Severity 2 Product is usable but severely limited. Task is unable to operate or caused other sw to fail
Projects
None yet
Development

No branches or pull requests

4 participants