unable to install helm chart via ansible because of missing pyhelm module

Bug #1829406 reported by Allain Legacy on 2019-05-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tee Ngo

Bug Description

Brief Description
Unable to use Ansible to install a helm chart. An error reports that the python helm module (pyhelm) is missing from the target system.

This is the Ansible task:

- name: Install helm chart
    host: localhost
      name: hello-world
      version: 0.1.0
        type: file
        location: /path/to/some/hello-world-0.1.0.tgz
    state: installed
    name: hello-world
    namespace: default

This is the resulting error from the playbook:

fatal: [yow-cgcs-wildcat-7]: FAILED! => {"changed": false, "msg": "Could not import the pyhelm python module. Please install `pyhelm` package."}

Minor, but if we want end users to integrate the Ansible configuration, system configuration, and application deployment into a higher level CI/CD type ansible playbook then we will need to provide this functionality.

Steps to Reproduce
Use the task provided above to try and run a sample helm chart on the target system.

Expected Behavior
The chart should have been installed on the running system.

Actual Behavior
An error prevents the chart from being installed.


System Configuration

Branch/Pull Time/Commit
Private load rebased on May 10.

Last Pass

See above

Test Activity
Developer testing

Allain Legacy (alegacy) on 2019-05-16
description: updated
Matt Peters (mpeters-wrs) wrote :

We should make this change for X6 since it would enable automated deployments of customer applications.

Ghada Khalil (gkhalil) wrote :

Marking as stx.2.0 gating given feedback from Matt that this is a useful capability to add to Ansible.

tags: added: stx.config
Changed in starlingx:
assignee: nobody → Tee Ngo (teewrs)
importance: Undecided → Medium
status: New → Triaged
tags: added: stx.2.0
Tee Ngo (teewrs) wrote :

This LP should be re-gated the following reasons:

1. It is not hindering automation. The system can still be deployed remotely using existing Ansible modules and local Helm client.

2. Currently, Ansible Helm module still has oustanding functional issues such as https://github.com/ansible/ansible/issues/37148 and deficiencies such as https://github.com/ansible/ansible/issues/32513.

3. This ask implies the need to expose StarlingX Tiller server/Helm service externally so it's accessible to the Ansible control host and to all Ansible users of the system.

4. The users will also be required to install extra packages such as pip & its dependencies, pygit2, pyhelm, grpcio, etc... which could be problematic/undesirable for their specific environments.

Overall this ask requires more thoughts/considerations. It can be revisited in the future release, should the support for remote Ansible Helm client still be necessary.

Ghada Khalil (gkhalil) wrote :

Removing the stx.2.0 label given Matt Peters agreed to the re-gate
From Matt: I’m ok with having it re-gated based on the current deployment usage of the local helm client.

tags: removed: stx.2.0
Changed in starlingx:
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.