Bug 1438640
Summary: | Host added to virt+gluster cluster displays a failed event message when checking for available updates for host with error message 'Command returned failure code 1 during SSH session' | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | RamaKasturi <knarra> |
Component: | Frontend.WebAdmin | Assignee: | bugs <bugs> |
Status: | CLOSED WONTFIX | QA Contact: | RamaKasturi <knarra> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.1.1.2 | CC: | bugs, knarra, mperina, oourfali, sabose |
Target Milestone: | --- | ||
Target Release: | --- | ||
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: | 2017-04-30 11:46:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1411323 |
Description
RamaKasturi
2017-04-04 02:09:58 UTC
Hi yaniv, I have copied engine and vdsm logs to the link below. http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/HC/1438640/ Thanks kasturi (In reply to RamaKasturi from comment #2) > Hi yaniv, > > I have copied engine and vdsm logs to the link below. > > http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/HC/1438640/ > > Thanks > kasturi Excellent, since now we can see in Engine the following: ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [77d49287] Yum: Cannot queue package ovirt-node-ng-image-update: Package ovirt-node-ng-image-update cannot be found 2017-04-03 06:47:50,520-04 INFO [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [77d49287] Yum: Performing yum transaction rollback 2017-04-03 06:47:50,521-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [77d49287] Failed to execute stage 'Package installation': Package ovirt-node-ng-image-update cannot be found Is that the case? (In reply to Yaniv Kaul from comment #3) > (In reply to RamaKasturi from comment #2) > > Hi yaniv, > > > > I have copied engine and vdsm logs to the link below. > > > > http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/HC/1438640/ > > > > Thanks > > kasturi > > Excellent, since now we can see in Engine the following: > ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) > [77d49287] Yum: Cannot queue package ovirt-node-ng-image-update: Package > ovirt-node-ng-image-update cannot be found > 2017-04-03 06:47:50,520-04 INFO > [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [77d49287] > Yum: Performing yum transaction rollback > 2017-04-03 06:47:50,521-04 ERROR > [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [77d49287] > Failed to execute stage 'Package installation': Package > ovirt-node-ng-image-update cannot be found > > Is that the case? Hi Yaniv, I changed the title of the bug to reflect the full error message where command returns failure during SSH session. Thanks kasturi Hi Yaniv, If the event message was "failed to check updates" i would be happy as there are no repos enabled on the node because of which it failed to check for update. But from the event message it appears to me that it fails to check update because 'Command returned failure code 1 during SSH session'. Thanks kasturi Every host (both type Centos/Fedora or NGN) needs to have oVirt repositories installed. If not or one of required packages are not available we fail check for upgrade. The error message itself is shown in Events tab, details are in specific host-deploy log (the exact name is shown in Events), but on engine side we just don't know why exactly host-deploy process failed, that's why we show stack trace on engine for all premature host-deploy SSH session exits. As Martin stated, if everything is configured properly, we won't have any error. For other cases, the events + host deploy logs are the address to troubleshoot. Closing as wontfix. |