Comment 36 for bug 1562249
Revision history for this message
| Wesley Wiedenmeier (wesley-wiedenmeier) wrote | #36 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Hi DeeVee,
Could you please post the configuration that was given to curtin when you installed? You can ask maas for the configuration with:
maas <session> node get-curtin-config <system-id>
I believe that what happened in your case was that 'id' attribute for the disk at path '/dev/cciss/c0d0' was 'cciss/c0d0', which has a slash in it. Due to the way curtin generates dname rules, a slash in the id of a device with a name attribute would cause curtin to be unable to write a dname rule link file, as the OS would interpret the slash as a new directory instead of just part of the filename.
If this is the case, then we have to decide whether it would be better for curtin to replace a slash in the id attribute for storage config elements when generating dname rules or for maas not to emit storage config ids with special characters.