| Summary: | method listVirtualGuests doesn't return correct id of virtual systems | ||
|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | Pavel Studeník <pstudeni> |
| Component: | API | Assignee: | Tomas Lestach <tlestach> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.4 | CC: | tkasparek, tlestach |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-16 07:43:29 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 1484117 | ||
Fixed: - created patch for Cobbler snippet “post_install_network_config” which was trying to use not initiated variable (ipv6_autoconfiguration) - this caused that snippet was not expanded into kickstart script - during execution of the kickstart script a steps which should follow after end of this snippet were not executed then (including machine registration) - due to not occurred machine registration an API function system.listVirtualGuests() was returning incorrect values then Spacewalk-git-commit: 21d0f35997fba82dcce6d3b551cc005b0d603a47 If the solution does not work for you, re-assign this bug please. Fixed: API function system.listVirtualGuests() still returns correct ids of properly registered virtual guests. But in case that virtual guest is not registered (for any reason), the key "id" is not present in result structure of the virtual guest. Spacewalk-git-commit: 14816d9f6b21e85003e7251fc2b6d7c517a59ade If the solution does not work for you, re-assign this bug please. Note: Spacewalk-git-commit: 21d0f35997fba82dcce6d3b551cc005b0d603a47 was reverted (in commit c069d4fa9d7812903b2f5c2b9d89fc05ae8a1179), solution was to apply Satellite patch which supports ipv6 on cobbler side (done in Spacewalk-git-commit: 191f262c0ab0497203428a95231d7b8de170e6d8 Spacewalk 2.5 was released. This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug. |
Description of problem: I received wrong id of virtual systems by method system.listVirtualGuests: >>> sys_list = client.system.listVirtualGuests(key, serverId) >>> for i in range(len(sys_list)): print sys_list[i] {'guest_name': 'system-wed27jan2016_01_56_09_6361', 'uuid': '5d43220357ed9471a22c5590a9cf280a', 'id': 1000010004} {'guest_name': 'system-wed27jan2016_14_09_54_27329', 'uuid': '5aaf5953634e5f83f408dab298cbf397', 'id': 1000010004} But ID 1000010004 is host of this virtual systems. On Satellite I received corrects ids. Version-Release number of selected component (if applicable): spacewalk-java-2.5.43-1.el6.noarch How reproducible: always Steps to Reproduce: 1. create some virtual guests on host 2. show virtual systems by api Actual results: System's id is id of host Expected results: System's id is id of correct virtual host