Description of problem: Content view tags appear as undefined Name: cont_view Description: Permission For: Content View Verb(s): Read Content Views On: undefined undefined Version-Release number of selected component (if applicable): Satellite-6.0.1-RHEL-6-20130524.3 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Tags are displayed as undefined for Content View Expected results: The actual content view/published views tags should be visible. Additional info:
Was this from UI or CLI? Can you provide details on the content view names you used to generate the above scenario? I've taken a look both on master and on my satellite install and do not see the same behavior.
That's strange, I find this issue on both satellite6/katello To be precise: It's while adding permissions for particular tags for a ROLE. katello-candlepin-cert-key-pair-1.0-1.noarch katello-glue-elasticsearch-1.4.2-7.el6sat.noarch katello-all-1.4.2-7.el6sat.noarch katello-cli-1.4.2-6.el6sat.noarch katello-cli-common-1.4.2-6.el6sat.noarch katello-qpid-client-key-pair-1.0-1.noarch katello-certs-tools-1.4.2-2.el6sat.noarch ruby193-rubygem-foreman-katello-engine-0.0.7-1.el6sat.noarch katello-glue-candlepin-1.4.2-7.el6sat.noarch katello-1.4.2-7.el6sat.noarch katello-foreman-all-1.4.2-7.el6sat.noarch signo-katello-0.0.12-1.el6sat.noarch katello-selinux-1.4.3-3.el6sat.noarch ruby193-rubygem-katello-foreman-engine-0.0.1-1.el6_4.noarch ruby193-rubygem-katello_api-0.0.3-2.el6_4.noarch katello-common-1.4.2-7.el6sat.noarch katello-configure-foreman-1.4.3-10.el6sat.noarch katello-configure-1.4.3-10.el6sat.noarch katello-glue-pulp-1.4.2-7.el6sat.noarch katello-qpid-broker-key-pair-1.0-1.noarch Here are the names used by me for content view pub007 pub123 pub343 pun1233 I will also be attaching the screenshot shortly.
Created attachment 754402 [details] contentview_names-tags_issue
Created attachment 754403 [details] the_undefined_as_seen_from_UI_satell6_24.3
This is strange. It looks like I have the same set of rpms on my install, but I do not see the same behavior. What browser & version are you using? From looking at the screenshots on comments #3 & #4, I am assuming you have a role/permission, but did not specify any content views. E.g. doesn't look like any were selected. katello-1.4.2-7.el6sat.noarch katello-all-1.4.2-7.el6sat.noarch katello-candlepin-cert-key-pair-1.0-1.noarch katello-certs-tools-1.4.2-2.el6sat.noarch katello-cli-1.4.2-6.el6sat.noarch katello-cli-common-1.4.2-6.el6sat.noarch katello-common-1.4.2-7.el6sat.noarch katello-configure-1.4.3-10.el6sat.noarch katello-configure-foreman-1.4.3-10.el6sat.noarch katello-foreman-all-1.4.2-7.el6sat.noarch katello-glue-candlepin-1.4.2-7.el6sat.noarch katello-glue-elasticsearch-1.4.2-7.el6sat.noarch katello-glue-pulp-1.4.2-7.el6sat.noarch katello-qpid-broker-key-pair-1.0-1.noarch katello-qpid-client-key-pair-1.0-1.noarch katello-selinux-1.4.3-3.el6sat.noarch ruby193-rubygem-foreman-katello-engine-0.0.7-1.el6sat.noarch ruby193-rubygem-katello_api-0.0.3-2.el6_4.noarch ruby193-rubygem-katello-foreman-engine-0.0.1-1.el6_4.noarch signo-katello-0.0.12-1.el6sat.noarch Will attach a screenshot for a similar scenario on my environment.
Created attachment 754533 [details] permission edit, no view selected
Created attachment 754534 [details] permission view, no view selected
On additional note, I'm testing with FF 18.0 and Chrome 22.0.1229.94
kedar, ok, you can ignore my comments above... i was able to repro it now... i was testing every scenario, except the one that generated it... :) scenario: 1. create a provider/product/repo, sync the repo 2. create content view definition 3. add repo to definition 4. publish a view from the definition 5. create a role 6. create a perm for the org.. Permission For : Content View Verbs: Read Content Views & Promote Content Views On: select the view DONE 7. View the permission... observed 'undefined'
See also https://github.com/Katello/katello/issues/2303
I've attempted to reproduce the issue described and it appears that it has already been resolved. This was also mentioned as resolved in https://github.com/Katello/katello/issues/2303 . I am going to move this to POST.
Verified: * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.8.25-1.el6sam.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.8.25-1.el6sam.noarch * candlepin-tomcat6-0.8.25-1.el6sam.noarch * elasticsearch-0.19.9-8.el6sat.noarch * foreman-1.3.0-13.el6sat.noarch * foreman-compute-1.3.0-13.el6sat.noarch * foreman-libvirt-1.3.0-13.el6sat.noarch * foreman-postgresql-1.3.0-13.el6sat.noarch * foreman-proxy-1.3.0-2.el6sat.noarch * katello-1.4.6-19.el6sat.noarch * katello-all-1.4.6-19.el6sat.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.4.4-1.el6sat.noarch * katello-cli-1.4.3-17.el6sat.noarch * katello-cli-common-1.4.3-17.el6sat.noarch * katello-common-1.4.6-19.el6sat.noarch * katello-configure-1.4.5-9.el6sat.noarch * katello-configure-foreman-1.4.5-9.el6sat.noarch * katello-configure-foreman-proxy-1.4.5-9.el6sat.noarch * katello-foreman-all-1.4.6-19.el6sat.noarch * katello-glue-candlepin-1.4.6-19.el6sat.noarch * katello-glue-elasticsearch-1.4.6-19.el6sat.noarch * katello-glue-pulp-1.4.6-19.el6sat.noarch * katello-qpid-broker-key-pair-1.0-1.noarch * katello-qpid-client-key-pair-1.0-1.noarch * katello-selinux-1.4.4-4.el6sat.noarch * openldap-2.4.23-31.el6.x86_64 * pulp-katello-plugins-0.2-1.el6sat.noarch * pulp-nodes-common-2.3.0-0.17.beta.el6sat.noarch * pulp-nodes-parent-2.3.0-0.17.beta.el6sat.noarch * pulp-puppet-plugins-2.3.0-0.17.beta.el6sat.noarch * pulp-rpm-plugins-2.3.0-0.17.beta.el6sat.noarch * pulp-selinux-2.3.0-0.17.beta.el6sat.noarch * pulp-server-2.3.0-0.17.beta.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-ldap_fluff-0.2.2-2.el6sat.noarch * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.0.7-1.el6sat.noarch * signo-0.0.20-3.el6sat.noarch * signo-katello-0.0.20-3.el6sat.noarch
This was verified and delivered with MDP2. Closing it out.
This was delivered and verified with MDP2. Closing the bug.