Red Hat - installer bug

[Sebastian Roth]

@Wayne-Workman I am unable to reproduce this issue on a fresh CentOS 7 install with 7286. I kind of guess that your minimal install might be missing the package redhat-lsb-core (util lsb_release) but the installer should take care of this and install this package if it’s missing. So I am not sure what’s going on.

rpm -qa | grep lsb
redhat-lsb-core-4.1-27.el7.centos.1.x86_64
redhat-lsb-submod-security-4.1-27.el7.centos.1.x86_64

[Tom Elliott]

Is this still a problem? Any way we can fully reproduce?

[Wayne Workman]

@Tom-Elliott I can try to reproduce. I actually took an image of the CentOS 7 setup just before putting fog onto it (because I plan to use it for other things).

I’ll see if I can reproduce.

[Sebastian Roth]

@Tom-Elliott said:

Any way we can fully reproduce?

Unfortunately I can’t. Looking at the script code I can only see the error message "Invalid input, please try again if you put in anything other than “1”, “2”, “3” or “”. My guess is that Wayne hit space and then enter (which we obviously don’t see in that copied console output).

[Wayne Workman]

@Sebastian-Roth It’s possible. I’ll see if I can reproduce.

[Tom Elliott]

I’m solving for now. Of course you’re more than welcome to reopen if you do indeed find this is a bug and not just a space/tab/unseen character.

[Wayne Workman]

On 8108 This issue is still present. I’ve installed countless times on Fedora and CentOS 7, and a whole lot recently on CentOS 7. Many brand new, unique storage nodes. Not the same server twice. And I’ve also seen this on many different servers at home, using Fedora.

[Tom Elliott]

@Wayne-Workman I only just pushed. It should show up now.

[Wayne Workman]

This is not fixed yet.

[Tom Elliott]

@Wayne-Workman Why can I not replicate?

[Tom Elliott]

[root@mastasql bin]# ^C
[root@mastasql bin]# lsb_release -a
LSB Version:    :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description:    CentOS Linux release 7.2.1511 (Core) 
Release:        7.2.1511
Codename:       Core
[root@mastasql bin]# 

  +------------------------------------------+
   |     ..#######:.    ..,#,..     .::##::.  |
   |.:######          .:;####:......;#;..     |
   |...##...        ...##;,;##::::.##...      |
   |   ,#          ...##.....##:::##     ..:: |
   |   ##    .::###,,##.   . ##.::#.:######::.|
   |...##:::###::....#. ..  .#...#. #...#:::. |
   |..:####:..    ..##......##::##  ..  #     |
   |    #  .      ...##:,;##;:::#: ... ##..   |
   |   .#  .       .:;####;::::.##:::;#:..    |
   |    #                     ..:;###..       |
   |                                          |
   +------------------------------------------+
   |      Free Computer Imaging Solution      |
   +------------------------------------------+
   |  Credits: http://fogproject.org/Credits  |
   |       http://fogproject.org/Credits      |
   |       Released under GPL Version 3       |
   +------------------------------------------+


   Version: 8138 Installer/Updater

  What version of Linux would you like to run the installation for?

          1) Redhat Based Linux (Redhat, CentOS, Mageia)
          2) Debian Based Linux (Debian, Ubuntu, Kubuntu, Edubuntu)
          3) Arch Linux

  Choice: [1] 



  Starting Redhat based Installation


  FOG Server installation modes:
      * Normal Server: (Choice N) 
          This is the typical installation type and
          will install all FOG components for you on this
          machine.  Pick this option if you are unsure what to pick.

      * Storage Node: (Choice S)
          This install mode will only install the software required
          to make this server act as a node in a storage group

  More information:  
     http://www.fogproject.org/wiki/index.php?title=InstallationModes

  What type of installation would you like to do? [N/s (Normal/Storage)] 

[Sebastian Roth]

@Wayne-Workman Can you please to me a favor? Run the installer like this:

sudo -i
cd /path/to/fogproject/bin
set -x
./installfog.sh
...
set +x

You’ll see a lot of stuff on the console. Can you copy&paste all of it and post here?

[Wayne Workman]

@Sebastian-Roth Will do, I can do this tomorrow morning on yet another new node.

[Tom Elliott]

@Wayne-Workman Are you seeing this, btw, on your home system as well?

[Wayne Workman]

@Tom-Elliott yeah.

Here in a minute I’m going to do what Sebastian said.

[Wayne Workman]

@Sebastian-Roth You’re not going to believe this and I’m going to sound like a liar but… it didn’t do it this time around…

[Tom Elliott]

@Wayne-Workman wtf ?

[Wayne Workman]

@Tom-Elliott idk

[Wayne Workman]

I’ll try again this afternoon on another new node.

[Wayne Workman]

This afternoon the bug did not appear, again. This particular install I didn’t update the OS first. So updates didn’t play a roll in the bug.

I’m unsure what was causing it. Have any more changes been made to the installer about this?