问题

通过Ansible从遥控器执行NC检查

9个月前
2021年7月2日
0答复
48次观点

n-tchen
侦察
0答复

你好，

我试图通过所有簇在所有群集上通过Ansible执行NC检查，因为直到知道它由于缺失的防火墙解锁而失败。直到最后，它似乎还不错，如果没有说“失败”或“通过”（或类似的东西），而是“未能执行NCC ..”：：

“ stdout_lines”：[
“”，，
“ ###################################，，，，
“＃TIMESTAMP：07/02/2021 2:33:05 PM（UTC +0200）”，
“ ###################################，，，，
“ ncc_version：4.0.1-329829c4”，
“集群ID：7805490355129540044”，
“群集名称：gbru0010”，
“带有服务VM ID 5的节点”，
“服务VM外部IP：10.202.89.19”，
“管理程序地址列表：[U'10.202.89.15']”，
“管理程序版本：VMware ESXI 6.7.0 build-17700523”，
“ IPMI地址列表：[U'10.202.89.11']”，
“软件版本：Euphrates-5.15.1稳定”，
“软件更改ID：7D5E4BD69E8EEC8E9A87EAF0DFAD7A1D9ACA53CB”，
“节点序列：HM19BS006502”，
“机架单元：NX-1065-G7”，
“节点位置：a”，
“块S/N：20FM6L300208”，
“带有服务VM ID 6”的节点，
“服务VM外部IP：10.202.89.20”，
“管理程序地址列表：[U'10.202.89.16']”，
“管理程序版本：VMware ESXI 6.7.0 build-17700523”，
“ IPMI地址列表：[U'10.202.89.12']”，
“软件版本：Euphrates-5.15.1稳定”，
“软件更改ID：7D5E4BD69E8EEC8E9A87EAF0DFAD7A1D9ACA53CB”，
“节点序列：HM19CS004151”，
“机架单元：NX-1065-G7”，
“节点位置：b”，
“块S/N：20FM6L300208”，
“带有服务VM ID 7的节点”，
“服务VM外部IP：10.202.89.21”，
“管理程序地址列表：[U'10.202.89.17']”，
“管理程序版本：VMware ESXI 6.7.0 build-17700523”，
“ IPMI地址列表：[U'10.202.89.13']”，
“软件版本：Euphrates-5.15.1稳定”，
“软件更改ID：7D5E4BD69E8EEC8E9A87EAF0DFAD7A1D9ACA53CB”，
“节点序列：HM19CS002942”，
“机架单元：NX-1065-G7”，
“节点位置：C”，
“块S/N：20FM6L300208”，
“”，，
“运行：health_checks system_checks dns_server_check”，
“”，，
“ [===============================================] 100％”，
“”，，
“ \ u001b [91mfail toge ting ting ncc用参数执行：['/home/nutanix/ncc/bin/ncc'，'health_checks'，'system_checks'，'dns_server_check'] \ u001b [0m u001b [0m'

因此，“未能执行NCC”之前的所有内容看起来都不错，并且在Prism元素中，NC-RUN的任务似乎也很好，所以我想，只有我回来的输出才是问题。Ansible任务是：

- 名称：执行给定的NCC命令
贝壳：
CMD：“源/etc/bashrc &&〜/ncc/bin/ncc health_checks system_checks dns_server_check”
注册：ncc_output

一个与环境变量相处的播放很多，但无法获得适当的“通过”或“失败”输出，我需要/想要的。有人想从遥控器执行NC检查吗？

问候，
马克斯

Hello,<\/p>

I'm trying to execute a NC-Check via Ansible on all of our clusters, because till know it failed because of a missing firewall unlock. It seems to work kind of fine until the very end, were it does not say \"Failed\" or \"Passed\" (or something like that) but \"Failed to execute NCC..\":<\/p>

\u00a0<\/p>

\u00a0 \u00a0 \u00a0 \u00a0 \"stdout_lines\": [
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"//www.jhbzcj.com/next/how-it-works-22/\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"################################################\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"# TIMESTAMP : 07\/02\/2021 \u00a02:33:05 PM (UTC +0200)\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"################################################\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"ncc_version: 4.0.1-329829c4\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"cluster id: 7805490355129540044\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"cluster name: gbru0010\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"node with service vm id 5\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0service vm external ip: 10.202.89.19\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0hypervisor address list: [u'10.202.89.15']\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0hypervisor version: VMware ESXi 6.7.0 build-17700523\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0ipmi address list: [u'10.202.89.11']\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0software version: euphrates-5.15.1-stable\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0software changeset ID: 7d5e4bd69e8eec8e9a87eaf0dfad7a1d9aca53cb\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0node serial: HM19BS006502\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0rackable unit: NX-1065-G7\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0node position: A\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0block S\/N: 20FM6L300208\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"node with service vm id 6\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0service vm external ip: 10.202.89.20\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0hypervisor address list: [u'10.202.89.16']\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0hypervisor version: VMware ESXi 6.7.0 build-17700523\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0ipmi address list: [u'10.202.89.12']\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0software version: euphrates-5.15.1-stable\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0software changeset ID: 7d5e4bd69e8eec8e9a87eaf0dfad7a1d9aca53cb\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0node serial: HM19CS004151\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0rackable unit: NX-1065-G7\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0node position: B\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0block S\/N: 20FM6L300208\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"node with service vm id 7\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0service vm external ip: 10.202.89.21\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0hypervisor address list: [u'10.202.89.17']\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0hypervisor version: VMware ESXi 6.7.0 build-17700523\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0ipmi address list: [u'10.202.89.13']\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0software version: euphrates-5.15.1-stable\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0software changeset ID: 7d5e4bd69e8eec8e9a87eaf0dfad7a1d9aca53cb\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0node serial: HM19CS002942\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0rackable unit: NX-1065-G7\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0node position: C\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \" \u00a0 \u00a0block S\/N: 20FM6L300208\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"//www.jhbzcj.com/next/how-it-works-22/\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"Running : health_checks system_checks dns_server_check\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"//www.jhbzcj.com/next/how-it-works-22/\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"[==================================================] 100%\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"//www.jhbzcj.com/next/how-it-works-22/\",
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"\\u001b[91mFailed to execute NCC with arguments: ['\/home\/nutanix\/ncc\/bin\/ncc', 'health_checks', 'system_checks', 'dns_server_check']\\u001b[0m\"<\/code><\/pre>
So everything before \"Failed to execute NCC..\" looks good and in Prism Element the task\u00a0of the NC-Run seems also fine, so i guess, only the output i get back is the problem. The Ansible-Task is:<\/p>
\u00a0 \u00a0 \u00a0 \u00a0 - name: Execute the given NCC-Command
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 shell:
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 cmd: \"source \/etc\/bashrc && ~\/ncc\/bin\/ncc health_checks system_checks dns_server_check\"
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 register: ncc_output<\/code><\/pre>A played a lot around with the enviroment-variables, but was not able to get an proper \"Passed\" or \"Failed\" output, what I would need\/want. Has someone an idea, what is missing, to execute a NC-Check from remote?<\/p>
Regards,
Markus<\/p>","quoteUsername":"n-tchen","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
            

             像
             引用
             
             
              
               
                分享


   
    
     
    
   
   
    
     
      
       
        由内部提供动力
       
       
        条款和条件
       
       
      
     
    
   
   
    
     
     注册
     已经有一个帐户？登录
     
      
      使用您的帐户登录
     
    
    
     
     登录社区
     
     使用您的帐户登录
    
    
     输入您的用户名或电子邮件地址。我们将向您发送带有指令的电子邮件以重置您的密码。
     
      
      
       
        用户名或电子邮件
       
       
        
       
      
      
       
       返回概述
      
      
     
    
    
    
     扫描病毒文件。
     抱歉，我们仍在检查该文件的内容，以确保它可以安全下载。请在几分钟后再试一次。
     好的
    
    
     该文件无法下载
     抱歉，我们的病毒扫描仪检测到该文件无法安全下载。
     好的
    
   
   Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">