Skip to content

v2.6
Compare
Choose a tag to compare
@nimrod-becker nimrod-becker released this 08 Jul 10:53
· 4010 commits to master since this release
v2.6.3
c63dc65

Version Info:

Additions:

  • Updated Pool & Bucket Statuses
  • Add configuration per account, to allow/prevent new bucket creation

Internal:

Closed Issues on this release:
(Automatically generated by comparing issue.closed_at with releases.published_at dates)

(#4863) Failed to upload data to NooBaa bucket - SignatureDoesNotMatch -- Customer reported
(#4855) Failed on pre-upgrade packages - 2.4.2-24f9e79 to 2.6.1-9492c8b
(#4844) Upgrade 2.4.2-24f9e79 to 2.6 stuck on 95% (Second step) -- Customer reported
(#4829) on upgrade setting swap is skipped - later on causing mongo to be killed for out of memory
(#4815) Could not resize server disk (physical size of partition did not change) -- Customer reported
(#4808) Vertical scroll in edit data placement resources table
(#4791) Spill-back status is not reported when spilling back occurs
(#4684) Drive latency should show sub millisecond percision
(#4775) Bucket status is "Rebuilding" when no rebuilds are currently occurring
(#4774) Bucket status "Data Spilling-back to resources" shows even after spill-back is done
(#4758) Server is running low on disk space alert, while disk space is fine (new system) -- Customer reported
(#4667) failure to get agent info causes the agent to get stuck in initializing -- Customer reported
(#4613) Data resiliency basic settings are configurable by keyboard arrows keys
(#4590) Agent reports "All drives has no access" when there is an IP issue (and doesn't report IP issue) -- Customer reported
(#4383) INVALID_SCHEMA_DB nodes
(#4085) Pool status while most nodes are migrating is "not enough healthy nodes", Should be "Most nodes are in process"
(#3894) Scrubber should identify persistent errors in blocks
(#3849) Pool has status 'Not enough healthy nodes' but actually has 3 nodes with low available capacity
(#3779) Inconsistency between pool/bucket/upload button -- Customer reported
(#3706) calc_hosts_pool_mode should not treat warning as errors (4 nodes pool with 2 nodes in low capacity would get not enough healthy nodes)
(#3703) Missing "spillback" status for a recovering bucket
(#3482) Hosts errors and issues mishmash can be confusing
(#3112) Duplicate pool modes for same reason
(#2708) Handling of non timezone explicit time in S3 http tags
(#2232) S3 bucket name from Host header to support subdomain buckets

Assets 2
Loading