Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use Jira Cloud for all bug tracking management.

Bug 1670785

Summary: rbd-target-api.service doesn't get started after starting rbd-target-gw.service.
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Servesha <sdudhgao>
Component: iSCSIAssignee: Mike Christie <mchristi>
Status: CLOSED ERRATA QA Contact: Madhavi Kasturi <mkasturi>
Severity: low Docs Contact: Bara Ancincova <bancinco>
Priority: low    
Version: 3.2CC: agunn, ceph-eng-bugs, ceph-qe-bugs, jdillama, mchristi, mmanjuna, mmurthy, sdudhgao, tchandra
Target Milestone: rc   
Target Release: 3.3   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ceph-iscsi-config-2.6-19.el7cp Doc Type: Bug Fix
Doc Text:
.The `rbd-target-api` service is started and stopped with respect to the `rbd-target-gw` service status Previously, the `rbd-target-api` service did not start after starting the `rbd-target-gw` service. Consequently, the `rolling_update.yml` playbook stopped at `TASK [stop ceph iscsi services]`, and the updating process did not continue. With this update, the `rbd-target-api` service is started and stopped with respect to the `rbd-target-gw` service status, and the updating process works as expected.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-21 15:10:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1726135    
Attachments:
Description Flags
Fix systemd deps none

Description Servesha 2019-01-30 11:08:10 UTC 
* Description of problem: 
rbd-target-api.service doesn't get started after starting rbd-target-gw.service.


* Version-Release number of selected component (if applicable): 
RHCS 3.2


* How reproducible:
Always


* Steps to Reproduce:
1. Check both the services- rbd-target-api.service and rbd-target-gw.service  are running.
2. Stop the service - rbd-target-gw.service
3. Check the status of the services- rbd-target-api.service and rbd-target-gw.service 
   => Both the services must be inactive and not running.
4. Start the service rbd-target-gw.service
5. Check the status of rbd-target-api.service

* Actual results: 
rbd-target-api.service doesn't get started after starting rbd-target-gw.service.


* Expected results: 
After starting rbd-target-gw.service, the service rbd-target-api.service should get started too.


* Additional info: 
To work around this problem :
STEP 1 : 
Add 'Wants=rbd-target-api.service' in the file /usr/lib/systemd/system/rbd-target-gw.service.

STEP 2 : 
Run the command : systemctl daemon-reload

STEP 3 : 

Check the status of the services - rbd-target-gw.service and rbd-target-api.service
Comment 2 Mike Christie 2019-05-02 22:12:17 UTC 
Created attachment 1562006 [details]
Fix systemd deps

Just attaching to bz so I do not forget, because the upstream repo for this is closed and this patch is not needed for ceph-iscsi.
Comment 12 errata-xmlrpc 2019-08-21 15:10:25 UTC 
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/RHSA-2019:2538