8000 Helm creation of postgreql fails when installing multiple AWX on different namespaces on same kubernetes · Issue #2991 · ansible/awx · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Helm creation of postgreql fails when installing multiple AWX on different namespaces on same kubernetes #2991
Closed
@themr0c

Description

@themr0c
ISSUE TYPE
  • Bug Report
COMPONENT NAME
  • Installer
SUMMARY

The name of the postgresql installed by helm is defined by kubernetes_deployment_name, which is not necessarly changed when you change the namespace.

kubernetes_deployment_name: awx

As a result, if AWX is already deployed on a first namespace, deployment on a second namespace will fail at this step:

- name: Deploy and Activate Postgres (Kubernetes)
  shell: |
    helm install --name {{ kubernetes_deployment_name }} --namespace {{ kubernetes_namespace }} \
      --set postgresqlUsername={{ pg_username }} \
      --set postgresqlPassword={{ pg_password }} \
      --set postgresqlDatabase={{ pg_database }} \
      --set persistence.size={{ pg_volume_capacity|default('5')}}Gi \
      --tiller-namespace={{ tiller_namespace | default('kube-system') }} \
      stable/postgresql
  when:
    - pg_hostname is not defined or pg_hostname == ''
    - postgres_svc_details is defined and postgres_svc_details.rc != 0
    - kubernetes_context is defined
  register: kubernetes_pg_activate
  no_log: yes
ENVIRONMENT
  • AWX version: 2.1.2
  • AWX install method: kubernetes
  • Ansible version: 2.7.5
STEPS TO REPRODUCE
  • deploy awx on a first namespace
  • deploy awx on a second namespace
EXPECTED RESULTS

successful AWX deployment

ACTUAL RESULTS
TASK [kubernetes : Deploy and Activate Postgres (Kubernetes)] ***************************************************
Thursday 10 January 2019  16:53:58 +0100 (0:00:00.167)       0:01:21.303 ****** 
Thursday 10 January 2019  16:53:58 +0100 (0:00:00.167)       0:01:21.299 ****** 
fatal: [awx]: FAILED! => changed=true 
  censored: 'the output has been hidden due to the fact that ''no_log: true'' was specified for this result'
ADDITIONAL INFORMATION

I don't know what would make more sense:

  • Use kubernetes_namespace instead of kubernetes_deployment_name for:
 helm install --name {{ kubernetes_namespace }} --namespace {{ kubernetes_namespace }} 

Or

  • Redefine kubernetes_deployment_name: "{{ kubernetes_namespace }}"

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0