Description of problem: An appliance hosted on RHEV 3.4 cannot be accessed with SSH using the default credentials for root. The same appliance running on a RHEV 3.3 or RHEV 3.5 environment can be logged into as expected. Version-Release number of selected component (if applicable): 5.4.0.1.20150512111354_4368716 How reproducible: always Steps to Reproduce: 1. Start a fresh appliance on a RHEV 3.4 environment. 2. Attempt to SSH into the appliance with the default root password 3. Actual results: Login fails for root user. Expected results: root user can login. Additional info:
I have an idea that might address this. I'm trying it and will post an update here by the end of the day.
Upstream has the same bug for botvinnik rc3...https://github.com/ManageIQ/manageiq/issues/2936
There was a fix in 3.4...but no change in 3.5. Can anyone really confirm this is *not* happenning in 3.5? How is this appliance created/initialized?
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/b3fa93547eacf70255d2d4149fa58de672eb990a commit b3fa93547eacf70255d2d4149fa58de672eb990a Author: Joe VLcek <jvlcek> AuthorDate: Tue May 19 14:27:40 2015 -0400 Commit: Joe VLcek <jvlcek> CommitDate: Tue May 19 14:58:04 2015 -0400 Revert "Enable ssh Password Authentication when using cloud-init" This should fix the problems in: https://github.com/ManageIQ/manageiq/issues/2936 https://bugzilla.redhat.com/show_bug.cgi?id=1222591 This reverts commit 5517dfa6fb1a548c34c12b4b1d5a043e21b9dc51. build/kickstarts/base.ks.erb | 3 --- 1 file changed, 3 deletions(-)
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/d449ddb58a2b684a494aeac17f5d6cbeb330e63a commit d449ddb58a2b684a494aeac17f5d6cbeb330e63a Author: Joe VLcek <jvlcek> AuthorDate: Tue May 19 14:27:58 2015 -0400 Commit: Joe VLcek <jvlcek> CommitDate: Tue May 19 14:58:53 2015 -0400 Revert "Install cloud-init package on the centos appliance" This should fix the problems in: https://github.com/ManageIQ/manageiq/issues/2936 https://bugzilla.redhat.com/show_bug.cgi?id=1222591 This reverts commit e5cf1565330441000ddec3763f5cd239740f73e2. build/kickstarts/base.ks.erb | 2 -- 1 file changed, 2 deletions(-)
New commit detected on cfme_productization/master: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme_productization.git;a=commit;h=0b42d2f5820e33fa99371349e1f5db91d945459e commit 0b42d2f5820e33fa99371349e1f5db91d945459e Author: Joe VLcek <jvlcek> AuthorDate: Tue May 19 16:27:51 2015 -0400 Commit: Joe VLcek <jvlcek> CommitDate: Wed Jun 3 14:05:31 2015 -0400 Remove cloud-init from the images https://bugzilla.redhat.com/show_bug.cgi?id=1222591 manageiq/build/productization/kickstarts/base-rhevm.ks | 4 ---- manageiq/build/productization/kickstarts/base-rhos.ks | 4 ---- manageiq/build/productization/kickstarts/base-vsphere.ks | 4 ---- 3 files changed, 12 deletions(-)
New commit detected on cfme_productization/master: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme_productization.git;a=commit;h=4a638f305698c7ee12cc28aa75ba1cc3e85a1f00 commit 4a638f305698c7ee12cc28aa75ba1cc3e85a1f00 Merge: ee82ef4 0b42d2f Author: Joe Rafaniello <jrafanie> AuthorDate: Wed Jun 3 14:15:09 2015 -0400 Commit: Joe Rafaniello <jrafanie> CommitDate: Wed Jun 3 14:15:09 2015 -0400 Merge branch 'revert_cloud_init' into 'master' Remove cloud-init from the images https://bugzilla.redhat.com/show_bug.cgi?id=1222591 I did not use git revert because there were a bunch of commits for this. We tried multiple things. Making this new commit seemed cleaner. See merge request !49 manageiq/build/productization/kickstarts/base-rhevm.ks | 4 ---- manageiq/build/productization/kickstarts/base-rhos.ks | 4 ---- manageiq/build/productization/kickstarts/base-vsphere.ks | 4 ---- 3 files changed, 12 deletions(-)
New commit detected on cfme_productization/5.4.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme_productization.git;a=commit;h=eac562358fe343d5cae3630065ad4765069dfd34 commit eac562358fe343d5cae3630065ad4765069dfd34 Author: Joe VLcek <jvlcek> AuthorDate: Tue May 19 16:27:51 2015 -0400 Commit: Joe VLcek <jvlcek> CommitDate: Wed Jun 3 14:20:00 2015 -0400 Remove cloud-init from the images https://bugzilla.redhat.com/show_bug.cgi?id=1222591 manageiq/build/productization/kickstarts/base-rhevm.ks | 4 ---- manageiq/build/productization/kickstarts/base-rhos.ks | 4 ---- manageiq/build/productization/kickstarts/base-vsphere.ks | 4 ---- 3 files changed, 12 deletions(-)
New commit detected on cfme_productization/5.4.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme_productization.git;a=commit;h=c47423c0579217915a8f47ca9aed0371ba74e314 commit c47423c0579217915a8f47ca9aed0371ba74e314 Merge: f09a1a6 eac5623 Author: Joe Rafaniello <jrafanie> AuthorDate: Wed Jun 3 14:24:02 2015 -0400 Commit: Joe Rafaniello <jrafanie> CommitDate: Wed Jun 3 14:24:02 2015 -0400 Merge branch 'revert-cloud-init-5.4.z' into '5.4.z' Remove cloud-init from the images https://bugzilla.redhat.com/show_bug.cgi?id=1222591 From: http://gitlab.cloudforms.lab.eng.rdu2.redhat.com/cloudforms/cfme_productization/merge_requests/49 See merge request !57 manageiq/build/productization/kickstarts/base-rhevm.ks | 4 ---- manageiq/build/productization/kickstarts/base-rhos.ks | 4 ---- manageiq/build/productization/kickstarts/base-vsphere.ks | 4 ---- 3 files changed, 12 deletions(-)
While testing this issue I uncovered a possibly more acceptable workaround. While creating the new appliance on RHEV 3.4 the root password can be added with the "Use Cloud-Init/Sysprep" checked in "Initial Run"->"Authentication". After adding the proper default password the system is accessible from both the console and ssh.
verified upstream in master.20150917141102_8144675 I was able to SSH into the appliance using default root credentials
Right, this is related to a RHEV issue that we are required to use the work around. I'll try to dig up the relevant BZ. It would be nice to see that fixed in a 3.4.z release
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/RHSA-2015:2551
Clarified versions in doc text.