Jira (FACT-3011) Facter 3 does not detect the type of xvda disks on Amazon 6 OSes

[Mihai Buzgau (Jira)]

Mihai Buzgau created an issue

Facter / FACT-3011 Facter 3 does not detect the type of xvda disks on Amazon 6 OSes Issue Type: Bug Assignee: Unassigned Components: Facter 3 Created: 2021/04/14 11:51 PM Labels: knownissue Priority: Normal Reporter: Mihai Buzgau Facter 3 does not detect the type of xvda type disks on Amazon 6 VMs: Output from Puppet facts diff:         {         "disks.xvda.type": {           "new_value": "ssd",           "old_value": null         }       }   Add Comment

This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)

[Mihai Buzgau (Jira)]

Mihai Buzgau updated an issue

Facter / FACT-3011 Facter 3 does not detect the type of xvda disks on Amazon 6 OSes

Change By: Mihai Buzgau Facter 3 does not detect the type of for xvda type disks on Amazon 6 VMs:

Output from Puppet facts diff:

{code:java}

{         "disks.xvda.type": {           "new_value": "ssd",           "old_value": null         }

}{code}

Add Comment

[Claire Cadman (Jira)]

Claire Cadman updated an issue

Facter / FACT-3011 Facter 3 does not detect the type of xvda disks on Amazon 6 OSes

Change By: Claire Cadman Labels: doc_reviewed knownissue

Add Comment

[Claire Cadman (Jira)]

Claire Cadman updated an issue

Facter / FACT-3011 Facter 3 does not detect the type of xvda disks on Amazon 6 OSes

Change By: Claire Cadman Labels: doc_reviewed known-issue-added knownissue

Add Comment

[Josh Cooper (Jira)]

Josh Cooper commented on FACT-3011

Re: Facter 3 does not detect the type of xvda disks on Amazon 6 OSes Thank you for reporting this issue. While we agree this is likely an improvement, we do not anticipate addressing this any time soon due to other issues demanding precedence. As such, this ticket will be closed as “Won’t Do”. We may revisit this at a later time, and if so, will re-open this ticket. If you are interested in submitting a patch to implement this issue, please open a pull request and re-open this ticket.

Add Comment

This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)