Bug 1786718
Summary: | [Upgrade] After upgrade from 6.6 to 6.7 hammer ping command failed | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Kavita <kgaikwad> |
Component: | Satellite Maintain | Assignee: | Kavita <kgaikwad> |
Status: | CLOSED WORKSFORME | QA Contact: | Jameer Pathan <jpathan> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.7.0 | CC: | apatel, boopathiraj.selvaraj, jpathan, kgaikwad, mmccune, rankumar |
Target Milestone: | 6.7.0 | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-01-28 09:55:48 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kavita
2019-12-27 13:09:31 UTC
Upstream bug assigned to kgaikwad Upstream bug assigned to kgaikwad Unable to reproduce this upgrading from 6.6.1 to SNAP8. [root@ci-vm-10-0-150-58 ~]# foreman-maintain upgrade run --target-version 6.7 .. ... Running Procedures after migrating to Satellite 6.7 ================================================================================ Start applicable services: Starting the following service(s): rh-mongodb34-mongod, postgresql, qdrouterd, qpidd, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, smart_proxy_dynflow_core, tomcat, dynflowd, httpd, puppetserver, foreman-proxy | All services started [OK] -------------------------------------------------------------------------------- re-enable sync plans: / Total 0 sync plans are now enabled. [OK] -------------------------------------------------------------------------------- Remove maintenance_mode chain from iptables: [OK] -------------------------------------------------------------------------------- Running Checks after upgrading to Satellite 6.7 ================================================================================ Check for verifying syntax for ISP DHCP configurations: [SKIPPED] DHCP feature is not enabled -------------------------------------------------------------------------------- Check whether all services are running: [OK] -------------------------------------------------------------------------------- Check whether all services are running using the ping call: [OK] -------------------------------------------------------------------------------- Check for paused tasks: [OK] -------------------------------------------------------------------------------- Check to verify no empty CA cert requests exist: [OK] -------------------------------------------------------------------------------- Check whether system is self-registered or not: [OK] -------------------------------------------------------------------------------- Check if only installed assets are present on the system: / Checking for presence of non-original assets... [OK] -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Upgrade finished. [root@ci-vm-10-0-150-58 ~]# rpm -q satellite satellite-6.7.0-4.beta.el7sat.noarch [root@ci-vm-10-0-150-58 ~]# hammer ping database: Status: ok Server Response: Duration: 0ms candlepin: Status: ok Server Response: Duration: 17ms candlepin_auth: Status: ok Server Response: Duration: 17ms pulp: Status: ok Server Response: Duration: 95ms pulp_auth: Status: ok Server Response: Duration: 31ms foreman_tasks: Status: ok Server Response: Duration: 4ms Can you reproduce and if so, share system reproducer information? Going to move this back ON_QA as this doesn't appear to be happening anymore or not reproducible in dev or in the QE automation for upgrades that I can see. Hello Mike, I have created this BZ when QE reported this issue for automation. But Jameer (QE for Foreman-Maintain) confirmed that he is not able to reproduce this scenario. @Jameer - Could you please share your observations while testing the latest builds. Hello Kavita, I was also not able to reproduce this issue. I upgraded Satellite 6.6.1 to Satellite 6.7 snap 7 and did hammer ping. Hammer ping command was working before and after satellite upgrade. Unable to reproduce this issue, closing this BZ as WORKSFORME. I came across the same issue now. Looking for a solution After Upgrade from 6.6 to 6.7 hammer command gets failed with below error # hammer ping Error: The server does not support such operation. /usr/bin/hammer created (In reply to Boopathiraj from comment #13) > path was missed and solved this issue for now. |