PowerVC hostname is not being properly set at the time of deploy

PowerVC 2.1.1 cloud-init cloud-init-22.1-4.noarch

partitions was deployed with the hostname smolabtestdeploy105 and should have used available ip address 172.26.103.172

the hostname on the partition was set to ibmtst6 ipaddress 172.26.103.172 which is a reverse ip that still exists in DNS. 

If we are not using the Set host name from DNS why is it doing a reverse lookup during the deploy and setting the hostname to something that existed in DNS. 

We are not using DNS or DCHP during the deploy cloud.init.

The partition that is capture has an /etc/resolv.conf file

not using Set host name from DNS

preserve_hostname=false

removed update_hostname

set_hostname is still in cloud.cfg

here is my cloud.cfg file:

root@ibmtst6 #cat cloud.cfg
# The top level settings are used as module
# and system configuration.

# A set of users which may be applied and/or used by various modules
# when a 'default' entry is found it will reference the 'default_user'
# from the distro configuration specified below
users:
   - default

# If this is set, 'root' will not be able to ssh in and they
# will get a message to login instead as the above $user (ubuntu)
disable_root: false

# Allow SSH password authorization
ssh_pwauth: true

# Delete existing SSH host keys
ssh_deletekeys: true

# Regen rsa and dsa host keys
ssh_genkeytypes: ['rsa', 'dsa']

# This will cause the set+update hostname module to not operate (if true)
preserve_hostname: false

datasource_list: ['ConfigDrive']

# Example datasource config
# datasource:
#    Ec2:
#      metadata_urls: [ 'blah.com' ]
#      timeout: 5 # (defaults to 50 seconds)
#      max_wait: 10 # (defaults to 120 seconds)

# The modules that run in the 'init' stage
cloud_init_modules:
 - migrator
 - seed_random
 - bootcmd
 - write-files
 - set_hostname
 - update_etc_hosts
 - ca-certs
 - rsyslog
 - users-groups
 - ssh
 - restore-volume-groups
 - set-multipath-hcheck-interval
 - update-bootlist
 - reset-rmc

# The modules that run in the 'config' stage
cloud_config_modules:
# Emit the cloud config ready event
# this can be used by upstart jobs for 'start on cloud-config'.
 - emit_upstart
 - disk_setup
 - mounts
 - ssh-import-id
 - locale
 - set-passwords
 - package-update-upgrade-install
 - landscape
 - timezone
 - puppet
 - chef
 - salt-minion
 - mcollective
 - disable-ec2-metadata
 - runcmd
 - byobu

# The modules that run in the 'final' stage
cloud_final_modules:
 - rightscale_userdata
 - scripts-vendor
 - scripts-per-once
 - scripts-per-boot
 - scripts-per-instance
 - scripts-user
 - ssh-authkey-fingerprints
 - keys-to-console
 - phone-home
 - final-message
 - power-state-change

# System and/or distro specific settings
# (not accessible to handlers/transforms)
system_info:
   # This will affect which distro class gets used
   distro: aix
   # Default user name + that default users groups (if added/used)
   default_user:
     name: root
     lock_passwd: false
   # Other config here will be given to the distro class and/or path classes
   paths:
      cloud_dir: /opt/freeware/var/lib/cloud/
      templates_dir: /opt/freeware/etc/cloud/templates/
      upstart_dir: /etc/rc.d/init.d/
   ssh_svcname: ssh

How can i disable cloud.cfg / cloud-init from using DNS to set the hostname of a partition during the deploy process. 

I want the partition name to be set to what is entered into the vmname field on the depoloy menu.

I have not turned on the option in the cloud.cfg to use DNS but if there is a DNS server set up for the partition that is captured for the image then it uses DNS reguardless of what is set in the cloud.cfg file. 

 PowerVC hostname is not being properly set at the time of deploy

PowerVC 2.1.1 cloud-init cloud-init-22.1-4.noarch

partitions was deployed with the hostname smolabtestdeploy105 and should have used available ip address 172.26.103.172

the hostname on the partition was set to ibmtst6 ipaddress 172.26.103.172 which is a reverse ip that still exists in DNS. 

If we are not using the Set host name from DNS why is it doing a reverse lookup during the deploy and setting the hostname to something that existed in DNS. 

We are not using DNS or DCHP during the deploy cloud.init.

The partition that is capture has an /etc/resolv.conf file

not using Set host name from DNS

preserve_hostname=false

removed update_hostname

set_hostname is still in cloud.cfg

here is my cloud.cfg file:

root@ibmtst6 #cat cloud.cfg
# The top level settings are used as module
# and system configuration.

# A set of users which may be applied and/or used by various modules
# when a 'default' entry is found it will reference the 'default_user'
# from the distro configuration specified below
users:
   - default

# If this is set, 'root' will not be able to ssh in and they
# will get a message to login instead as the above $user (ubuntu)
disable_root: false

# Allow SSH password authorization
ssh_pwauth: true

# Delete existing SSH host keys
ssh_deletekeys: true

# Regen rsa and dsa host keys
ssh_genkeytypes: ['rsa', 'dsa']

# This will cause the set+update hostname module to not operate (if true)
preserve_hostname: false

datasource_list: ['ConfigDrive']

# Example datasource config
# datasource:
#    Ec2:
#      metadata_urls: [ 'blah.com' ]
#      timeout: 5 # (defaults to 50 seconds)
#      max_wait: 10 # (defaults to 120 seconds)

# The modules that run in the 'init' stage
cloud_init_modules:
 - migrator
 - seed_random
 - bootcmd
 - write-files
 - set_hostname
 - update_etc_hosts
 - ca-certs
 - rsyslog
 - users-groups
 - ssh
 - restore-volume-groups
 - set-multipath-hcheck-interval
 - update-bootlist
 - reset-rmc

# The modules that run in the 'config' stage
cloud_config_modules:
# Emit the cloud config ready event
# this can be used by upstart jobs for 'start on cloud-config'.
 - emit_upstart
 - disk_setup
 - mounts
 - ssh-import-id
 - locale
 - set-passwords
 - package-update-upgrade-install
 - landscape
 - timezone
 - puppet
 - chef
 - salt-minion
 - mcollective
 - disable-ec2-metadata
 - runcmd
 - byobu

# The modules that run in the 'final' stage
cloud_final_modules:
 - rightscale_userdata
 - scripts-vendor
 - scripts-per-once
 - scripts-per-boot
 - scripts-per-instance
 - scripts-user
 - ssh-authkey-fingerprints
 - keys-to-console
 - phone-home
 - final-message
 - power-state-change

# System and/or distro specific settings
# (not accessible to handlers/transforms)
system_info:
   # This will affect which distro class gets used
   distro: aix
   # Default user name + that default users groups (if added/used)
   default_user:
     name: root
     lock_passwd: false
   # Other config here will be given to the distro class and/or path classes
   paths:
      cloud_dir: /opt/freeware/var/lib/cloud/
      templates_dir: /opt/freeware/etc/cloud/templates/
      upstart_dir: /etc/rc.d/init.d/
   ssh_svcname: ssh