Bug 1484871
Summary: | target service doesn't start as /etc/target/saveconfig.json file is not available | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | krishnaram Karthick <kramdoss> |
Component: | CNS-deployment | Assignee: | Raghavendra Talur <rtalur> |
Status: | CLOSED ERRATA | QA Contact: | krishnaram Karthick <kramdoss> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | cns-3.6 | CC: | akhakhar, annair, asriram, hchiramm, jarrpa, madam, mliyazud, mzywusko, pprakash, rhs-bugs, rreddy, rtalur, srmukher |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | CNS 3.6 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rhgs-server-docker-3.3.0-15 cns-deploy-5.0.0-23.el7rhgs | Doc Type: | Bug Fix |
Doc Text: |
Previously, on restart of rhgs-server container target service failed to start as saveconfig.json was not found. With this update, /etc/target is bind mounted to host and gluster-block-target service starts as expected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-10-11 06:58:29 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: | 1445448 |
Description
krishnaram Karthick
2017-08-24 12:54:28 UTC
This was an issue in bind mount of /etc/target which is corrected now in the template and next cns-build will have the fix. Verified the fix in build - cns-deploy-5.0.0-23.el7rhgs.x86_64 gluster-block-target service starts without any issues and the configuration file is stored in /etc/target/saveconfig.json sh-4.2# ls -l /etc/target/saveconfig.json -rw-------. 1 root root 24696 Aug 29 06:17 /etc/target/saveconfig.json snippet of gluster-template: volumeMounts: - mountPath: /etc/target name: glusterfs-gblock Moving the bug to verified. Changed the doc text a little bit. Looks good to me. 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/RHEA-2017:2877 |