Created attachment 1269403 [details] screenshots and logs Description of problem: when adding a tag to a container service under the Smart Management we are adding ["Tag"] while on other objects we simply state the TAG. See screennshots attached Version-Release number of selected component (if applicable): cfme-5.8.0.9-alpha2.1.el7cf.x86_64 How reproducible: 100% Steps to Reproduce: 1. add a container provider 2. navigate to computes -> containers -> containers services 3. press the policies button -> add a tag Actual results: in the Smart Management table, the tag appears with ["<TAG>"] instead of just <TAG> as it does on other objects Expected results: Tag should not have [" Additional info: screenshots and logs
Dafna, is this just a ui rendering issue? What is in the database? Is this a regression?
I don't know if this is a regression, This is a test that is in Einta's sanity test so perhaps she would know if this was run in the past. I don't know exactly where is the smart management is in the db. if you know the exact table I would be happy to look. in the "tags" table itself I could see the list of tags name presented correctly. vmdb_production=# table tags; id | name -----+------------------------------------------------ 1 | /managed/roles/change_managers 2 | /managed/roles/operators 3 | /managed/location 4 | /managed/location/ny 5 | /managed/location/chicago 6 | /managed/location/london 7 | /managed/location/paris 8 | /managed/function 9 | /managed/function/desktop 10 | /managed/function/active_directory 11 | /managed/function/application_servers 12 | /managed/function/database 13 | /managed/function/dhcp 14 | /managed/function/evm_appliance 15 | /managed/function/infrastructure 16 | /managed/function/messaging 17 | /managed/function/security 18 | /managed/owner 19 | /managed/owner/prod_linux 20 | /managed/owner/prod_ops 21 | /managed/owner/win2008_test 22 | /managed/environment 23 | /managed/environment/dev 24 | /managed/environment/prod 25 | /managed/environment/quar 26 | /managed/environment/test 27 | /managed/environment/qa 28 | /managed/user/role 29 | /managed/user/role/administrator 30 | /managed/user/role/super_administrator 31 | /managed/user/role/support 32 | /managed/user/role/auditor 33 | /managed/user/role/approver 34 | /managed/user/role/user 35 | /managed/user/role/operator 36 | /managed/service_level 37 | /managed/service_level/silver 38 | /managed/service_level/gold 39 | /managed/service_level/platinum 40 | /managed/customer 41 | /managed/lob 42 | /managed/department 43 | /managed/department/accounting 44 | /managed/department/automotive 45 | /managed/department/communication 46 | /managed/department/defense 47 | /managed/department/engineering 48 | /managed/department/finance 49 | /managed/department/hr 50 | /managed/department/presales 51 | /managed/department/retail 52 | /managed/department/support 53 | /managed/department/trading 54 | /managed/department/healthcare 55 | /managed/department/marketing 56 | /managed/department/purchasing 57 | /managed/department/vi_operations 58 | /managed/department/retail_test 59 | /managed/cc 60 | /managed/cc/001 61 | /managed/cc/002 62 | /managed/network_location 63 | /managed/network_location/dmz 64 | /managed/network_location/internal 65 | /managed/network_location/cloud 66 | /managed/exclusions 67 | /managed/exclusions/do_not_analyze 68 | /managed/exclusions/do_not_clone 69 | /managed/prov_scope 70 | /managed/prov_scope/all 71 | /managed/prov_scope/evmgroup_user_self_service 72 | /managed/operations 73 | /managed/operations/analysis_failed 74 | /managed/operations/analysis_required 75 | /managed/operations/analysis_success 76 | /managed/quota_max_cpu 77 | /managed/quota_max_cpu/1 78 | /managed/quota_max_cpu/2 79 | /managed/quota_max_cpu/3 80 | /managed/quota_max_cpu/4 81 | /managed/quota_max_cpu/5 82 | /managed/quota_max_cpu/10 83 | /managed/quota_max_cpu/20 84 | /managed/quota_max_cpu/30 85 | /managed/quota_max_cpu/40 86 | /managed/quota_max_cpu/50 87 | /managed/prov_max_cpu 88 | /managed/prov_max_cpu/1 89 | /managed/prov_max_cpu/2 90 | /managed/prov_max_cpu/3 91 | /managed/prov_max_cpu/4 92 | /managed/prov_max_cpu/5 93 | /managed/prov_max_vm 94 | /managed/prov_max_vm/1 95 | /managed/prov_max_vm/2 96 | /managed/prov_max_vm/3 97 | /managed/prov_max_vm/4 98 | /managed/prov_max_vm/5 99 | /managed/quota_max_memory 100 | /managed/quota_max_memory/1024 101 | /managed/quota_max_memory/2048 102 | /managed/quota_max_memory/4096 103 | /managed/quota_max_memory/8192 104 | /managed/quota_max_memory/10240 105 | /managed/quota_max_memory/20480 106 | /managed/quota_max_memory/40960 107 | /managed/quota_max_memory/81920 108 | /managed/prov_max_memory 109 | /managed/prov_max_memory/1024 110 | /managed/prov_max_memory/2048 111 | /managed/prov_max_memory/4096 112 | /managed/prov_max_memory/8192 113 | /managed/quota_max_storage 114 | /managed/quota_max_storage/10 115 | /managed/quota_max_storage/20 116 | /managed/quota_max_storage/40 117 | /managed/quota_max_storage/100 118 | /managed/quota_max_storage/200 119 | /managed/quota_max_storage/400 120 | /managed/quota_max_storage/1000 121 | /managed/prov_max_retirement_days 122 | /managed/prov_max_retirement_days/30 123 | /managed/prov_max_retirement_days/60 124 | /managed/prov_max_retirement_days/90 125 | /managed/prov_max_retirement_days/180 126 | /managed/lifecycle 127 | /managed/lifecycle/retire_full (127 rows)
*** Bug 1444636 has been marked as a duplicate of this bug. ***
According to bug 1444636 this issue affect also other pages: - Routes - Container Services - Nodes - Container Templates - Image Registries
Submitted upstream: https://github.com/ManageIQ/manageiq-ui-classic/pull/1180
Yaacov should this be on POST?
merged upstream: https://github.com/ManageIQ/manageiq-ui-classic/pull/1180