{"action":"opened","issue":{"url":"https://api.github.com/repos/xcat2/xcat-core/issues/1768","repository_url":"https://api.github.com/repos/xcat2/xcat-core","labels_url":"https://api.github.com/repos/xcat2/xcat-core/issues/1768/labels{/name}","comments_url":"https://api.github.com/repos/xcat2/xcat-core/issues/1768/comments","events_url":"https://api.github.com/repos/xcat2/xcat-core/issues/1768/events","html_url":"https://github.com/xcat2/xcat-core/issues/1768","id":173284627,"number":1768,"title":"Disks added to kvm do not match device labels","user":{"login":"gurevichmark","id":16106630,"avatar_url":"https://avatars.githubusercontent.com/u/16106630?v=3","gravatar_id":"","url":"https://api.github.com/users/gurevichmark","html_url":"https://github.com/gurevichmark","followers_url":"https://api.github.com/users/gurevichmark/followers","following_url":"https://api.github.com/users/gurevichmark/following{/other_user}","gists_url":"https://api.github.com/users/gurevichmark/gists{/gist_id}","starred_url":"https://api.github.com/users/gurevichmark/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gurevichmark/subscriptions","organizations_url":"https://api.github.com/users/gurevichmark/orgs","repos_url":"https://api.github.com/users/gurevichmark/repos","events_url":"https://api.github.com/users/gurevichmark/events{/privacy}","received_events_url":"https://api.github.com/users/gurevichmark/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-25T19:07:39Z","updated_at":"2016-08-25T19:07:39Z","closed_at":null,"body":"\r\nOn MN create a VM with an initial disk of 15G, then I add a disk of 10G and another disk of 5G:\r\n\r\nmkvm <vmname> -s 15G\r\nchvm <vmname> -a 10G\r\nchvm <vmname> -a 5G\r\nrpower <vmname> on\r\n\r\nOn the KVM host things appear as expected:\r\n`virsh dumpxml <vmname>` displays 3 disks: sda size of 15G, sdb size of 10G and sdc size of 5G\r\n\r\n![image](https://cloud.githubusercontent.com/assets/16106630/17981969/f40e0572-6ad3-11e6-8a1d-2f5513532d2e.png)\r\n\r\n\r\nAnd on KVM host volume information size is displayed as expected:\r\n\r\n![image](https://cloud.githubusercontent.com/assets/16106630/17981979/017c8576-6ad4-11e6-9095-d5fcc26671e3.png)\r\n\r\n![image](https://cloud.githubusercontent.com/assets/16106630/17981989/06f301a6-6ad4-11e6-83d5-b5c4de92e29e.png)\r\n\r\nBut when I login to the VM, the additional disks appear to be switched in sizes:\r\n\r\n![image](https://cloud.githubusercontent.com/assets/16106630/17982008/1225a6a0-6ad4-11e6-836d-6a3213b961bd.png)\r\n\r\nIt almost seems that <target dev=\"xxx\"> is not being used to assign label to the disk\r\n\r\nAdditionally command `ls /dev/disk/by-*` can be used to see the mapping of the label to the scsi id. But even that does not seem to match the XML file specification.\r\n\r\nThe documentation states the disk labels are just a suggestion and are not guaranteed:\r\n\r\n![image](https://cloud.githubusercontent.com/assets/16106630/17982147/a896f3a0-6ad4-11e6-92d2-6f888398b011.png)\r\n\r\nBut perhaps there is a way to enforce labels some other way ? @daniceexi suggested we should have the mapping correct, since the disk device label can be used by the user when changing disk size and removing disks.\r\n "}}
{"actor":{"display_login":"gurevichmark"}}