no iSCSI gateway information in the dashboard

Bug #2040271 reported by Nobuto Murata
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceph Dashboard Charm
New
Undecided
Unassigned
OpenStack Ceph iSCSI Charm
New
Undecided
Unassigned

Bug Description

By following the document below, the iSCSI tab in the Ceph dashboard (/#/block/iscsi/overview) shows no information.
https://ubuntu.com/ceph/docs/vmware

$ juju run --wait=5m ceph-mon/leader create-pool name=vmware-iscsi

Running operation 9 with 1 task
  - task 10 on unit-ceph-mon-0

Waiting for task 10...
pool 'vmware-iscsi' created
set pool 23 size to 3
set pool 23 target_size_ratio to 0.1
enabled application 'unknown' on pool 'vmware-iscsi'

$ juju run --wait=5m ceph-iscsi/leader create-target \
   client-initiatorname=iqn.1998-01.com.vmware:node-gadomski-6a5e962a \
   client-username=vmwareclient \
   client-password=12to16characters \
   image-size=5G \
   image-name=disk-1 \
   pool-name=vmware-iscsi

Running operation 12 with 1 task
  - task 13 on unit-ceph-iscsi-1

Waiting for task 13...
iqn: iqn.2003-01.com.ubuntu.iscsi-gw:iscsi-igw

rbd: --user is deprecated, use --id

Then, the tab in the dashboard is still empty.

> iSCSI Targets not available
>
> Please consult the documentation on how to configure and enable the iSCSI Targets management functionality.
> Available information:
>
> There are no gateways defined

"gwcli" itself recognized iSCSI gateways and the target so it may be an orchesrator thing but there is no such message as "no orchestrator configured" either thus confusing to Charmed Ceph users.

$ juju ssh ceph-iscsi/leader -- sudo gwcli ls iscsi-targets
o- iscsi-targets .................................. [DiscoveryAuth: None, Targets: 1]
  o- iqn.2003-01.com.ubuntu.iscsi-gw:iscsi-igw ............ [Auth: None, Gateways: 2]
    o- disks ............................................................. [Disks: 1]
    | o- iscsi/disk-1 ............................... [Owner: new-troll.maas, Lun: 0]
    o- gateways ............................................... [Up: 2/2, Portals: 2]
    | o- new-troll.maas ...................................... [192.168.151.103 (UP)]
    | o- robust-lion.maas .................................... [192.168.151.104 (UP)]
    o- host-groups ..................................................... [Groups : 0]
    o- hosts .......................................... [Auth: ACL_ENABLED, Hosts: 1]
      o- iqn.1998-01.com.vmware:node-gadomski-6a5e962a ... [Auth: CHAP, Disks: 1(5G)]
        o- lun 0 .......................... [iscsi/disk-1(5G), Owner: new-troll.maas]

$ juju ssh ceph-iscsi/leader -- sudo gwcli ls disks
o- disks ............................................................. [5G, Disks: 1]
  o- iscsi ............................................................. [iscsi (5G)]
    o- disk-1 ........................................... [iscsi/disk-1 (Online, 5G)]

Revision history for this message
Nobuto Murata (nobuto) wrote :

iSCSI overview tab

Revision history for this message
Nobuto Murata (nobuto) wrote :

iSCSI targets tab.

Revision history for this message
Nobuto Murata (nobuto) wrote :

Okay, two issues here:

1. there is a relation between ceph-iscsi and ceph-dashboard charm, but there is no such mention in neither charm's README or the documentation

> ceph-dashboard:iscsi-dashboard ceph-iscsi:admin-access

https://ubuntu.com/ceph/docs/install-dashboard
https://ubuntu.com/ceph/docs/vmware
https://github.com/openstack/charm-ceph-iscsi/blob/master/README.md
https://github.com/openstack/charm-ceph-dashboard/blob/master/README.md

2. After adding the relation, gateways are shown up as "down" although gwcli shows those two gateways are up.

$ juju ssh ceph-iscsi/leader -- sudo gwcli ls /iscsi-targets/iqn.2003-01.com.ubuntu.iscsi-gw:iscsi-igw/gateways
o- gateways ................................................... [Up: 2/2, Portals: 2]
  o- new-troll.maas .......................................... [192.168.151.103 (UP)]
  o- robust-lion.maas ........................................ [192.168.151.104 (UP)]

Revision history for this message
Nobuto Murata (nobuto) wrote :

It worked after adding both vault:certificates and ceph-dashboard:iscsi-dashboard relations.

Not so sure why the health check from the dashboard didn't work with HTTP, but in any case, this kind of setup steps should be documented appropriately even if it's a limitation from an upstream.

[before adding a vault relation for certificates but after adding the dashboard relation]

# ceph dashboard iscsi-gateway-list | jq .
{
  "gateways": {
    "new-troll.maas": {
      "service_url": "http://admin:XKFUJ7HR@192.168.151.103:5000"
    },
    "robust-lion.maas": {
      "service_url": "http://admin:XKFUJ7HR@192.168.151.104:5000"
    }
  }
}

^^^ using HTTP as expected.

[after adding both vault certificate relation and dashboard relation]

# ceph dashboard iscsi-gateway-list | jq .
{
  "gateways": {
    "new-troll.maas": {
      "service_url": "https://admin:XKFUJ7HR@192.168.151.103:5000"
    },
    "robust-lion.maas": {
      "service_url": "https://admin:XKFUJ7HR@192.168.151.104:5000"
    }
  }
}

^^^ using HTTPS as expected

Revision history for this message
Nobuto Murata (nobuto) wrote :

I've redeployed the env, and this time it works with HTTP too.

$ curl -s http://admin:44LU8WsX@192.168.151.104:5000/api/_ping
{"message":"pong"}

So as long as the following point is satisfied, I think we can close the bug:

> 1. there is a relation between ceph-iscsi and ceph-dashboard charm, but there is no such mention in neither charm's README or the documentation
>
> > ceph-dashboard:iscsi-dashboard ceph-iscsi:admin-access
>
> https://ubuntu.com/ceph/docs/install-dashboard
> https://ubuntu.com/ceph/docs/vmware
> https://github.com/openstack/charm-ceph-iscsi/blob/master/README.md
> https://github.com/openstack/charm-ceph-dashboard/blob/master/README.md

Revision history for this message
Luciano Lo Giudice (lmlogiudice) wrote :

Hello Nobuto, and thanks for taking a look at this.

Taking into consideration the steps needed to solve this issue, I believe we can close this bug and instead open a documentation one. Do you agree with that?

Revision history for this message
Nobuto Murata (nobuto) wrote :

Yes, it's a documentation bug. But documentations are in each charm so please close it with an associated Gerrit review instead of closing it now.

Revision history for this message
Luciano Lo Giudice (lmlogiudice) wrote :

Documentation bug report: https://bugs.launchpad.net/charm-guide/+bug/2041703

I'm marking this one as closed.

Changed in charm-ceph-dashboard:
status: New → Invalid
Changed in charm-ceph-iscsi:
status: New → Invalid
Revision history for this message
Nobuto Murata (nobuto) wrote :

Again, README is in each charm.

====
1. there is a relation between ceph-iscsi and ceph-dashboard charm, but there is no such mention in neither charm's README or the documentation

> ceph-dashboard:iscsi-dashboard ceph-iscsi:admin-access

https://ubuntu.com/ceph/docs/install-dashboard
https://ubuntu.com/ceph/docs/vmware
https://github.com/openstack/charm-ceph-iscsi/blob/master/README.md
https://github.com/openstack/charm-ceph-dashboard/blob/master/README.md
====

Changed in charm-ceph-dashboard:
status: Invalid → New
Changed in charm-ceph-iscsi:
status: Invalid → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.