Bug #706

DEFAULT_DEVICE_PREFIX in oned.conf doesn't work

Added by Tino Vázquez over 9 years ago. Updated over 9 years ago.

Status:ClosedStart date:07/05/2011
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

Category:Core & System
Target version:Release 3.0
Resolution:invalid Pull request:
Affected Versions:

Description

You can just set the default device prefix it in the DISK section of the VM

History

#1 Updated by Ruben S. Montero over 9 years ago

  • Target version set to Release 3.0

#2 Updated by Ruben S. Montero over 9 years ago

  • Category set to Core & System
  • Assignee set to Carlos Martín

#3 Updated by Carlos Martín over 9 years ago

  • Status changed from New to Closed
  • Resolution set to invalid

This looks more like a misunderstanding than a bug.

The DEFAULT_DEVICE_PREFIX works as explained in the oned.conf documentation

Default value for DEV_PREFIX field when it is omitted in a template

The DEFAULT_DEVICE_PREFIX fills the DEV_PREFIX attribute for new Images that don't have it set in the template, so changing it in oned.conf only affects new Images. Maybe this is not the expected behaviour from the above description, we'll update the doc. to make it clear.

Also available in: Atom PDF