search

SatelliteQE / robottelo-ci

Jenkins jobs configuration files to be used to run Robottelo against Satellite 6.
GNU General Public License v3.0
14 stars 45 forks source link

Investigate the failure's of recent Upstream tier Jobs #1459

Closed san7ket closed 5 years ago

san7ket commented 5 years ago

@lpramuk @rplevka @mirzal @latran anyone interested?

san7ket commented 5 years ago

Task is to investigate failure and report it here, if you can also fix that would be great. If it's an product issue file a upstream issue.

latran commented 5 years ago

@san7ket Sure I can try to pick this up. Mind you I haven't done much on upstream tier jobs, but I'm happy to learn and help out. How/where do I begin?

latran commented 5 years ago

I reviewed the latest 6.5 tier 1 job and found these test case failures:



tests/foreman/api/test_docker.py::test_positive_update_upstream_name

tests/foreman/api/test_host.py::test_positive_update_managed_parameter

tests/foreman/api/test_syncplan.py::test_positive_update_interval

tests/foreman/api/test_multiple_paths.py::test_positive_delete_and_get_requests

tests/foreman/cli/test_host.py::test_positive_create_using_libvirt_without_mac

tests/foreman/cli/test_organization.py::test_positive_multibyte_latin1_org_names
san7ket commented 5 years ago

@latran I don't mean the test failures, I meant the Job failures, why the Job turns red. Test failures are the responsiblity of component owner. You can find the latest failures Jenkins-Server/job/automation-upstream-nightly-tier1-rhel7/182/ If you are interested to take this up, I can show you where to look, in tuesday's call.

latran commented 5 years ago

@san7ket yes that sounds good. Let's do that.

rplevka commented 5 years ago

@san7ket @latran It is a real issue, pulp services seem to be failing after doing katello-service restart:

# hammer ping

candlepin:      
    Status:          ok
    Server Response: Duration: 445ms
candlepin_auth: 
    Status:          ok
    Server Response: Duration: 39ms
pulp:           
    Status:          FAIL
    Server Response:
pulp_auth:      
    Status: FAIL
foreman_tasks:  
    Status:          ok
    Server Response: Duration: 4ms

@evgeni @ekohl - upstream nightly (provisioned using forklift) builds have been failing like this since 2018-02-28 (however, maybe earlier, we have a gap between 2018-02-17 and 2018-02-28). Could you look into this? ping me if you need more info

evgeni commented 5 years ago

@rplevka so the initial install is fine, but after you do a restart, pulp fails to start up properly?