Project

General

Profile

Actions

Bug #6665

closed

Hammer ping fail when run via ssh and no user and password is provided

Added by Elyézer Rezende over 10 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:

Description

When running hammer ping via ssh it is able to run and return a non-zero return code because pulp_auth and doesn't show pulp_auth status. But when the user and password is provided hammer ping return all information plus a zero return code.

If the user and password is required, hammer ping command should fail instead to return not complete information and don't warn the user about the user and pass requirement.

$ ssh root@myforeman.com hammer ping
candlepin:
    Status:          ok
    Server Response: Duration: 26ms
candlepin_auth:
    Status:          ok
    Server Response: Duration: 26ms
pulp:
    Status:          ok
    Server Response: Duration: 18ms
pulp_auth:
    Status:
    Server Response: Message:
elasticsearch:
    Status:          ok
    Server Response: Duration: 18ms
katello_jobs:
    Status:          ok
    Server Response: Duration: 44ms

$ echo $?
1

$ ssh root@myforeman.com hammer -u admin -p password ping
candlepin:
    Status:          ok
    Server Response: Duration: 24ms
candlepin_auth:
    Status:          ok
    Server Response: Duration: 25ms
pulp:
    Status:          ok
    Server Response: Duration: 17ms
pulp_auth:
    Status:          ok
    Server Response: Duration: 180ms
elasticsearch:
    Status:          ok
    Server Response: Duration: 12ms
katello_jobs:
    Status:          ok
    Server Response: Duration: 42ms

$ echo $?
0
Actions

Also available in: Atom PDF