Bug 638584
| Summary: | virt guest: restart/shutdown/allocate mem or cpu doesnt work | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Petr Sklenar <psklenar> |
| Component: | Virtualization | Assignee: | Milan Zázrivec <mzazrivec> |
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 540 | Keywords: | Regression |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-09-29 12:43:23 UTC | Type: | --- |
| 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: | 487677 | ||
taking back, I am sorry works for me |
Description of problem: virt guest: restart/shutdown/allocate mem or cpu doesn't work Version-Release number of selected component (if applicable): Satellite-5.4.0-RHEL5-re20100924.0 How reproducible: always Steps to Reproduce: 1. sat540 and connect a kvm host 2. create kvm guest through provisioning 3. try some of the feature: stop, start, reboot, allocate mem, allocate cpu Actual results: # rhn_check -vv D: check_action {'action': "<?xml version='1.0'?>\n<methodCall>\n<methodName>virt.shutdown</methodName>\n<params>\n<param>\n<value><string>7bf6273dc8857992775edb71b8ce5b43</string></value>\n</param>\n</params>\n</methodCall>\n", 'version': 2, 'id': 85} updateLoginInfo() login info D: login(forceUpdate=True) invoked logging into up2date server D: writeCachedLogin() invoked D: Wrote pickled loginInfo at 1285759859.63 with expiration of 1285763459.63 seconds. successfully retrieved authentication token from up2date server D: logininfo: {'X-RHN-Server-Id': 1000010022, 'X-RHN-Auth-Server-Time': '1285759893.02', 'X-RHN-Auth': 'RZRiYp4DalBMoyRkzLzXkg==', 'X-RHN-Auth-Channels': [['rhel-x86_64-server-5', '20100926053655', '1', '1'], ['rhn-tools-rhel-x86_64-server-5', '20100926053655', '0', '1'], ['rhel-x86_64-server-vt-5', '20100926053655', '0', '1']], 'X-RHN-Auth-User-Id': '', 'X-RHN-Auth-Expire-Offset': '3600.0'} D: handle_action {'action': "<?xml version='1.0'?>\n<methodCall>\n<methodName>virt.shutdown</methodName>\n<params>\n<param>\n<value><string>7bf6273dc8857992775edb71b8ce5b43</string></value>\n</param>\n</params>\n</methodCall>\n", 'version': 2, 'id': 85} D: handle_action actionid = 85, version = 2 D: do_call virt.shutdown ('7bf6273dc8857992775edb71b8ce5b43',) libvir: QEMU error : operation failed: shutdown operation failed D: Sending back response ((6,), 'Fatal error in Python code occured', {}) D: do_call packages.checkNeedUpdate ('rhnsd=1',) Loaded plugins: rhnplugin D: local action status: (0, 'rpm database not modified since last update (or package list recently updated)', {}) Expected results: I can schedule all the virt-guest actions Additional info: