Jira (FACT-3020) Invalid value for NVMe partitions on Facter 3

10 views
Skip to first unread message

Mihai Buzgau (Jira)

unread,
Apr 15, 2021, 9:40:02 AM4/15/21
to puppe...@googlegroups.com
Mihai Buzgau created an issue
 
Facter / Bug FACT-3020
Invalid value for NVMe partitions on Facter 3
Issue Type: Bug Bug
Assignee: Unassigned
Components: Facter 3
Created: 2021/04/15 6:39 AM
Labels: knownissue
Priority: Normal Normal
Reporter: Mihai Buzgau

Invalid values for NVMe mountpoints on Facter 3.

 
puppet facts show mountpoints./
{
"mountpoints./":

{ "available": "5.74 GiB", "available_bytes": 6161899520, "capacity": "24.24%", "device": "PARTUUID=4ef7520f-474e-4d3e-a298-fe71ee0e99c5", "filesystem": "ext4", "options": [ "rw", "relatime", "discard" ], "size": "7.59 GiB", "size_bytes": 8150749184, "used": "1.84 GiB", "used_bytes": 1972072448 }

device should be "/dev/nvme0n1p1"and mount should be set to "/"

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

Gabriel Nagy (Jira)

unread,
Apr 16, 2021, 4:52:01 AM4/16/21
to puppe...@googlegroups.com
Gabriel Nagy commented on Bug FACT-3020
 
Re: Invalid value for NVMe partitions on Facter 3

This is not necessarily related to NVMe, but to devices that have PARTUUID in /proc/cmdline. Related facter 4 ticket: https://tickets.puppetlabs.com/browse/FACT-2829

Claire Cadman (Jira)

unread,
Apr 16, 2021, 5:37:02 AM4/16/21
to puppe...@googlegroups.com
Claire Cadman updated an issue
 
Change By: Claire Cadman
Labels: doc_reviewed knownissue

Claire Cadman (Jira)

unread,
Apr 16, 2021, 5:37:02 AM4/16/21
to puppe...@googlegroups.com
Claire Cadman updated an issue
Change By: Claire Cadman
Labels: doc_reviewed known-issue-added knownissue

Josh Cooper (Jira)

unread,
Apr 21, 2022, 1:37:02 PM4/21/22
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Invalid values for NVMe mountpoints on Facter 3.

  {noformat}
puppet facts show  mountpoints./
{
  "mountpoints./": {
    "available": "5.74 GiB",
    "available_bytes": 6161899520,
    "capacity": "24.24%",
    "device": "PARTUUID=4ef7520f-474e-4d3e-a298-fe71ee0e99c5",
    "filesystem": "ext4",
    "options": [
      "rw",
      "relatime",
      "discard"
    ],
    "size": "7.59 GiB",
    "size_bytes": 8150749184,
    "used": "1.84 GiB",
    "used_bytes": 1972072448
  }
{noformat}

device should be "/dev/nvme0n1p1"and mount should be set to "/"
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Atlassian logo

Josh Cooper (Jira)

unread,
Apr 21, 2022, 1:38:05 PM4/21/22
to puppe...@googlegroups.com
Josh Cooper commented on Bug FACT-3020
 
Re: Invalid value for NVMe partitions on Facter 3

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.

Reply all
Reply to author
Forward
0 new messages