Re: [ovirt-users] Failed gdeploy

[Kasturi Narra]

Hi Sean,

 This error is expected and there is a bug to change this script so
that it can  properly disable multipath devices. To continue you can simply
add 'ignore_script_errors=yes'  under script3 which continues with this
failure. Please note that this script is used to disable multipath devices
and proceeding with this script simply means that you will have multipath
enabled for all your devices.

[script3]

file=/usr/share/gdeploy/scripts/disable-multipath.sh
ignore_script_errors=yes

Thanks
kasturi

On Fri, Sep 22, 2017 at 9:41 PM, Sean McMurray  wrote:

> After reading https://bugzilla.redhat.com/show_bug.cgi?id=1469469 and
> https://bugzilla.redhat.com/show_bug.cgi?id=1491548#c2 I changed
> gdeployConfig.conf so that [script3] has file=/usr/share/gdeploy/script
> s/disable-multipath.sh
>
> That gives me a different failture:
>
> TASK [Run a shell script] **
> 
> **
> task path: /tmp/tmp4kfKbY/run-script.yml:7
> failed: [192.168.1.3] (item=/usr/share/gdeploy/scripts/disable-multipath.sh)
> => {"changed": true, "failed": true, "failed_when_result": true, "item":
> "/usr/share/gdeploy/scripts/disable-multipath.sh", "rc": 1, "stderr":
> "Shared connection to 192.168.1.3 closed.\r\n", "stdout": "iscsiadm: No
> active sessions.\r\nThis script will prevent listing iscsi devices when
> multipath CLI is called\r\nwithout parameters, and so no LUNs will be
> discovered by applications like VDSM\r\n(oVirt, RHV) which shell-out to
> call `/usr/sbin/multipath` after target login\r\nSep 22 08:58:47 | DM
> multipath kernel driver not loaded\r\nSep 22 08:58:47 | DM multipath kernel
> driver not loaded\r\n", "stdout_lines": ["iscsiadm: No active sessions.",
> "This script will prevent listing iscsi devices when multipath CLI is
> called", "without parameters, and so no LUNs will be discovered by
> applications like VDSM", "(oVirt, RHV) which shell-out to call
> `/usr/sbin/multipath` after target login", "Sep 22 08:58:47 | DM multipath
> kernel driver not loaded", "Sep 22 08:58:47 | DM multipath kernel driver
> not loaded"]}
> failed: [192.168.1.2] (item=/usr/share/gdeploy/scripts/disable-multipath.sh)
> => {"changed": true, "failed": true, "failed_when_result": true, "item":
> "/usr/share/gdeploy/scripts/disable-multipath.sh", "rc": 1, "stderr":
> "Shared connection to 192.168.1.2 closed.\r\n", "stdout": "iscsiadm: No
> active sessions.\r\nThis script will prevent listing iscsi devices when
> multipath CLI is called\r\nwithout parameters, and so no LUNs will be
> discovered by applications like VDSM\r\n(oVirt, RHV) which shell-out to
> call `/usr/sbin/multipath` after target login\r\nSep 22 15:57:47 | DM
> multipath kernel driver not loaded\r\nSep 22 15:57:47 | DM multipath kernel
> driver not loaded\r\n", "stdout_lines": ["iscsiadm: No active sessions.",
> "This script will prevent listing iscsi devices when multipath CLI is
> called", "without parameters, and so no LUNs will be discovered by
> applications like VDSM", "(oVirt, RHV) which shell-out to call
> `/usr/sbin/multipath` after target login", "Sep 22 15:57:47 | DM multipath
> kernel driver not loaded", "Sep 22 15:57:47 | DM multipath kernel driver
> not loaded"]}
> failed: [192.168.1.1] (item=/usr/share/gdeploy/scripts/disable-multipath.sh)
> => {"changed": true, "failed": true, "failed_when_result": true, "item":
> "/usr/share/gdeploy/scripts/disable-multipath.sh", "rc": 1, "stderr":
> "Shared connection to 192.168.1.1 closed.\r\n", "stdout": "iscsiadm: No
> active sessions.\r\nThis script will prevent listing iscsi devices when
> multipath CLI is called\r\nwithout parameters, and so no LUNs will be
> discovered by applications like VDSM\r\n(oVirt, RHV) which shell-out to
> call `/usr/sbin/multipath` after target login\r\nSep 22 08:58:50 | DM
> multipath kernel driver not loaded\r\nSep 22 08:58:50 | DM multipath kernel
> driver not loaded\r\n", "stdout_lines": ["iscsiadm: No active sessions.",
> "This script will prevent listing iscsi devices when multipath CLI is
> called", "without parameters, and so no LUNs will be discovered by
> applications like VDSM", "(oVirt, RHV) which shell-out to call
> `/usr/sbin/multipath` after target login", "Sep 22 08:58:50 | DM multipath
> kernel driver not loaded", "Sep 22 08:58:50 | DM multipath kernel driver
> not loaded"]}
> to retry, use: --limit @/tmp/tmp4kfKbY/run-script.retry
>
> PLAY RECAP 
> ***
> 192.168.1.1: ok=0changed=0unreachable=0 failed=1
> 192.168.1.2: ok=0changed=0unreachable=0 failed=1
> 192.168.1.3: ok=0changed=0unreachable=0 failed=1
>
>
> On 09/22/2017 09:05 AM, Sean McMurray wrote:
>
>> My latest attempt to deploy went like this (/tmp/tmpaQJuTG/run-script.yml
>> 

[ovirt-users] Failed gdeploy

[Sean McMurray]

My latest attempt to deploy went like this 
(/tmp/tmpaQJuTG/run-script.yml and /tmp/gdeployConfig.conf are pasted 
below the gdeploy transcript):


# gdeploy -k -vv -c /tmp/gdeployConfig.conf --trace
Using /etc/ansible/ansible.cfg as config file

PLAYBOOK: run-script.yml 
*

1 plays in /tmp/tmpaQJuTG/run-script.yml

PLAY [gluster_servers] 
***

META: ran handlers

TASK [Run a shell script] 


task path: /tmp/tmpaQJuTG/run-script.yml:7
changed: [192.168.1.3] => 
(item=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h 
192.168.1.1,192.168.1.2,192.168.1.3) => {"changed": true, "failed": 
false, "failed_when_result": false, "item": 
"/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h 
192.168.1.1,192.168.1.2,192.168.1.3", "rc": 0, "stderr": "Shared 
connection to 192.168.1.3 closed.\r\n", "stdout": "", "stdout_lines": []}
changed: [192.168.1.2] => 
(item=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h 
192.168.1.1,192.168.1.2,192.168.1.3) => {"changed": true, "failed": 
false, "failed_when_result": false, "item": 
"/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h 
192.168.1.1,192.168.1.2,192.168.1.3", "rc": 0, "stderr": "Shared 
connection to 192.168.1.2 closed.\r\n", "stdout": "", "stdout_lines": []}
changed: [192.168.1.1] => 
(item=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h 
192.168.1.1,192.168.1.2,192.168.1.3) => {"changed": true, "failed": 
false, "failed_when_result": false, "item": 
"/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h 
192.168.1.1,192.168.1.2,192.168.1.3", "rc": 0, "stderr": "Shared 
connection to 192.168.1.1 closed.\r\n", "stdout": "scp: 
/tmp/*_host_ip_2017_09_22.txt: No such file or directory\r\nscp: 
/tmp/*_host_ip_2017_09_22.txt: No such file or directory\r\n", 
"stdout_lines": ["scp: /tmp/*_host_ip_2017_09_22.txt: No such file or 
directory", "scp: /tmp/*_host_ip_2017_09_22.txt: No such file or 
directory"]}

META: ran handlers
META: ran handlers

PLAY RECAP 
***

192.168.1.1: ok=1changed=1unreachable=0 failed=0
192.168.1.2: ok=1changed=1unreachable=0 failed=0
192.168.1.3: ok=1changed=1unreachable=0 failed=0

Using /etc/ansible/ansible.cfg as config file

PLAYBOOK: chkconfig_service.yml 
**

1 plays in /tmp/tmpaQJuTG/chkconfig_service.yml

PLAY [gluster_servers] 
***

META: ran handlers

TASK [Enable or disable services] 


task path: /tmp/tmpaQJuTG/chkconfig_service.yml:7
ok: [192.168.1.3] => (item=chronyd) => {"changed": false, "enabled": 
true, "item": "chronyd", "name": "chronyd", "status": 
{"ActiveEnterTimestamp": "Fri 2017-09-22 08:05:49 PDT", 
"ActiveEnterTimestampMonotonic": "57218106256", "ActiveExitTimestamp": 
"Fri 2017-09-22 08:05:49 PDT", "ActiveExitTimestampMonotonic": 
"57218037256", "ActiveState": "active", "After": 
"systemd-journald.socket var.mount tmp.mount ntpd.service -.mount 
system.slice sntp.service basic.target ntpdate.service", "AllowIsolate": 
"no", "AmbientCapabilities": "0", "AssertResult": "yes", 
"AssertTimestamp": "Fri 2017-09-22 08:05:49 PDT", 
"AssertTimestampMonotonic": "57218053902", "Before": "multi-user.target 
imgbase-config-vdsm.service shutdown.target", "BlockIOAccounting": "no", 
"BlockIOWeight": "18446744073709551615", "CPUAccounting": "no", 
"CPUQuotaPerSecUSec": "infinity", "CPUSchedulingPolicy": "0", 
"CPUSchedulingPriority": "0", "CPUSchedulingResetOnFork": "no", 
"CPUShares": "18446744073709551615", "CanIsolate": "no", "CanReload": 
"no", "CanStart": "yes", "CanStop": "yes", "CapabilityBoundingSet": 
"18446744073709551615", "ConditionResult": "yes", "ConditionTimestamp": 
"Fri 2017-09-22 08:05:49 PDT", "ConditionTimestampMonotonic": 
"57218053870", "Conflicts": "shutdown.target systemd-timesyncd.service 
ntpd.service", "ControlGroup": "/system.slice/chronyd.service", 
"ControlPID": "0", "DefaultDependencies": "yes", "Delegate": "no", 
"Description": "NTP client/server", "DevicePolicy": "auto", 
"Documentation": "man:chronyd(8) man:chrony.conf(5)", "EnvironmentFile": 
"/etc/sysconfig/chronyd (ignore_errors=yes)", "ExecMainCode": "0", 
"ExecMainExitTimestampMonotonic": "0", "ExecMainPID": "7300", 

Re: [ovirt-users] Failed gdeploy

[Sean McMurray]

After reading https://bugzilla.redhat.com/show_bug.cgi?id=1469469 and 
https://bugzilla.redhat.com/show_bug.cgi?id=1491548#c2 I changed 
gdeployConfig.conf so that [script3] has 
file=/usr/share/gdeploy/scripts/disable-multipath.sh


That gives me a different failture:

TASK [Run a shell script] 


task path: /tmp/tmp4kfKbY/run-script.yml:7
failed: [192.168.1.3] 
(item=/usr/share/gdeploy/scripts/disable-multipath.sh) => {"changed": 
true, "failed": true, "failed_when_result": true, "item": 
"/usr/share/gdeploy/scripts/disable-multipath.sh", "rc": 1, "stderr": 
"Shared connection to 192.168.1.3 closed.\r\n", "stdout": "iscsiadm: No 
active sessions.\r\nThis script will prevent listing iscsi devices when 
multipath CLI is called\r\nwithout parameters, and so no LUNs will be 
discovered by applications like VDSM\r\n(oVirt, RHV) which shell-out to 
call `/usr/sbin/multipath` after target login\r\nSep 22 08:58:47 | DM 
multipath kernel driver not loaded\r\nSep 22 08:58:47 | DM multipath 
kernel driver not loaded\r\n", "stdout_lines": ["iscsiadm: No active 
sessions.", "This script will prevent listing iscsi devices when 
multipath CLI is called", "without parameters, and so no LUNs will be 
discovered by applications like VDSM", "(oVirt, RHV) which shell-out to 
call `/usr/sbin/multipath` after target login", "Sep 22 08:58:47 | DM 
multipath kernel driver not loaded", "Sep 22 08:58:47 | DM multipath 
kernel driver not loaded"]}
failed: [192.168.1.2] 
(item=/usr/share/gdeploy/scripts/disable-multipath.sh) => {"changed": 
true, "failed": true, "failed_when_result": true, "item": 
"/usr/share/gdeploy/scripts/disable-multipath.sh", "rc": 1, "stderr": 
"Shared connection to 192.168.1.2 closed.\r\n", "stdout": "iscsiadm: No 
active sessions.\r\nThis script will prevent listing iscsi devices when 
multipath CLI is called\r\nwithout parameters, and so no LUNs will be 
discovered by applications like VDSM\r\n(oVirt, RHV) which shell-out to 
call `/usr/sbin/multipath` after target login\r\nSep 22 15:57:47 | DM 
multipath kernel driver not loaded\r\nSep 22 15:57:47 | DM multipath 
kernel driver not loaded\r\n", "stdout_lines": ["iscsiadm: No active 
sessions.", "This script will prevent listing iscsi devices when 
multipath CLI is called", "without parameters, and so no LUNs will be 
discovered by applications like VDSM", "(oVirt, RHV) which shell-out to 
call `/usr/sbin/multipath` after target login", "Sep 22 15:57:47 | DM 
multipath kernel driver not loaded", "Sep 22 15:57:47 | DM multipath 
kernel driver not loaded"]}
failed: [192.168.1.1] 
(item=/usr/share/gdeploy/scripts/disable-multipath.sh) => {"changed": 
true, "failed": true, "failed_when_result": true, "item": 
"/usr/share/gdeploy/scripts/disable-multipath.sh", "rc": 1, "stderr": 
"Shared connection to 192.168.1.1 closed.\r\n", "stdout": "iscsiadm: No 
active sessions.\r\nThis script will prevent listing iscsi devices when 
multipath CLI is called\r\nwithout parameters, and so no LUNs will be 
discovered by applications like VDSM\r\n(oVirt, RHV) which shell-out to 
call `/usr/sbin/multipath` after target login\r\nSep 22 08:58:50 | DM 
multipath kernel driver not loaded\r\nSep 22 08:58:50 | DM multipath 
kernel driver not loaded\r\n", "stdout_lines": ["iscsiadm: No active 
sessions.", "This script will prevent listing iscsi devices when 
multipath CLI is called", "without parameters, and so no LUNs will be 
discovered by applications like VDSM", "(oVirt, RHV) which shell-out to 
call `/usr/sbin/multipath` after target login", "Sep 22 08:58:50 | DM 
multipath kernel driver not loaded", "Sep 22 08:58:50 | DM multipath 
kernel driver not loaded"]}

to retry, use: --limit @/tmp/tmp4kfKbY/run-script.retry

PLAY RECAP 
***

192.168.1.1: ok=0changed=0unreachable=0 failed=1
192.168.1.2: ok=0changed=0unreachable=0 failed=1
192.168.1.3: ok=0changed=0unreachable=0 failed=1


On 09/22/2017 09:05 AM, Sean McMurray wrote:
My latest attempt to deploy went like this 
(/tmp/tmpaQJuTG/run-script.yml and /tmp/gdeployConfig.conf are pasted 
below the gdeploy transcript):


# gdeploy -k -vv -c /tmp/gdeployConfig.conf --trace
Using /etc/ansible/ansible.cfg as config file

PLAYBOOK: run-script.yml 
*

1 plays in /tmp/tmpaQJuTG/run-script.yml

PLAY [gluster_servers] 
***

META: ran handlers

TASK [Run a shell script] 


task path: