Bug 831811
| Summary: | oVirt Agent running guest on Fedora 16 isn't allowing reboot action to occur | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Justin Clift <jclift> | ||||||
| Component: | deltacloud-core | Assignee: | Michal Fojtik <mfojtik> | ||||||
| Status: | CLOSED EOL | QA Contact: | Rehana <aeolus-qa-list> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 1.1.0 | CC: | kwade, morazi | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-03-27 19:07:41 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 591618 [details]
Screenshot of the error message and page it occurs on
changing state back to new and changing project to deltacloud this is not conductor issue Removing this from consideration for 1.1 |
Created attachment 591611 [details] Fedora 16 image template this error happens with. Description of problem: The oVirt guest agent isn't giving "reboot" capability when running in Fedora 16 guests. (haven't tried other guests yet) In this particular case, it's a newly created F16 image (template file attached), launched and running ok. Am able to ssh into it using the IP address displayed by Aeolus, which shows the oVirt agent is definitely running. However, in the deployments tab, selecting the running instance and clicking the "Reboot selected instances" button gives an error flash message: "reboot is an invalid action" (screenshot attached) No idea if the problem is with the oVirt guest, or with Aeolus not recognising reboot should be allowed. Version-Release number of selected component (if applicable): Aeolus server components: $ rpm -qa | grep -i aeolus | sort aeolus-all-0.10.1-1.fc16.noarch aeolus-conductor-0.10.1-1.fc16.noarch aeolus-conductor-daemons-0.10.1-1.fc16.noarch aeolus-conductor-devel-0.10.1-1.fc16.noarch aeolus-conductor-doc-0.10.1-1.fc16.noarch aeolus-configure-2.6.0-1.fc16.noarch rubygem-aeolus-cli-0.5.0-1.fc16.noarch rubygem-aeolus-image-0.5.0-1.fc16.noarch $ rpm -qa | grep -i deltacloud | sort deltacloud-core-0.5.0-2.fc16.noarch deltacloud-core-ec2-0.5.0-2.fc16.noarch deltacloud-core-rhevm-0.5.0-2.fc16.noarch deltacloud-core-vsphere-0.5.0-2.fc16.noarch rubygem-deltacloud-client-0.5.0-1.fc16.noarch In the guest: # rpm -qa | grep -i ovirt ovirt-guest-agent-1.0.0-1.fc16.x86_64 The oVirt environment is using oVirt Engine 3.0, with a single oVirt 2.3 ISO based node (and separate NFS server). How reproducible: Every time. Steps to Reproduce: 1. Launch a new Fedora 16 oVirt guest, with the oVirt agent included. 2. Wait for the IP address to appear in the Aeolus interface. (shows successful agent operation) 3. Click on Monitor -> [pool name] -> Deployments 4. Click the name of the oVirt Deployment, to display the instances for it 5. Click the checkbox next to the running instance (to select it), then click the "Reboot selected instances" button above it. 6. A warning dialog appears asking "Are you sure you want to proceed"? Confirm. 7. The "reboot is an invalid action" flash message appears now. Actual results: No reboot is performed. Expected results: The guest should reboot, as would be the case in a VMware guest using the VMware agent. Additional info: