# Kernel 'Python 3' is referencing a kernel provisioner ('local-provisioner') that is not available. Ensure the appropriate package has been installed and retry **URL:** \ **Category:** Kernels\ **Created:** [August 19, 2021, 9:50pm UTC](https://discourse.jupyter.org/t/kernel-python-3-is-referencing-a-kernel-provisioner-local-provisioner-that-is-not-available-ensure-the-appropriate-package-has-been-installed-and-retry/10436 "2021-08-19T21:50:04Z")\ **Posts on this page:** 1\ **Showing post:** 3

**Author:** ![kevin-bates](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/kevin-bates/32/234_2.png) [@kevin-bates](https://discourse.jupyter.org/u/kevin-bates)\ **Post date:** [August 20, 2021, 2:01pm UTC](https://discourse.jupyter.org/t/kernel-python-3-is-referencing-a-kernel-provisioner-local-provisioner-that-is-not-available-ensure-the-appropriate-package-has-been-installed-and-retry/10436/3 "2021-08-20T14:01:06Z")

Hi @AOrazaev, we should definitely change the error message specifically for `local-provisioner` since that provisioner is directly baked into jupyter\_client (7.0+) as its confusing relative to _that_ provisioner. As noted in the linked thread, it should be present so there’s some way that the jupyter\_client code is made available w/o the requisite entrypoint registration - which is how `local-provisioner` is deemed available. Do you or others happen to know by which “installation or packaging” mechanism entrypoints get registered? There’s obviously some path in which the package modules are made available, yet package-specific entrypoints are not. Thank you. --- _[View the full topic](https://discourse.jupyter.org/t/kernel-python-3-is-referencing-a-kernel-provisioner-local-provisioner-that-is-not-available-ensure-the-appropriate-package-has-been-installed-and-retry/10436)._