Red Hat Bugzilla – Bug 1468901
domain shows up in Hammer but not in UI
Last modified: 2018-06-22 17:48:19 EDT
Created attachment 1295636 [details] https://127.0.0.1/domains rhel 7.3 domainname: test.spg dnsdomainname test.spg Linux sat.test.spg 3.10.0-514.26.2.el7.x86_64 #1 SMP Fri Jun 30 05:26:04 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Backend System Status Component Status Message candlepin OK candlepin_auth OK foreman_tasks OK pulp OK pulp_auth OK Description of problem: [root@sat admin]# history |grep "hammer domain" 57 hammer domain create --name test.spg [root@sat admin]# hammer domain list ---|--------- ID | NAME ---|--------- 1 | test.spg ---|--------- Now looking at the UI https://127.0.0.1/domains So on the UI MY DOMAIN THAT SHOWS UNDER HAMMER IS NOT SHOWING in UI Version-Release number of selected component (if applicable): How reproducible: Multiple installs Satellite 6.2.10 same result Steps to Reproduce: 1. hammer domain create --name test.spg 2. Goto UI at https://127.0.0.1/domains 3. Shows create new domain Actual results: Expected results: should show test.spg as the domain Additional info:
Hello, can you please paste output of `hammer domain info --name test.spg` to see what organizations the domain is assigned to and check if you see the domain when you switch to "Any context" in the UI? You'll find the switcher in on the left side of the top horizontal menu.
This bug only happens when during the initial install when "satellite-installer -v --scenario satellite --capsule-puppet=true" If I remove the option and install without i am able to see the domain
Ok, this is a nice pointer. Still, would you mind checking the steps I mention in my previous comment? Thank you!
I am unable to provide info, as I am limited on resources and had to reinstall before I got your email. all I can give you is what I tried to set it up with satellite-installer -v --capsule-puppet=true --foreman-admin-password=redhat --foreman-admin-username=admin --foreman-initial-location=DENVER --foreman-initial-organization=REDHAT --foreman-proxy-dhcp=true --foreman-proxy-dhcp-gateway=10.168.100.1 --foreman-proxy-dhcp-interface=eth0 --foreman-proxy-dhcp-nameservers=10.168.100.233 --foreman-proxy-dhcp-range="10.168.100.20 10.168.100.250" --foreman-proxy-dns-interface=eth0 --foreman-proxy-dns-zone=test.spg --foreman-proxy-dns=true --foreman-proxy-dns-listen-on both --foreman-proxy-plugin-discovery-install-images=true --foreman-proxy-puppetca=true --foreman-proxy-templates=true --foreman-proxy-tftp=true --foreman-proxy-tftp-servername=sat.test.spg
have you changed your organization context to any? It could be there, since you didn't specify an organization during creation.
Most likely the organization/location selected in the UI didn't match those of hammer (defaults to "any context"). Could you try to reproduce and confirm it's a bug? I have recently installed 6.3 latest beta snap - without this issue. New domains created from facts may not have Organization, but they are visible under "Any context"