Bug #30496: hammer ping returns 0 even when services are in a failed state - Hammer CLI - Foreman

Actions

Copy link

Bug #30496

closed

hammer ping returns 0 even when services are in a failed state

Added by Jonathon Turel over 5 years ago. Updated almost 5 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Oleh Fedorenko

Category:

Target version:

Difficulty:

Triaged:

Yes

Bugzilla link:

1941240

Pull request:

https://github.com/theforeman/hammer-cli-foreman/pull/545

Team Backlog:

Fixed in Releases:

hammer-cli-foreman-2.3.0

Found in Releases:

In Kanboard:

Red Hat JIRA:

Description

I'm not sure if this is a regression but it does seem like a bug:

[vagrant@centos7-katello-devel katello (master)]$ hammer ping ; echo $?
database:         
    Status:          ok
    Server Response: Duration: 0ms
candlepin:        
    Status:          FAIL
    Server Response: Message: Failed to open TCP connection to localhost:8443 (Connection refused - connect(2) for "localhost" port 8443)
candlepin_events: 
    Status:          FAIL
    message:         Not running
    Server Response: Duration: 0ms
candlepin_auth:   
    Status:          FAIL
    Server Response: Message: A backend service [ Candlepin ] is unreachable
katello_events:   
    Status:          ok
    message:         7 Processed, 0 Failed
    Server Response: Duration: 0ms
pulp:             
    Status:          ok
    Server Response: Duration: 34ms
pulp_auth:        
    Status:          ok
    Server Response: Duration: 13ms
foreman_tasks:    
    Status:          ok
    Server Response: Duration: 3ms

0