whenever I try to edit my vms - it causes a error then reload. I can't edit the VMs at this point, I'm running Windows 7, but i recently created a Cent 7 Desktop with Firefox and still same issue.
Has anyone else seen this issue, its been frustrating on trying to work around it since it complete reloads the page either using the reload or Esc key, back to the login prompt, and I've tried to edit the VM from different views also - same results. this is connecting to the esxi host directly - no vcenter.
Cause: <div ng-include="tab.contentUrl">
Version: 1.21.0
Build: 5724747
ESXi: 6.5.0
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
Exception stack:
@https://172.16.134.89/ui/scripts/main.js:370:719
e@https://172.16.134.89/ui/scripts/main.js:319:3872
Fe/this.$get</</<@https://172.16.134.89/ui/scripts/main.js:319:23883
I/<@https://172.16.134.89/ui/scripts/main.js:319:15273
r@https://172.16.134.89/ui/scripts/main.js:318:21124
I@https://172.16.134.89/ui/scripts/main.js:319:15257
g@https://172.16.134.89/ui/scripts/main.js:319:11540
G/<@https://172.16.134.89/ui/scripts/main.js:319:11155
Ae</<.link@https://172.16.134.89/ui/scripts/main.js:322:1165
Z@https://172.16.134.89/ui/scripts/main.js:319:21038
I@https://172.16.134.89/ui/scripts/main.js:319:15506
g@https://172.16.134.89/ui/scripts/main.js:319:11540
G/<@https://172.16.134.89/ui/scripts/main.js:319:11155
Q/<@https://172.16.134.89/ui/scripts/main.js:319:12029
h@https://172.16.134.89/ui/scripts/main.js:319:14061
je</<.compile/</</<@https://172.16.134.89/ui/scripts/main.js:322:684
f/<@https://172.16.134.89/ui/scripts/main.js:320:10283
Pe/this.$get</n.prototype.$eval@https://172.16.134.89/ui/scripts/main.js:320:17493
Pe/this.$get</n.prototype.$digest@https://172.16.134.89/ui/scripts/main.js:320:16060
Pe/this.$get</n.prototype.$apply@https://172.16.134.89/ui/scripts/main.js:320:17773
l@https://172.16.134.89/ui/scripts/main.js:319:26637
F@https://172.16.134.89/ui/scripts/main.js:319:28783
wf/</C.onload@https://172.16.134.89/ui/scripts/main.js:319:29325
It's probably because the cent 7 64 guestOS identifier wasn't introduced until 6.5. I've seen someone else have a similar issue of errors thrown in the UI. If the host client is allowing you to create a 5.5-compatible VM with that ID, then it's probably a bug because AFAIK the Flex client will not allow that unless you choose 6.5 compatibility.
Update to v1.24 from the fling site which was just updated today.
Updated - thank you - it did improve things but appears to been an issue with specific vm
this error occurred still trying to edit the vm with the issue:
Cause: TypeError: ConfigOptionsOS is null Version: 1.24.0 Build: 7119706 ESXi: 6.5.0 Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 Exception stack: @https://172.16.134.89/ui/scripts/main.js:374:952 e@https://172.16.134.89/ui/scripts/main.js:319:3872 Fe/this.$get</</<@https://172.16.134.89/ui/scripts/main.js:319:23883 I/<@https://172.16.134.89/ui/scripts/main.js:319:15273 r@https://172.16.134.89/ui/scripts/main.js:318:21124 I@https://172.16.134.89/ui/scripts/main.js:319:15257 g@https://172.16.134.89/ui/scripts/main.js:319:11540 G/<@https://172.16.134.89/ui/scripts/main.js:319:11155 Q/<@https://172.16.134.89/ui/scripts/main.js:319:12029 h@https://172.16.134.89/ui/scripts/main.js:319:14061 ie</<.link/<@https://172.16.134.89/ui/scripts/main.js:321:31965 Pe/this.$get</n.prototype.$digest@https://172.16.134.89/ui/scripts/main.js:320:16343 Pe/this.$get</n.prototype.$apply@https://172.16.134.89/ui/scripts/main.js:320:17773 @https://172.16.134.89/ui/scripts/main.js:429:269 n.event.dispatch@https://172.16.134.89/ui/scripts/main.js:317:14412 n.event.add/r.handle@https://172.16.134.89/ui/scripts/main.js:317:11234
- i created a 5.5 compatible vm using centos 7 64bit - this vm was recently created but unused, I create several more shell vms, but going back to this one results in those errors when trying to edit.
I deleted it and tried recreating the 5.5 compatible vm and still had same error.
I also tried creating a new vm with a different name - used 5.5 compatibility - linux - cent 7 64 bit option and when you get the the compatibility, it would error out still same error as above.
Cause: TypeError: ConfigOptionsOS is null Version: 1.24.0 Build: 7119706 ESXi: 6.5.0 Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 Exception stack: @https://172.16.134.89/ui/scripts/main.js:374:952 e@https://172.16.134.89/ui/scripts/main.js:319:3872 Fe/this.$get</</<@https://172.16.134.89/ui/scripts/main.js:319:23883 I/<@https://172.16.134.89/ui/scripts/main.js:319:15273 r@https://172.16.134.89/ui/scripts/main.js:318:21124 I@https://172.16.134.89/ui/scripts/main.js:319:15257 g@https://172.16.134.89/ui/scripts/main.js:319:11540 G/<@https://172.16.134.89/ui/scripts/main.js:319:11155 Q/<@https://172.16.134.89/ui/scripts/main.js:319:12029 h@https://172.16.134.89/ui/scripts/main.js:319:14061 ie</<.link/<@https://172.16.134.89/ui/scripts/main.js:321:31965 Pe/this.$get</n.prototype.$digest@https://172.16.134.89/ui/scripts/main.js:320:16343 Pe/this.$get</n.prototype.$apply@https://172.16.134.89/ui/scripts/main.js:320:17773 @https://172.16.134.89/ui/scripts/main.js:429:269 n.event.dispatch@https://172.16.134.89/ui/scripts/main.js:317:14412 n.event.add/r.handle@https://172.16.134.89/ui/scripts/main.js:317:11234
It would work if i stuck to 6.5 compatibility which i ended up resorting to so I can move forward for now.
It's probably because the cent 7 64 guestOS identifier wasn't introduced until 6.5. I've seen someone else have a similar issue of errors thrown in the UI. If the host client is allowing you to create a 5.5-compatible VM with that ID, then it's probably a bug because AFAIK the Flex client will not allow that unless you choose 6.5 compatibility.
I suspect that is the case - guess the os selection should be updated to reflect the compatibility.
thank you
I just walked through the UI for creating a new VM, and I don't even see that choice in the drop-down list.
In fact, it's not even present for 6.5 compatibility, and it probably should be. So how were you using that guestOS ID unless you set it manually in the VMX?
This is what I got - at configuration step of the build -
Cause: TypeError: ConfigOptionsOS is null
Version: 1.24.0
Build: 7119706
ESXi: 6.5.0
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
Exception stack:
@https://172.16.134.89/ui/scripts/main.js:374:952
e@https://172.16.134.89/ui/scripts/main.js:319:3872
Fe/this.$get</</<@https://172.16.134.89/ui/scripts/main.js:319:23883
I/<@https://172.16.134.89/ui/scripts/main.js:319:15273
r@https://172.16.134.89/ui/scripts/main.js:318:21124
I@https://172.16.134.89/ui/scripts/main.js:319:15257
g@https://172.16.134.89/ui/scripts/main.js:319:11540
G/<@https://172.16.134.89/ui/scripts/main.js:319:11155
Q/<@https://172.16.134.89/ui/scripts/main.js:319:12029
h@https://172.16.134.89/ui/scripts/main.js:319:14061
ie</<.link/<@https://172.16.134.89/ui/scripts/main.js:321:31965
Pe/this.$get</n.prototype.$digest@https://172.16.134.89/ui/scripts/main.js:320:16343
Pe/this.$get</n.prototype.$apply@https://172.16.134.89/ui/scripts/main.js:320:17773
l@https://172.16.134.89/ui/scripts/main.js:319:26637
F@https://172.16.134.89/ui/scripts/main.js:319:28783
wf/</C.onload@https://172.16.134.89/ui/scripts/main.js:319:29325
This looks like just another GUI issue, where the available guest OSs are not updated correctly, in the drop down list.
You'll see different guest operating systems available depending on what you selected before.
Sample:
So what you currently need to do in order to see the correct guest operating systems, is to
André
PS: Even with the steps mentioned, the list still doesn't seem to completely match the guest OS support on the HCL.
Interesting. My results were somewhat different, and I noticed odd behavior depending on how I navigated in the UI. I'm pinging Etienne and will point him to this thread.