Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

salt.module.mdadm.create fails on debian, probably others #15532

Closed
drawks opened this issue Sep 4, 2014 · 4 comments
Closed

salt.module.mdadm.create fails on debian, probably others #15532

drawks opened this issue Sep 4, 2014 · 4 comments
Labels
Bug broken, incorrect, or confusing behavior Core relates to code central or existential to Salt info-needed waiting for more info P3 Priority 3 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Milestone

Comments

@drawks
Copy link

drawks commented Sep 4, 2014

Due to mdadm's insistence on prompting to continue after displaying the following warning:

mdadm: Note: this array has metadata at the start and
    may not be suitable as a boot device.  If you plan to
    store '/boot' on this device please ensure that
    your boot-loader understands md/v1.x metadata, or use
    --metadata=0.90
Continue creating array?

when creating any array even when specifying the --force flag the creation of arrays with mdadm will always fail unless the metadata version is explicitly set with the --metadata flag. The default behavior is to choose default metadata version, which is 1.2, on most recent platforms as of this writing. If mdadm is called with --metadata=default the warning and continue prompt are not displayed. However making this the default behavior makes it impossible to then pass a different value to the metadata flag when calling the module.

So, IMHO, the metadata flag of mdadm should be promoted to a named option of this module that defaults to the value default.

@basepi
Copy link
Contributor

basepi commented Sep 5, 2014

Agreed! Thanks for fixing this!

@basepi basepi added Bug labels Sep 5, 2014
@basepi basepi added this to the Approved milestone Sep 5, 2014
thatch45 added a commit that referenced this issue Sep 6, 2014
Resolve issue #15532 set metadata to mdadm
@arroyoc
Copy link

arroyoc commented Jun 30, 2015

@drawks, It looks like this was fixed with #15533. If so feel free to close it.

@arroyoc arroyoc added info-needed waiting for more info P3 Priority 3 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around Core relates to code central or existential to Salt and removed severity-low 4th level, cosemtic problems, work around exists labels Jun 30, 2015
@drawks
Copy link
Author

drawks commented Jun 30, 2015

ah yes, fixed

@drawks drawks closed this as completed Jun 30, 2015
@arroyoc
Copy link

arroyoc commented Jun 30, 2015

@drawks, Great! Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior Core relates to code central or existential to Salt info-needed waiting for more info P3 Priority 3 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Projects
None yet
Development

No branches or pull requests

3 participants