← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1631960] Re: An unexpected API error when booting a server with resonable parameters.

 

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

-- 
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/1631960

Title:
  An unexpected API error when booting a server with resonable
  parameters.

Status in OpenStack Compute (nova):
  Expired

Bug description:
  I get an unexpected API error when I boot a server with nova boot.
  Before this, I list flavors and images. I think my parameters are
  resonaable. As follows:

  wh@ubuntu:~/devstack$ nova list
  +----+------+--------+------------+-------------+----------+
  | ID | Name | Status | Task State | Power State | Networks |
  +----+------+--------+------------+-------------+----------+
  +----+------+--------+------------+-------------+----------+
  wh@ubuntu:~/devstack$ nova flavor-list
  +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
  | ID | Name      | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
  +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
  | 1  | m1.tiny   | 512       | 1    | 0         |      | 1     | 1.0         | True      |
  | 2  | m1.small  | 2048      | 20   | 0         |      | 1     | 1.0         | True      |
  | 3  | m1.medium | 4096      | 40   | 0         |      | 2     | 1.0         | True      |
  | 4  | m1.large  | 8192      | 80   | 0         |      | 4     | 1.0         | True      |
  | 42 | m1.nano   | 64        | 0    | 0         |      | 1     | 1.0         | True      |
  | 5  | m1.xlarge | 16384     | 160  | 0         |      | 8     | 1.0         | True      |
  | 84 | m1.micro  | 128       | 0    | 0         |      | 1     | 1.0         | True      |
  | c1 | cirros256 | 256       | 0    | 0         |      | 1     | 1.0         | True      |
  | d1 | ds512M    | 512       | 5    | 0         |      | 1     | 1.0         | True      |
  | d2 | ds1G      | 1024      | 10   | 0         |      | 1     | 1.0         | True      |
  | d3 | ds2G      | 2048      | 10   | 0         |      | 2     | 1.0         | True      |
  | d4 | ds4G      | 4096      | 20   | 0         |      | 4     | 1.0         | True      |
  +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
  wh@ubuntu:~/devstack$ glance image-list
  +--------------------------------------+---------------------------------+
  | ID                                   | Name                            |
  +--------------------------------------+---------------------------------+
  | dff7ce82-5453-427c-98b1-88422bf53e3c | cirros-0.3.4-x86_64-uec         |
  | 38fab68d-e787-45de-b022-10d70a24b2b9 | cirros-0.3.4-x86_64-uec-kernel  |
  | cb2a8ab4-a18c-48cc-817d-08d3caaf6659 | cirros-0.3.4-x86_64-uec-ramdisk |
  +--------------------------------------+---------------------------------+
  wh@ubuntu:~/devstack$ nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64-uec virtual_machine1
  ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
  <type 'exceptions.IOError'> (HTTP 500) (Request-ID: req-7ed777bb-c9e9-4ed8-bd7d-55470efaa8b5)

  And I feel strange about nova list command. Because it can list virtual_machine1 even an unexpected API error occurred. 
  Supplementary explanation:
  nova version:6.0.0
  My code is the latest master branch.
  Think for your help.

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


References