Bug 746551

Summary: Latest skynet client "cannot resolve host address" on push
Product: [Community] PressGang CCMS Reporter: Joshua Wulf <jwulf>
Component: CSProcessorAssignee: Lee Newson <lnewson>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.xCC: jwulf, lcarlon, topic-tool-list
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-22 17:27:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joshua Wulf 2011-10-17 03:38:08 UTC
[jwulf@gaura Zanata topicized]$ skynet push -c -n Python-command-reference-post.txt
ERROR: Cannot resolve the host address!


Client is the one published with Build 5 of CSProcessor, from Client URL: http://10.64.1.77/skynet.jar

skynet.ini:

[jwulf@gaura Zanata topicized]$ cat ~/.config/skynet.ini
[server]
# server is the URL of the server running the webservice
server=http://localhost:8080/
# apikey is the Skynet apikey used to authenticate the user
apikey=123456


I know that the webservice is up, because this works:

[jwulf@gaura Zanata topicized]$ wget http://localhost:8080/csprocessor/build?id=1\&apikey=123456
--2011-10-17 13:36:40--  http://localhost:8080/csprocessor/build?id=1&apikey=123456
Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15606 (15K) [application/zip]
Saving to: “build?id=1&apikey=123456”

100%[========================================================================================================================>] 15,606      --.-K/s   in 0s      

2011-10-17 13:36:42 (431 MB/s) - “build?id=1&apikey=123456” saved [15606/15606]

The following also works:


[jwulf@gaura Zanata topicized]$ skynet pull -c --post 1

Comment 1 Lee Newson 2011-10-17 22:33:09 UTC
Found the issue it had to do with inserting the wrong address for that push, which is why the pull's would work.

Comment 2 Lee Newson 2011-10-18 06:23:35 UTC
Uploaded with client build 7