yahoo-eng-team team mailing list archive

[Charlotte Han <han.rong3@xxxxxxxxxx>]

Public bug reported:

Steps to reproduce
==================
A chronological list of steps which will bring off the
issue you noticed:
* I had a compute node, set allow_resize_to_same_host=true.

* I did boot a instance with flavor m1.tiny
1   | m1.tiny       | 512       | 1    | 0         |      | 1     | 1.0         | True    

* then I did boot many instance
* then I did Z
A list of openstack client commands (with correct argument value)
would be the most descriptive example. To get more information use:

    $ nova --debug <command> <arg1> <arg2=value>
    or
    $ openstack --debug <command> <arg1> <arg2=value>

Expected result
===============
After the execution of the steps above, what should have
happened if the issue wasn't present?

Actual result
=============
What happened instead of the expected result?
How did the issue look like?

Environment
===========
1. Exact version of OpenStack you are running. See the following
  list for all releases: http://docs.openstack.org/releases/

   If this is from a distro please provide
       $ dpkg -l | grep nova
       or
       $ rpm -ql | grep nova
   If this is from git, please provide
       $ git log -1

2. Which hypervisor did you use?
   (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
   What's the version of that?

2. Which storage type did you use?
   (For example: Ceph, LVM, GPFS, ...)
   What's the version of that?

3. Which networking type did you use?
   (For example: nova-network, Neutron with OpenVSwitch, ...)

Logs & Configs
==============
The tool *sosreport* has support for some OpenStack projects.
It's worth having a look at it. For example, if you want to collect
the logs of a compute node you would execute:

   $ sudo sosreport -o openstack_nova --batch

on that compute node. Attach the logs to this bug report. Please
consider that these logs need to be collected in "DEBUG" mode.
This bug contains information that is:
PublicEdit

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1609193

Title:
  resize error on the same current host with enough vcpu resource

Status in OpenStack Compute (nova):
  New

Bug description:
  Steps to reproduce
  ==================
  A chronological list of steps which will bring off the
  issue you noticed:
  * I had a compute node, set allow_resize_to_same_host=true.

  * I did boot a instance with flavor m1.tiny
  1   | m1.tiny       | 512       | 1    | 0         |      | 1     | 1.0         | True    

  * then I did boot many instance
  * then I did Z
  A list of openstack client commands (with correct argument value)
  would be the most descriptive example. To get more information use:

      $ nova --debug <command> <arg1> <arg2=value>
      or
      $ openstack --debug <command> <arg1> <arg2=value>

  Expected result
  ===============
  After the execution of the steps above, what should have
  happened if the issue wasn't present?

  Actual result
  =============
  What happened instead of the expected result?
  How did the issue look like?

  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
    list for all releases: http://docs.openstack.org/releases/

     If this is from a distro please provide
         $ dpkg -l | grep nova
         or
         $ rpm -ql | grep nova
     If this is from git, please provide
         $ git log -1

  2. Which hypervisor did you use?
     (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
     What's the version of that?

  2. Which storage type did you use?
     (For example: Ceph, LVM, GPFS, ...)
     What's the version of that?

  3. Which networking type did you use?
     (For example: nova-network, Neutron with OpenVSwitch, ...)

  Logs & Configs
  ==============
  The tool *sosreport* has support for some OpenStack projects.
  It's worth having a look at it. For example, if you want to collect
  the logs of a compute node you would execute:

     $ sudo sosreport -o openstack_nova --batch

  on that compute node. Attach the logs to this bug report. Please
  consider that these logs need to be collected in "DEBUG" mode.
  This bug contains information that is:
  PublicEdit

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