You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected Behavior
When we provision a couchbase VDB for the first time on the target host, we do not see staging data inserted or populated into the target VDB. We should see the actual data being generated during the first time VDB provision operation.
Actual Behavior
No data found on the target host during the initial VDB provision operation. This happens only on the first provision job, after performing VDB refresh we can see the staging data generated or populated on the target host (VDB).
Note
This issue is observed only when we install couchbase database on any host for the first time.
Steps To Reproduce the Problem
Provision a VDB on a target host (with a fresh couchbase installation)
Ensure the target host does not have couchbase binaries already installed on it.
After the provision job, no data is found in buckets available on the couchbase console.
Version
Couchbase 5.5.4 version
Additional Context
We do not see this issue whenever we provision a VDB on any target host which has an existing couchbase installation. This behavior is observed only when we provision a VDB on a freshly setup couchbase installation.
The text was updated successfully, but these errors were encountered:
Expected Behavior
When we provision a couchbase VDB for the first time on the target host, we do not see staging data inserted or populated into the target VDB. We should see the actual data being generated during the first time VDB provision operation.
Actual Behavior
No data found on the target host during the initial VDB provision operation. This happens only on the first provision job, after performing VDB refresh we can see the staging data generated or populated on the target host (VDB).
Note
This issue is observed only when we install couchbase database on any host for the first time.
Steps To Reproduce the Problem
Version
Couchbase 5.5.4 version
Additional Context
We do not see this issue whenever we provision a VDB on any target host which has an existing couchbase installation. This behavior is observed only when we provision a VDB on a freshly setup couchbase installation.
The text was updated successfully, but these errors were encountered: