Hide Forgot
Description of problem: If the rbd-target-gw service is started BEFORE the host is registered to the configuration object, the service fails with a python backtrace. Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. start the rbd-target-gw service before configuratin OR create a one node configuration then try and start the service on node 2 2. 3. Actual results: backtrace and rbd-target-gw service fails Expected results: Service should check whether there is any work to do, and message accordingly Additional info:
Please test against 1.5test release
Paul, Had a question here. Should'nt the rbd-target-gw service be masked when the gateway is configured on the node? the steps I tried: 1. started the rbd-target-gw service on a node which does not have the gateway configured. 2. configred the iscsi gateway on that node. 3. I am still able to manipulate the rbd-target-gw service. Let me know if I have misunderstood this. Thanks, Tejas
What is the impact of this issue? Is this the admin starting the service before they add the node the playbook and re-run ansible? If so, that seems like this could be documented and fixed in the next release.
Issue is resolved with 1.5 released to QE today (fri 04 nov) Crash is exactly that - admin starts the service, prior to any playbook run. Rather than let the daemon fail and cause confusion, the code now checks if there is anything to do, no work = no-op.
(In reply to Tejas from comment #4) > Paul, > > Had a question here. Should'nt the rbd-target-gw service be masked when > the gateway is configured on the node? > > the steps I tried: > 1. started the rbd-target-gw service on a node which does not have the > gateway configured. > 2. configred the iscsi gateway on that node. > 3. I am still able to manipulate the rbd-target-gw service. > > Let me know if I have misunderstood this. > > Thanks, > Tejas rbd-target-gw replaces the target service - so it needs to be present and active on all nodes. It is responsible for rebuilding the iscsi configuration following a reboot, by reading and applying the current configuration object. if you start the rbd-target-gw on a gateway that is not yet configured, the daemon should not crash. please retest this scenario on the 1.5 downstream release.
Verified in build: ceph-iscsi-config-1.5-1.el7cp No crash seen.
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-2016:2817