Bug 1205960
| Summary: | [RFE] installer check for underscores in hostname | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | jnikolak | ||||||||
| Component: | Installation | Assignee: | Katello Bug Bin <katello-bugs> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Sanket Jagtap <sjagtap> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 6.0.8 | CC: | cwelton, kbidarka, mmccune | ||||||||
| Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged | ||||||||
| Target Release: | Unused | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| URL: | http://projects.theforeman.org/issues/10175 | ||||||||||
| Whiteboard: | FAILEDQA in Upstream | ||||||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2016-07-27 08:49:56 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
jnikolak
2015-03-26 01:35:01 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. We located that this was caused by having an underscore in the hostname. If there could be some validation like we have for capitals, than it would be good. ######### katello-installer --reset The hostname contains a a capital letter. This is not supported. Please modify the hostname to be all lowercase. If this is not possible, than the bug can be closed. Reworded the summary to state this is an RFE to check for underscores in the installer pre-run checks. Created redmine issue http://projects.theforeman.org/issues/10175 from this bug *** Bug 1205044 has been marked as a duplicate of this bug. *** Moving to POST since upstream bug http://projects.theforeman.org/issues/10175 has been closed ------------- Anonymous Applied in changeset commit:katello-installer|5621fa77a6f6e110519cd60d9b8d1a51d67dc622. *** This bug is failing in upstream ****. # rpm -qa | grep foreman foreman-proxy-1.11.0-0.develop.201510201341git00875b3.el7.noarch foreman-selinux-1.11.0-0.develop.201510071426git6234447.el7.noarch tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-3.el7.noarch tfm-rubygem-foreman_docker-1.4.1-2.fm1_10.el7.noarch foreman-libvirt-1.11.0-0.develop.201510201422git6eb234a.el7.noarch foreman-compute-1.11.0-0.develop.201510201422git6eb234a.el7.noarch foreman-release-scl-1-1.el7.x86_64 foreman-gce-1.11.0-0.develop.201510201422git6eb234a.el7.noarch foreman-debug-1.11.0-0.develop.201510201422git6eb234a.el7.noarch tfm-rubygem-foreman_gutterball-0.0.1-3.el7.noarch hp-sl2x170zg6-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch tfm-rubygem-foreman_discovery-4.1.1-1.fm1_11.el7.noarch foreman-vmware-1.11.0-0.develop.201510201422git6eb234a.el7.noarch tfm-rubygem-foreman_hooks-0.3.9-1.el7.noarch tfm-rubygem-foreman-tasks-0.7.6-1.fm1_10.el7.noarch tfm-rubygem-hammer_cli_foreman_tasks-0.0.8-1.el7.noarch tfm-rubygem-foreman_bootdisk-6.0.0-2.fm1_10.el7.noarch hp-sl2x170zg6-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch hp-sl2x170zg6-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-ovirt-1.11.0-0.develop.201510201422git6eb234a.el7.noarch foreman-1.11.0-0.develop.201510201422git6eb234a.el7.noarch tfm-rubygem-hammer_cli_foreman_docker-0.0.3-4.el7.noarch foreman-release-1.11.0-0.develop.201510201422git6eb234a.el7.noarch foreman-postgresql-1.11.0-0.develop.201510201422git6eb234a.el7.noarch tfm-rubygem-hammer_cli_foreman-0.4.0-1.201510201150gitab068d9.el7.noarch steps: # katello-installer --reset Installing Notice: /Stage[main]/Foreman::Database/Foreman::Ra [99%] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0] Installing Debug: Executing '/usr/bin/systemctl is-enabled fo [99%] Installing Debug: Executing '/usr/bin/systemctl is-enabled fo [99%] Installing Debug: /Stage[main]/Foreman::Service/Service[forem [99%] Installing Debug: /Stage[main]/Certs::Foreman/Exec[foreman_ce [99%] Installing Notice: /Stage[main]/Certs::Foreman/Exec[foreman_c [99%] Installing Notice: /Stage[main]/Foreman_proxy::Register/Forem [99%] Installing Debug: Stored state in 0.27 seconds [99%] Installing Done [100%]Installing Done [100%] [] Something went wrong! Check the log for ERROR-level output The full log is at /var/log/katello-installer/katello-installer.log attached the full log Created attachment 1086842 [details]
katello-installer log
Moving to POST since upstream bug http://projects.theforeman.org/issues/10175 has been closed ------------- Anonymous Applied in changeset commit:katello-installer|5621fa77a6f6e110519cd60d9b8d1a51d67dc622. FAILEDQA: # rpm -qa | grep foreman dell-pem600-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-release-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch foreman-ovirt-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch foreman-libvirt-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch foreman-postgresql-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch foreman-selinux-1.11.0-0.develop.201510071426git6234447.el7.noarch tfm-rubygem-foreman_hooks-0.3.9-1.el7.noarch tfm-rubygem-hammer_cli_foreman_tasks-0.0.8-1.el7.noarch tfm-rubygem-foreman_gutterball-0.0.1-3.el7.noarch dell-pem600-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch dell-pem600-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch tfm-rubygem-foreman_discovery-4.1.2-1.fm1_11.el7.noarch foreman-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch tfm-rubygem-foreman_docker-1.4.1-2.fm1_10.el7.noarch tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-3.el7.noarch foreman-debug-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch foreman-proxy-1.11.0-0.develop.201511111339git7cbe47a.el7.noarch foreman-compute-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch tfm-rubygem-hammer_cli_foreman_docker-0.0.3-4.el7.noarch tfm-rubygem-foreman_bootdisk-6.0.0-2.fm1_10.el7.noarch tfm-rubygem-hammer_cli_foreman-0.4.0-1.201511111650gitdda13df.el7.noarch foreman-gce-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch foreman-release-scl-1-1.el7.x86_64 foreman-vmware-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch tfm-rubygem-foreman-tasks-0.7.6-1.fm1_10.el7.noarch steps: # katello-installer --reset Installing Notice: /Stage[main]/Foreman::Database/Foreman::Ra [99%] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0] Installing Debug: Executing '/usr/bin/systemctl is-enabled fo [99%] Installing Debug: Executing '/usr/bin/systemctl is-enabled fo [99%] Installing Notice: /Stage[main]/Foreman::Service/Exec[restart [99%] Installing Debug: /Stage[main]/Certs::Foreman/Exec[foreman_ce [99%] Installing Notice: /Stage[main]/Certs::Foreman/Exec[foreman_c [99%] Installing Notice: /Stage[main]/Foreman_proxy::Register/Forem [99%] Installing Debug: Stored state in 0.29 seconds [99%] Installing Done [100%]Installing Done [100%] [] Something went wrong! Check the log for ERROR-level output The full log is at /var/log/katello-installer/katello-installer.log Created attachment 1097278 [details]
katello-installer log
Moving to POST since upstream bug http://projects.theforeman.org/issues/10175 has been closed ------------- Anonymous Applied in changeset commit:katello-installer|5621fa77a6f6e110519cd60d9b8d1a51d67dc622. Installer shows an warning/error and then stops successfully. Build: snap9.0 Output: Output of 'hostname -f' does not seems to be valid FQDN Make sure above command gives fully qualified domain name. At least one dot must be present and underscores are not allowed. If needed, change the hostname permanently via 'hostname' command and editing appropriate configuration file. (e.g. on Red Hat systems /etc/sysconfig/network). If 'hostname -f' still returns unexpected result, check /etc/hosts and put hostname entry in the correct order, for example: 1.2.3.4 full.hostname.com full Fully qualified hostname must be the first entry on the line Your system does not meet configuration criteria *** Bug 1205027 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1500 |