解决了

kimagedlete行动不允许，目录项目由群集拥有

  • 2018年11月10日
  • 9回复
  • 1957年的观点
Davidteague
Userlevel 1
徽章 +1
因此，我不得不用新的棱镜中心代替我的棱镜中心，不幸的是，它已经拥有图像的所有权。有了我的新Prism Central，我无法删除任何旧图像，我会遇到此错误。不允许使用KimageDelete操作，目录项目由集群4452164C-24B6-479D-B16B-A8635FBE2741拥有，我相信这是我的旧Prism Central Uuid。我无法从本地群集中删除它们，因为它们被挂在了中央。这是令人沮丧的，因为我试图将PC用作管理和部署VM的主要切入点。
图标

最好的答案Sneha Patekar2019年12月10日，23:44

@DavidTeague<\/user-mention>\u00a0@Claus Jan<\/user-mention>\u00a0@DennisFFM<\/user-mention>\u00a0@tanel<\/user-mention>\u00a0@Joe_E<\/user-mention>\u00a0@storm<\/user-mention>\u00a0@Steven2018<\/user-mention>\u00a0@jeffearl<\/user-mention>\u00a0<\/p>

Thank you for sharing your questions here, I apologize you had to wait it so long.<\/p>

To address your issue, the issue in specific was earlier resolved using a workaround which resulted in many other issues.\u00a0<\/p>

But this issue is now resolved in\u00a0AOS 5.11 and\u00a05.10.5.<\/strong><\/p>

\u00a0<\/p>

The following cases are addressed by these changes:<\/p>

  • Allow images to be deleted if it owned by an older\u00a0PC from a new PC.<\/li>
  • If image is an orphan image (which means just present on PC)\u00a0it can be deleted.<\/li>
  • If image is on a PE and is not owned by that PE - The image can either be deleted by unregistering the PE or migrating image to new PC and deleting from PC.<\/li> <\/ul>

    Recommendation to customers having this problem is to upgrade to 5.10.5 or later and then attempt to clean up the images again.<\/strong><\/p>

    As an\u00a0alternative when an upgrade is not possible or the issue remains post upgrade is to use a new\u00a0script has been\u00a0developed by engineering.\u00a0This script will be\u00a0part of AOS bundle as of 5.10.9 and 5.11.2. For previous versions it can be downloaded manually. This script will not make any catalog RPC calls and rather\u00a0just remove metadata cleanly from IDF and it is the last resort to\u00a0have a way to clean-up the entire image.<\/p>

    I am concerned that the script is not openly shared with the customers but will have to open a Nutanix case with Support who will further help with the issue.\u00a0<\/p>

    I hope this was helpful!!<\/p>

    \u00a0<\/p>

    Thank you,<\/p>

    Sneha P<\/p>","className":"post__content__best_answer"}">

查看原件
大卫·蒂格（David Teague），高级服务器工程师，洛德公司
该主题已关闭以供评论

9回复

C
是的，对我来说同样的问题。是否有通过CLI删除这些旧图像的方法？使用ACLI Image.Delete尝试，但遇到相同的错误。
d
同样在这里...
t
徽章 +1
同样的问题
j
同样的问题。有没有人运气解决这个问题？
s
徽章 +4
与其他问题相同。请问任何人吗？
j
对于我的问题，我最终与支持联系，发现我的图像与不再是Prism Central的一部分的集群绑定在一起。我可以从Prism Central中获得图像的唯一方法是支持我提供Python脚本以强行删除双层图像。
s
这里同样的问题。
joe_e您能否分享此处提供的支持的Python脚本？
\nJoe_E could you please share the python script that support provided here?","quoteUsername":"Steven2018","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
j
Userlevel 1
徽章 +7

我知道这个线程有点过时，但是我想知道是否有人发现了如何解决这个问题。我也有一个由已删除的PC实例拥有的束或孤立的图像文件。我无法通过棱镜元素将它们删除，ACLI报告了错误：不支持：不允许使用Kimagedelete操作，目录项目由集群000B4257-317拥有有什么想法在引擎盖下可能会做什么，提供的支持的Python脚本可能会做什么？有没有办法更新图像文件上的所有权元数据，以便它们将与原始CE集群重新关联？

I know this thread is a bit dated, but I wonder if anyone has discovered how to address this problem. I too have a bunch or orphaned image files that are owned by a deleted PC instance. I can\u2019t remove them via Prism element, and acli reports the error:\u00a0NotSupported: Operation kImageDelete not allowed, catalog item is owned by cluster 000b4257-317\u2026<\/em>\u00a0Any ideas what the elusive, support-provided Python script might be doing under the hood? Is there a way to update the ownership metadata on the image files so they will re-associate with the original CE cluster, perhaps?\u00a0<\/p>","quoteUsername":"jeffearl","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
s
秩
UserLevel 2
徽章 +1

@DavidTeague @Claus Jan @dennisffm @tanel @joe_e @风暴 @Steven2018 @jeffearl

感谢您在这里分享您的问题，我很抱歉您必须等待这么长时间。

为了解决您的问题，特定问题的问题早些时候使用了解决其他问题的解决方法。

但是现在解决了这个问题AOS 5.11和5.10.5。

这些更改解决了以下案例：

  • 如果图像由旧PC从新PC拥有，则可以删除图像。
  • 如果图像是孤儿图像（这意味着仅在PC上存在），则可以删除。
  • 如果图像在PE上，并且该PE不拥有 - 可以通过解开PE或将图像迁移到新PC并从PC上删除来删除图像。

向遇到此问题的客户推荐将升级到5.10.5或更高版本，然后尝试再次清理图像。

作为替代方案，当无法进行升级或升级后问题仍然是使用新脚本的问题。此脚本将是5.10.9和5.11.2的AOS捆绑包的一部分。对于以前的版本，可以手动下载。该脚本不会进行任何目录RPC调用，而只是从IDF中清除元数据，这是最后一种方法可以清理整个图像。

我担心该脚本没有与客户公开共享，但将不得不在支持该问题的支持下打开Nutanix案例。

我希望这可以帮到你！！

谢谢，

Sneha p

@DavidTeague<\/user-mention>\u00a0@Claus Jan<\/user-mention>\u00a0@DennisFFM<\/user-mention>\u00a0@tanel<\/user-mention>\u00a0@Joe_E<\/user-mention>\u00a0@storm<\/user-mention>\u00a0@Steven2018<\/user-mention>\u00a0@jeffearl<\/user-mention>\u00a0<\/p>

Thank you for sharing your questions here, I apologize you had to wait it so long.<\/p>

To address your issue, the issue in specific was earlier resolved using a workaround which resulted in many other issues.\u00a0<\/p>

But this issue is now resolved in\u00a0AOS 5.11 and\u00a05.10.5.<\/strong><\/p>

\u00a0<\/p>

The following cases are addressed by these changes:<\/p>

  • Allow images to be deleted if it owned by an older\u00a0PC from a new PC.<\/li>
  • If image is an orphan image (which means just present on PC)\u00a0it can be deleted.<\/li>
  • If image is on a PE and is not owned by that PE - The image can either be deleted by unregistering the PE or migrating image to new PC and deleting from PC.<\/li> <\/ul>

    Recommendation to customers having this problem is to upgrade to 5.10.5 or later and then attempt to clean up the images again.<\/strong><\/p>

    As an\u00a0alternative when an upgrade is not possible or the issue remains post upgrade is to use a new\u00a0script has been\u00a0developed by engineering.\u00a0This script will be\u00a0part of AOS bundle as of 5.10.9 and 5.11.2. For previous versions it can be downloaded manually. This script will not make any catalog RPC calls and rather\u00a0just remove metadata cleanly from IDF and it is the last resort to\u00a0have a way to clean-up the entire image.<\/p>

    I am concerned that the script is not openly shared with the customers but will have to open a Nutanix case with Support who will further help with the issue.\u00a0<\/p>

    I hope this was helpful!!<\/p>

    \u00a0<\/p>

    Thank you,<\/p>

    Sneha P<\/p>","quoteUsername":"Sneha Patekar","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu