Submitter: Jenkins
Branch:    master

commit fb3b47ea5b5e278246fcaf4689a7a2e6d6892ca3
Author: Hesam Chobanlou <>
Date:   Sun Sep 3 19:48:28 2017 -0400

    Update docs to include standardization of VM diagnostics
    VM diagnostics has been updated with v2.48 to include a standard formatting.
    This change will update the admin documentation to mention the new standard
    Change-Id: I2498ae5400ad0903f6084bacaf96f0b76731b5a3
    Closes-bug: 1696033

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

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).

      Standardization of VM diagnostics info API.

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Dear bug triager. This bug was created since a commit was marked with 
  Your project "openstack/nova" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit a9448389932ae010897bf5a19239588bf198ee52
  Author: Sergey Nikitin <>
  Date:   Tue Aug 16 15:04:14 2016 +0300

      Standardization of VM diagnostics info API.
      Before this patch, VM diagnostics response was just a
      'blob' of data returned by each hypervisor. New API
      version makes diagnostics response standardized.
      New response has a set of fields which each hypervisor
      will try to fill. If hypervisor unable to provide a
      specific field then this field will be reported as 'None'.
      Tempest tests: I7757c5beeea3d3b0bc15a51cafc5ea2ada65e76c
      DocImpact: admin guide docs should be updated to mention
      standardized version of the diagnostics response
      blueprint: restore-vm-diagnostics
      Change-Id: If0b1493cc5c1c7f0d9896dd68342ad4dea4f7da2

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to