[
https://issues.apache.org/jira/browse/CLOUDSTACK-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589514#comment-14589514
]
ASF GitHub Bot commented on CLOUDSTACK-8567:
--------------------------------------------
GitHub user sanjaytripathi opened a pull request:
https://github.com/apache/cloudstack/pull/468
CLOUDSTACK-8567 Migrating primary storage causes name_label field to …
The fix is to set the VDI name-label in XenServer.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sanjaytripathi/apache.cloudstack
CLOUDSTACK-8567
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/468.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #468
----
commit a2f63975c7f89902eb62b9448c3bae52e39da88e
Author: Sanjay Tripathi <[email protected]>
Date: 2015-04-17T08:12:26Z
CLOUDSTACK-8567 Migrating primary storage causes name_label field to blank.
----
> Migrating primary storage causes name_label field to blank
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-8567
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8567
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Environment: XenServer
> Reporter: Sanjay Tripathi
> Assignee: Sanjay Tripathi
> Fix For: 4.6.0
>
>
> If user migrate a disk across primary storages the name_label (on XS) field
> is not maintained. They would like the disk name to be maintained as it makes
> administration easier.
> I see the name_label is blanked and the disk no longer has a name. This is an
> issue if user has multiple disks on the SR without names.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
