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
When running snaps-boot with -i switch, e.g.:
sudo -i python {git dir}/snaps-boot/iaas_launch.py -f {location of your configuration} -i
The Ansible script will fail with:
rku@intelbuild-two:~$ sudo -i python /home/rku/snaps-boot/iaas_launch.py -f /home/rku/hosts.yaml -i
INFO:iaas_launch:Launching Operation Starts ........
INFO:iaas_launch:Running as user root
INFO:iaas_launch:Reading configuration file [/home/rku/hosts.yaml]
INFO:file_utils:Loaded configuration
INFO:file_utils:Closing configuration file
INFO:iaas_launch:Rebar configuration {'password': 'r0cketsk8ts', 'user': 'rocketskates'}
INFO:pxe_utils:setIsolCpus function
INFO:pxe_utils:isolate cpu's for 10.30.9.11 are 4-17,22-35,40-54,57-71
INFO:pxe_utils:hugepagesz for 10.30.9.11 2MB
INFO:pxe_utils:hugepages for 10.30.9.11 24000
INFO:ansible_utils:Applying playbook [/home/rku/snaps-boot/snaps_boot/ansible_p/commission/setIsolCpus.yaml] with variables - {'isolcpus': '4-17,22-35,40-54,57-71', 'target': '10.30.9.11', hugepages': '24000', 'hugepagesz': '2MB'}
[WARNING]: No inventory was parsed, only implicit localhost is available
PLAY [10.30.9.11] ***************************************************************************************************************************************************************************
TASK [Gathering Facts] **********************************************************************************************************************************************************************
fatal: [10.30.9.11]: FAILED! => {"msg": "Privilege escalation method not found: None"}
to retry, use: --limit @/home/rku/snaps-boot/snaps_boot/ansible_p/commission/setIsolCpus.retry
PLAY RECAP **********************************************************************************************************************************************************************************
10.30.9.11 : ok=0 changed=0 unreachable=0 failed=1
Traceback (most recent call last):
File "/home/rku/snaps-boot/iaas_launch.py", line 219, in
__run(args)
File "/home/rku/snaps-boot/iaas_launch.py", line 104, in __run
pxe_utils.set_isol_cpus(config)
File "/home/rku/snaps-boot/snaps_boot/provision/pxe_utils.py", line 166, in set_isol_cpus
'hugepages': hugepages})
File "/usr/local/lib/python2.7/dist-packages/snaps_common/ansible_snaps/ansible_utils.py", line 143, in apply_playbook
playbook_path, ret_val, connection))
snaps_common.ansible_snaps.ansible_utils.AnsibleException: Error applying playbook [/home/rku/snaps-boot/snaps_boot/ansible_p/commission/setIsolCpus.yaml] with value [2] using the connectio type of [ssh]
This is fixed by three steps, (1) add ubuntu to sudo group, (2) add the line 'ubuntu ALL=(ALL) NOPASSWD:ALL' to visudo, and (3) add the line 'become_method: sudo' to snaps_boot/ansible_p/commission/setIsolCpus.yaml and snaps_boot/ansible_p/commission/delIsolCpus.yaml.
This issue requests that steps (1) and (2) be added to either the -p or the -s scripts. Step (3) will be fixed in a separate pr.
The text was updated successfully, but these errors were encountered:
When running snaps-boot with -i switch, e.g.:
sudo -i python {git dir}/snaps-boot/iaas_launch.py -f {location of your configuration} -i
The Ansible script will fail with:
rku@intelbuild-two:~$ sudo -i python /home/rku/snaps-boot/iaas_launch.py -f /home/rku/hosts.yaml -i
INFO:iaas_launch:Launching Operation Starts ........
INFO:iaas_launch:Running as user root
INFO:iaas_launch:Reading configuration file [/home/rku/hosts.yaml]
INFO:file_utils:Loaded configuration
INFO:file_utils:Closing configuration file
INFO:iaas_launch:Rebar configuration {'password': 'r0cketsk8ts', 'user': 'rocketskates'}
INFO:pxe_utils:setIsolCpus function
INFO:pxe_utils:isolate cpu's for 10.30.9.11 are 4-17,22-35,40-54,57-71
INFO:pxe_utils:hugepagesz for 10.30.9.11 2MB
INFO:pxe_utils:hugepages for 10.30.9.11 24000
INFO:ansible_utils:Applying playbook [/home/rku/snaps-boot/snaps_boot/ansible_p/commission/setIsolCpus.yaml] with variables - {'isolcpus': '4-17,22-35,40-54,57-71', 'target': '10.30.9.11', hugepages': '24000', 'hugepagesz': '2MB'}
[WARNING]: No inventory was parsed, only implicit localhost is available
PLAY [10.30.9.11] ***************************************************************************************************************************************************************************
TASK [Gathering Facts] **********************************************************************************************************************************************************************
fatal: [10.30.9.11]: FAILED! => {"msg": "Privilege escalation method not found: None"}
to retry, use: --limit @/home/rku/snaps-boot/snaps_boot/ansible_p/commission/setIsolCpus.retry
PLAY RECAP **********************************************************************************************************************************************************************************
10.30.9.11 : ok=0 changed=0 unreachable=0 failed=1
Traceback (most recent call last):
File "/home/rku/snaps-boot/iaas_launch.py", line 219, in
__run(args)
File "/home/rku/snaps-boot/iaas_launch.py", line 104, in __run
pxe_utils.set_isol_cpus(config)
File "/home/rku/snaps-boot/snaps_boot/provision/pxe_utils.py", line 166, in set_isol_cpus
'hugepages': hugepages})
File "/usr/local/lib/python2.7/dist-packages/snaps_common/ansible_snaps/ansible_utils.py", line 143, in apply_playbook
playbook_path, ret_val, connection))
snaps_common.ansible_snaps.ansible_utils.AnsibleException: Error applying playbook [/home/rku/snaps-boot/snaps_boot/ansible_p/commission/setIsolCpus.yaml] with value [2] using the connectio type of [ssh]
This is fixed by three steps, (1) add ubuntu to sudo group, (2) add the line 'ubuntu ALL=(ALL) NOPASSWD:ALL' to visudo, and (3) add the line 'become_method: sudo' to snaps_boot/ansible_p/commission/setIsolCpus.yaml and snaps_boot/ansible_p/commission/delIsolCpus.yaml.
This issue requests that steps (1) and (2) be added to either the -p or the -s scripts. Step (3) will be fixed in a separate pr.
The text was updated successfully, but these errors were encountered: