yahoo-eng-team team mailing list archive

[Salomon Tseng <1654188@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I noticed that instances' config drive would been tried to import into
image backend and local disk.config file is to be deleted if image
backend is RBD.

All functions work as expected, what puzzled me once is that the nova-compute log claimed:
[instance: b54f657b-268c-438a-ba48-a6ee9de0fd8d] Using config drive
[instance: b54f657b-268c-438a-ba48-a6ee9de0fd8d] Creating config drive at /var/lib/nova/instances/b54f657b-268c-438a-ba48-a6ee9de0fd8d/disk.config

but this file didn't exist actually.

I figured out that it had been imported into RBD backend and deleted
from local after I read related code. I'm worried this may confuse some
cloud administrators who don't read source codes.

Maybe it's better to print info log before the config drive is to be imported into image backend and deleted from local, just as the following:
[instance: b54f657b-268c-438a-ba48-a6ee9de0fd8d] Using config drive
[instance: b54f657b-268c-438a-ba48-a6ee9de0fd8d] Creating config drive at /var/lib/nova/instances/b54f657b-268c-438a-ba48-a6ee9de0fd8d/disk.config
[instance: b54f657b-268c-438a-ba48-a6ee9de0fd8d] Importing config drive into image backend at 192.168.120.241:vms/b54f657b-268c-438a-ba48-a6ee9de0fd8d_disk.config
[instance: b54f657b-268c-438a-ba48-a6ee9de0fd8d] Deleting local config drive /var/lib/nova/instances/b54f657b-268c-438a-ba48-a6ee9de0fd8d/disk.config

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: config-drive

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

Title:
  nova compute log misleading config drvie's state

Status in OpenStack Compute (nova):
  New

Bug description:
  I noticed that instances' config drive would been tried to import into
  image backend and local disk.config file is to be deleted if image
  backend is RBD.

  All functions work as expected, what puzzled me once is that the nova-compute log claimed:
  [instance: b54f657b-268c-438a-ba48-a6ee9de0fd8d] Using config drive
  [instance: b54f657b-268c-438a-ba48-a6ee9de0fd8d] Creating config drive at /var/lib/nova/instances/b54f657b-268c-438a-ba48-a6ee9de0fd8d/disk.config

  but this file didn't exist actually.

  I figured out that it had been imported into RBD backend and deleted
  from local after I read related code. I'm worried this may confuse
  some cloud administrators who don't read source codes.

  Maybe it's better to print info log before the config drive is to be imported into image backend and deleted from local, just as the following:
  [instance: b54f657b-268c-438a-ba48-a6ee9de0fd8d] Using config drive
  [instance: b54f657b-268c-438a-ba48-a6ee9de0fd8d] Creating config drive at /var/lib/nova/instances/b54f657b-268c-438a-ba48-a6ee9de0fd8d/disk.config
  [instance: b54f657b-268c-438a-ba48-a6ee9de0fd8d] Importing config drive into image backend at 192.168.120.241:vms/b54f657b-268c-438a-ba48-a6ee9de0fd8d_disk.config
  [instance: b54f657b-268c-438a-ba48-a6ee9de0fd8d] Deleting local config drive /var/lib/nova/instances/b54f657b-268c-438a-ba48-a6ee9de0fd8d/disk.config

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