Booting Instance and accessing console-log throws nova-api error

[Sai Sindhur Malleni]

On booting a nova instance and immediately trying to access the console-log using nova console-log, an error message reporting an unexpected API Error is seen in a Mitaka-Stable environment. The Nova API Log is as follows : http://paste.openstack.org/show/508203/

[Sean Dague (sdague)]

You are trying to access a console on a server before it is ACTIVE?

[Sai Sindhur Malleni (smalleni)]

Not really, trying to access console when the instance is not active(spawning) should return an error like this
[stack@manager ~]$ nova console-log 9d928976-47e4-4c84-8fc8-aa8bddb2b5dd
ERROR (NotFound): Instance instance-000004b1 could not be found. (HTTP 404) (Request-ID: req-c5a452e1-364a-461d-a87f-2df8ef94850d)
But what i was seeing was different as can be seen in the log.

[stgleb (gstepanov)]

It actually tries to access log file created by libvirt, but it is not already created.
I will try to do something with that.

[Jay Pipes (jaypipes)]

Gleb is no longer working on OpenStack, so set to New and unassigned him.

[Tao Li (eric-litao)]

I tried several times and could‘t reproduce your error。 If the console does not existed，the ‘nova console-log xxx’ returns empty。and If the instance is spawning， the cli returns the content of console file despite of the file content is partial.
I think the error occured arising from one of these reasons.
1. The system configration. If it occured in centos, you should ensure selinux disabled etc.
2. Some unkonwn operation removed the file before chowning it.

This is the log that i tested it in attachment.

[Sean Dague (sdague)]

There is a failure to reproduce here, marking incomplete

[Sean Dague (sdague)]

Automatically discovered version mitaka in description. If this is incorrect, please update the description to include 'nova version: ...'

[Launchpad Janitor (janitor)]

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