Reviewed:  https://review.opendev.org/728629
Committed: 
https://git.openstack.org/cgit/openstack/masakari/commit/?id=4322968b893b242f229912c2b70e3895f0227402
Submitter: Zuul
Branch:    master

commit 4322968b893b242f229912c2b70e3895f0227402
Author: Dmitriy Rabotyagov <drabotya...@vexxhost.com>
Date:   Sat May 16 12:22:13 2020 +0300

    Search in nova services instead of hypervisors
    
    Nova services and hypervisor naming can differ, as they retireve node
    names in different way.
    In the meanwhile we operate with nova.services while enabling/disabling
    nodes duringh the incident. So we're supposed to have in database record
    matching to what we have in service list, but not in hypervisor list.
    
    Closes-Bug: #1839715
    Change-Id: I9c591d33f17a8d5950bdb1fc2d686e2301fc6d95


** Changed in: masakari
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839715

Title:
  masakari fails if hypervisor name does not match nova service name

To manage notifications about this bug go to:
https://bugs.launchpad.net/masakari/+bug/1839715/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to