Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN

[Josh Cooper (Jira)]

Title: Message Title

Josh Cooper updated an issue   Facter / FACT-2882 Gem-based Facter 4.0.x does not return the complete FQDN Change By: Josh Cooper The gem-based facter 4.0.x does not return the correct fqdn – it returns the hostname with dot instead of returning hostname with the domain suffix. Example: facter fqdn Output: myhostname. The correct output: myhostname.mydomain.com This breaks scripts which issue http request to the fqdn (like: [http://myhostname.:1234|http://myhostname.:1234/] is not reachable). ---- Add new os support on litmus modules *Before to start, make sure the new platform is provided by vmpooler and it's fully equipped* *an image with the new os is available from puppet agent team* [Here|https://confluence.puppetlabs.com/display/ECO/How+to+add+support+for+new+platforms] you can find a list with all the converted modules to use litmus Step1: Using pdksync, check/update metadata.json, ci-job-configs/jenkii/platform/projects/modules-unified.yaml *metadata.json file* - check for section: operatingsystem_support - add new version under the intended operatingsystem and save *[ci-job-configs/jenkii/platform/projects/modules-unified.yaml|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/modules-unified.yaml]* - check for the module and add new platform under smoke_platforms| pe_platforms (if this platform was released) Step2: Using pdksync, create PR with the changes on modules Step3: Create PR on [ci-job-configs|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/modules-unified.yaml] Step4: Deploy experimental platform intended module Step5: Run ad-hoc tests using that experimental Step6: Check testing results Step7: If failures, fix them, re-execute all the testing part until they are green Step8: Ask for review/merge (-) check for vmpooler platform (-) pdksync: update metadata.json (-) pdksync: push changes, create commit (-) create PR on ci-job-configs (-) deploy experimental platform intended module (-) run tests through ad-hoc jenkins using that experimental (-) check testing report (-) if failures, fix them, re-execute ad-hoc until they are green (-) review/merge PR Add Comment   This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379598.1606874598000.89823.1606936320480%40Atlassian.JIRA.