Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-28362

The example output of "hammer ping" command is wrong in "Using the Hammer CLI tool" doc of Satellite 6.16

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • Endeavour
    • Sat_docs_14_2024
    • Informational
    • None

      Description of problem:

      This is not a blocker at all but The output of hammer ping has changed quite a bit and the latest output i.e. 

      # hammer ping
database:         
    Status:          ok
    Server Response: Duration: 0ms
cache:            
    servers: 
     1) Status:          ok
        Server Response: Duration: 0ms
candlepin:        
    Status:          ok
    Server Response: Duration: 19ms
candlepin_auth:   
    Status:          ok
    Server Response: Duration: 17ms
candlepin_events: 
    Status:          ok
    message:         1 Processed, 0 Failed
    Server Response: Duration: 0ms
katello_events:   
    Status:          ok
    message:         3 Processed, 0 Failed
    Server Response: Duration: 0ms
pulp3:            
    Status:          ok
    Server Response: Duration: 148ms
pulp3_content:    
    Status:          ok
    Server Response: Duration: 54ms
foreman_tasks:    
    Status:          ok
    Server Response: Duration: 3ms

      which does not match what we mentioned in "Chapter 9. Troubleshooting Satellite by using Hammer" of 6.16 product doc i.e. 

      $ hammer ping
candlepin:
    Status:          ok
    Server Response: Duration: 22ms
candlepin_auth:
    Status:          ok
    Server Response: Duration: 17ms
pulp:
    Status:          ok
    Server Response: Duration: 41ms
pulp_auth:
    Status:          ok
    Server Response: Duration: 23ms
foreman_tasks:
    Status:          ok
    Server Response: Duration: 33ms

      This should be updated. 

       

              apetrova@redhat.com Aneta Šteflová Petrová
              rhn-support-saydas Sayan Das
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: