[jira] [Assigned] (CLOUDSTACK-8075) UI > Instances menu > Add Instance > Select a template > add a new tab (4th tab): "shared" tab.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-8075: - Assignee: Jessica Wang (was: Brian Federle) Assigning to Jessica to implement API call changes. > UI > Instances menu > Add Instance > Select a template > add a new tab (4th > tab): "shared" tab. > --- > > Key: CLOUDSTACK-8075 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8075 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.5.0 > > Attachments: jessica-2014-12-16-A.PNG > > > (1) add a new tab (4th tab): "shared" tab. > (as attachment "jessica-2014-12-16-A") > (2) change label of the 3rd tab from "My Templates" to "Mine" (to be > consistent with label of 1st/2nd/4th tab) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6148) UI for feature "Use Secondary IP Address of NIC in load balancing"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-6148: -- Assignee: (was: Brian Federle) > UI for feature "Use Secondary IP Address of NIC in load balancing" > -- > > Key: CLOUDSTACK-6148 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6148 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang > Fix For: 4.4.3 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-1471) Pop up window for host details/(host related operation) are not properly alligned with window size
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-1471: -- Assignee: (was: Brian Federle) > Pop up window for host details/(host related operation) are not properly > alligned with window size > -- > > Key: CLOUDSTACK-1471 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1471 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: prashant kumar mishra >Priority: Minor > Fix For: 4.4.3 > > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, > screenshot-4.jpg > > > 1-Add large number of host in a cluster (in my environment i am having 33) > 2-When you place mouse pointer on last host in list(first from bottom) > 3-Pop up window will come up but details are not visible to user. > for more details please check attachment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5001) [UI] Cluster details are not getting displayed after completing the Add cluster Task
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-5001: -- Assignee: (was: Brian Federle) > [UI] Cluster details are not getting displayed after completing the Add > cluster Task > > > Key: CLOUDSTACK-5001 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5001 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.1 >Reporter: Sailaja Mada > Fix For: Future > > Attachments: alllogs.rar, errorsnap1.png > > > Steps: > 1. Configure Adv Zone with VMWARE > 2. Tried to add one more cluster from the same DataCenter. > Observation: > 1. AddCluster Task gets completed . But UI does not display the details of > the Cluster. > 2. We need to go back to Infra page and then list clusters to ensure that it > is added. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5000) [UI] UI does not invoke a screen to add second Primary storage if one of the zone does not have any pod
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-5000: -- Assignee: (was: Brian Federle) > [UI] UI does not invoke a screen to add second Primary storage if one of the > zone does not have any pod > --- > > Key: CLOUDSTACK-5000 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5000 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.1 >Reporter: Sailaja Mada > Fix For: 4.5.1 > > Attachments: NoAddPrimarySscreen.png, alllogs.rar > > > Steps: > 1. Configure Adv Zone with VMWARE with Zone wide Primary storage > 2. In the same setup i have one of the zone Disabled which have no pods and > clusters > 3. Tried to add one more Primary storage. > Observation: > UI does not invoke a screen to add second Primary storage if one of the zone > does not have any pod -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-3932) EN: Truncation issue occurred in secondary storage URL.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-3932. --- Resolution: Fixed > EN: Truncation issue occurred in secondary storage URL. > --- > > Key: CLOUDSTACK-3932 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3932 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: > Build#CloudPlatform-4.2-283(CloudPlatform-4.2-283-rhel6.3.tar.gz) > XenServer6.1 for Host Server > CentOS6.3 for NFS, CS-Mgr Servers. > Client & Browser: Win7-Chrome, Win7-Firefox22.0, Mac-Safari, Win8-IE10 >Reporter: Minying Bao >Priority: Minor > Attachments: Truncation.jpg > > > Repro Steps > 1. Open the browser and login to Web Portal. > 2. Navigate the “infrastructure” tab. > 3. Click “secondary storage-> view all” button. > 4. Move the mouse cursor to “plus” button. > 5. Observe the URL. > Expected Result > It should display as normal. > Actual Result > Truncation issue occurred. Please refer to the screenshots as attached. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-5139) Provision Secondary Storage Dialog incorrectly displays all storage providers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-5139: - Assignee: Jessica Wang (was: Brian Federle) > Provision Secondary Storage Dialog incorrectly displays all storage providers > - > > Key: CLOUDSTACK-5139 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5139 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: Chris Suich >Assignee: Jessica Wang >Priority: Critical > Labels: ui > Fix For: 4.3.0 > > Attachments: Screen Shot 2013-10-30 at 2.59.04 PM.png, Screen Shot > 2013-10-30 at 2.59.48 PM.png > > > The secondary storage provisioning dialog currently assumes any storage > provider returned by listStorageProviders will be able to be handled by the > UI. However, the UI only supports Nfs, S3 and Swift secondary storage. The > secondary storage provisioning dropdown should only display the providers > which it knows how to handle. > See attached images for example -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4445) [UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter with Chrome Browser
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4445: -- Priority: Major (was: Critical) > [UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter > with Chrome Browser > -- > > Key: CLOUDSTACK-4445 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4445 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.1 >Reporter: Sailaja Mada >Assignee: Brian Federle > Fix For: 4.3.0 > > Attachments: addremovedc.png, dedicatePOD1.png, dedicatecluster1.png, > dedicatehost1.png, dedicatezone1.png > > > Observation : > Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter . > Expected behavior : > We should have icons to identify these new options separately. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-5273) Applying static Nat by selecting the VM using List view under static Nat configuration page is making CS inaccessible.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-5273. --- Resolution: Duplicate > Applying static Nat by selecting the VM using List view under static Nat > configuration page is making CS inaccessible. > -- > > Key: CLOUDSTACK-5273 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5273 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: manasaveloori >Assignee: Brian Federle >Priority: Critical > Fix For: 4.3.0 > > > Steps: > 1.Have CS with any HV. > 2.Deploy a View VM. > 3.Go to the network and acquire an IP. > 4.Configure static nat->while selecting the VM we are having 2 options > ,one is list view[checkbox] and another is radio button. > 5.Select the VM using list view[checkbox] on left side and click apply > Observation: > Static nat rule will not get applied but the CS gets hanged and the > following is the error shown in fire bug. > 200 OK 1.39s jquery.js (line 7829) > TypeError: args.context.instances[0] is undefined > virtualmachineid: args.context.instances[0].id -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-5301) Router page is not listing VPC types router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-5301. --- Resolution: Unresolved Assignee: Alena Prokharchyk (was: Brian Federle) Alena, can you verify we should even display VPC routers on the infrastructure listing? I recall we are only showing non-VPC routers (as indicated by forvpc=false in the API call), though this may have changed. > Router page is not listing VPC types router > --- > > Key: CLOUDSTACK-5301 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5301 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 > Environment: 4.3 build : CloudPlatform-4.3-860-rhel6.3 >Reporter: shweta agarwal >Assignee: Alena Prokharchyk >Priority: Critical > Fix For: 4.3.0 > > Attachments: router.jpg > > > Repro steps : > create few VR and VPC VR > From infrastructure page select Router view all > Bug : > Router page is not showing VPC router (router belonging to type VPC)\ > this brings a discrepancy in Count shown on infrastructure page and the list > shown on router page > As in my case infrastructure page shows 16 router > but when i select router view all it shows only 12 entries as 4 router > belongs to VPC > API call > http://10.147.40.27:8080/client/api?command=listRouters&listAll=true&page=1&pagesize=20&response=json&sessionkey=lYYot5QzbQ89KDvUiFH66cT19hs%3D&forvpc=false&_=1385 > 633369178 > Need to make one more call > with VPC=true as well > This is affecting group by feature on router page introduced recently for > upgrading router . Grouping feature is also giving wrong count. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-5114) Select VM for static NAT screen shouldn't have checkbox.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-5114. --- Resolution: Fixed > Select VM for static NAT screen shouldn't have checkbox. > > > Key: CLOUDSTACK-5114 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5114 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Jessica Wang >Assignee: Brian Federle >Priority: Critical > Fix For: 4.3.0 > > Attachments: jessica_screenshot_1.jpg > > > The checkboxes shouldn’t be in “Select VM for static NAT” screen. > Only one VM is allowed to select, so it should be selected by only radio > button. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Reopened] (CLOUDSTACK-5301) Router page is not listing VPC types router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reopened CLOUDSTACK-5301: --- Assignee: Brian Federle (was: Alena Prokharchyk) > Router page is not listing VPC types router > --- > > Key: CLOUDSTACK-5301 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5301 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 > Environment: 4.3 build : CloudPlatform-4.3-860-rhel6.3 >Reporter: shweta agarwal >Assignee: Brian Federle >Priority: Critical > Fix For: 4.3.0 > > Attachments: router.jpg > > > Repro steps : > create few VR and VPC VR > From infrastructure page select Router view all > Bug : > Router page is not showing VPC router (router belonging to type VPC)\ > this brings a discrepancy in Count shown on infrastructure page and the list > shown on router page > As in my case infrastructure page shows 16 router > but when i select router view all it shows only 12 entries as 4 router > belongs to VPC > API call > http://10.147.40.27:8080/client/api?command=listRouters&listAll=true&page=1&pagesize=20&response=json&sessionkey=lYYot5QzbQ89KDvUiFH66cT19hs%3D&forvpc=false&_=1385 > 633369178 > Need to make one more call > with VPC=true as well > This is affecting group by feature on router page introduced recently for > upgrading router . Grouping feature is also giving wrong count. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-5301) Router page is not listing VPC types router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-5301. --- Resolution: Fixed > Router page is not listing VPC types router > --- > > Key: CLOUDSTACK-5301 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5301 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 > Environment: 4.3 build : CloudPlatform-4.3-860-rhel6.3 >Reporter: shweta agarwal >Assignee: Brian Federle >Priority: Critical > Fix For: 4.3.0 > > Attachments: router.jpg > > > Repro steps : > create few VR and VPC VR > From infrastructure page select Router view all > Bug : > Router page is not showing VPC router (router belonging to type VPC)\ > this brings a discrepancy in Count shown on infrastructure page and the list > shown on router page > As in my case infrastructure page shows 16 router > but when i select router view all it shows only 12 entries as 4 router > belongs to VPC > API call > http://10.147.40.27:8080/client/api?command=listRouters&listAll=true&page=1&pagesize=20&response=json&sessionkey=lYYot5QzbQ89KDvUiFH66cT19hs%3D&forvpc=false&_=1385 > 633369178 > Need to make one more call > with VPC=true as well > This is affecting group by feature on router page introduced recently for > upgrading router . Grouping feature is also giving wrong count. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4061) UI issue with Japanese localized ui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4061: -- Summary: UI issue with Japanese localized ui (was: UI issue with japanses localized ui) > UI issue with Japanese localized ui > --- > > Key: CLOUDSTACK-4061 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4061 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Ahmad Emneina >Assignee: Brian Federle > Fix For: 4.3.0 > > Attachments: localizationUI.png > > > Localized UI issue. see screenshot -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-4644) Tool Tip information is not provided for the new fields which are added in 4.2 ( Ex: Register Template , Compute Offering, Network Offering UI )
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-4644: - Assignee: Jessica Tomechak (was: Brian Federle) Hey Jessica, can you provide copy for the tooltip fields mentioned in this bug? Thanks. > Tool Tip information is not provided for the new fields which are added in > 4.2 ( Ex: Register Template , Compute Offering, Network Offering UI ) > > > Key: CLOUDSTACK-4644 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4644 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Jessica Tomechak > Fix For: 4.3.0 > > > Observation: > Tool Tip information is not provided for the new fields which are added in > 4.2 ( Ex: Register Template , Compute Offering, Network Offering UI ) > 1. Register Template UI : > New Fields are : Dynamically Scalable , Routing - There is no quick info > provided for these > 2. Create Compute Offering UI : isVolatile , Deployment Planner, Planner > mode > 3. Create Network Offering UI : Persistent , Default egress policy > 4. Add Affinity Groups : Name, Description > 5. Add Guest Network : Secondary Isolated VLAN ID: > 6. Add Region : id, name, end point > 7. Configure LDAP : All the fields, Except query filter -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-4061) UI issue with Japanese localized ui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4061. --- Resolution: Fixed > UI issue with Japanese localized ui > --- > > Key: CLOUDSTACK-4061 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4061 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Ahmad Emneina >Assignee: Brian Federle > Fix For: 4.3.0 > > Attachments: localizationUI.png > > > Localized UI issue. see screenshot -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-5368) ListViews marked with 'needsRefresh' do not have loading overlay removed on error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839002#comment-13839002 ] Brian Federle commented on CLOUDSTACK-5368: --- commit a00f1887c46632538b8390fa420cff4b1595f420 [4.3] Author: Chris Suich Date: Wed Dec 4 10:06:05 2013 -0500 Fixed issue with ListView 'needsRefresh' overlays not being removed JIRA-5368 commit 4ecf6df5f64cc048cac110dbb73f11c66dc16750 [master] Author: Chris Suich Date: Wed Dec 4 10:06:05 2013 -0500 Fixed issue with ListView 'needsRefresh' overlays not being removed JIRA-5368 > ListViews marked with 'needsRefresh' do not have loading overlay removed on > error > - > > Key: CLOUDSTACK-5368 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5368 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: Chris Suich >Assignee: Chris Suich > Fix For: 4.3.0 > > > ListView actions marked with 'needsRefresh' add a loading overlay before the > action is performed. If the operation succeeds, the overlay is properly > removed. If it fails, the overlay is NOT removed. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-5266) QuickView in "group by zone/pod/cluster" listView doesn't work. (QuickView in all other listView work well)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-5266. --- Resolution: Fixed > QuickView in "group by zone/pod/cluster" listView doesn't work. (QuickView in > all other listView work well) > > > Key: CLOUDSTACK-5266 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5266 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Brian Federle > Fix For: 4.3.0 > > Attachments: > QuickView_in_groupByZonePodClusterView_in_VirtualRouters_page.jpg > > > QuickView in "group by zone/pod/cluster" listView (in Virtual Routers page) > doesn't work. > QuickView in all other listView work well. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-4046) Can't edit global settings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4046: -- Fix Version/s: (was: 4.3.0) Future This will be fixed in a future release, once several widget/UI refactor tasks have been completed. > Can't edit global settings > -- > > Key: CLOUDSTACK-4046 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4046 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Assignee: Brian Federle >Priority: Minor > Fix For: Future > > Attachments: CloudStack_GlobalSettingsOK.png, > CloudStack_GlobalSettingsOK2.png, CloudStack_GlobalSettingsOK3.png > > > Hi, > in our Cloudstack, we've got a strange behavior. > gradually as one moves down the settings, the "Edit" box disappears. > See screenshots. > Regards -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-2570) [UI]Resource Name is mentioned twice with view VNMC devices
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-2570. --- Resolution: Fixed > [UI]Resource Name is mentioned twice with view VNMC devices > > > Key: CLOUDSTACK-2570 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2570 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Brian Federle >Priority: Minor > Fix For: 4.3.0 > > Attachments: screenshot-1.jpg > > > Setup: Advanced Networking Zone with Nexus VMWARE Cluster > Steps: > 1. Access Management server as adimin > 2. Infrastructure -> Physical Network -> Network service providers -> Add > VNMC provider > 3. View VNMC devices -> Select the device > Observation: > 1.Resource Name is mentioned twice with view VNMC devices . It has to be > removed. (Attached the snapshot) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5450) Data values cleared when navigating back through add zone wizard
Brian Federle created CLOUDSTACK-5450: - Summary: Data values cleared when navigating back through add zone wizard Key: CLOUDSTACK-5450 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5450 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Brian Federle Priority: Minor Fix For: Future When adding an advanced zone using the add zone wizard, navigating back to the beginning of the wizard and then stepping forward again resulted in the guest VLAN range and the primary storage server address being cleared necessitating the values to be reentered. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-4938) Add account password confirmation broken
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4938. --- Resolution: Fixed Commit 8821d75442cb68ff2fbca4debc282a335c502754 in branch refs/heads/master from Brian Federle [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8821d75 ] CLOUDSTACK-5480: Fix broken password confirm validation Properly destroy add account dialog on close, to fix password confirm validation pointing to wrong dialog's field. > Add account password confirmation broken > > > Key: CLOUDSTACK-4938 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4938 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Brian Federle >Assignee: Brian Federle >Priority: Blocker > Fix For: 4.3.0 > > > Currently the password confirmation field is not validating, even if the > confirmation value is correct. The validation needs to be fixed, otherwise > the add account dialog will not execute. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-4938) Add account password confirmation broken
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847653#comment-13847653
]
Brian Federle commented on CLOUDSTACK-4938:
---
Ian, give this a try again and see if my fix worked. I think the problem is
that your custom UI wasn't removed from the DOM after the dialog closed,
causing the password confirm to incorrectly point to one of the old forms, in
some cases -- I couldn't reproduce consistently.
When using the standard widgets (i.e., the built in createForm: {} options) DOM
cleanup should be handled automatically, but with custom widgets you need to
explicitly destroy any UI, or at least verify to make sure it was removed from
the DOM via Firebug, i.e, after the dialog closes make sure there are no
instances of $('.account-wizard') left.
> Add account password confirmation broken
>
>
> Key: CLOUDSTACK-4938
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4938
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.3.0
>Reporter: Brian Federle
>Assignee: Brian Federle
>Priority: Blocker
> Fix For: 4.3.0
>
>
> Currently the password confirmation field is not validating, even if the
> confirmation value is correct. The validation needs to be fixed, otherwise
> the add account dialog will not execute.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-3067) UI for Dedicating POD/Cluster/Host is misleading Icons should be changed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-3067: -- Attachment: release.png dedicate.png > UI for Dedicating POD/Cluster/Host is misleading Icons should be changed. > - > > Key: CLOUDSTACK-3067 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3067 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Brian Federle > Fix For: 4.3.0 > > Attachments: DedicateResource_Previous.jpg, > DedicateResource_current.jpg, ReleaseResource_current.jpg, > ReleaseResource_expected.jpg, dedicate.png, release.png > > > The UI Icons for dedicating the Pod/Cluster/Host are not proper.The Icons > resemble the Edit option and they are the same for dedicating the > Pod/Cluster/Host and also for releasing the same. > The UI should be changed to dedicating and releasing with the icons which are > used for dedicating the Zone and releasing the Zone. > The current UI looks like edit option and that is misleading as we see two > options side by side(i.e edit as well dedicating option). -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-3067) UI for Dedicating POD/Cluster/Host is misleading Icons should be changed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-3067. --- Resolution: Cannot Reproduce Looks like the icons were fixed previously, please verify in the latest build. I posted screenshots of the icons I see for all dedicate/release actions. > UI for Dedicating POD/Cluster/Host is misleading Icons should be changed. > - > > Key: CLOUDSTACK-3067 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3067 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Brian Federle > Fix For: 4.3.0 > > Attachments: DedicateResource_Previous.jpg, > DedicateResource_current.jpg, ReleaseResource_current.jpg, > ReleaseResource_expected.jpg, dedicate.png, release.png > > > The UI Icons for dedicating the Pod/Cluster/Host are not proper.The Icons > resemble the Edit option and they are the same for dedicating the > Pod/Cluster/Host and also for releasing the same. > The UI should be changed to dedicating and releasing with the icons which are > used for dedicating the Zone and releasing the Zone. > The current UI looks like edit option and that is misleading as we see two > options side by side(i.e edit as well dedicating option). -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-4445) [UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter with Chrome Browser
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4445. --- Resolution: Cannot Reproduce Icons look fine for me in both Chrome and FF. Possibly was a cache issue? > [UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter > with Chrome Browser > -- > > Key: CLOUDSTACK-4445 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4445 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.1 >Reporter: Sailaja Mada >Assignee: Brian Federle > Fix For: 4.3.0 > > Attachments: addremovedc.png, dedicatePOD1.png, dedicatecluster1.png, > dedicatehost1.png, dedicatezone1.png > > > Observation : > Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter . > Expected behavior : > We should have icons to identify these new options separately. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-1816) [UI] UI support for Cisco ASA 1000v
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-1816. --- Resolution: Fixed This was implemented in 4.2, so this bug should be closed (maybe forgot to mark resolved?) > [UI] UI support for Cisco ASA 1000v > --- > > Key: CLOUDSTACK-1816 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1816 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Brian Federle >Assignee: Jessica Wang > Fix For: 4.3.0 > > Original Estimate: 120h > Remaining Estimate: 120h > > New service provider UI needs to be added for Cisco ASA 1000v. This includes > standard list/add/remove actions, in addition to provider specific firewall > rule management. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-3266) [UI] Failed to delete Anti affinitygroup for the first time
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-3266. --- Resolution: Cannot Reproduce Deleting affinity group right after creation works fine for me...most likely due to an API fix where the group's ID is now being returned correctly after creation. > [UI] Failed to delete Anti affinitygroup for the first time > > > Key: CLOUDSTACK-3266 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3266 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sailaja Mada > Fix For: 4.3.0 > > Attachments: apilog.log, deleteAntiAff.png, management-server.log > > > Setup : Advanced Networking Zone - VMWARE > Steps: > 1. Have one instance deployed with enw user account > 2. later create Anti affinitygroup 1 > 3. Tried to delete it from UI > It failed saying: > 2013-06-28 14:37:18,594 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) > ===END=== 10.144.6.19 -- GET > command=deleteAffinityGroup&response=json&sessionkey=cAlesfWeL1LC7v5VBrAi%2B%2FiRJ%2F8%3D&_=1372410634034 > 2013-06-28 14:37:18,595 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-113:job-91) Executing > org.apache.cloudstack.api.command.user.affinitygroup.DeleteAffinityGroupCmd > for job-91 > 2013-06-28 14:37:18,620 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-113:job-91) Unexpected exception while executing > org.apache.cloudstack.api.command.user.affinitygroup.DeleteAffinityGroupCmd > com.cloud.exception.InvalidParameterValueException: Either the affinity group > Id or group name must be specified to delete the group > at > org.apache.cloudstack.affinity.AffinityGroupServiceImpl.deleteAffinityGroup(AffinityGroupServiceImpl.java:147) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.affinitygroup.DeleteAffinityGroupCmd.execute(DeleteAffinityGroupCmd.java:125) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-06-28 14:37:18,620 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-113:job-91) Complete async job-91, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: Either the affinity group Id or > group name must be specified to delete the group > 5. Again tried deleting the second group. > Then it deleted the group. (Attached UI and logs) -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5477) TypeError: args.context.snapshots is undefined url: createURL("listSnapshots&id=" + args.context.snapshots[0].id),
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Federle updated CLOUDSTACK-5477:
--
Priority: Critical (was: Major)
Moving to critical since it is a widget issue that may affect multiple places
in UI for 4.3
> TypeError: args.context.snapshots is undefined url:
> createURL("listSnapshots&id=" + args.context.snapshots[0].id),
> -
>
> Key: CLOUDSTACK-5477
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5477
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.3.0
> Environment: Storage,Volumes,
>Reporter: rashid
>Assignee: Brian Federle
>Priority: Critical
> Fix For: 4.3.0
>
>
> It's a UI bug. Through api i am getting results.
> Goto INSTANCE>(VMNAME)>view volumes>
> ex: Home>Instances> win2012> Volumes>ROOT-10
> After this
> goto Storage>VOLUMES>select any volume
> ex: Home> Storage - Volumes > ROOT-10
> nothing is displayed.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Assigned] (CLOUDSTACK-5477) TypeError: args.context.snapshots is undefined url: createURL("listSnapshots&id=" + args.context.snapshots[0].id),
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Federle reassigned CLOUDSTACK-5477:
-
Assignee: Brian Federle
> TypeError: args.context.snapshots is undefined url:
> createURL("listSnapshots&id=" + args.context.snapshots[0].id),
> -
>
> Key: CLOUDSTACK-5477
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5477
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.3.0
> Environment: Storage,Volumes,
>Reporter: rashid
>Assignee: Brian Federle
> Fix For: 4.3.0
>
>
> It's a UI bug. Through api i am getting results.
> Goto INSTANCE>(VMNAME)>view volumes>
> ex: Home>Instances> win2012> Volumes>ROOT-10
> After this
> goto Storage>VOLUMES>select any volume
> ex: Home> Storage - Volumes > ROOT-10
> nothing is displayed.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5477) TypeError: args.context.snapshots is undefined url: createURL("listSnapshots&id=" + args.context.snapshots[0].id),
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Federle resolved CLOUDSTACK-5477.
---
Resolution: Fixed
> TypeError: args.context.snapshots is undefined url:
> createURL("listSnapshots&id=" + args.context.snapshots[0].id),
> -
>
> Key: CLOUDSTACK-5477
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5477
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.3.0
> Environment: Storage,Volumes,
>Reporter: rashid
>Assignee: Brian Federle
>Priority: Critical
> Fix For: 4.3.0
>
>
> It's a UI bug. Through api i am getting results.
> Goto INSTANCE>(VMNAME)>view volumes>
> ex: Home>Instances> win2012> Volumes>ROOT-10
> After this
> goto Storage>VOLUMES>select any volume
> ex: Home> Storage - Volumes > ROOT-10
> nothing is displayed.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5276) ListView for selecting VM under LB,portforwarding and static nat configuration pages is not valid.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-5276. --- Resolution: Fixed > ListView for selecting VM under LB,portforwarding and static nat > configuration pages is not valid. > > > Key: CLOUDSTACK-5276 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5276 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: manasaveloori >Assignee: Brian Federle >Priority: Critical > Fix For: 4.3.0 > > Attachments: listview.jpg > > > While configuring the portforwarding,LB and static NAT,we need to select the > VMs. > As per the new UI we are getting two options to select the VMS(listview on > left side and individual select option on right side). > While selecting the VMs using the listview widget, the rules are not getting > applied in VR but just seen in UI.The correct functionality is with right > hand side select buttons. I think the listview is not valid under these > configuration pages. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5532) Long tag values are not readable within the UI
Brian Federle created CLOUDSTACK-5532: - Summary: Long tag values are not readable within the UI Key: CLOUDSTACK-5532 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5532 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Brian Federle Assignee: Brian Federle Priority: Critical Fix For: 4.3.0 If tag key and/or value are very long, then it causes overflow and wrapping in the UI. The key and value need to be truncated if they exceed a min. width. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5532) Long tag values are not readable within the UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-5532. --- Resolution: Fixed > Long tag values are not readable within the UI > -- > > Key: CLOUDSTACK-5532 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5532 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Brian Federle >Assignee: Brian Federle >Priority: Critical > Fix For: 4.3.0 > > > If tag key and/or value are very long, then it causes overflow and wrapping > in the UI. The key and value need to be truncated if they exceed a min. width. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5476) [UI] zone level settings are missing from UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-5476. --- Resolution: Fixed > [UI] zone level settings are missing from UI > - > > Key: CLOUDSTACK-5476 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5476 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: prashant kumar mishra >Assignee: Brian Federle >Priority: Critical > Fix For: 4.3.0 > > Attachments: 4.3 screenshot.jpg > > > steps to repro > -- > 1-prepare a cs setup > 2- goto zone > 3-there should be a setting tab > actual > - > zone level setting tab is missing ;please check scareen shot -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5476) [UI] zone level settings are missing from UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-5476. --- Resolution: Cannot Reproduce It was a CSS issue, where the settings tab was wrapping over so it wasn't visible. Maybe try clearing your browser/tomcat cache? > [UI] zone level settings are missing from UI > - > > Key: CLOUDSTACK-5476 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5476 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: prashant kumar mishra >Assignee: Brian Federle >Priority: Critical > Fix For: 4.3.0 > > Attachments: 4.3 screenshot.jpg > > > steps to repro > -- > 1-prepare a cs setup > 2- goto zone > 3-there should be a setting tab > actual > - > zone level setting tab is missing ;please check scareen shot -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Assigned] (CLOUDSTACK-5551) [UI] Search not working in account's setting page
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Federle reassigned CLOUDSTACK-5551:
-
Assignee: Rayees Namathponnan (was: Brian Federle)
Rayees, I fixed the UI for the settings pages' search, however the API is still
not filtering properly when searching by the 'name' field. This needs to be
corrected at the API level.
i.e., if I correctly pass '&name=...' to listConfigurations, I still get every
item:
.../client/api?command=listConfigurations&zoneid=4d4f73aa-5ba6-441d-9001-20f9a5f58a62&response=json&...&name=guest.domain.suffix&listAll=true&page=1&pagesize=20&...
{ "listconfigurationsresponse" : { "count":8 ,"configuration" : [...] } }
> [UI] Search not working in account's setting page
> --
>
> Key: CLOUDSTACK-5551
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5551
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.3.0
> Environment: branch 4.3
>Reporter: Rayees Namathponnan
>Assignee: Rayees Namathponnan
>Priority: Critical
> Fix For: 4.3.0
>
>
> Steps to reproduce
> Step 1 : Install Management server with 4.3 build
> Step 2 : create an account
> Step 3 : select the account -> select setting
> Step 4 : In search box, enter
> Expected Result
> Nothing should be displayed in search result
> Actual Result
> Search is not working here, same content before search displayed
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5544) JS error on snapshot view of storage tab
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Federle resolved CLOUDSTACK-5544.
---
Resolution: Fixed
> JS error on snapshot view of storage tab
>
>
> Key: CLOUDSTACK-5544
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5544
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.3.0
>Reporter: Chris Suich
>Assignee: Brian Federle
> Labels: ui
> Fix For: 4.3.0
>
>
> In this bit of code:
>var snapshotActionfilter = function(args) {
>var jsonObj = args.context.item;
>if (jsonObj.state == 'Destroyed') {
>return [];
>}
>var allowedActions = [];
>if (jsonObj.state == "BackedUp") {
>allowedActions.push("createTemplate");
>allowedActions.push("createVolume");
>if (jsonObj.revertable && args.context.volumes[0].vmstate ==
> "Stopped") {
>allowedActions.push("revertSnapshot");
>}
>}
>allowedActions.push("remove");
>return allowedActions;
>}
> An error is thrown on the snapshot view of the storage tab if
> jsonObj.revertable is true, since args.context.volumes is undefined when on
> this page.
> We should remove the ' && args.context.volumes[0].vmstate == "Stopped"'
> condition and simply make that check on the server side since the volume/vm
> state information is not available when looking at the snapshots page.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Reopened] (CLOUDSTACK-2340) [AWS Style Health Checks] Response of the API listLoadBalancerRuleInstances should show the service state of a VM if health check is configured for it
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reopened CLOUDSTACK-2340: --- > [AWS Style Health Checks] Response of the API listLoadBalancerRuleInstances > should show the service state of a VM if health check is configured for it > -- > > Key: CLOUDSTACK-2340 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2340 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.2.0 >Reporter: Abhinav Roy >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > > In the current implementation of the API listLoadBalancerRuleInstances we > don't see the service state of a VM which has health check configured and > hence the user doesn't get to know the state of that service from the UI. > So, filing this bug so that we add some parameter in the API response which > shows the service state and hence using that we can make the state visible in > the UI also. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4010) Change required in the UI to pass startdate/enddate parameter rather than olderthan parameter in the archive/delete alerts/events API.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4010. --- Resolution: Fixed > Change required in the UI to pass startdate/enddate parameter rather than > olderthan parameter in the archive/delete alerts/events API. > -- > > Key: CLOUDSTACK-4010 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4010 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sanjay Tripathi >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.2.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4035) [Upgrade][2.2.16 to 4.2] [UI] Autoscale wizard missing counter param in UI - fails configuration
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Federle updated CLOUDSTACK-4035:
--
Component/s: (was: UI)
Upgrade
API
Change label to remove UI since this looks like a backend issue. If this indeed
ends up requiring a UI fix, please re-add UI label.
> [Upgrade][2.2.16 to 4.2] [UI] Autoscale wizard missing counter param in UI -
> fails configuration
>
>
> Key: CLOUDSTACK-4035
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4035
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Upgrade
>Affects Versions: 4.2.0
> Environment: Upgraded setup from 2.2.16 to 4.2, Netscaler as external
> LB device
>Reporter: Sowmya Krishnan
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: countermissing.png, DB_DUMP_2216_before_upgrade.sql,
> DB_DUMP_42_after_upgrade.sql
>
>
> Steps
> =
> Upgrade from 2.2.16 to 4.2.
> Create a network offering with LB service provided by Netscaler
> Acquire a public IP and configure autoscaling with it
> Fails during configuration since counter value is missing
> Firebug log:
> { "conditionresponse" :
> {"uuidList":[],"errorcode":431,"cserrorcode":,"errortext":"Unable to
> execute API command condition due to missing parameter counterid"} }
> Attached screen shot
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4057) Cannot unselect VPC network when only want to select isolated network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4057. --- Resolution: Fixed commit 1c2362c163e68041553b8307b421f1060166cd3a Author: Brian Federle Date: Fri Jul 26 14:29:55 2013 -0700 Instance wizard: Fix logic preventing VPC network from being unchecked > Cannot unselect VPC network when only want to select isolated network > - > > Key: CLOUDSTACK-4057 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4057 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Ahmad Emneina >Priority: Blocker > Fix For: 4.2.0 > > Attachments: vpc_issue.png > > > I got an environment where an isolated network (non-VPC, cfiso1) and an > isolated network (VPC, WebTier) is present. > When trying to add to a new instance cfiso01 only this is not possible in the > GUI. I am not able to unselect “WebTier”. > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4078) [UI][Upgrade]List VM details and NICS UI is not proper after upgrading from 3.0.7 to 4.2.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4078: -- Component/s: (was: UI) Upgrade issue, so most likely a backend issue. Removing UI component. > [UI][Upgrade]List VM details and NICS UI is not proper after upgrading from > 3.0.7 to 4.2. > - > > Key: CLOUDSTACK-4078 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4078 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >Affects Versions: 4.2.0 > Environment: Upgrade from 3.0.7 to 4.2 >Reporter: manasaveloori >Priority: Critical > Fix For: 4.2.0 > > Attachments: VM_details.jpg, VM_NICS.jpg > > > Steps: > 1.Have CS with 3.0.7 build. > 2.Deploy VMs. > 3.Upgrade to 4.2 . > Observed that the VM details and NICS tabs are not properly aligned. > Attaching the screen shot for the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4061) UI issue with japanses localized ui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4061: -- Priority: Major (was: Critical) Cosmetic issue. Reducing priority > UI issue with japanses localized ui > --- > > Key: CLOUDSTACK-4061 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4061 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Ahmad Emneina > Fix For: 4.2.0 > > Attachments: localizationUI.png > > > Localized UI issue. see screenshot -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2340) [AWS Style Health Checks] Response of the API listLoadBalancerRuleInstances should show the service state of a VM if health check is configured for it
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-2340. --- Resolution: Fixed > [AWS Style Health Checks] Response of the API listLoadBalancerRuleInstances > should show the service state of a VM if health check is configured for it > -- > > Key: CLOUDSTACK-2340 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2340 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.2.0 >Reporter: Abhinav Roy >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > > In the current implementation of the API listLoadBalancerRuleInstances we > don't see the service state of a VM which has health check configured and > hence the user doesn't get to know the state of that service from the UI. > So, filing this bug so that we add some parameter in the API response which > shows the service state and hence using that we can make the state visible in > the UI also. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2955) [PortableIPrange][UI] deletePortableIpRange fails because of UI firing an incorrect API
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Federle updated CLOUDSTACK-2955:
--
Attachment: response.jpg
> [PortableIPrange][UI] deletePortableIpRange fails because of UI firing an
> incorrect API
> ---
>
> Key: CLOUDSTACK-2955
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2955
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.2.0
> Environment: commit id # 673b293d75419a4b76379092db2b204cdc6160a4
>Reporter: venkata swamybabu budumuru
>Assignee: Brian Federle
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: response.jpg
>
>
> Steps to reproduce :
> 1. Have latest CS installation with at least 1 advanced zone
> 2. createPortableIpRange with at least 1 range
> 3. Try to deletePortableIpRange which was just added in previous step
> Observations:
> (i) deletePortablIpRange fails with the following error.
> Here is the firebug snippet
> _ 1371032217698
> command deletePortableIpRange
> response json
> sessionkey62Rxynqub3NPvpxcfpUlvhj+1aE=
> { "deleteportablepublicipresponse" :
> {"uuidList":[],"errorcode":431,"cserrorcode":,"errortext":"Unable to
> execute API command deleteportablepublicip due to missing parameter id"} }
> (ii) Above API didn't send the parameter "id" hence it failed in this case.
> Attaching all the logs along with db dump to the bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2955) [PortableIPrange][UI] deletePortableIpRange fails because of UI firing an incorrect API
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Federle updated CLOUDSTACK-2955:
--
Component/s: (was: UI)
API
Assignee: (was: Brian Federle)
API bug. Please see attached screenshot; the jobresult object is returning null
as the key instead of 'portableiprange'
> [PortableIPrange][UI] deletePortableIpRange fails because of UI firing an
> incorrect API
> ---
>
> Key: CLOUDSTACK-2955
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2955
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: commit id # 673b293d75419a4b76379092db2b204cdc6160a4
>Reporter: venkata swamybabu budumuru
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: response.jpg
>
>
> Steps to reproduce :
> 1. Have latest CS installation with at least 1 advanced zone
> 2. createPortableIpRange with at least 1 range
> 3. Try to deletePortableIpRange which was just added in previous step
> Observations:
> (i) deletePortablIpRange fails with the following error.
> Here is the firebug snippet
> _ 1371032217698
> command deletePortableIpRange
> response json
> sessionkey62Rxynqub3NPvpxcfpUlvhj+1aE=
> { "deleteportablepublicipresponse" :
> {"uuidList":[],"errorcode":431,"cserrorcode":,"errortext":"Unable to
> execute API command deleteportablepublicip due to missing parameter id"} }
> (ii) Above API didn't send the parameter "id" hence it failed in this case.
> Attaching all the logs along with db dump to the bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-4089) Provide a drop down to specify VLAN,Switch type, Traffic label name while configuring Zone(VMWARE)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-4089: - Assignee: Brian Federle > Provide a drop down to specify VLAN,Switch type, Traffic label name while > configuring Zone(VMWARE) > -- > > Key: CLOUDSTACK-4089 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4089 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: dropPN.png > > > Observation: > Setup: VMWARE > 1. While configuring Zone, During Physical network creation , currently > there is a text field to specify VLAN Id for the traffic , Traffic label > name & Switch type (vmwaresvs,vmwaredvs,nexusdvs) > 2. It is text field and there is a possibility of missing some of the > parameters. > 3. While adding cluster we have an option to specify the traffic label name > and drop down to select the Switch type. > This is the request to provide a drop down to specify VLAN,Switch type, > Traffic label name while configuring Zone(VMWARE). This will avoid a lot of > confusion between Zone vs Cluster level configuration. > It also simplifies the configuration process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-4089) Provide a drop down to specify VLAN,Switch type, Traffic label name while configuring Zone(VMWARE)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-4089: - Assignee: Jessica Wang (was: Brian Federle) Assigning to Jessica to implement/modify API calls for this. > Provide a drop down to specify VLAN,Switch type, Traffic label name while > configuring Zone(VMWARE) > -- > > Key: CLOUDSTACK-4089 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4089 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > Attachments: dropPN.png > > > Observation: > Setup: VMWARE > 1. While configuring Zone, During Physical network creation , currently > there is a text field to specify VLAN Id for the traffic , Traffic label > name & Switch type (vmwaresvs,vmwaredvs,nexusdvs) > 2. It is text field and there is a possibility of missing some of the > parameters. > 3. While adding cluster we have an option to specify the traffic label name > and drop down to select the Switch type. > This is the request to provide a drop down to specify VLAN,Switch type, > Traffic label name while configuring Zone(VMWARE). This will avoid a lot of > confusion between Zone vs Cluster level configuration. > It also simplifies the configuration process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-4089) Provide a drop down to specify VLAN,Switch type, Traffic label name while configuring Zone(VMWARE)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729831#comment-13729831 ] Brian Federle commented on CLOUDSTACK-4089: --- Jessica: I just added the new fields for the configure traffic type dialog (see screenshot). Can you go in and add the necessary server calls? Sailaja: Please specify exactly what new API parameters need to be passed in, since I did not see them in this bug. > Provide a drop down to specify VLAN,Switch type, Traffic label name while > configuring Zone(VMWARE) > -- > > Key: CLOUDSTACK-4089 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4089 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > Attachments: dropPN.png, edit-traffic-type-vmware.jpg > > > Observation: > Setup: VMWARE > 1. While configuring Zone, During Physical network creation , currently > there is a text field to specify VLAN Id for the traffic , Traffic label > name & Switch type (vmwaresvs,vmwaredvs,nexusdvs) > 2. It is text field and there is a possibility of missing some of the > parameters. > 3. While adding cluster we have an option to specify the traffic label name > and drop down to select the Switch type. > This is the request to provide a drop down to specify VLAN,Switch type, > Traffic label name while configuring Zone(VMWARE). This will avoid a lot of > confusion between Zone vs Cluster level configuration. > It also simplifies the configuration process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4089) Provide a drop down to specify VLAN,Switch type, Traffic label name while configuring Zone(VMWARE)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4089: -- Attachment: edit-traffic-type-vmware.jpg > Provide a drop down to specify VLAN,Switch type, Traffic label name while > configuring Zone(VMWARE) > -- > > Key: CLOUDSTACK-4089 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4089 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > Attachments: dropPN.png, edit-traffic-type-vmware.jpg > > > Observation: > Setup: VMWARE > 1. While configuring Zone, During Physical network creation , currently > there is a text field to specify VLAN Id for the traffic , Traffic label > name & Switch type (vmwaresvs,vmwaredvs,nexusdvs) > 2. It is text field and there is a possibility of missing some of the > parameters. > 3. While adding cluster we have an option to specify the traffic label name > and drop down to select the Switch type. > This is the request to provide a drop down to specify VLAN,Switch type, > Traffic label name while configuring Zone(VMWARE). This will avoid a lot of > confusion between Zone vs Cluster level configuration. > It also simplifies the configuration process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4077) UI glitches for Archive/Delete events and alerts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4077. --- Resolution: Incomplete Please provide documentation for what IDs correspond to what event types, I cannot find it in the bug report. The event type field can then be converted to a drop-down of specific event type IDs. > UI glitches for Archive/Delete events and alerts > > > Key: CLOUDSTACK-4077 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4077 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Latest Cloudstack 4.2 build with host on KVM >Reporter: Pavan Kumar Bandarupally >Priority: Critical > Fix For: 4.2.0 > > Attachments: after-delete.jpg, before-delete.jpg, UI bug archive > events type number.jpg, UI bug delete alerts TYPE.jpg, UI bug end date.jpg, > UI bug start date.jpg > > > In the UI page for Archive/Delete alerts and events, some of the tool-tip > advices are misleading. > 1) For Archive events, By event type, the tool-tip gives and advice "Archive > all events by specifying its TYPE (integer number). For events TYPE will be > something like USER.LOGIN and not integer value. For alerts TYPE will be > integer number. [ UI bug archive events type number.jpg ] > 2) 1) For Delete alerts, By event type, the tool-tip gives and advice > "Archive all events by specifying its TYPE (USER.LOGIN). For alerts TYPE will > be integer and not string [ UI bug delete alerts TYPE.jpg ] > 3) For Archive events, By date, both start date and end date tool-tips bear > same message "Archive all events which have been created after this date" . > For end date the message should be " before this date" [ UI bug start > date.jpg and UI bug end date.jpg ] > 4) If an event is Archived individually ( by selecting archive event from the > event Quickview description ), the event will not be removed from the UI > until the page is reloaded. ( User has to navigate to some page or click on > the left side events tab again for the event to disappear from UI). > 5) When user deletes an event by type, remaining events (other than the > deleted events) will be shown twice (redundantly) in the UI page immediately > after the delete operation. User has to reload the page to see the events > distinctly. [ before-delete.jpg and after-delete.jpg ] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CLOUDSTACK-4077) UI glitches for Archive/Delete events and alerts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reopened CLOUDSTACK-4077: --- > UI glitches for Archive/Delete events and alerts > > > Key: CLOUDSTACK-4077 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4077 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Latest Cloudstack 4.2 build with host on KVM >Reporter: Pavan Kumar Bandarupally >Priority: Critical > Fix For: 4.2.0 > > Attachments: after-delete.jpg, before-delete.jpg, UI bug archive > events type number.jpg, UI bug delete alerts TYPE.jpg, UI bug end date.jpg, > UI bug start date.jpg > > > In the UI page for Archive/Delete alerts and events, some of the tool-tip > advices are misleading. > 1) For Archive events, By event type, the tool-tip gives and advice "Archive > all events by specifying its TYPE (integer number). For events TYPE will be > something like USER.LOGIN and not integer value. For alerts TYPE will be > integer number. [ UI bug archive events type number.jpg ] > 2) 1) For Delete alerts, By event type, the tool-tip gives and advice > "Archive all events by specifying its TYPE (USER.LOGIN). For alerts TYPE will > be integer and not string [ UI bug delete alerts TYPE.jpg ] > 3) For Archive events, By date, both start date and end date tool-tips bear > same message "Archive all events which have been created after this date" . > For end date the message should be " before this date" [ UI bug start > date.jpg and UI bug end date.jpg ] > 4) If an event is Archived individually ( by selecting archive event from the > event Quickview description ), the event will not be removed from the UI > until the page is reloaded. ( User has to navigate to some page or click on > the left side events tab again for the event to disappear from UI). > 5) When user deletes an event by type, remaining events (other than the > deleted events) will be shown twice (redundantly) in the UI page immediately > after the delete operation. User has to reload the page to see the events > distinctly. [ before-delete.jpg and after-delete.jpg ] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Deleted] (CLOUDSTACK-4077) UI glitches for Archive/Delete events and alerts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4077: -- Comment: was deleted (was: Please provide documentation for what IDs correspond to what event types, I cannot find it in the bug report. The event type field can then be converted to a drop-down of specific event type IDs.) > UI glitches for Archive/Delete events and alerts > > > Key: CLOUDSTACK-4077 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4077 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Latest Cloudstack 4.2 build with host on KVM >Reporter: Pavan Kumar Bandarupally >Priority: Critical > Fix For: 4.2.0 > > Attachments: after-delete.jpg, before-delete.jpg, UI bug archive > events type number.jpg, UI bug delete alerts TYPE.jpg, UI bug end date.jpg, > UI bug start date.jpg > > > In the UI page for Archive/Delete alerts and events, some of the tool-tip > advices are misleading. > 1) For Archive events, By event type, the tool-tip gives and advice "Archive > all events by specifying its TYPE (integer number). For events TYPE will be > something like USER.LOGIN and not integer value. For alerts TYPE will be > integer number. [ UI bug archive events type number.jpg ] > 2) 1) For Delete alerts, By event type, the tool-tip gives and advice > "Archive all events by specifying its TYPE (USER.LOGIN). For alerts TYPE will > be integer and not string [ UI bug delete alerts TYPE.jpg ] > 3) For Archive events, By date, both start date and end date tool-tips bear > same message "Archive all events which have been created after this date" . > For end date the message should be " before this date" [ UI bug start > date.jpg and UI bug end date.jpg ] > 4) If an event is Archived individually ( by selecting archive event from the > event Quickview description ), the event will not be removed from the UI > until the page is reloaded. ( User has to navigate to some page or click on > the left side events tab again for the event to disappear from UI). > 5) When user deletes an event by type, remaining events (other than the > deleted events) will be shown twice (redundantly) in the UI page immediately > after the delete operation. User has to reload the page to see the events > distinctly. [ before-delete.jpg and after-delete.jpg ] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-4077) UI glitches for Archive/Delete events and alerts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-4077: - Assignee: Brian Federle > UI glitches for Archive/Delete events and alerts > > > Key: CLOUDSTACK-4077 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4077 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Latest Cloudstack 4.2 build with host on KVM >Reporter: Pavan Kumar Bandarupally >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: after-delete.jpg, before-delete.jpg, UI bug archive > events type number.jpg, UI bug delete alerts TYPE.jpg, UI bug end date.jpg, > UI bug start date.jpg > > > In the UI page for Archive/Delete alerts and events, some of the tool-tip > advices are misleading. > 1) For Archive events, By event type, the tool-tip gives and advice "Archive > all events by specifying its TYPE (integer number). For events TYPE will be > something like USER.LOGIN and not integer value. For alerts TYPE will be > integer number. [ UI bug archive events type number.jpg ] > 2) 1) For Delete alerts, By event type, the tool-tip gives and advice > "Archive all events by specifying its TYPE (USER.LOGIN). For alerts TYPE will > be integer and not string [ UI bug delete alerts TYPE.jpg ] > 3) For Archive events, By date, both start date and end date tool-tips bear > same message "Archive all events which have been created after this date" . > For end date the message should be " before this date" [ UI bug start > date.jpg and UI bug end date.jpg ] > 4) If an event is Archived individually ( by selecting archive event from the > event Quickview description ), the event will not be removed from the UI > until the page is reloaded. ( User has to navigate to some page or click on > the left side events tab again for the event to disappear from UI). > 5) When user deletes an event by type, remaining events (other than the > deleted events) will be shown twice (redundantly) in the UI page immediately > after the delete operation. User has to reload the page to see the events > distinctly. [ before-delete.jpg and after-delete.jpg ] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4077) UI glitches for Archive/Delete events and alerts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4077. --- Resolution: Fixed > UI glitches for Archive/Delete events and alerts > > > Key: CLOUDSTACK-4077 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4077 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Latest Cloudstack 4.2 build with host on KVM >Reporter: Pavan Kumar Bandarupally >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: after-delete.jpg, before-delete.jpg, UI bug archive > events type number.jpg, UI bug delete alerts TYPE.jpg, UI bug end date.jpg, > UI bug start date.jpg > > > In the UI page for Archive/Delete alerts and events, some of the tool-tip > advices are misleading. > 1) For Archive events, By event type, the tool-tip gives and advice "Archive > all events by specifying its TYPE (integer number). For events TYPE will be > something like USER.LOGIN and not integer value. For alerts TYPE will be > integer number. [ UI bug archive events type number.jpg ] > 2) 1) For Delete alerts, By event type, the tool-tip gives and advice > "Archive all events by specifying its TYPE (USER.LOGIN). For alerts TYPE will > be integer and not string [ UI bug delete alerts TYPE.jpg ] > 3) For Archive events, By date, both start date and end date tool-tips bear > same message "Archive all events which have been created after this date" . > For end date the message should be " before this date" [ UI bug start > date.jpg and UI bug end date.jpg ] > 4) If an event is Archived individually ( by selecting archive event from the > event Quickview description ), the event will not be removed from the UI > until the page is reloaded. ( User has to navigate to some page or click on > the left side events tab again for the event to disappear from UI). > 5) When user deletes an event by type, remaining events (other than the > deleted events) will be shown twice (redundantly) in the UI page immediately > after the delete operation. User has to reload the page to see the events > distinctly. [ before-delete.jpg and after-delete.jpg ] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4078) [UI][Upgrade]List VM details and NICS UI is not proper after upgrading from 3.0.7 to 4.2.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4078. --- Resolution: Unresolved Assignee: (was: Brian Federle) Looks like a cache issue; the upgrade script may not have copied all the newer CSS files. Please have someone familiar with the upgrade process to look at this. This is not a UI code issue, but rather a problem in the build process. Namely, make sure these files are up to date: -css/cloudstack3.css -scripts/ folder -images/ folder > [UI][Upgrade]List VM details and NICS UI is not proper after upgrading from > 3.0.7 to 4.2. > - > > Key: CLOUDSTACK-4078 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4078 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI, Upgrade >Affects Versions: 4.2.0 > Environment: Upgrade from 3.0.7 to 4.2 >Reporter: manasaveloori >Priority: Critical > Fix For: 4.2.0 > > Attachments: VM_details.jpg, VM_NICS.jpg > > > Steps: > 1.Have CS with 3.0.7 build. > 2.Deploy VMs. > 3.Upgrade to 4.2 . > Observed that the VM details and NICS tabs are not properly aligned. > Attaching the screen shot for the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4078) [UI][Upgrade]List VM details and NICS UI is not proper after upgrading from 3.0.7 to 4.2.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4078: -- Component/s: (was: UI) Not a UI bug, rather an issue with missing CSS. Build system needs to be checked first. > [UI][Upgrade]List VM details and NICS UI is not proper after upgrading from > 3.0.7 to 4.2. > - > > Key: CLOUDSTACK-4078 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4078 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >Affects Versions: 4.2.0 > Environment: Upgrade from 3.0.7 to 4.2 >Reporter: manasaveloori >Priority: Critical > Fix For: 4.2.0 > > Attachments: VM_details.jpg, VM_NICS.jpg > > > Steps: > 1.Have CS with 3.0.7 build. > 2.Deploy VMs. > 3.Upgrade to 4.2 . > Observed that the VM details and NICS tabs are not properly aligned. > Attaching the screen shot for the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-4111) [PortableIP][UI] Prompt "Acquire New IP - Cross Zones - YES/NO" wizard only when there is portable IP range added at region level.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-4111: - Assignee: Jessica Wang (was: Brian Federle) Hey Jessica can you take a look at this one? thanks. > [PortableIP][UI] Prompt "Acquire New IP - Cross Zones - YES/NO" wizard only > when there is portable IP range added at region level. > -- > > Key: CLOUDSTACK-4111 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4111 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: commit id # 9cd4e089a5798f422961940efbf8ae33ed906b87 >Reporter: venkata swamybabu budumuru >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > > Steps to reproduce: > 1. Have latest CloudStack setup with at least one advanced zone. > 2. Create an isolated network and deploy at least 1 VM using this network. > 3. Go to Netoworks -> View IP Address -> Acquire IP Address > Observations: > (i)Though there is no portable IP range at region level added in the above > steps, it still prompts for "Cross zones" wizard. > (ii) Enable the above wizard only when there is portable IP ranged exists in > the system. > (iii) This means, when there is no portable ip range and when user tries to > acquire an ip then we should send isPortable=False as part of the > associateIpAddress API. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-2162) [UI] "Invalid scopeundefined" occurs when build a cloud via choosing "Contine with basic installation" button.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-2162: - Assignee: Jessica Wang (was: Brian Federle) Jessica, this issue was reopened after I fixed it, but I can't reproduce the error mentioned. Can you give it a try yourself, and if not resolve as Cannot Reproduce? Thanks. > [UI] "Invalid scopeundefined" occurs when build a cloud via choosing "Contine > with basic installation" button. > -- > > Key: CLOUDSTACK-2162 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2162 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Build No.#244 > (CloudStack-non-OSS-MASTER-244-rhel6.3.tar.gz) > XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr > Server, Win7Entx64SP1 for Client machine. >Reporter: Minying Bao >Assignee: Jessica Wang >Priority: Blocker > Fix For: 4.2.0 > > Attachments: After clicking Back button.jpg, > Build#224_management-server.log, Build#224_setupManagement.log, > Build#224_SSVM & CPVM were not created.jpg, Build#256_AddZone_1.jpg, > Build#256_AddZone_2.jpg, Build#256_AddZone_3.jpg, > Build#256_CLOUDSTACK-2162_1.jpg, Build#256_CLOUDSTACK-2162_2.jpg, > Build#256_CLOUDSTACK-2162_3.jpg, Build#334_msg1.jpg, Build#334_msg2.jpg, > Build#334_msg3.jpg, Build#334_msg4.jpg, Invalid scopeundefined.jpg, > ManagementServer.log > > > Repro Steps > Setup the cloudstack environment as normal. (Configured NFS & CS-Mgr Servers) > Launch browser, start CloudStack GUI via [http://cs-mgr IP:8080/client] and > finish to build a cloud step by step. > Expected Result > CloudStack should be set up successfully without any error. > Actual Result > An error "Invalid scopeundefined" occurs. (refer to screenshot named "Invalid > scopeundefined") > And then click "Back" button, the page will nevigate to the "Add Primary > Storage" page. Re-check, all the parameters are correct. (refer to screenshot > named "After clicking Back button") -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4078) [UI][Upgrade]List VM details and NICS UI is not proper after upgrading from 3.0.7 to 4.2.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4078. --- Resolution: Cannot Reproduce Just verified on another machine (with same upgrade path), and the UI rendered fine on Chrome/FF, so this is probably a cache issue in the web browser. > [UI][Upgrade]List VM details and NICS UI is not proper after upgrading from > 3.0.7 to 4.2. > - > > Key: CLOUDSTACK-4078 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4078 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >Affects Versions: 4.2.0 > Environment: Upgrade from 3.0.7 to 4.2 >Reporter: manasaveloori >Priority: Critical > Fix For: 4.2.0 > > Attachments: VM_details.jpg, VM_NICS.jpg > > > Steps: > 1.Have CS with 3.0.7 build. > 2.Deploy VMs. > 3.Upgrade to 4.2 . > Observed that the VM details and NICS tabs are not properly aligned. > Attaching the screen shot for the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-240) Create-Tag feature is not avialable for VPN Customer Gateway
[ https://issues.apache.org/jira/browse/CLOUDSTACK-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-240: - Assignee: (was: Brian Federle) > Create-Tag feature is not avialable for VPN Customer Gateway > - > > Key: CLOUDSTACK-240 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-240 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: pre-4.0.0 >Reporter: prashant kumar mishra >Priority: Minor > Fix For: 4.2.0 > > > There is no option to tag VPN Customer Gateway. > Steps to check > -- > -- > 1-Go to network tab > 2-From select view select VPN Customer Gateway > 3- Click on add VPN Customer Gateway > 5-Select the VPN Customer Gateway > 6-there is no option to create/add Tag for VPN Customer Gateway > Release Planning: > Dev List Discussion: Unknown > Functional Spec: N/A > Feature Branch: Unknown > Documentation: Not needed > QA: Needs to be tested -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1888) [UI]Child Domain Admin accounts can not set/update the resource limits
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-1888: -- Assignee: (was: Brian Federle) > [UI]Child Domain Admin accounts can not set/update the resource limits > --- > > Key: CLOUDSTACK-1888 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1888 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sailaja Mada > Fix For: 4.2.0 > > Attachments: DomainAdminView.png > > > Setup: Advanced Networking zone with Xen 6.1 [4.2] > Steps: > 1. Create Child domain (CDC1) under ROOT > 2. Create Domain account CDC1Admin1 under Child Domain CDC1 > 3. Access Management Server as this domain admin account > Observation: Child Domain Admin accounts can not set/update the resource > limits. It is supported via API. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2464) [GSLB][UI] "Add GSLB" wizard doesn't prompt for "PersistenceType"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-2464: -- Assignee: (was: Brian Federle) > [GSLB][UI] "Add GSLB" wizard doesn't prompt for "PersistenceType" > - > > Key: CLOUDSTACK-2464 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2464 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f >Reporter: venkata swamybabu budumuru >Priority: Minor > Fix For: 4.2.0 > > Attachments: logs.tgz, Screen Shot 2013-05-13 at 10.14.15 PM.png > > > Steps to reproduce : > 1. Have CloudStack with at least 1 advanced zone. > 2. Have at least one non-ROOT domain user > 3. Login as the above user and try to create a GSLB rule > Regions -> Local Region -> View GSLB -> Add GSLB > Observations: > (i) It opens up "Add GSLB" wizard but, that doesn't ask about "Persistence > Type" > (ii) Currently supported Persistence Type is "SourceIP" which by default > assumed by the CloudStack but, we should also give the flexibility to say > "NONE" > Attaching the screenshot, logs and db dump to the bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-4054) [UI] Register template missing some fields
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-4054: - Assignee: Brian Federle > [UI] Register template missing some fields > -- > > Key: CLOUDSTACK-4054 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4054 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Ahmad Emneina >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: screenshot-1.jpg > > > Fields highlighted (see attachment) are missing until you change from All > Zones to Single Zone and back to All Zones again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3364) normal users are not allowed to edit their own iso
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Federle updated CLOUDSTACK-3364:
--
Assignee: (was: Brian Federle)
> normal users are not allowed to edit their own iso
> --
>
> Key: CLOUDSTACK-3364
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3364
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.2.0
>Reporter: shweta agarwal
> Fix For: 4.2.0
>
>
> Repro steps:
> 1.Create a domain
> 2.create a account under that domain
> 3.create a ISO as a account under the non root domain
> 4.Edit the ISO
> BUg :
> gets message:
> Only ROOT admins are allowed to modify this attribute.
> API:
> http://10.147.38.141:8080/client/api?command=updateIsoPermissions&response=json&sessionkey=8rczMjm4sfljFOEi6dL2xT631sc%3D&id=2b8c87a0-4325-418d-80af-ce6f691edcd7&zoneid=bfdf7ac5-16c3-491e-aabd-f7ad696612b8&ispublic=false&isfeatured=false&isextractable=false&_=1372941865923
> response:
> { "updateisopermissionsresponse" :
> {"uuidList":[],"errorcode":431,"cserrorcode":4350,"errortext":"Only ROOT
> admins are allowed to modify this attribute."} }
> This may be because in case of edit ISO we show extractable and featured
> field as editable to normal user , which normal user is not allowed to do
> and api passes these as parameters
> In case of template these fields are shown as non editable hence API passed
> does not contain isfeatured and isextractable fields
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-1579) List view widget: Support actions on multiple rows
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-1579: - Assignee: (was: Brian Federle) > List view widget: Support actions on multiple rows > -- > > Key: CLOUDSTACK-1579 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1579 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Brian Federle > Fix For: Future > > Original Estimate: 144h > Remaining Estimate: 144h > > Currently, actions can only be executed manually, 1 row at a time. Need to > implement ability to select multiple list view items, and perform actions on > them at once: > -Adds checkboxes to the left side of the list view > -If 1 or more rows are checked, adds toolbar menu under table header with > supported actions to apply to all selected rows > Technical requirements: > -Need design for new layout and UX for executing multi-row actions > -Refactor list view widget code to support selection of multiple list items, > and passing multiple items of data to API call code. > -Change API calls to support multiple row objects passed though the context > object, in all sections where it is useful: > -- Instances page > -- Events/alerts (for deleting multiple events/alerts) > -- Storage page > -- etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3268) [UI]No UI for Transferring Portable IP Across Networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-3268. --- Resolution: Fixed > [UI]No UI for Transferring Portable IP Across Networks > -- > > Key: CLOUDSTACK-3268 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3268 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Radhika Nair >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > > There is no UI for transferring a Portable IP across network. No UI for > transferring to a specific VM in a specific network. > We have been firing APIs to accomplish that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4054) [UI] Register template missing some fields
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4054. --- Resolution: Fixed > [UI] Register template missing some fields > -- > > Key: CLOUDSTACK-4054 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4054 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Ahmad Emneina >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: screenshot-1.jpg > > > Fields highlighted (see attachment) are missing until you change from All > Zones to Single Zone and back to All Zones again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4124) UI: Anti-Affinity: "Add VM Instance" box should provide an option to edit Selected Affnity Group on the Last Step
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4124: -- Assignee: Brian Federle > UI: Anti-Affinity: "Add VM Instance" box should provide an option to edit > Selected Affnity Group on the Last Step > -- > > Key: CLOUDSTACK-4124 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4124 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Chandan Purushothama >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: UICapture30.PNG > > > Corresponding UI Screenshot has been attached to the bug report. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4122) UI: VMWare Cluster Entry Tool Tip is Incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4122: -- Assignee: Brian Federle > UI: VMWare Cluster Entry Tool Tip is Incorrect > -- > > Key: CLOUDSTACK-4122 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4122 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Chandan Purushothama >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: UICapture29.png > > > Cluster name cannot be any Name. It should be already declared on the > VCenter. Attached the corresponding screenshot of the UI to the bug report. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4122) UI: VMWare Cluster Entry Tool Tip is Incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4122. --- Resolution: Fixed > UI: VMWare Cluster Entry Tool Tip is Incorrect > -- > > Key: CLOUDSTACK-4122 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4122 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Chandan Purushothama >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: UICapture29.png > > > Cluster name cannot be any Name. It should be already declared on the > VCenter. Attached the corresponding screenshot of the UI to the bug report. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1460) UI : List Storage table has unused column name Actions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-1460: -- Assignee: (was: Brian Federle) > UI : List Storage table has unused column name Actions > -- > > Key: CLOUDSTACK-1460 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1460 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0, 4.2.0 > Environment: RHEL 6.3 >Reporter: Parth Jagirdar >Priority: Minor > Attachments: storage column.jpg > > > Either Actions column should be removed from the table Or should actually be > populated by some actions. > A Blank column shouldn't exists. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2769) [UI] UI lists deleted project and upon selecting the project an error is received
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-2769: -- Assignee: (was: Brian Federle) > [UI] UI lists deleted project and upon selecting the project an error is > received > - > > Key: CLOUDSTACK-2769 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2769 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Master >Reporter: Parth Jagirdar > Attachments: project_deleted2.jpg, project_deleted.jpg > > > UI lists project that has been deleted. > Steps:: > Create a project. > Create an instance within it. > Destroy instance. > Delete the project. > Observe project is still listed on UI. and Upon selecting it, an error > message is received. > Refer to attached screens. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4124) UI: Anti-Affinity: "Add VM Instance" box should provide an option to edit Selected Affnity Group on the Last Step
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4124. --- Resolution: Fixed > UI: Anti-Affinity: "Add VM Instance" box should provide an option to edit > Selected Affnity Group on the Last Step > -- > > Key: CLOUDSTACK-4124 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4124 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Chandan Purushothama >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: UICapture30.PNG > > > Corresponding UI Screenshot has been attached to the bug report. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-579) Missing button to reload a ISO file (or file required for a template)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-579: - Assignee: (was: Brian Federle) > Missing button to reload a ISO file (or file required for a template) > - > > Key: CLOUDSTACK-579 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-579 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.1.0 >Reporter: Charles Moulliard > Attachments: Screen Shot 2012-12-03 at 18.52.56 (2).png > > > The Web UI interface does not propose a button to reload-upload of an ISO > file if an error occurs within the management server. In consequence, to > relaunch upload, we must remove the entry from the ISO list and add a new one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-563) Unable to create guest network in UI for Advanced Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-563: - Assignee: (was: Brian Federle) > Unable to create guest network in UI for Advanced Zone > -- > > Key: CLOUDSTACK-563 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-563 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.0.0 > Environment: CS 4.0 on CentOS 6.3 > vSphere 5.0 clusters with Advanced networks >Reporter: ilya musayev > Labels: Bug, UI > > The UI would not allow for creation of guest Network. - Please look at the > attached image. > Screenshot - http://i50.tinypic.com/33zfmvs.jpg > The drop down for NetworkOfferings is blank > There is a dropdown for VPC - which is also blank (not needed for shared > networks) > We also need the ability to pick the proper Physical Network Name - which is > not available/ > This feature is also broken in the Add A Zone wizard, i will open a separate > bug request for that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-371) When naming physical networks in the zone wizard, special characters like () break the wizard
[ https://issues.apache.org/jira/browse/CLOUDSTACK-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-371: - Assignee: (was: Brian Federle) > When naming physical networks in the zone wizard, special characters like () > break the wizard > - > > Key: CLOUDSTACK-371 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-371 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.0.0 > Environment: Tested with ACS build 733 on Centos 6,3 in > Chrome/Firefox/IE >Reporter: kelcey damage >Priority: Minor > > When naming physical networks in the zone wizard, special characters like () > break the wizard. > This will cause further pages in the wizard to render blank. Also attempting > to go back and fix the name will cause traffic tokens to get frozen and > corrupt, as well as fail to re-draw correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1458) Add Zone wizard UI gets visually broken if additional browser toolbars are used.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-1458: -- Assignee: (was: Brian Federle) > Add Zone wizard UI gets visually broken if additional browser toolbars are > used. > > > Key: CLOUDSTACK-1458 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1458 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0, 4.2.0 > Environment: RHEL 6.3 Chrome with Ask toolbar >Reporter: Parth Jagirdar > Attachments: add zone wizard.jpg, browser toolbar.jpg > > > If browser has some toolbar (issue observed with Ask toolbar) then create > zone wizard buttons get misaligned. > Refer to screen name "browser toolbar" > Now if user attempts to disable the toolbar then UI looks like "add zone > wizard". which is completely unacceptable. > Once in this state; Toolbar enable/disable has no effect on UI. > However a page refresh will get the UI in normal mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1283) UI - Tooltip - Need a clean way to differentiate between Alt Tag's and Tooltips.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-1283: -- Assignee: (was: Brian Federle) > UI - Tooltip - Need a clean way to differentiate between Alt Tag's and > Tooltips. > > > Key: CLOUDSTACK-1283 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1283 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0, 4.2.0 > Environment: RHEL 6.3 Build 15 >Reporter: Parth Jagirdar >Priority: Minor > Attachments: 4 (2).jpg, 4 (3).jpg > > > Please refer to Comments in > https://issues.apache.org/jira/browse/CLOUDSTACK-176 > It may be that these are not Tooltips. (Refer to both screens attached) > But it is definitely within the feature scope; due to fact that a new feature > should not disrupt an existing one. Assuming ALT TAG's were pre existent. > Either we should make them both work in harmony and with clear distinction. > Or should disable 1 features as other is doing the exact same job. > Tagging as Minor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3266) [UI] Failed to delete Anti affinitygroup for the first time
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-3266: -- Assignee: (was: Brian Federle) > [UI] Failed to delete Anti affinitygroup for the first time > > > Key: CLOUDSTACK-3266 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3266 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sailaja Mada > Attachments: apilog.log, deleteAntiAff.png, management-server.log > > > Setup : Advanced Networking Zone - VMWARE > Steps: > 1. Have one instance deployed with enw user account > 2. later create Anti affinitygroup 1 > 3. Tried to delete it from UI > It failed saying: > 2013-06-28 14:37:18,594 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) > ===END=== 10.144.6.19 -- GET > command=deleteAffinityGroup&response=json&sessionkey=cAlesfWeL1LC7v5VBrAi%2B%2FiRJ%2F8%3D&_=1372410634034 > 2013-06-28 14:37:18,595 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-113:job-91) Executing > org.apache.cloudstack.api.command.user.affinitygroup.DeleteAffinityGroupCmd > for job-91 > 2013-06-28 14:37:18,620 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-113:job-91) Unexpected exception while executing > org.apache.cloudstack.api.command.user.affinitygroup.DeleteAffinityGroupCmd > com.cloud.exception.InvalidParameterValueException: Either the affinity group > Id or group name must be specified to delete the group > at > org.apache.cloudstack.affinity.AffinityGroupServiceImpl.deleteAffinityGroup(AffinityGroupServiceImpl.java:147) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.affinitygroup.DeleteAffinityGroupCmd.execute(DeleteAffinityGroupCmd.java:125) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-06-28 14:37:18,620 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-113:job-91) Complete async job-91, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: Either the affinity group Id or > group name must be specified to delete the group > 5. Again tried deleting the second group. > Then it deleted the group. (Attached UI and logs) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1770) Ability to delete Events and Alerts: Select multiple alerts and events.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-1770: -- Assignee: (was: Brian Federle) > Ability to delete Events and Alerts: Select multiple alerts and events. > --- > > Key: CLOUDSTACK-1770 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1770 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI > Environment: NA >Reporter: Parth Jagirdar > Fix For: Future > > > API handles multiple ID's. > UI should also have an ability to select multiple alerts and events. And > perform an action on them (Say delete) in one go. > If we can get this to work in harmony with CLOUDSTACK 662 and CLOUDSTACK 1769 > then that would be really great. > Here is a use case from top of my head:: > Admin wants to delete all login INFO in domain XYZ. > So he searched LEVEL = INFO, domain ROOT with description text contains > "Logged in" > Once results appeared he selected all (by check boxes) the ADMIN in account > and left SYSTEM behind. > And deleted them at once. > If this is too complicated then please log your comments and we can discuss > this further. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1284) UI - Tooltip - Inconsistent tool tip rendering among installation wizards
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-1284: -- Assignee: (was: Brian Federle) > UI - Tooltip - Inconsistent tool tip rendering among installation wizards > - > > Key: CLOUDSTACK-1284 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1284 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0, 4.2.0 > Environment: RHEL 6.3 Build #15 >Reporter: Parth Jagirdar >Priority: Minor > Attachments: 4 (1).jpg > > > ToolTips on Basic Zone installation wizard (The one you get at upon a fresh > install just after Login page) have Heading/Title "Hints" which is > inconsistent with all other tooltips presented in other wizards. (Screen 4) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1036) GUI eats lots of CPU on browser side when managing larger (80-100) port forwarding rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-1036: -- Assignee: (was: Brian Federle) > GUI eats lots of CPU on browser side when managing larger (80-100) port > forwarding rules > > > Key: CLOUDSTACK-1036 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1036 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Frank Breedijk >Priority: Minor > > I was managin an evironment with 40 instances and 80-100 port forwarding > rules. Adding a rules takes ages because there seems to be a lot of client > side JSON parsing going on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-4195) Instance wizard: Better flow for network selection
Brian Federle created CLOUDSTACK-4195: - Summary: Instance wizard: Better flow for network selection Key: CLOUDSTACK-4195 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4195 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Brian Federle Fix For: Future In the current instance wizard UI, select network step, it is difficult to select and unselect networks. Need a more intuitive flow for this step, which will require less complex selection logic. Current problems: - If network is default, need to select another network as default before unchecking. - If network is VPC, only one network can be selected, but the current UI portrays this in a confusing way, where the checkbox will be unchecked automatically. Maybe have this selected via dropdown, etc. to make more intuitive? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3839) [UI] add host is taking too long which causes createstorage pool to fail as the host is not up
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-3839: - Assignee: Jessica Wang (was: Brian Federle) > [UI] add host is taking too long which causes createstorage pool to fail as > the host is not up > -- > > Key: CLOUDSTACK-3839 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3839 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Srikanteswararao Talluri >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > > Steps to reproduce: > == > Use zone create wizard to create a new zone. As the zone create process tries > to add primary storage, it finds that hosts are not ready yet. > Addition of primary storage succeeds after a while. > ===START=== 10.101.255.7 -- GET > command=createStoragePool&zoneid=ed246d25-b804-4b8d-a0b2-0ee9eb8fbb22&podId=6069566c-a491-4056-ad3d-67c9b83efc5b&clusterid=8f4faf37-46d7-42aa-97cd-df6d5166fff2&name=prim2&scope=cluster&url=nfs%3A%2F%2F10.147.28.8%2Fvol%2FdgVol%2Fautomation%2Fadv%2Fpri_2&response=json&sessionkey=9sDYqfDP16zFHMd0sNfNd4OnhlA%3D&_=1374805818616 > 2013-07-26 13:25:28,682 DEBUG > [datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl] > (catalina-exec-1:null) createPool Params @ scheme - nfs storageHost - > 10.147.28.8 hostPath - /vol/dgVol/automation/adv/pri_2 port - -1 > 2013-07-26 13:25:28,721 DEBUG [cloud.storage.StorageManagerImpl] > (catalina-exec-1:null) Failed to add data store > com.cloud.utils.exception.CloudRuntimeException: No host up to associate a > storage pool with in cluster 2 > at > org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.attachCluster(CloudStackPrimaryDataStoreLifeCycleImpl.java:368) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:724) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:175) > at > org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:168) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-07-26 13:25:28,729 INFO [cloud.api.ApiServer] (catalina-exec-1:null) > null > 2013-07-26 13:25:28,730 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) > ===END=== 10.101.255.7 -- GET > command=createStoragePool&zoneid=ed246d25-b804-4b8d-a0b2-0ee9eb8fbb22&podId=6069566c-a491-4056-ad3d-67c9b83efc5b&clusterid=8f4faf37-46d7-42aa-97cd-df6d5166fff2&name=prim2&scope=cluster&url=nfs%3A%2F%2F10.147.28.8%2Fvol%2FdgVol%2Fautomation%2Fadv%2Fpri_2&response=json&sessionkey=9sDYqfDP16zFHMd0sNfNd4OnhlA%3D&_=1374805818616 -- This message is au
[jira] [Resolved] (CLOUDSTACK-4242) UI - CSS regression - AutoScale Configuration button fails to be grayed out when it contains "disabled" CSS class
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4242. --- Resolution: Fixed > UI - CSS regression - AutoScale Configuration button fails to be grayed out > when it contains "disabled" CSS class > - > > Key: CLOUDSTACK-4242 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4242 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Brian Federle > Fix For: 4.2.0 > > Attachments: 2013-08-01-bug4035-DB_DUMP_42_after_upgrade.sql, > autoscale_button_containing_disbaled_CSS_class_is_not_grayed_out.jpg > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4077) UI glitches for Archive/Delete events and alerts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4077. --- Resolution: Fixed > UI glitches for Archive/Delete events and alerts > > > Key: CLOUDSTACK-4077 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4077 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Latest Cloudstack 4.2 build with host on KVM >Reporter: Pavan Kumar Bandarupally >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: after-delete.jpg, before-delete.jpg, UI bug archive > events type number.jpg, UI bug delete alerts TYPE.jpg, UI bug end date.jpg, > UI bug start date.jpg > > > In the UI page for Archive/Delete alerts and events, some of the tool-tip > advices are misleading. > 1) For Archive events, By event type, the tool-tip gives and advice "Archive > all events by specifying its TYPE (integer number). For events TYPE will be > something like USER.LOGIN and not integer value. For alerts TYPE will be > integer number. [ UI bug archive events type number.jpg ] > 2) 1) For Delete alerts, By event type, the tool-tip gives and advice > "Archive all events by specifying its TYPE (USER.LOGIN). For alerts TYPE will > be integer and not string [ UI bug delete alerts TYPE.jpg ] > 3) For Archive events, By date, both start date and end date tool-tips bear > same message "Archive all events which have been created after this date" . > For end date the message should be " before this date" [ UI bug start > date.jpg and UI bug end date.jpg ] > 4) If an event is Archived individually ( by selecting archive event from the > event Quickview description ), the event will not be removed from the UI > until the page is reloaded. ( User has to navigate to some page or click on > the left side events tab again for the event to disappear from UI). > 5) When user deletes an event by type, remaining events (other than the > deleted events) will be shown twice (redundantly) in the UI page immediately > after the delete operation. User has to reload the page to see the events > distinctly. [ before-delete.jpg and after-delete.jpg ] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-4219) [UI][Autoscale] Enable/disable in autoscale configuration breaks due to Apply throwing error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-4219. --- Resolution: Fixed > [UI][Autoscale] Enable/disable in autoscale configuration breaks due to Apply > throwing error > > > Key: CLOUDSTACK-4219 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4219 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: 4.2 Branch, NS as external LB device >Reporter: Sowmya Krishnan >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: cloud.dmp, jessica_1.jpg, jessica_2.jpg > > > For updating any Autoscale config, we need to first disable AutoscaleVMgroup > and then make the changes and enable the VMgroup again. > Currently this is working fine through API > From UI, the same is broken since after disabling Autoscale config, updation > doesn't work: Clicking on Apply throws the following error: > (Firebug log): > TypeError: formData is undefined > http://:8080/client/scripts/ui-custom/autoscaler.js?t=1376068487788 > Line 361 > After enabling back autoscale the updated configuration is not applied. > Steps: > Network-> IP Addresses -> Load Balancing - View All -> Autoscale -> Configure > Disable autoscale > Update any of the config -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3839) [UI] add host is taking too long which causes createstorage pool to fail as the host is not up
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13737120#comment-13737120 ] Brian Federle commented on CLOUDSTACK-3839: --- Hey Jessica, can you double check the API call logic? -- not sure if this is possible to fix from the widget code. > [UI] add host is taking too long which causes createstorage pool to fail as > the host is not up > -- > > Key: CLOUDSTACK-3839 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3839 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Srikanteswararao Talluri >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > > Steps to reproduce: > == > Use zone create wizard to create a new zone. As the zone create process tries > to add primary storage, it finds that hosts are not ready yet. > Addition of primary storage succeeds after a while. > ===START=== 10.101.255.7 -- GET > command=createStoragePool&zoneid=ed246d25-b804-4b8d-a0b2-0ee9eb8fbb22&podId=6069566c-a491-4056-ad3d-67c9b83efc5b&clusterid=8f4faf37-46d7-42aa-97cd-df6d5166fff2&name=prim2&scope=cluster&url=nfs%3A%2F%2F10.147.28.8%2Fvol%2FdgVol%2Fautomation%2Fadv%2Fpri_2&response=json&sessionkey=9sDYqfDP16zFHMd0sNfNd4OnhlA%3D&_=1374805818616 > 2013-07-26 13:25:28,682 DEBUG > [datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl] > (catalina-exec-1:null) createPool Params @ scheme - nfs storageHost - > 10.147.28.8 hostPath - /vol/dgVol/automation/adv/pri_2 port - -1 > 2013-07-26 13:25:28,721 DEBUG [cloud.storage.StorageManagerImpl] > (catalina-exec-1:null) Failed to add data store > com.cloud.utils.exception.CloudRuntimeException: No host up to associate a > storage pool with in cluster 2 > at > org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.attachCluster(CloudStackPrimaryDataStoreLifeCycleImpl.java:368) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:724) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:175) > at > org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:168) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-07-26 13:25:28,729 INFO [cloud.api.ApiServer] (catalina-exec-1:null) > null > 2013-07-26 13:25:28,730 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) > ===END=== 10.101.255.7 -- GET > command=createStoragePool&zoneid=ed246d25-b804-4b8d-a0b2-0ee9eb8fbb22&podId=6069566c-a491-4056-ad3d-67c9b83efc5b&clusterid=8f4faf37-46d7-42aa-97cd-df6d5166fff2&name=prim2&scope=cluster&url=nfs%3A%2F%2F10.147.28.8%2Fvol
[jira] [Assigned] (CLOUDSTACK-4266) [UI] VSM specific input fields to be made optional on UI if no traffic chooses Nexus 1000v
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-4266: - Assignee: Jessica Wang (was: Brian Federle) > [UI] VSM specific input fields to be made optional on UI if no traffic > chooses Nexus 1000v > -- > > Key: CLOUDSTACK-4266 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4266 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > > Currently Nexus VSM specific input fields like Nexus 1000v ip/user/password > etc. are mandatory in UI (shows red asterisk) while adding clsuter if global > config parameter 'vmware.use.nexus.vswitch' is true. > We need to amend this because we now have option to override the cloud level > setting (which is from global configuration parameter set to 'true') or zone > level setting (traffic lebel at zone level) at cluster level while adding > cluster. Hence it makes no sense to ask user to provide VSM details, while > adding cluster, when user chooses not to use Nexus 1000v for any of the > traffics. > Hence need to make these fields as optional (remove the red asterisks) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-4302) Required UI changes
Brian Federle created CLOUDSTACK-4302: - Summary: Required UI changes Key: CLOUDSTACK-4302 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4302 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Brian Federle Assignee: Brian Federle Priority: Critical Fix For: 4.2.0 During VM deployment through the VM wizard UI, when the user chooses the dedicated zone, the dedicated affinity group should be preselected for him and non-editable in the wizard. How can UI know which group to preselect? -->UI can call listDedicatedZones API passing in the zoneId selected in the VM wizard -->The reponse should return DedicateZoneResponse object, if zone is dedicated -->This object should have ‘affinitygroupid’ parameter set -->UI should preselect the group matching this id on the AffinityGroups tab of the wizard -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4302) Instance wizard: Support affinity groups for dedicated zones
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4302: -- Summary: Instance wizard: Support affinity groups for dedicated zones (was: Required UI changes) > Instance wizard: Support affinity groups for dedicated zones > > > Key: CLOUDSTACK-4302 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4302 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Brian Federle >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Original Estimate: 48h > Remaining Estimate: 48h > > During VM deployment through the VM wizard UI, when the user chooses the > dedicated zone, the dedicated affinity group should be preselected for him > and non-editable in the wizard. > How can UI know which group to preselect? > -->UI can call listDedicatedZones API passing in the zoneId selected in the > VM wizard > -->The reponse should return DedicateZoneResponse object, if zone is dedicated > -->This object should have ‘affinitygroupid’ parameter set > -->UI should preselect the group matching this id on the AffinityGroups tab > of the wizard -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4302) Instance wizard UI: Support affinity groups for dedicated zones
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4302: -- Summary: Instance wizard UI: Support affinity groups for dedicated zones (was: Instance wizard: Support affinity groups for dedicated zones) > Instance wizard UI: Support affinity groups for dedicated zones > --- > > Key: CLOUDSTACK-4302 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4302 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Brian Federle >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Original Estimate: 48h > Remaining Estimate: 48h > > During VM deployment through the VM wizard UI, when the user chooses the > dedicated zone, the dedicated affinity group should be preselected for him > and non-editable in the wizard. > How can UI know which group to preselect? > -->UI can call listDedicatedZones API passing in the zoneId selected in the > VM wizard > -->The reponse should return DedicateZoneResponse object, if zone is dedicated > -->This object should have ‘affinitygroupid’ parameter set > -->UI should preselect the group matching this id on the AffinityGroups tab > of the wizard -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-4302) Instance wizard UI: Support affinity groups for dedicated zones
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-4302: - Assignee: Jessica Wang (was: Brian Federle) Assigning to Jessica to make API call changes. > Instance wizard UI: Support affinity groups for dedicated zones > --- > > Key: CLOUDSTACK-4302 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4302 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Brian Federle >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > Original Estimate: 48h > Remaining Estimate: 48h > > During VM deployment through the VM wizard UI, when the user chooses the > dedicated zone, the dedicated affinity group should be preselected for him > and non-editable in the wizard. > How can UI know which group to preselect? > -->UI can call listDedicatedZones API passing in the zoneId selected in the > VM wizard > -->The reponse should return DedicateZoneResponse object, if zone is dedicated > -->This object should have ‘affinitygroupid’ parameter set > -->UI should preselect the group matching this id on the AffinityGroups tab > of the wizard -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4058) Under host details we show ACS version and not host version
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4058: -- Assignee: Brian Federle > Under host details we show ACS version and not host version > --- > > Key: CLOUDSTACK-4058 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4058 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, UI, VMware >Affects Versions: 4.2.0 >Reporter: Ahmad Emneina >Assignee: Brian Federle > Fix For: 4.2.0 > > > On the host details pane, version shows cloudstack version and not esxi > version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3397) When Template creation from a snapshot fails, the UI pop-up also displays the API resonse
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-3397: - Assignee: Brian Federle > When Template creation from a snapshot fails, the UI pop-up also displays the > API resonse > -- > > Key: CLOUDSTACK-3397 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3397 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Abhinav Roy >Assignee: Brian Federle > Fix For: 4.2.0 > > Attachments: fail-template.jpg > > > Steps : > === > 1. Deploy CS advanced zone setup . > 2. Deploy a VM > 3. Goto the root volume of the VM and take Snapshot > 4. Go to that snapshot and try to create a template from the snapshot. > Observed behaviour : > === > The template creation fails and the response displayed in the UI pop-up in > same as the API response in the logs. > Attaching screenshot for reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3105) UI- "View Hosts" option in Vm detail page lists all the hosts. listHosts call is made with hostid instead of id.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Federle updated CLOUDSTACK-3105:
--
Assignee: Brian Federle
> UI- "View Hosts" option in Vm detail page lists all the hosts. listHosts call
> is made with hostid instead of id.
>
>
> Key: CLOUDSTACK-3105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3105
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.2.0
> Environment: Build from master
>Reporter: Sangeetha Hariharan
>Assignee: Brian Federle
> Fix For: 4.2.0
>
>
> UI- "View Hosts" option in Vm detail page lists all the hosts.
> Go to Instances list and select ant 1 instance , so that the detail view of
> the instance is presented.
> Click on "View Hosts" option.
> All hosts are listed in this view.
> listHosts API call passes Vm's host uuid in hostid parameter instead of id.
> 2013-06-20 18:23:10,295 INFO [cloud.api.ApiServer] (catalina-exec-5:null)
> (userId=2 accountId=2 sessionId=7D5DEB7A62BBD2DE48298AAC7C351909)
> 10.252.120.103 -- GET
> command=listHosts&type=Routing&hostid=7cdff16f-623e-40df-98f5-393d223fec52&page=1&pagesize=20&response=json&sessionkey=feUkuow%2BfRcVloUXlGs37A%2BWNjw%3D&_=1371777803998
> 200 { "listhostsresponse" : { "count":2 ,"host" : [
> {"id":"360a6630-600b-4472-803f-5958c1b71203","name":"Rack3Host20.lab.vmops.com","state":"Up","type":"Routing","ipaddress":"10.223.59.66","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","zonetype":"Advanced","podid":"7b15cf66-8e01-459f-bd51-1bb382ab5ddb","podname":"POD-1","version":"4.2.0-SNAPSHOT","hypervisor":"XenServer","cpunumber":4,"cpuspeed":2261,"cpuallocated":"0%","cpuused":"0.05%","cpuwithoverprovisioning":"9044.0","networkkbsread":3521,"networkkbswrite":10295,"memorytotal":16190149248,"memoryallocated":1073741824,"memoryused":2168436,"capabilities":"xen-3.0-x86_64
> , xen-3.0-x86_32p , hvm-3.0-x86_32 , hvm-3.0-x86_32p ,
> hvm-3.0-x86_64","lastpinged":"1970-01-16T04:07:03-0800","managementserverid":7471666038533,"clusterid":"18fd96c3-1036-49ac-8291-63081b6cebc3","clustername":"XenCluster1","clustertype":"CloudManaged","islocalstorageactive":false,"created":"2013-06-20T17:34:14-0700","events":"Ping;
> Remove; StartAgentRebalance; AgentDisconnected; ManagementServerDown;
> HostDown; AgentConnected; ShutdownRequested;
> PingTimeout","resourcestate":"Enabled","hypervisorversion":"6.1.0","hahost":false},
>
> {"id":"7cdff16f-623e-40df-98f5-393d223fec52","name":"Rack3Host23.lab.vmops.com","state":"Up","type":"Routing","ipaddress":"10.223.59.67","zoneid":"c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6","zonename":"ZONE-NTIER-AGN","zonetype":"Advanced","podid":"7b15cf66-8e01-459f-bd51-1bb382ab5ddb","podname":"POD-1","version":"4.2.0-SNAPSHOT","hypervisor":"XenServer","cpunumber":4,"cpuspeed":2261,"cpuallocated":"0%","cpuused":"0.1%","cpuwithoverprovisioning":"9044.0","networkkbsread":7193,"networkkbswrite":30348,"memorytotal":16190149248,"memoryallocated":3355443200,"memoryused":4580544,"capabilities":"xen-3.0-x86_64
> ,
> xen-3.0-x86_32p","lastpinged":"1970-01-16T04:05:17-0800","managementserverid":7471666038533,"clusterid":"18fd96c3-1036-49ac-8291-63081b6cebc3","clustername":"XenCluster1","clustertype":"CloudManaged","islocalstorageactive":false,"created":"2013-06-19T11:30:41-0700","events":"Ping;
> Remove; StartAgentRebalance; AgentDisconnected; ManagementServerDown;
> HostDown; AgentConnected; ShutdownRequested;
> PingTimeout","resourcestate":"Enabled","hypervisorversion":"6.1.0","hahost":false}
> ] } }
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4060) When the only sg is default, it should be selected automatically.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4060: -- Assignee: Brian Federle > When the only sg is default, it should be selected automatically. > - > > Key: CLOUDSTACK-4060 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4060 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Ahmad Emneina >Assignee: Brian Federle > Fix For: 4.2.0 > > > When the only sg is default, it should be selected automatically. even when > deploying and def sec group isnt selected, the vm is deployed to that > security group. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4061) UI issue with japanses localized ui
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle updated CLOUDSTACK-4061: -- Assignee: Brian Federle > UI issue with japanses localized ui > --- > > Key: CLOUDSTACK-4061 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4061 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Ahmad Emneina >Assignee: Brian Federle > Fix For: 4.2.0 > > Attachments: localizationUI.png > > > Localized UI issue. see screenshot -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
