[Yahoo-eng-team] [Bug 984996] Re: Instance directory does not exist: Unable to pre-create chardev file console.log

2015-06-24 Thread Thierry Carrez
** Changed in: nova Status: Fix Committed = Fix Released ** Changed in: nova Milestone: None = liberty-1 -- 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/984996

[Yahoo-eng-team] [Bug 984996] Re: Instance directory does not exist: Unable to pre-create chardev file console.log

2015-04-23 Thread Thierry Carrez
** Changed in: nova/kilo Status: Fix Committed = Fix Released -- 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/984996 Title: Instance directory does not exist:

[Yahoo-eng-team] [Bug 984996] Re: Instance directory does not exist: Unable to pre-create chardev file console.log

2015-04-21 Thread Thierry Carrez
** Also affects: nova/kilo Importance: Undecided Status: New ** Changed in: nova/kilo Milestone: None = kilo-rc2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova).

[Yahoo-eng-team] [Bug 984996] Re: Instance directory does not exist: Unable to pre-create chardev file console.log

2015-04-13 Thread Matt Riedemann
We're also seeing this in the aiopcpu job during block live migration: http://logs.openstack.org/14/172614/13/experimental/check-tempest-dsvm- aiopcpu- full/599095f/logs/10.209.0.151-subnode/screen-n-cpu.txt.gz?level=TRACE#_2015-04-11_19_32_41_959 The error was also mentioned with live migrate

[Yahoo-eng-team] [Bug 984996] Re: Instance directory does not exist: Unable to pre-create chardev file console.log

2014-12-16 Thread Justin Shepherd
Marking this bug as invalid. 1. It was filed against folsom 2. Bug has not been updated in over 8 months, since last update ** Changed in: nova Status: Confirmed = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to