CI: random error in: nova : Discovering nova hosts (Duplicate host mapping)

Bug #1832987 reported by Radosław Piliszek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Medium
Radosław Piliszek
Queens
Fix Released
Medium
Unassigned
Rocky
Fix Released
Medium
Unassigned
Stein
Fix Released
Medium
Unassigned
Train
Fix Released
Medium
Radosław Piliszek

Bug Description

Task: nova : Discovering nova hosts
Stdout : ERROR: Duplicate host mapping was encountered. This command should be run once after all compute hosts have been deployed and should not be run in parallel. When run in parallel, the commands will collide with each other trying to map the same hosts in the database at the same time. Error: Host 'primary' mapping already exists
Link: http://logs.openstack.org/33/665533/1/check/kolla-ansible-centos-source/6d822a4/primary/ara-report/

Revision history for this message
Radosław Piliszek (yoctozepto) wrote :

auto-confirmed because in CI

Changed in kolla-ansible:
status: New → Incomplete
status: Incomplete → Confirmed
Changed in kolla-ansible:
assignee: nobody → Radosław Piliszek (yoctozepto)
Revision history for this message
Mark Goddard (mgoddard) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.opendev.org/665554
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=ce680bcfe2208f19a23630ee3feff4b9bd40c595
Submitter: Zuul
Branch: master

commit ce680bcfe2208f19a23630ee3feff4b9bd40c595
Author: Radosław Piliszek <email address hidden>
Date: Sun Jun 16 20:37:35 2019 +0200

    Avoid parallel discover_hosts (nova-related race condition)

    In a rare event both kolla-ansible and nova-scheduler try to do
    the mapping at the same time and one of them fails.
    Since kolla-ansible runs host discovery on each deployment,
    there is no need to change the default of no periodic host discovery.

    I added some notes for future. They are not critical.
    I made the decision explicit in the comments.
    I changed the task name to satisfy recommendations.
    I removed the variable because it is not used (to avoid future doubts).

    Closes-Bug: #1832987

    Change-Id: I3128472f028a2dbd7ace02abc179a9629ad74ceb
    Signed-off-by: Radosław Piliszek <email address hidden>

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

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/667984

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

Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/668033

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

Fix proposed to branch: stable/queens
Review: https://review.opendev.org/668104

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

Fix proposed to branch: stable/pike
Review: https://review.opendev.org/668106

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

Reviewed: https://review.opendev.org/667984
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=ed3d1e37ffa3c513957e184693d5ae7e451e92d8
Submitter: Zuul
Branch: stable/stein

commit ed3d1e37ffa3c513957e184693d5ae7e451e92d8
Author: Radosław Piliszek <email address hidden>
Date: Sun Jun 16 20:37:35 2019 +0200

    Avoid parallel discover_hosts (nova-related race condition)

    In a rare event both kolla-ansible and nova-scheduler try to do
    the mapping at the same time and one of them fails.
    Since kolla-ansible runs host discovery on each deployment,
    there is no need to change the default of no periodic host discovery.

    I added some notes for future. They are not critical.
    I made the decision explicit in the comments.
    I changed the task name to satisfy recommendations.
    I removed the variable because it is not used (to avoid future doubts).

    Closes-Bug: #1832987
    Change-Id: I3128472f028a2dbd7ace02abc179a9629ad74ceb
    Signed-off-by: Radosław Piliszek <email address hidden>
    (cherry picked from commit ce680bcfe2208f19a23630ee3feff4b9bd40c595)

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

Reviewed: https://review.opendev.org/668033
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d8c6e54667f6fb127664a9d5c41d25b78f9ac893
Submitter: Zuul
Branch: stable/rocky

commit d8c6e54667f6fb127664a9d5c41d25b78f9ac893
Author: Radosław Piliszek <email address hidden>
Date: Sun Jun 16 20:37:35 2019 +0200

    Avoid parallel discover_hosts (nova-related race condition)

    In a rare event both kolla-ansible and nova-scheduler try to do
    the mapping at the same time and one of them fails.
    Since kolla-ansible runs host discovery on each deployment,
    there is no need to change the default of no periodic host discovery.

    I added some notes for future. They are not critical.
    I made the decision explicit in the comments.
    I changed the task name to satisfy recommendations.
    I removed the variable because it is not used (to avoid future doubts).

    Closes-Bug: #1832987
    Change-Id: I3128472f028a2dbd7ace02abc179a9629ad74ceb
    Signed-off-by: Radosław Piliszek <email address hidden>
    (cherry picked from commit ce680bcfe2208f19a23630ee3feff4b9bd40c595)

tags: added: in-stable-rocky
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 8.0.0.0rc2

This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc2 release candidate.

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

Reviewed: https://review.opendev.org/668104
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=73747860dc943661deca4260342d90b25dadd9f7
Submitter: Zuul
Branch: stable/queens

commit 73747860dc943661deca4260342d90b25dadd9f7
Author: Radosław Piliszek <email address hidden>
Date: Sun Jun 16 20:37:35 2019 +0200

    Avoid parallel discover_hosts (nova-related race condition)

    In a rare event both kolla-ansible and nova-scheduler try to do
    the mapping at the same time and one of them fails.
    Since kolla-ansible runs host discovery on each deployment,
    there is no need to change the default of no periodic host discovery.

    I added some notes for future. They are not critical.
    I made the decision explicit in the comments.
    I changed the task name to satisfy recommendations.
    I removed the variable because it is not used (to avoid future doubts).

    Closes-Bug: #1832987
    Change-Id: I3128472f028a2dbd7ace02abc179a9629ad74ceb
    Signed-off-by: Radosław Piliszek <email address hidden>
    (cherry picked from commit ce680bcfe2208f19a23630ee3feff4b9bd40c595)
    (cherry picked from commit ed3d1e37ffa3c513957e184693d5ae7e451e92d8)

tags: added: in-stable-queens
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on kolla-ansible (stable/pike)

Change abandoned by Radosław Piliszek (<email address hidden>) on branch: stable/pike
Review: https://review.opendev.org/668106
Reason: because it requires more backports to be made than expected

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

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

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

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

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

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

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.