uninstalled libraries continue to get installed on cluster startup

[reedzhang]

We have been trying to update some library versions by uninstalling the old versions and installing new ones. However, the old libraries continue to get installed on cluster startup despite not showing up in the "libraries" tab of the cluster page. We can see in the log4j logs that they're getting installed, and we can import them in notebooks to verify that their versions are what we're trying to uninstall. Is this a known issue? How can I view/modify what the cluster decides to install on startup if it's not the libraries tab?

[shan_chandra]

could you please check if there are any global init scripts specified at the workspace level? or init scripts specified in the cluster from which the libraries are getting installed.

[Prabakar]

Hi @Reed Zhang​ 

Please go to the library and check if this cluster is marked to get the library automatically installed on the cluster. If so please uncheck it to resolve the issue.

[Prabakar]

@Reed Zhang​ were you able to resolve this issue? If so could you please mark it as the best answer to close this thread?

[reedzhang · Accepted solution]

The issue seemed to go away on its own. At some point the libraries page started showing what was getting installed to the cluster, and removing libraries from the page caused them to stop getting installed on cluster startup. I'm guessing there was some bug causing a disconnect between what the libraries page was showing and what the cluster was actually using to install libraries. I doubt it was anything specific to that cluster (like init scripts, etc.) as we were seeing it on other clusters too.