Jira (FACT-3204) Facter networking_facts_with_vlans.rb tests failing on ubuntu 22.04
Title: Message Title
Aria Li updated an issue
Facter / FACT-3204
Facter networking_facts_with_vlans.rb tests failing on ubuntu 22.04
Change By:
Aria Li
Output when test is passing (see passing build [here|https://jenkins-platform.delivery.puppetlabs.net/job/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME=facter,SLAVE_LABEL=k8s-beaker,TEST_TARGET=ubuntu2204-64a/1040/consoleText]):{code:java}top-printing.vmpooler-prod.puppet.net (top-printing.vmpooler-prod.puppet.net) 23:27:12$ facter networking --json ..."ens4.1": { "bindings": [{ "address": "11.0.0.1", "netmask": "255.255.255.0", "network": "11.0.0.0"} ], "ip": "11.0.0.1", "mac": "42:01:0a:fd:20:6d", "mtu": 1460, "netmask": "255.255.255.0", "network": "11.0.0.0"},{code}Output, as of recently, when test is failing (see failing build [here|https://jenkins-platform.delivery.puppetlabs.net/job/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME=facter,SLAVE_LABEL=k8s-beaker,TEST_TARGET=ubuntu2204-64a/1047/consoleText]):{code:java}swank-attitude.vmpooler-prod.puppet.net (swank-attitude.vmpooler-prod.puppet.net) 10:46:10$ facter networking --json..."ens4.1": { "bindings6": [{ "address": "fe80::4001:aff:fefd:2047", "netmask": ":::::", "network": "fe80::", "scope6": "link", "flags": ["tentative","permanent" ]} ], "ip6": "fe80::4001:aff:fefd:2047", "mac": "42:01:0a:fd:20:47", "mtu": 1460, "netmask6": ":::::", "network6": "fe80::", "scope6": "link"},{code}This was first noticed when the puppet-agent main pipeline kept on failing at the vanagon integration step for the [ubuntu 22.04 facter|https://jenkins-platform.delivery.puppetlabs.net/job/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME=facter,SLAVE_LABEL=k8s-beaker,TEST_TARGET=ubuntu2204-64a/] cell.The build is failing at the [networking_facts_with_vlabs.rb|https://github.com/puppetlabs/facter/blob/main/acceptance/tests/facts/networking_facts_with_vlans.rb#L33] test because the values within the ens4.1 hash do not match the [ regex |https://github . com/puppetlabs/facter/blob/d9d8324b02c26be2eb17a1d8ff26306a331431e2/acceptance/tests/facts/networking_facts_with_vlans.rb#L14-L15C77].
Jira (FACT-3204) Facter networking_facts_with_vlans.rb tests failing on ubuntu 22.04
Title: Message Title
Aria Li updated an issue
Facter / FACT-3204
Facter networking_facts_with_vlans.rb tests failing on ubuntu 22.04
Change By:
Aria Li
Output when test is passing (see passing build [here|https://jenkins-platform.delivery.puppetlabs.net/job/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME=facter,SLAVE_LABEL=k8s-beaker,TEST_TARGET=ubuntu2204-64a/1040/consoleText]): {code:java} top-printing.vmpooler-prod.puppet.net (top-printing.vmpooler-prod.puppet.net) 23:27:12$ facter networking --json ..."ens4.1": { "bindings": [{ "address": "11.0.0.1", "netmask": "255.255.255.0", "network": "11.0.0.0"} ], "ip": "11.0.0.1", "mac": "42:01:0a:fd:20:6d", "mtu": 1460, "netmask": "255.255.255.0", "network": "11.0.0.0"},{code}Output, as of recently, when test is failing (see failing build [here|https : //jenkins-platform.delivery.puppetlabs.net/job/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME=facter,SLAVE_LABEL=k8s-beaker,TEST_TARGET=ubuntu2204-64a/1047/consoleText]): {code:java} swank-attitude.vmpooler-prod.puppet.net (swank-attitude.vmpooler-prod.puppet.net) 10:46:10$ facter networking --json..."ens4.1": { "bindings6": [{ "address": "fe80::4001:aff:fefd:2047", "netmask": ":::::", "network": "fe80::", "scope6": "link", "flags": ["tentative","permanent" ]} ], "ip6": "fe80::4001:aff:fefd:2047", "mac": "42:01:0a:fd:20:47", "mtu": 1460, "netmask6": ":::::", "network6": "fe80::", "scope6": "link"},{code} This was first noticed when the puppet-agent main pipeline kept on failing at the vanagon integration step for the [ubuntu 22.04 facter|https://jenkins-platform.delivery.puppetlabs.net/job/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME=facter,SLAVE_LABEL=k8s-beaker,TEST_TARGET=ubuntu2204-64a/] cell.The build is failing at the [networking_facts_with_vlabs.rb|https://github.com/puppetlabs/facter/blob/main/acceptance/tests/facts/networking_facts_with_vlans.rb#L33] test because the values within the ens4.1 hash do not match the regex.
Jira (FACT-3204) Facter networking_facts_with_vlans.rb tests failing on ubuntu 22.04
Title: Message Title
Aria Li created an issue
Facter / FACT-3204
Facter networking_facts_with_vlans.rb tests failing on ubuntu 22.04
Issue Type:
Bug
Assignee:
Unassigned
Created:
2023/05/19 3:18 PM
Priority:
Normal
Reporter:
Aria Li
Output when test is passing (see passing build here):
top-printing.vmpooler-prod.puppet.net (top-printing.vmpooler-prod.puppet.net) 23:27:12$ facter networking --json
...
"ens4.1": {
"bindings": [
{
"address": "11.0.0.1",
"netmask": "255.255.255.0",
Jira (PDB-5646) Remove fake_platform from puppetdb pipelines
Title: Message Title Aria Li created an issue PuppetDB / PDB-5646 Remove fake_platform from puppetdb pipelines Issue Type: Task Assignee: Unassigned Created: 2023/05/19 1:50 PM Labels: os Priority: Normal Reporter: Aria Li Remove fake_platform from the puppetdb pipelines defined in jenkii/enterprise/projects/puppetdb.yaml in ci-job-configs. Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Jira (PDB-5646) Remove fake_platform from puppetdb pipelines
Title: Message Title Aria Li updated an issue PuppetDB / PDB-5646 Remove fake_platform from puppetdb pipelines Change By: Aria Li Epic Link: PA-5476 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.485905.168452942.851.1684529460245%40Atlassian.JIRA.
Jira (PUP-11858) 11. Update Public-facing Puppet docs to remove fake_platform
Title: Message Title Aria Li created an issue Puppet / PUP-11858 11. Update Public-facing Puppet docs to remove fake_platform Issue Type: Task Assignee: Unassigned Created: 2023/05/19 1:50 PM Labels: os Priority: Normal Reporter: Aria Li See https://github.com/puppetlabs/ci-job-configs/wiki/Removing-Platform(s)-From-puppet-agent#11-update-public-facing-puppet-docs Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Jira (PUP-11858) 11. Update Public-facing Puppet docs to remove fake_platform
Title: Message Title Aria Li updated an issue Puppet / PUP-11858 11. Update Public-facing Puppet docs to remove fake_platform Change By: Aria Li Epic Link: PA-5476 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.485903.1684529418000.849.1684529460150%40Atlassian.JIRA.
Jira (FACT-3186) facter 4.2.13: bug "facter partitions"
Title: Message Title Michael Hashizume updated an issue Facter / FACT-3186 facter 4.2.13: bug "facter partitions" Change By: Michael Hashizume Sprint: Phoenix 2023- 06 05 - 07 24 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481372.1676386915000.847.1684529280049%40Atlassian.JIRA.
Jira (FACT-3186) facter 4.2.13: bug "facter partitions"
Title: Message Title Michael Hashizume assigned an issue to Michael Hashizume Facter / FACT-3186 facter 4.2.13: bug "facter partitions" Change By: Michael Hashizume Assignee: Michael Hashizume Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481372.1676386915000.846.1684528920025%40Atlassian.JIRA.
Jira (FACT-3178) Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC
Title: Message Title Aria Li updated an issue Facter / FACT-3178 Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC Change By: Aria Li Sprint: Phoenix 2023- 06 05 - 07 24 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.479125.1673888594000.600.1684512180145%40Atlassian.JIRA.
Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Saurabh Dikshit updated an issue PuppetDB / PDB-5633 Investigate why (some?) command discards aren't including the stack Change By: Saurabh Dikshit Zendesk Ticket Count: 1 2 Zendesk Ticket IDs: 51495 ,52057 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.484959.1682619597000.557.1684506960026%40Atlassian.JIRA.
Jira (PDB-5549) PuppetDB 7.11.1: /pdb/admin/v1/archive returns 257 bytes
Title: Message Title Sebastian Döring commented on PDB-5549 Re: PuppetDB 7.11.1: /pdb/admin/v1/archive returns 257 bytes Problem is still observed in 7.13.0-1bullseye Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.470699.1665479002000.416.1684487400023%40Atlassian.JIRA.
Jira (PUP-11857) Notify resource, unexpected behavior
Title: Message Title
Andrey Semenov updated an issue
Puppet / PUP-11857
Notify resource, unexpected behavior
Change By:
Andrey Semenov
*Puppet Version: 7.24.0**Puppet Server Version: 7.11.0**OS Name/Version: Ubuntu 20.04* {code:java}# TODOclass some::path { notify { 'False as message': message => false} # ==> Skipped resource notify { 'True as message': message => true} # ==> 'true' notify { 'Undef as message': message => undef} # ==> ''}include some::path{code} [https://www.puppet.com/docs/puppet/ 5.5 7 /types/notify.html#notify-attribute-message]The documentation says that message can only be a string.But if you pass false, you will get a very convenient mechanism for debugging information. To what extent is the use of false acceptable?*Desired Behavior:*I was expecting something like this{code:java}Error: Evaluation Error: Illegal title type at index 0. Expected String, got Boolean{code}*Actual Behavior:*{code:java}❯ puppet apply test.ppNotice: Compiled catalog for macbook-air-wilful.local in environment production in 0.02 secondsNotice: trueNotice: /Stage[main]/Some::Path/Notify[True as message]/message: defined 'message' as trueNotice: Undef as messageNotice: /Stage[main]/Some::Path/Notify[Undef as message]/message: defined 'message' as 'Undef as message'Notice: Applied catalog in 0.01 seconds{code}
Add Comment
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Jira (PUP-11857) Notify resource, unexpected behavior
Title: Message Title
Andrey Semenov updated an issue
Puppet / PUP-11857
Notify resource, unexpected behavior
Change By:
Andrey Semenov
*Puppet Version: 7.24.0**Puppet Server Version: 7.11.0**OS Name/Version: Ubuntu 20.04* {code:java}# TODOclass some::path { notify { 'False as message': message => false} # ==> Skipped resource notify { 'True as message': message => true} . # ==> 'true' notify { 'Undef as message': message => undef} # ==> ''}include some::path{code} [https://www.puppet.com/docs/puppet/5.5/types/notify.html#notify-attribute-message]The documentation says that message can only be a string.But if you pass false, you will get a very convenient mechanism for debugging information. To what extent is the use of false acceptable?*Desired Behavior:*I was expecting something like this{code:java}Error: Evaluation Error: Illegal title type at index 0. Expected String, got Boolean{code}*Actual Behavior:*{code:java}❯ puppet apply test.ppNotice: Compiled catalog for macbook-air-wilful.local in environment production in 0.02 secondsNotice: trueNotice: /Stage[main]/Some::Path/Notify[True as message]/message: defined 'message' as trueNotice: Undef as messageNotice: /Stage[main]/Some::Path/Notify[Undef as message]/message: defined 'message' as 'Undef as message'Notice: Applied catalog in 0.01 seconds{code}
Add Comment
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Jira (PUP-11857) Notify resource, unexpected behavior
Title: Message Title
Andrey Semenov updated an issue
Puppet / PUP-11857
Notify resource, unexpected behavior
Change By:
Andrey Semenov
*Puppet Version: 7.24.0**Puppet Server Version: 7.11.0**OS Name/Version: Ubuntu 20.04* {code:java} # TODOclass some::path \ { notify \ { 'False as message': message => false} # Ignore ==> Skipped resource ! notify \ { 'True as message': message => true} . # Show ` ==> ' true ` ' notify \ { 'Undef as message': message => undef} # Show `` ==> '' }include some::path {code} [https://www.puppet.com/docs/puppet/5.5/types/notify.html#notify-attribute-message]The documentation says that message can only be a string.But if you pass false, you will get a very convenient mechanism for debugging information. To what extent is the use of false acceptable?*Desired Behavior:*I was expecting something like this{code:java}Error: Evaluation Error: Illegal title type at index 0. Expected String, got Boolean{code}*Actual Behavior:*{code:java}❯ puppet apply test.ppNotice: Compiled catalog for macbook-air-wilful.local in environment production in 0.02 secondsNotice: trueNotice: /Stage[main]/Some::Path/Notify[True as message]/message: defined 'message' as trueNotice: Undef as messageNotice: /Stage[main]/Some::Path/Notify[Undef as message]/message: defined 'message' as 'Undef as message'Notice: Applied catalog in 0.01 seconds{code}
Add Comment
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Jira (PUP-11857) Notify resource, unexpected behavior
Title: Message Title
Andrey Semenov updated an issue
Puppet / PUP-11857
Notify resource, unexpected behavior
Change By:
Andrey Semenov
*Puppet Version: 7.24.0**Puppet Server Version: 7.11.0**OS Name/Version: Ubuntu 20.04* *```* {code:java} # TODOclass some::path \ { notify \{ 'False as message': message => false} # Ignore resource! notify \{ 'True as message': message => true} # Show `true` notify \{ 'Undef as message': message => undef} # Show ``}include some::path {code} *```* [https://www.puppet.com/docs/puppet/5.5/types/notify.html#notify-attribute-message]The documentation says that message can only be a string.But if you pass false, you will get a very convenient mechanism for debugging information. To what extent is the use of false acceptable?*Desired Behavior:*I was expecting something like this ``` {code:java} Error: Evaluation Error: Illegal title type at index 0. Expected String, got Boolean {code} ``` *Actual Behavior:* ``` {code:java} ❯ puppet apply test.ppNotice: Compiled catalog for macbook-air-wilful.local in environment production in 0.02 secondsNotice: trueNotice: /Stage[main]/Some::Path/Notify[True as message]/message: defined 'message' as trueNotice: Undef as messageNotice: /Stage[main]/Some::Path/Notify[Undef as message]/message: defined 'message' as 'Undef as message'Notice: Applied catalog in 0.01 seconds ``` {code}
Add Comment
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Jira (PUP-11857) Notify resource, unexpected behavior
Title: Message Title
Андрей Владимирович Семенов created an issue
Puppet / PUP-11857
Notify resource, unexpected behavior
Issue Type:
Bug
Assignee:
Unassigned
Components:
Docs, Language
Created:
2023/05/19 12:48 AM
Priority:
Normal
Reporter:
Андрей Владимирович Семенов
Puppet Version: 7.24.0 Puppet Server Version: 7.11.0 OS Name/Version: Ubuntu 20.04 ```
TODO class some::path { notify \{ 'False as message': message => false} # Ignore resource! notify { 'True as message': message => true} # Show `true` notify { 'Undef as message': message => undef} # Show `` }
include some::path ``` https://www.puppet.com/docs/puppet/5.5/types/notify.html#notify-attribute-message The documentation says that message can only be a string. But if you pass false, you will get a very convenient mechanism for debugging information. To what extent is the use of false acceptable? Desired Behavior: I was expecting something like this ``` Error: Evaluation Error: Illegal title type at index 0. Expected String, got Boolean ``` Actual Behavior: ``` ❯ puppet apply test.pp Notice: Compiled catalog for macbook-air-wilful.local in environment production in 0.02 seconds Notice: true Notice: /Stage[main]/Some::Path/Notify[True as message]/message: defined 'message' as true Notice: Undef as message Notice: /Stage[main]/Some::Path/Notify[Undef as message]/message: defined 'message' as 'Undef as message' Notice: Applied catalog in 0.01 seconds ```
