cbpy-installer results in a reg key of HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\3.9 with path pointing to C:\Jenkins\workspace\couchbase-server-windows\install\lib\python\runtime. If the key exists, cbpy might be fooled to skip the install. It seems to be rather inconsistent based on our testing. If an end user tries to uninstall/reinstall 7.0.4 (comes with 3.9 runtime), he might run into issue. If future relases (i.e. 7.0.5) comes out with the same cbpy, users definitely will have trouble.

10:56
We need to make sure cbpy-installer doesn't depend on the registery key.

Thanks Ming Ho Any ETA on the fix?

ceej and I have a toy build ready for test.

Arunkumar Senthilnathan here is the link to the toy build. http://latestbuilds.service.couchbase.com/builds/latestbuilds/couchbase-server/toybuilds/1082[…]r-enterprise_7.0.4-10827-windows_amd64-unsigned.msi

I would suggest probably, a plain install, an upgrade from 7.0.3, and an install of the toy build after uninstalling 7.0.3. I am just guessing these are likely some of the scenarios our customers might have.

Chris Hillery and I have both validated locally. Would be super helpful if QE can give us a hand on this toy build as the original issue is rather inconsistent.

Ming Ho I tested the following:

1. Plain install of toy build --> works fine
2. Upgrade from 7.0.3 --> works fine
3. Install of toy build after uninstalling 7.0.3 --> works fine

However, when I tried to upgrade from toy build to 7.1.0, I am seeing issues. Upgrade went through fine but not able to see 8091 come up. Can you please take a look?

The 7.0.4->7.1.0 issue is tracked by MB-52313 now along with the related Java issue. Meanwhile, this issue should be resolved with https://github.com/couchbase/tlm/commit/8980799e90b074f5e28aa0969d12b355bbcfb6ef in 7.0.4-7279.