Bug 1479738 - Heketi pod url not reachable able after upgrade process is completed
Heketi pod url not reachable able after upgrade process is completed
Status: CLOSED NOTABUG
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: heketi (Show other bugs)
cns-3.6
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Michael Adam
Tejas Chaphekar
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-09 06:01 EDT by Tejas Chaphekar
Modified: 2017-08-09 09:00 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-09 09:00:22 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tejas Chaphekar 2017-08-09 06:01:44 EDT
Description of problem:
Not able to run the heketi-cli commands from heketi-client after the upgrade process is complete

Version-Release number of selected component (if applicable):
RHEL-7.4
OCP - 3.6
heketi-client-5.0.0-6.el7rhgs.x86_64
cns-deploy-5.0.0-12.el7rhgs.x86_64


How reproducible:
Twice

Steps to Reproduce:
1.Update the CNS from 3.5 to 3.6 on OCP 3.6 setup
2.Export the HEKETI_CLI_SERVER parameter into the heketi-client machine
3.Run heketi-cli commands

Expected results:

Heketi-cli commands should be executed successfully

Actual results:

Getting the following error

Error: Get http://heketi-storage-project.cloudapps.mystorage.com/clusters: dial tcp: lookup heketi-storage-project.cloudapps.mystorage.com on 10.70.34.2:53: no such host


Additional info:

Prior to updating the CNS from 3.5 to 3.6 the heketi-cli commands were working with exporting same HEKETI_CLI_SERVER parameter
Comment 2 Humble Chirammal 2017-08-09 06:14:08 EDT
Set proper dnsmasq and it should resolve the issue.
Comment 3 Humble Chirammal 2017-08-09 09:00:22 EDT
As discussed in todays scrum this looks to be an issue with configuration or setup or some intermittent issue with previous OCP builds and I was told that this is no longer an issue with latest OCP builds. I am closing this bug as per this data and please feel free to reopen if the issue exist.

Note You need to log in before you can comment on or make changes to this bug.