Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
1
-
SDK34, SDK36
Description
When we create a new bucket and immediately connect to it then it's possible for select bucket to fail. When this happens it's still possible for us to successfully get and apply a cluster config, which will not contain any bucket settings. We should not set bucket settings to unsupported until we receive and actual bucket config.
Attachments
Gerrit Reviews
| For Gerrit Dashboard: GOCBC-1469 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 196376,4 | GOCBC-1469: Only set bucket capabilities when received bucket config | master | gocbcore | Status: MERGED | +2 | +1 |
| 196599,1 | GOCBC-1469: Parse feature not available error in collections mgr | master | gocb | Status: ABANDONED | 0 | 0 |
| 196603,6 | GOCBC-1469: Use waituntilready in collection history retention test | master | gocb | Status: MERGED | +2 | +1 |