ramdisk init fragments should be numbered
Bug #1251706 reported by
Chris Jones
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Right now we assemble all the ramdisk init fragments with a simple loop over an "ls". This means that we are assembling the init script in alphabetical order, which is good.
What is not good is that the various init fragments we ship, are not carrying prefixed numbers, so there is no obvious way for element authors to force their functionality to happen at a particular point in the process (e.g. forcing a network driver kernel module to load before the deploy element starts trying to use the network card)
| Changed in tripleo: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Roman Podoliaka (rpodolyaka) wrote | #1 |
| Changed in tripleo: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
https:/