Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1141150 [details] Lifecycle environment not displayed properly Description of problem: Lifecycle Environment - UI does not display the environment path and new environments properly Version-Release number of selected component (if applicable): # rpm -qa | grep foreman tfm-rubygem-hammer_cli_foreman_tasks-0.0.10-2.el7sat.noarch tfm-rubygem-foreman-tasks-0.7.14.1-1.el7sat.noarch foreman-libvirt-1.11.0.7-1.el7sat.noarch tfm-rubygem-foreman_gutterball-0.0.1-6.el7sat.noarch foreman-discovery-image-3.0.5-3.el7sat.noarch foreman-selinux-1.11.0-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman-0.5.1.2-1.el7sat.noarch foreman-gce-1.11.0.7-1.el7sat.noarch foreman-debug-1.11.0.7-1.el7sat.noarch tfm-rubygem-foreman_theme_satellite-0.1.3-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-4.el7sat.noarch foreman-1.11.0.7-1.el7sat.noarch tfm-rubygem-foreman_bootdisk-6.1.0-1.el7sat.noarch foreman-postgresql-1.11.0.7-1.el7sat.noarch amd-ma78gm-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch amd-ma78gm-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-proxy-1.11.0.2-1.el7sat.noarch foreman-installer-1.11.0.0-1.el7sat.noarch foreman-compute-1.11.0.7-1.el7sat.noarch foreman-ovirt-1.11.0.7-1.el7sat.noarch tfm-rubygem-foreman-redhat_access-1.0.1-2.el7sat.noarch tfm-rubygem-foreman_discovery-5.0.0.2-1.el7sat.noarch foreman-vmware-1.11.0.7-1.el7sat.noarch foreman-installer-katello-3.0.0.9-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman_docker-0.0.4-1.el7sat.noarch tfm-rubygem-foreman_docker-2.0.1.1-1.el7sat.noarch tfm-rubygem-foreman_hooks-0.3.9-2.el7sat.noarch amd-ma78gm-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch tfm-rubygem-foreman_remote_execution-0.3.0.2-1.el7sat.noarch tfm-rubygem-foreman_openscap-0.5.3.2-1.el7sat.noarch How reproducible: everytime Steps to Reproduce: 1.Login to WebUI -> Content -> LifeCycleEnvironment Paths 2. 3. Actual results: UI does not display the lifecycle environments properly Expected results: UI displays the lifecycle environments properly Additional info: foreman-debug attached