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

2022-04-21 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  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.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395615.1618493953000.15933.1650562680048%40Atlassian.JIRA.


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

2022-04-21 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3020  
 
 
  Invalid value for NVMe partitions on Facter 3   
 

  
 
 
 
 

 
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 "/"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

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

2021-04-16 Thread Claire Cadman (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claire Cadman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3020  
 
 
  Invalid value for NVMe partitions on Facter 3   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395615.1618493953000.11088.1618565820233%40Atlassian.JIRA.


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

2021-04-16 Thread Claire Cadman (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claire Cadman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3020  
 
 
  Invalid value for NVMe partitions on Facter 3   
 

  
 
 
 
 

 
Change By: 
 Claire Cadman  
 
 
Labels: 
 doc_reviewed knownissue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395615.1618493953000.11087.1618565820186%40Atlassian.JIRA.


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

2021-04-16 Thread Gabriel Nagy (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy commented on  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  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395615.1618493953000.11055.1618563120181%40Atlassian.JIRA.


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

2021-04-15 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3020  
 
 
  Invalid value for NVMe partitions on Facter 3   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Facter 3  
 
 
Created: 
 2021/04/15 6:39 AM  
 
 
Labels: 
 knownissue  
 
 
Priority: 
  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