We noticed that in our Dev environment, Zookeeper hasn’t been upgraded as we recently moved from 4.17.05 to 4.18.01 and then 4.19.01.
Dev environment: Apigee version 4.19.01, Zookeeper version 3.4.5-0.0.2002
Test environment: Apigee version 4.19.01, Zookeeper version 3.4.5-1.0.905
Prod environment (not upgraded yet): Apigee version 4.17.05, Zookeeper version 3.4.5-1.0.905
Is this a known issue?
How can we remedy this situation so ZK is the same version across the board?
Thanks!
Thomas, as I found apigee-zookeeper-3.4.5-0.0.2002 is valid for OPDK 4.19.01 release. I just checked this in one of the OPDK environments I have and I saw the same:
$ apigee-all version
+ apigee-service apigee-attribution version
apigee-attribution-4.19.01-0.0.708
+ apigee-service apigee-cassandra version
apigee-cassandra-2.1.16-0.0.2046
+ apigee-service apigee-service version
apigee-service-4.19.01-0.0.1408
+ apigee-service apigee-setup version
apigee-setup-4.19.01-0.0.1108
+ apigee-service apigee-zookeeper version
apigee-zookeeper-3.4.5-0.0.2002
I believe at the time you installed apigee-zookeeper in the Dev environment, the upstream package repository may have had apigee-zookeeper-3.4.5-0.0.2002 as the latest version.
May be you could check for updates using the below command in the Dev environment:
$ sudo yum list available --showduplicates apigee-zookeeper
If you could see updates above, may be the update process mentioned on the documentation can be followed to update apigee-zookeeper to its latest version:
[https://docs.apigee.com/private-cloud/v4.19.01/update-apigee-edge-4180x-41901](https://docs.apigee.com/private-cloud/v4.19.01/update-apigee-edge-4180x-41901)
Thanks for your reply! You are probably right, as the Dev environment was installed at a different time than either Test or Prod. I don’t think there is any mention of the ZK upgrade in the documentation for upgrading to 4.19.01, and since it’s the same major version, I guess it’s compatible.