Bug 1101161
Summary: | spacecmd system_applyerrata error | ||
---|---|---|---|
Product: | [Community] Spacewalk | Reporter: | littlekai <littlekai9> |
Component: | Server | Assignee: | Eric Herget <eherget> |
Status: | CLOSED WORKSFORME | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.0 | CC: | eherget, littlekai9 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-06-30 20:35:24 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1484117 |
Description
littlekai
2014-05-26 10:25:08 UTC
Hi any idea? What version of Spacewalk (i.e. the server side) is this? Could you please provide output from server from the following file: /var/log/rhn/rhn_web_api.log matching the execution of spacecmd system_applyerrata? Thank you. thanks for your response, I will raise a change to provide this information I have tested this issue and am unable to reproduce with latest release. I set up a client configured with a channel to which I applied a newly created erratum with a newer version of a package than is currently installed on the client. I run the command and get this output: -------------screen dump---------------- [root@spacewalk-rhel6 ~]# spacecmd -y system_applyerrata client-f23.rdu.redhat.com EHBA:2016-5555 INFO: Connected to https://spacewalk-rhel6.rdu.redhat.com/rpc/api as admin Errata Systems -------------- ------- EHBA:2016-5555 1 INFO: Scheduled 1 system(s) for EHBA:2016-5555 [root@spacewalk-rhel6 ~]# ------------end of screen dump-------------- I'm closing this as WORKSFORME. Please reopen if able to reproduce in current release. This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug. |