Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gwcli: Gateway status UNKNOWN #155

Open
discostur opened this issue Mar 12, 2019 · 2 comments
Open

gwcli: Gateway status UNKNOWN #155

discostur opened this issue Mar 12, 2019 · 2 comments

Comments

@discostur
Copy link

discostur commented Mar 12, 2019

Hi,

i've deployed ceph mimic via ceph-ansible and my iscsi gateways are working correctly (connected to virtualization cluster) but gwcli shows UNKNOWN GW status:

o- / ......................................................................................................................... [...]
  o- clusters ........................................................................................................ [Clusters: 1]
  | o- ceph ............................................................................................................ [HEALTH_OK]
  |   o- pools ......................................................................................................... [Pools: 3]
  |   | o- .rgw.root ....................................................................... [(x3), Commit: 0b/50.6T (0%), Used: 1K]
  |   | o- 1234-company-ovirt ...................................................... [(x3), Commit: 100G/50.6T (0%), Used: 1G]
  |   | o- rbd ............................................................................. [(x3), Commit: 0b/50.6T (0%), Used: 2K]
  |   o- topology ............................................................................................... [OSDs: 40,MONs: 3]
  o- disks ........................................................................................................ [100G, Disks: 1]
  | o- 1234-company-ovirt.lun01 ............................................................................... [lun01 (100G)]
  o- iscsi-target ..................................................................................................... [Targets: 1]
    o- iqn.2019-03.com.redhat.iscsi-gw:ceph-igw ...................................................................... [Gateways: 2]
      o- gateways ............................................................................................ [Up: 0/2, Portals: 2]
      | o- ceph-osd01 .................................................................................... [192.168.26.31 (UNKNOWN)]
      | o- ceph-osd02 .................................................................................... [192.168.26.32 (UNKNOWN)]
      o- host-groups .................................................................................................. [Groups : 0]
      o- hosts .......................................................................................................... [Hosts: 1]
        o- iqn.1994-05.com.redhat:94cd4f32b257 ............................................. [LOGGED-IN, Auth: CHAP, Disks: 1(100G)]
          o- lun 0 ....................................................... [1234-company-ovirt.lun01(100G), Owner: ceph-osd01]

Trusted IPs are set up correctly in /etc/ceph/iscsi-gateway.cfg:

trusted_ip_list = 192.168.26.31,192.168.26.32

I am able to curl from both gw1 / gw2 to the other gateway and get the config via api:

curl --user user:pass 192.168.26.32:5000/api/config
{
  "clients": {
    "iqn.1994-05.com.redhat:94cd4f32b257": {
      "auth": {
...
@mikechristie
Copy link
Contributor

mikechristie commented Mar 12, 2019

What are the values of api_* in /etc/ceph/iscsi-gateway.cfg?

I think you might have wanted to set api_secure = false. If not set, api_secure = true by default and the iscsi-gateway.crt/.key files probably did not get copied over to /etc/ceph by ansible.

@discostur
Copy link
Author

discostur commented Mar 12, 2019

@mikechristie here are the values:

[config]
cluster_name = ceph
gateway_keyring = ceph.client.admin.keyring

# To support the API, the bear minimum settings are:
api_secure = False

# Optional settings related to the CLI/API service
api_user = user
api_password = pass
api_port = 5000
loop_delay = 1
trusted_ip_list = 192.168.26.31,192.168.26.32

In /etc/ceph there are no crt/key files but that should be ok because of api_secure=false in /etc/ceph/iscsi-gateway.cfg ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants