If not, see <http://www.gnu.org/licenses/>. ... openshift.dynamic import DynamicClient 36 from openshift.dynamic.exceptions import ResourceNotFoundError, ...
SUMMARY So, I've already read through all of the following earlier issues: k8s_raw module shows openshift missing Python client even all dependencies are ...
Install the dynamic attributes connector and configure adapters, connectors, ... ImportError: No module named ansible. ansible-playbook, ansible-galaxy, …
If you have tried all methods provided above but failed, maybe your module has the same name as a built-in module. Or, a module with the same name existing in a folder that has a high priority in sys.path than your module's. To debug, say your from foo.bar import baz complaints ImportError: No module named bar.
The error was: ImportError: No module named kubernetes fatal: [localhost]: FAILED! ... "msg": "Failed to import the required Python library (openshift) on ...
08.04.2019 · If Ansible is not installed in the same environment as the openshift python module I don't think the lookup plugin will find it (if you're just using the lookup plugin to retrieve resources from the cluster, I recommend the k8s_facts module instead because it's behavior will match the other modules.)
19.02.2018 · openshift_deployment_type=origin openshift_release=v3.9 openshift_image_tag=v3.9.0 openshift_pkg_version=-3.9.0 Not sure whether the fact generation comes before this. If so then maybe its fixed.
04.02.2019 · - name: deploy kured daemonset k8s: state: present context: " {{ cluster_name}} " # Does not help removing this host: " redacted " # tried specifying this, but does not help kubeconfig: " ~/.kube/config " # Tried specifying this, does not help either src: " …
03.01.2019 · SUMMARY So, I've already read through all of the following earlier issues: k8s_raw module shows openshift missing Python client even all dependencies are satisfied Execute k8s task failed And I've been debugging this issue for my Pi Dram...
12.12.2019 · Based on discussions in issue #327 the openshift client is gathering all v1 resources, Is this correct? Yes, we're discovering all the core V1 resources (ie, /api/v1) If so, why? The client is fully dynamic, and uses the discovery interface to discover all resources, including the core resources.