Bug 800278

Summary: Browser compatibility issues on Chrome
Product: [Retired] CloudForms Cloud Engine Reporter: Rehana <redakkan>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED WONTFIX QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, dajohnso, deltacloud-maint, hbrock, ssachdev
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-09 13:39:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Chrome
none
FireFox
none
chrome_observation_2
none
FF_observation_2
none
firefox_observation_3
none
chrome_observation_3 none

Description Rehana 2012-03-06 08:20:21 UTC
Created attachment 567866 [details]
Chrome

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Login to conductor from Chrome(Version 17.0.963.56)
2.Go to "cloud"
3.Click "New comp outline" button

  
Actual results:
Observed that the alignment of page is not correct(PFA:chrome.png)


Expected results:
the alignment should be same as FireFox 10 (PFA.FF.png)


Additional info:

[root@ibm-ls22-03 ~]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.8.0-39.el6.noarch
aeolus-configure-2.5.0-16.el6.noarch
rubygem-aeolus-cli-0.3.0-12.el6.noarch
aeolus-all-0.8.0-39.el6.noarch
rubygem-aeolus-image-0.3.0-11.el6.noarch
aeolus-conductor-0.8.0-39.el6.noarch
aeolus-conductor-daemons-0.8.0-39.el6.noarch

Comment 1 Rehana 2012-03-06 08:21:11 UTC
Created attachment 567867 [details]
FireFox

Comment 2 Rehana 2012-03-19 08:54:14 UTC
Observation 2 on chrome browser:
Same issue as mentioned in the "Description" but this was observed under "Create Account" for Ec2 provider

1. Login to conductor
2. Add Ec2 provider
3. Now add account for the EC2 Provider

Actual result:
Observed that the alignment of page is not correct(PFA:chrome_observation_2.png) 

Expected results:
the alignment should be same as FireFox 10 (PFA.FF_observation_2.png)

Additional info:

rpm -qa | grep aeolus
aeolus-configure-2.5.0-18.el6.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.3.0-14.el6.noarch
aeolus-conductor-0.8.0-43.el6.noarch
aeolus-conductor-doc-0.8.0-43.el6.noarch
aeolus-conductor-daemons-0.8.0-43.el6.noarch
aeolus-all-0.8.0-43.el6.noarch

Comment 3 Rehana 2012-03-19 08:55:07 UTC
Created attachment 571057 [details]
chrome_observation_2

Comment 4 Rehana 2012-03-19 08:55:45 UTC
Created attachment 571058 [details]
FF_observation_2

Comment 5 Rehana 2012-03-19 09:55:48 UTC
Observation 3 on chrome browser:

Observed that in the "edit" page of "cloud provider account" for key and certificate label it says "Already uploaded.Re upload" and also "no file chosen"


screen shot attached for firefox(firefox_observation_3.png) and chrome(pfa: chrome_observation_3.png)

expected result:

It should not display both the messages, it is expected to behave same as firefox.


rpm -qa | grep aeolus
aeolus-configure-2.5.0-18.el6.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.3.0-14.el6.noarch
aeolus-conductor-0.8.0-43.el6.noarch
aeolus-conductor-doc-0.8.0-43.el6.noarch
aeolus-conductor-daemons-0.8.0-43.el6.noarch
aeolus-all-0.8.0-43.el6.noarch

Comment 6 Rehana 2012-03-19 09:56:23 UTC
Created attachment 571076 [details]
firefox_observation_3

Comment 7 Rehana 2012-03-19 09:57:18 UTC
Created attachment 571077 [details]
chrome_observation_3

Comment 8 Hugh Brock 2012-05-07 15:59:03 UTC
Could we recheck this on latest Chrome?

Comment 9 Dave Johnson 2012-05-09 13:39:10 UTC
So the length of the upload file field is not something we will worry with at this time.