#8726 Provide a better error message with updatedns and FQDN Is not provided
Closed: fixed 2 years ago by frenaud. Opened 3 years ago by rcritten.

Issue

The --updatedns option for host-mod requires a FQDN otherwise an obscure error message is shown, 'idnsname' is required.

What it means is that a FQDN isn't key[0] so the zone can't be determined.

Steps to Reproduce

1.
$ ipa host-mod client --platform=linux --updatedns
ipa: ERROR: 'idnsname' is required


Metadata Update from @antorres:
- Issue assigned to antorres

3 years ago

Could you provide more info on how to reproduce? I can't reproduce it:

[root@master ~]# ipa host-add client.ipa.local --ip-address=10.0.139.223
-----------------------------
Added host "client.ipa.local"
-----------------------------
  Host name: client.ipa.local
  Principal name: host/client.ipa.local@IPA.LOCAL
  Principal alias: host/client.ipa.local@IPA.LOCAL
  Password: False
  Keytab: False
  Managed by: client.ipa.local

[root@master ~]# ipa host-mod client --platform=linux --updatedns
----------------------
Modified host "client"
----------------------
  Host name: client.ipa.local
  Platform: linux
  Principal name: host/client.ipa.local@IPA.LOCAL
  Principal alias: host/client.ipa.local@IPA.LOCAL
  Password: False
  Keytab: False
  Managed by: client.ipa.local

I tried again with a pretty recent master (d8b8f54) and I can reproduce this exactly as I reported it.

I don't know if using local as the tld is related or not but it's a special zone for use with multicast DNS. I use .test instead and that's where I the failure.

master:

  • 3a4939f host: try to resolve FQDN before command execution
  • 3e77d31 ipatests: test host update using shortname

ipa-4-9:

  • 48370cb host: try to resolve FQDN before command execution
  • 27a65a1 ipatests: test host update using shortname

Metadata Update from @frenaud:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata