You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TASK [scm : set_fact] *************************************************************************************************************************************************************************
task path: /home/deploy/cloudera-playbook/roles/scm/tasks/cms.yml:9
fatal: [cdh1.dev]: FAILED! => {
"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute u'cdh1.dev'\n\nThe error appears to be in '/home/deploy/cloudera-playbook/roles/scm/tasks/cms.yml': line 9, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- set_fact:\n ^ here\n"
}
The text was updated successfully, but these errors were encountered:
xerox-xeon
changed the title
kdb5_util: Improper format of Kerberos configuration file while initializing Kerberos code
The task includes an option with an undefined variable.
Aug 2, 2020
If the list of hosts is empty then this suggests that the Cloudera Manager agents may not be able to report in and register. If you log into Cloudera Manager is the list of hosts empty? Check the agent logs to see if there's any indication there as to why they are unable to register with the server.
TASK [scm : set_fact] *************************************************************************************************************************************************************************
task path: /home/deploy/cloudera-playbook/roles/scm/tasks/cms.yml:9
fatal: [cdh1.dev]: FAILED! => {
"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute u'cdh1.dev'\n\nThe error appears to be in '/home/deploy/cloudera-playbook/roles/scm/tasks/cms.yml': line 9, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- set_fact:\n ^ here\n"
}
The text was updated successfully, but these errors were encountered: