Bug 1283271
| Summary: | There is no difference between regular and bootable cinder image | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Eyal Shenitzky <eshenitz> | ||||
| Component: | BLL.Storage | Assignee: | Daniel Erez <derez> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Raz Tamir <ratamir> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.6.0.2 | CC: | amureini, bugs, derez, tnisan | ||||
| Target Milestone: | --- | Flags: | sbonazzo:
ovirt-4.2-
|
||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-02-28 16:32:20 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This issue is indeed a known gap found in early Cinder pre-integration phases. Bootable attribute can be set manually using the set-bootable command: https://blueprints.launchpad.net/cinder/+spec/add-bootable-option. Since this flag has no real meaning or effect, merely stored in Cinder's DB; and the addition would require a change in openstack-java-sdk, marking as an RFE for 4.0 for reconsideration. @Tal/Allon - can you please remove the ovirt-3.6.z flag request. This bug is marked for z-stream, yet the milestone is for a major version, therefore the milestone has been reset. Please set the correct milestone or drop the z stream flag. This isn't an RFE, it's a bug, at most. (In reply to Daniel Erez from comment #1) > This issue is indeed a known gap found in early Cinder pre-integration > phases. Bootable attribute can be set manually using the set-bootable > command: https://blueprints.launchpad.net/cinder/+spec/add-bootable-option. > > Since this flag has no real meaning or effect, merely stored in Cinder's DB; > and the addition would require a change in openstack-java-sdk, marking as an > RFE for 4.0 for reconsideration. Was it implemented in openstack-java-sdk? (In reply to Yaniv Kaul from comment #4) > (In reply to Daniel Erez from comment #1) > > This issue is indeed a known gap found in early Cinder pre-integration > > phases. Bootable attribute can be set manually using the set-bootable > > command: https://blueprints.launchpad.net/cinder/+spec/add-bootable-option. > > > > Since this flag has no real meaning or effect, merely stored in Cinder's DB; > > and the addition would require a change in openstack-java-sdk, marking as an > > RFE for 4.0 for reconsideration. > > Was it implemented in openstack-java-sdk? No, unfortunately the project hasn't been actively maintained for the last year: https://github.com/woorea/openstack-java-sdk/issues/193 Since we don't release new versions of openstack-java-sdk, which is required to fix this issue (as explained in https://bugzilla.redhat.com/show_bug.cgi?id=1283271#c1). Closing for now. |
Created attachment 1096122 [details] vdsm+cinder+engine logs Description of problem: When creating a cinder bootable disk the image create as regular disk, But the disk appears in the engine as bootable. Version-Release number of selected component (if applicable): engine - 3.6.0.3-0.1.el6 vdsm -4.17.10.1-0.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Create bootable cinder disk Run "cinder list" on the cinder external provider to check results. Actual results: Disk appears as regular on cinder and as bootable on the engine. Expected results: Disk appears as bootable on cinder and on the engine. Additional info: Vdsm cinder and engine log attached