Solved

X-ray not working after upgrading AOS to 5.8.1

  • 20 August 2018
  • 8 replies
  • 13327 views

Badge
Hi,

I have upgraded AOS to 5.8.1. and thereafter Xray 3.0 test cases fails.
It fails at cloning the images.

BR
CL
icon

Best answer by Priyadarshi_Pd 21 August 2018, 08:10

Hello @CeylonLion
Unfortunately you will have to de-register the cluster from Prism central before you can run X-Ray on that cluster as a target. This is a known bug, and we are looking into resolving this.

Thanks
Pd
View original

This topic has been closed for comments

8 replies

Userlevel 7
Badge +35
Hi @CeylonLion Thanks for sharing, I'll see who I can ping and include on this post. 👍
Badge
Hi @CeylonLion Thanks for sharing, I'll see who I can ping and include on this post. 👍
Thanks alot. I cannot find any logs in CVM or xray host to troubleshoot nor any post on that.
It fails at cloning the images if I have manually deleted the golden template ( which created from the previous failed test case)
If golden template is there it fails at cluster clearance stage ( before cloning ).
Userlevel 2
Badge +10
Hi @CeylonLion are you by chance using prism central?
Userlevel 7
Badge +35
Hi @CeylonLion did you see the reply from Chris?
Badge
Hi @CeylonLion are you by chance using prism central?
@cwilson Yes. Using 5.8 Prism Central
Badge +2
Hello @CeylonLion
Unfortunately you will have to de-register the cluster from Prism central before you can run X-Ray on that cluster as a target. This is a known bug, and we are looking into resolving this.

Thanks
Pd
Badge
Hello @CeylonLion
Unfortunately you will have to de-register the cluster from Prism central before you can run X-Ray on that cluster as a target. This is a known bug, and we are looking into resolving this.

Thanks
Pd

Hi @Priyadarshi_Pd Thanks for the response.
But it is not an option for me.
I have used xray without a problem in AOS 5.5.4.
What are the bug impacted AOS versions then?
Badge +2
The bug is with PC image service - the mechanism X-Ray used to work with PC image service seems to have a bug with the most recent release.