Ok.. so I believe I figured out whats happening. This problem has been
causing issues for me for 2 years.
I was using safari pointed against CloudStack 4.3.1 env and noticed a
trend where my create vm would not work time to time. I initiated
"firebug" and went thru the deployment wizard once more, this time i
noticed the error:
"GET
/client/api?command=deployVirtualMachine&response=...layname=kvm03&name=kvm03&group=kvm&_=1422045760139
505 HTTP Version not supported 127m"
Then i did some googling and it brought me to this page, which
summarizes an issue with Tomcat 6.0.37 and 7.0.37. Versions in between
or lower maybe affected.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54947
Next is to try this out on version of tomcat that have this patched.
What tomcat versions newer than 6.0.37 can be used?
Regards
ilya
PS: Interesting observation, but Chrome would not show this error in
"debug mode". So for now, i'm sticking to Safari with Firebug for
debugging :)
On 12/17/14 5:55 PM, ilya musayev (JIRA) wrote:
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250989#comment-14250989
]
ilya musayev commented on CLOUDSTACK-7907:
------------------------------------------
Alex and Andrija
Besides management-server.log file, there should also be an api log file, can
you see your call there?
The management server log file should also log this api request, would it be
possible to include the log file and 200 lines above and 200 below the api call?
Regards
ilya
UI heavily broken
-----------------
Key: CLOUDSTACK-7907
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7907
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the default.)
Components: API
Affects Versions: 4.3.0, 4.4.1
Environment: not relevant
Reporter: Andrija Panic
Priority: Critical
(A serious one, that we encounter pretty often):
Issue: I start new VM deloyment wizard, choose template etc.... at the end when I click
the finish, when the job should be sent to MGMT server - simply nothing happens - so ajax
does't get executed at all, no litle circle spinning etc - no logs in mgmt server, simply
ajax doesn't get executed...Same behaviour sometimes happen when I click on
"Configure" on the VPC.
I confirmed behaviour in acs 4.3.0 and I'm still checking in 4.4.1, but I doubt
anything has changed
OR
2)
(not a big issue, however very annoying):
I filter instances by some account/domain, then click on some instance (view it's
properties or whatever), than in the breadcrumb I click back on "instances",
and instead of being show the page with all the filtered instances, I get back to the
home page of ACS...
So it doesn't really happens always, but randomly, with different browsers,
clearing all cache etc...
The issue here is that nothing get's logged to MGMT log at all...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
