Jira (FACT-3069) Facter 4.x on MS Azure: wrong domain is used in FQDN

[Sanjay Tripathi (Jira)]

Sanjay Tripathi created an issue

Facter / FACT-3069 Facter 4.x on MS Azure: wrong domain is used in FQDN Issue Type: Bug Affects Versions: FACT 4.0.44 Assignee: Unassigned Components: Facter 4 Created: 2021/08/31 9:50 AM Priority: Blocker Reporter: Sanjay Tripathi Facter 4.x on MS Azure: wrong domain is used in FQDN When running Facter 4.0.49 on MicroSoft Azure, instead of using the actual DNS domain, the Azure's default DNS suffix: reddog.microsoft.com is being used: Facter: fact "domain" has resolved to: reddog.microsoft.com Facter: fact "networking.fqdn" has resolved to: myhost.reddog.microsoft.com Facter: fact "fqdn" has resolved to: myhost.reddog.microsoft.com The actual DNS domain is: mydomain.mytld The DNS does not have myhost.reddog.microsoft.com, so any network request to the bad FQDN fails. Whereas Facter 3.x has the correct domain on the same Azure environment: Facter: fact "domain" has resolved to "mydomain.mytld" Facter: fact "fqdn" has resolved to "myhost.mydomain.mytld". Add Comment

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

[Ciprian Badescu (Jira)]

Ciprian Badescu commented on FACT-3069

Re: Facter 4.x on MS Azure: wrong domain is used in FQDN Sanjay Tripathi, on which OS is this happening?

Add Comment

[Sanjay Tripathi (Jira)]

Sanjay Tripathi commented on FACT-3069

Re: Facter 4.x on MS Azure: wrong domain is used in FQDN

The OS is Windows 2019.

Add Comment

[Sanjay Tripathi (Jira)]

Sanjay Tripathi commented on FACT-3069

Re: Facter 4.x on MS Azure: wrong domain is used in FQDN

Facter 4.x's domain and FQDN are incorrect on Windows 2016 DataCenter running on AWS: In one AWS environment on Windows 2016 DataCenter: Facter logs the correct hostname and domain in the "Managed to read" debug line: Facter: Managed to read hostname: myhost and domain: mydomain.mytld But the following are incorrect: Facter: fact "networking.domain" has resolved to: ec2.internal Facter: fact "domain" has resolved to: ec2.internal Facter: fact "networking.fqdn" has resolved to: myhost.ec2.internal Facter: fact "fqdn" has resolved to: myhost.ec2.internal -------------------- In another AWS environment on Windows 2016 DataCenter: In this environment, too, Facter logs the correct hostname and domain in the "Managed to read" debug line: Facter: Managed to read hostname: myhost and domain: mydomain.mytld But the following are incorrect: Facter: fact "networking.domain" has resolved to: mydomain1.mytld1 mysubdomain1.mydomain2.mytld2 mysubdomain2.mydomain1.mytld1 Facter: fact "domain" has resolved to: mydomain1.mytld1 mysubdomain1.mydomain2.mytld2 mysubdomain2.mydomain1.mytld1 Facter: fact "networking.fqdn" has resolved to: myhost.mydomain1.mytld1 mysubdomain1.mydomain2.mytld2 mysubdomain2.mydomain1.mytld1 Facter: fact "fqdn" has resolved to: myhost.mydomain1.mytld1 mysubdomain1.mydomain2.mytld2 mysubdomain2.mydomain1.mytld1 (Note that the output has multiple domain suffixes, separated by spaces) Should a separate ticket be logged for AWS?

Add Comment

[Sanjay Tripathi (Jira)]

Sanjay Tripathi commented on FACT-3069

Re: Facter 4.x on MS Azure: wrong domain is used in FQDN

Is there an ETA for fixing these Facter 4.x issues with discovering domain and FQDN on Azure and AWS?

Add Comment

[Sanjay Tripathi (Jira)]

Sanjay Tripathi commented on FACT-3069

Re: Facter 4.x on MS Azure: wrong domain is used in FQDN

Hello, Is there any update about this ticket? It affects all Azure and AWS environments.

Add Comment

[Ciprian Badescu (Jira)]

Ciprian Badescu updated an issue

Facter / FACT-3069

Facter 4.x on MS Azure: wrong domain is used in FQDN

Change By: Ciprian Badescu Labels: needs_repro

Add Comment

[Gabriel Nagy (Jira)]

Gabriel Nagy commented on FACT-3069

Re: Facter 4.x on MS Azure: wrong domain is used in FQDN Hi Sanjay Tripathi, we're going to start looking over this. This happening on both Azure and AWS might be linked to the fact that the Windows flavor is DataCenter, so there shouldn't be a separate ticket for that.

Add Comment

[Gabriel Nagy (Jira)]

Gabriel Nagy commented on FACT-3069

Re: Facter 4.x on MS Azure: wrong domain is used in FQDN

Sanjay Tripathi it's likely that you are hitting the same issue fixed in https://tickets.puppetlabs.com/browse/FACT-2923. Is this error reproducible with the latest puppet-agent/facter?

Add Comment

[Sanjay Tripathi (Jira)]

Sanjay Tripathi commented on FACT-3069

Re: Facter 4.x on MS Azure: wrong domain is used in FQDN

We are on 4.0.49 with Puppet agent 6.16. Should we try https://rubygems.org/gems/facter/versions/4.2.4 ?

Add Comment

[Ciprian Badescu (Jira)]

Ciprian Badescu commented on FACT-3069

Re: Facter 4.x on MS Azure: wrong domain is used in FQDN

I'm not sure that you can simply update the gem. Can you try puppet 6.21.1 or newer?

Add Comment

[Sanjay Tripathi (Jira)]

Sanjay Tripathi commented on FACT-3069

Re: Facter 4.x on MS Azure: wrong domain is used in FQDN

We use open-source Puppet Agent 6.16.0 with Facter 4.0.49. In our setup, we can update just the Facter gem. If this issue is resolved in higher Facter 4.x versions (actually, looks like FACT-2923 was fixed in 4.0.50), we can try https://rubygems.org/gems/facter/versions/4.2.4 . Please confirm.

Add Comment

[Ciprian Badescu (Jira)]

Ciprian Badescu commented on FACT-3069

Re: Facter 4.x on MS Azure: wrong domain is used in FQDN

Hi Sanjay Tripathi, You can try to manually update the facter gem, but this is not something that we tested or support. We recommend you to upgrade to latest open-source puppet-agent version or at least 6.21.1. Since the problem is known and already addressed in newer versions, I will close this ticket.

Add Comment