Upgrade failing due to not finding the osa_secrets_file_name variable when running the user-secrets-adjustment.yml playbook

Bug #1624029 reported by Castulo J. Martinez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Undecided
Matthew Thode

Bug Description

When running the run_upgrade.sh script for upgrading from stable/mitaka to master the upgrade is failing with this error message:

The error appears to have been in '/opt/openstack-ansible/scripts/upgrade-utilities/playbooks/user-secrets-adjustment.yml': line 25, column 7, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

      register: secrets
    - name: Add missing secret
      ^ here
"}

msg: the field 'args' has an invalid value, which appears to include a variable that is undefined. The error was: 'osa_secrets_file_name' is undefined

Apparently, the osa_secrets_file_name variable that is defined in the openstack/openstack-ansible/blob/master/scripts/upgrade-utilities/playbooks/defaults/main.yml playbook is not being found.

This seems to be related to this change:
https://github.com/openstack/openstack-ansible/commit/bceb1e15e61af8f996831f54477e840d123522f8

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (master)

Fix proposed to branch: master
Review: https://review.openstack.org/370981

Changed in openstack-ansible:
assignee: nobody → Matthew Thode (prometheanfire)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (master)

Reviewed: https://review.openstack.org/370981
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=2ec74e9d8a012673bdad9343e5f9931f89bb8faa
Submitter: Jenkins
Branch: master

commit 2ec74e9d8a012673bdad9343e5f9931f89bb8faa
Author: Matthew Thode <email address hidden>
Date: Thu Sep 15 11:24:48 2016 -0500

    load variables as a simple var for upgrades

    This is needed because the upgrade.sh script runs each task on it's own.
    Not as a natural play. extra vars (as defined automaticly via the
    openstack-ansible command) still take precidence.

    Change-Id: I86c95d3fb6f9d931093ff6622b25e814920940f6
    Closes-Bug: 1624029

Changed in openstack-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/371228

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (stable/mitaka)

Reviewed: https://review.openstack.org/371228
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=42b2a79c816f289060a0abd35d3ef3924eb46852
Submitter: Jenkins
Branch: stable/mitaka

commit 42b2a79c816f289060a0abd35d3ef3924eb46852
Author: Matthew Thode <email address hidden>
Date: Thu Sep 15 11:24:48 2016 -0500

    load variables as a simple var for upgrades

    This is needed because the upgrade.sh script runs each task on it's own.
    Not as a natural play. extra vars (as defined automaticly via the
    openstack-ansible command) still take precidence.

    Change-Id: I86c95d3fb6f9d931093ff6622b25e814920940f6
    Closes-Bug: 1624029
    (cherry picked from commit 2ec74e9d8a012673bdad9343e5f9931f89bb8faa)

tags: added: in-stable-mitaka
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible 13.3.4

This issue was fixed in the openstack/openstack-ansible 13.3.4 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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