.Ceph ceph-ansible now installs the gwcli command during iscsi-gw install
Previously, when using Ansible playbooks from `ceph-ansible` to configure an iSCSI target, the `gwcli` command needed to verify the installation was not available. This was because the `ceph-iscsi-cli` package, which provides the `gwcli` command, was not included as a part of the install for the Ansible playbooks. With this update to {product}, the Ansible playbooks now install the `ceph-iscsi-cli` package as a part of iSCSI target configuration.
Description of problem:
Following our iscsi target installation steps that are documented here [1], after running the playbook the user should then verify that gwcli has been installed. The gwcli command is not available following the install.
I have tested with the following ceph-ansible versions and get the same results.
Old package: ceph-ansible-3.0.14-1.el7cp.noarch
New package: ceph-ansible-3.0.39-1.el7cp.noarch
To install the gwcli I had to use the manual steps below.
1. Install ceph-iscsi-cli
[root@vm250-194 ~]# yum -y install ceph-iscsi-cli
2. Try to run gwcli and it fails.
[root@vm250-194 ~]# gwcli
Unable to access the configuration object : REST API failure, code : 500
GatewayError:
3. Need to enable and start the rbd-target-api service for the gwcli to work
[root@vm250-194 ~]# systemctl enable rbd-target-api
[root@vm250-194 ~]# systemctl start rbd-target-api
[root@vm250-194 ~]# systemctl status rbd-target-api
● rbd-target-api.service - Ceph iscsi target configuration API
Loaded: loaded (/usr/lib/systemd/system/rbd-target-api.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2018-07-12 09:17:05 EDT; 1min 11s ago
Main PID: 16836 (rbd-target-api)
CGroup: /system.slice/rbd-target-api.service
└─16836 /usr/bin/python /usr/bin/rbd-target-api
Jul 12 09:17:05 vm250-194.gsslab.pnq2.redhat.com systemd[1]: Started Ceph iscsi target configuration API.
Jul 12 09:17:05 vm250-194.gsslab.pnq2.redhat.com systemd[1]: Starting Ceph iscsi target configuration API...
Jul 12 09:17:09 vm250-194.gsslab.pnq2.redhat.com rbd-target-api[16836]: Started the configuration object watcher
Jul 12 09:17:09 vm250-194.gsslab.pnq2.redhat.com rbd-target-api[16836]: Checking for config object changes every 1s
Jul 12 09:17:09 vm250-194.gsslab.pnq2.redhat.com rbd-target-api[16836]: API server using TLSv1 (older version of werkzeug)
Jul 12 09:17:09 vm250-194.gsslab.pnq2.redhat.com rbd-target-api[16836]: * Running on https://0.0.0.0:5000/
[root@vm250-194 ~]#
[1] https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/block_device_guide/using_an_iscsi_gateway#configuring_the_iscsi_target_using_ansible
Version-Release number of selected component (if applicable):
How reproducible:every time
Steps to Reproduce:
1.Follow documentation to install iscsi gw target.
2.
3.
Actual results:
Expected results:gwcli needs to be installed as part of the ceph-ansible run to complete the configuration.
Additional info:checking the ansible.log there is no reference to a task to install the ceph-iscsi-cli package
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:2819
Description of problem: Following our iscsi target installation steps that are documented here [1], after running the playbook the user should then verify that gwcli has been installed. The gwcli command is not available following the install. I have tested with the following ceph-ansible versions and get the same results. Old package: ceph-ansible-3.0.14-1.el7cp.noarch New package: ceph-ansible-3.0.39-1.el7cp.noarch To install the gwcli I had to use the manual steps below. 1. Install ceph-iscsi-cli [root@vm250-194 ~]# yum -y install ceph-iscsi-cli 2. Try to run gwcli and it fails. [root@vm250-194 ~]# gwcli Unable to access the configuration object : REST API failure, code : 500 GatewayError: 3. Need to enable and start the rbd-target-api service for the gwcli to work [root@vm250-194 ~]# systemctl enable rbd-target-api [root@vm250-194 ~]# systemctl start rbd-target-api [root@vm250-194 ~]# systemctl status rbd-target-api ● rbd-target-api.service - Ceph iscsi target configuration API Loaded: loaded (/usr/lib/systemd/system/rbd-target-api.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2018-07-12 09:17:05 EDT; 1min 11s ago Main PID: 16836 (rbd-target-api) CGroup: /system.slice/rbd-target-api.service └─16836 /usr/bin/python /usr/bin/rbd-target-api Jul 12 09:17:05 vm250-194.gsslab.pnq2.redhat.com systemd[1]: Started Ceph iscsi target configuration API. Jul 12 09:17:05 vm250-194.gsslab.pnq2.redhat.com systemd[1]: Starting Ceph iscsi target configuration API... Jul 12 09:17:09 vm250-194.gsslab.pnq2.redhat.com rbd-target-api[16836]: Started the configuration object watcher Jul 12 09:17:09 vm250-194.gsslab.pnq2.redhat.com rbd-target-api[16836]: Checking for config object changes every 1s Jul 12 09:17:09 vm250-194.gsslab.pnq2.redhat.com rbd-target-api[16836]: API server using TLSv1 (older version of werkzeug) Jul 12 09:17:09 vm250-194.gsslab.pnq2.redhat.com rbd-target-api[16836]: * Running on https://0.0.0.0:5000/ [root@vm250-194 ~]# [1] https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/block_device_guide/using_an_iscsi_gateway#configuring_the_iscsi_target_using_ansible Version-Release number of selected component (if applicable): How reproducible:every time Steps to Reproduce: 1.Follow documentation to install iscsi gw target. 2. 3. Actual results: Expected results:gwcli needs to be installed as part of the ceph-ansible run to complete the configuration. Additional info:checking the ansible.log there is no reference to a task to install the ceph-iscsi-cli package