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

win_format: allocation_unit_size has no effect #56961

Closed
iwhd opened this issue May 25, 2019 · 5 comments · Fixed by #56966
Closed

win_format: allocation_unit_size has no effect #56961

iwhd opened this issue May 25, 2019 · 5 comments · Fixed by #56966
Labels
affects_2.8 This issue/PR affects Ansible v2.8 bug This issue/PR relates to a bug. has_pr This issue has an associated PR. module This issue/PR relates to a module. support:community This issue/PR relates to code supported by the Ansible community. windows Windows community

Comments

@iwhd
Copy link

iwhd commented May 25, 2019

SUMMARY

When allocation_unit_size parameter is set, the partition is formatted with the default one instead

ISSUE TYPE
  • Bug Report
COMPONENT NAME

win_format

ANSIBLE VERSION
ansible 2.8.0
OS / ENVIRONMENT

Windows Server 2019

STEPS TO REPRODUCE

Run playbook with win_format module, where custom allocation unit size is set:

- name: Format partition
  win_format:
    drive_letter: D
    file_system: NTFS
    allocation_unit_size: 512
    full: False
EXPECTED RESULTS

Partition allocation size unit should be set to 512

ACTUAL RESULTS

Partition was formatted with default (4096) allocation size unit


TASK [Format partition] ***********************************************************************************************************
changed: [win2019] => {
    "changed": true, 
    "invocation": {
        "module_args": {
            "allocation_unit_size": 512, 
            "compress": null, 
            "drive_letter": "D", 
            "file_system": "NTFS", 
            "force": false, 
            "full": false, 
            "integrity_streams": null, 
            "label": null, 
            "large_frs": null, 
            "new_label": null, 
            "path": null
        }
    }
}

TASK [debug] ***********************************************************************************************************
ok: [win2019] => {
    "ansible_facts.disks[1].partitions[0].volumes[0]": {
        "allocation_unit_size": 4096, 
        "drive_type": "Fixed", 
        "health_status": "Healthy", 
        "label": "", 
        "object_id": "{1}\\\\win2019\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{c2b6d3ca-7f00-11e9-b427-806e6f6e6963}:VO:\\\\?\\Volume{509328f7-0000-0000-0000-100000000000}\\\"", 
        "path": "\\\\?\\Volume{509328f7-0000-0000-0000-100000000000}\\", 
        "size": 85897244672, 
        "size_remaining": 85794185216, 
        "type": "NTFS"
    }
}

@ansibot
Copy link
Contributor

ansibot commented May 25, 2019

Files identified in the description:

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

@ansibot
Copy link
Contributor

ansibot commented May 25, 2019

@ansibot ansibot added affects_2.8 This issue/PR affects Ansible v2.8 bug This issue/PR relates to a bug. module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. support:community This issue/PR relates to code supported by the Ansible community. windows Windows community labels May 25, 2019
@varunchopra
Copy link

varunchopra commented May 26, 2019

This is just sad on my part. Fix for this soon.

Please test #56966 if possible and let me know if the issue persists.

@ansibot ansibot removed the needs_triage Needs a first human triage before being processed. label May 26, 2019
@iwhd
Copy link
Author

iwhd commented May 26, 2019

With changes from #56966 it works as expected.

@ansibot
Copy link
Contributor

ansibot commented Jun 3, 2019

@ansibot ansibot added the has_pr This issue has an associated PR. label Jul 29, 2019
@ansible ansible locked and limited conversation to collaborators Oct 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.8 This issue/PR affects Ansible v2.8 bug This issue/PR relates to a bug. has_pr This issue has an associated PR. module This issue/PR relates to a module. support:community This issue/PR relates to code supported by the Ansible community. windows Windows community
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants