After new research and some troubleshooting tips I´ve found that editing the "iscsi-gateway.cfg" file manually and inserting the "api_host" variable makes the container start normally. But it can only be done after the service is deployed because containers are dynamically created by cephadm. After that you can edit the file under the following path: " /var/lib/ceph/<cluster_id>/<container>/iscsi-gateway.cfg" . In my case the entry was set that way: api_host = iscsi-gw After that containers come up and I can enter each one through Docker. But when I run the gwcli the error below returns: root@iscsi-gw:~# docker exec -it b32af67facaa sh sh-4.4# gwcli REST API failure, code : 500 Unable to access the configuration object AttributeError: 'Settings' object has no attribute 'api_endpoint' Can someone advise me how to get rid of this? Don´t know if I have to set the variable or there is some kind of bug from the code. tks. On Wed, May 25, 2022 at 4:52 PM Teoman Onay <tonay@xxxxxxxxxx> wrote: > Hello, > > Silly question but have you created the pool which will be used by the > gateway?? > > On Wed, 25 May 2022, 21:25 Heiner Hardt, <hhardt1912@xxxxxxxxx> wrote: > >> Sorry to be intransigent asking again but is there anyone facing issues on >> deploying iscsi-gateway daemons through CEPHADM? >> >> I´m still having issues trying to deploy iscsi-gateways with no success >> because service containers fail to load ending up with the error : "Error: >> No such object" . >> >> Any help will be great. Thanks. >> >> On Thu, May 19, 2022 at 4:41 PM Heiner Hardt <hhardt1912@xxxxxxxxx> >> wrote: >> >> > Hi, >> > >> > Is there anyone facing issues on deploying iscsi-gateway daemons through >> > CEPHADM? When I try to create a new iscsi service it finishes the >> deploy, >> > starts the container correctly but destroys it right after starting it. >> The >> > daemon shows up with error as it cannot be started. >> > >> > Bellow follows the 2 containers deployed and destroyed in matter of >> > seconds: >> > >> > 602dc3f8dce4 quay.io/ceph/ceph >> > "/usr/bin/rbd-target…" Less than a second ago Up Less than a second >> > >> > >> ceph-fec08570-b6d7-11ec-af55-01f54f89bfd2-iscsi-connector-iscsi-gw-gwpnnq >> > 28429d6f364a quay.io/ceph/ceph >> > "/usr/bin/tcmu-runner" Less than a second ago Up Less than a second >> > >> > >> ceph-fec08570-b6d7-11ec-af55-01f54f89bfd2-iscsi-connector-iscsi-gw-gwpnnq-tcmu >> > >> > It seems the services are failing to come up for some reason but I >> cannot >> > figure why. >> > >> > 2022-05-19 19:25:36,543 7f739d861740 DEBUG /usr/bin/docker: [ >> > >> quay.io/prometheus/node-exporter@sha256:f2269e73124dd0f60a7d19a2ce1264d33d08a985aed0ee6b0b89d0be470592cd >> > ] >> > 2022-05-19 19:25:36,679 7f739d861740 DEBUG /usr/bin/docker: >> node_exporter, >> > version 1.3.1 (branch: HEAD, revision: >> > a2321e7b940ddcff26873612bccdf7cd4c42b6b6) >> > 2022-05-19 19:25:36,679 7f739d861740 DEBUG /usr/bin/docker: build >> user: >> > root@243aafa5525c >> > 2022-05-19 19:25:36,680 7f739d861740 DEBUG /usr/bin/docker: build >> date: >> > 20211205-11:09:49 >> > 2022-05-19 19:25:36,680 7f739d861740 DEBUG /usr/bin/docker: go >> version: >> > go1.17.3 >> > 2022-05-19 19:25:36,680 7f739d861740 DEBUG /usr/bin/docker: platform: >> > linux/amd64 >> > 2022-05-19 19:25:36,696 7f739d861740 DEBUG systemctl: enabled >> > 2022-05-19 19:25:36,703 7f739d861740 DEBUG systemctl: failed >> > 2022-05-19 19:25:36,752 7f739d861740 DEBUG /usr/bin/docker: >> > 2022-05-19 19:25:36,752 7f739d861740 DEBUG /usr/bin/docker: Error: No >> such >> > object: >> > >> ceph-fec08570-b6d7-11ec-af55-01f54f89bfd2-iscsi-connector-iscsi-gw-gwpnnq >> > 2022-05-19 19:25:36,810 7f739d861740 DEBUG /usr/bin/docker: >> > 2022-05-19 19:25:36,810 7f739d861740 DEBUG /usr/bin/docker: Error: No >> such >> > object: >> > >> ceph-fec08570-b6d7-11ec-af55-01f54f89bfd2-iscsi.connector.iscsi-gw.gwpnnq >> > 2022-05-19 19:25:36,823 7f739d861740 DEBUG systemctl: enabled >> > 2022-05-19 19:25:36,833 7f739d861740 DEBUG systemctl: active >> > >> > This Ceph cluster runs on Ubuntu 20.04 and were upgraded to Quincy >> > recently (version 17.2.0 ). >> > >> > Any thoughts? >> > >> > >> _______________________________________________ >> ceph-users mailing list -- ceph-users@xxxxxxx >> To unsubscribe send an email to ceph-users-leave@xxxxxxx >> > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |