manila haproxy backend name mismatch

Bug #1947026 reported by Amine
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Undecided
Unassigned

Bug Description

Hi

openstack ansible tag 22.3.1

when deploying manila, playbook failed on [set haproxy state] because haproxy backend is defined as "manilla-api-back" in os-manila.yml while it is named manila-back in haproxy.

correcting the mismatch solved the issue.

best

Amine

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (master)
Changed in openstack-ansible:
status: New → In Progress
Revision history for this message
Amine (amine-bouabdallah) wrote :

thanks.

the fix shouldn't also include the condition ?

when:
        - "'manila' in group_names"
        - "groups['manila'] | length > 1"
          # - "'manila_api' in group_names"
          # - "groups['manila_api'] | length > 1"

Revision history for this message
Dmitriy Rabotyagov (noonedeadpunk) wrote :

Hi,

No, it should not. Because you need to disable haproxy only when you run manila role against manila_api endpoints and don't disable api when you ran it against manila-share hosts for instance.

Group names are correct and manila_api group must exist according to https://opendev.org/openstack/openstack-ansible/src/branch/master/inventory/env.d/manila.yml#L16

Revision history for this message
Amine (amine-bouabdallah) wrote :

Hi.

noted.
still there is something there as when keeping the condition as is :

when:
  - "'manila_api' in group_names"
  - "groups['manila_api'] | length > 1"

the manila playbook fails at the same haproxy set state task. but when changed to

when:
  - "'manila' in group_names"
  - "groups['manila'] | length > 1"
it passes.

attached you can find a truncated error log for the first case.

Revision history for this message
Dmitriy Rabotyagov (noonedeadpunk) wrote :

Can you please attach log file with the error you see?

Revision history for this message
Amine (amine-bouabdallah) wrote :

sure...here it is

Revision history for this message
Dmitriy Rabotyagov (noonedeadpunk) wrote :

Ok, so I see here quite different issue. And I guess when you change condition, you don't see error because it's never satisfied.
I'm not quite sure what _exactly_ goes wrong there atm though. I will try to reproduce issue in sandbox and return back to you.

Revision history for this message
Dmitriy Rabotyagov (noonedeadpunk) wrote (last edit ):

I tried to reproduce that, but I don't see any issue in my sandbox deployment but it works: https://paste.opendev.org/show/810077/

I did that on 22.3.1 with fix cherry-picked.

My guess why you have failure, is because you need to run haproxy-install.yml after defining group for manila in openstack_user_config or conf.d. Otherwise you won't have endpoints created which might be result of the failure.

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

Reviewed: https://review.opendev.org/c/openstack/openstack-ansible/+/813885
Committed: https://opendev.org/openstack/openstack-ansible/commit/78d9a8596ad14e1caa483887545abb587c6c9fd9
Submitter: "Zuul (22348)"
Branch: master

commit 78d9a8596ad14e1caa483887545abb587c6c9fd9
Author: Dmitriy Rabotyagov <email address hidden>
Date: Wed Oct 13 22:02:03 2021 +0300

    Fix manila haproxy manage

    In manila playbook we incorrectly defined haproxy backend name.
    This wasn't catched by CI since we do single node deployment.

    Closes-Bug: #1947026
    Change-Id: I924504060179542bd2347b5155f70795d065381b

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/wallaby)

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/openstack-ansible/+/814650

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

Fix proposed to branch: stable/victoria
Review: https://review.opendev.org/c/openstack/openstack-ansible/+/814651

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

Reviewed: https://review.opendev.org/c/openstack/openstack-ansible/+/814650
Committed: https://opendev.org/openstack/openstack-ansible/commit/eb029212158f1b9fe52cba51dd8cc09b13c47c0c
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit eb029212158f1b9fe52cba51dd8cc09b13c47c0c
Author: Dmitriy Rabotyagov <email address hidden>
Date: Wed Oct 13 22:02:03 2021 +0300

    Fix manila haproxy manage

    In manila playbook we incorrectly defined haproxy backend name.
    This wasn't catched by CI since we do single node deployment.

    Closes-Bug: #1947026
    Change-Id: I924504060179542bd2347b5155f70795d065381b

tags: added: in-stable-wallaby
tags: added: in-stable-victoria
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (stable/victoria)

Reviewed: https://review.opendev.org/c/openstack/openstack-ansible/+/814651
Committed: https://opendev.org/openstack/openstack-ansible/commit/5c9007aa838a5d043752cdbc30b1d351736fa4ea
Submitter: "Zuul (22348)"
Branch: stable/victoria

commit 5c9007aa838a5d043752cdbc30b1d351736fa4ea
Author: Dmitriy Rabotyagov <email address hidden>
Date: Wed Oct 13 22:02:03 2021 +0300

    Fix manila haproxy manage

    In manila playbook we incorrectly defined haproxy backend name.
    This wasn't catched by CI since we do single node deployment.

    Closes-Bug: #1947026
    Change-Id: I924504060179542bd2347b5155f70795d065381b

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible 22.3.3

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible 23.1.2

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible 24.0.0.0rc1

This issue was fixed in the openstack/openstack-ansible 24.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible 25.0.0.0b1

This issue was fixed in the openstack/openstack-ansible 25.0.0.0b1 development milestone.

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

Other bug subscribers

Bug attachments

Remote bug watches

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