1.3.5 RC8 Boot Key Sequence

[sudburr]

Server

• FOG Version: 1.3.5 RC8
• OS: CentOS 7.x

Client

• Service Version: n/a
• OS: n/a

Description

In-place upgrading versions of 1.3.0 and later with 1.3.5 RC8, the iPXE Boot Menu option of ‘Boot Key Sequence’ is being reset from its intended setting to ’ - Please select an option - '.

[Tom Elliott]

I’m not seeing any issues with this.

[Wayne Workman]

Cross-linking another thread about the same thing:
https://forums.fogproject.org/topic/9550/1-3-5-rc-7-boot-key-sequence-reset

[Wayne Workman]

@sudburr Can you dig into the apache logs and try to find something related to this issue? I cannot replicate the problem.

[sudburr]

I had this happen on 19 servers (no storage nodes) of varying versions 1.3.0 + up to and including RC5.

No relevant indicators or errors in /var/log/httpd/error_log or /opt/trunkgit/fogproject/bin/error_logs .

[sudburr]

Upgrading from RC8 to RC10 it happened again.

Nothing to report from the apache log, but here are some snippets from fogproject/bin/error_logs/fog_error_1.3.5-RC-10.log .

xinetd-2.3.15-13.el7.x86_64
New password: Retype new password: Changing password for user fog.
passwd: all authentication tokens updated successfully.
Failed to execute operation: Invalid argument
● mariadb.service - MariaDB database server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)

Feb 21 11:05:46 xyzfog systemd[1]: Started MariaDB database server.
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
Signature ok
subject=/CN=10.12.40.14
Getting CA Private Key
ln: failed to create symbolic link ‘/var/www/html/fog/fog’: File exists
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)

Feb 21 11:07:36 xyzfog systemd[1]: Starting The Apache HTTP Server...
Feb 21 11:07:36 xyzfog systemd[1]: Started The Apache HTTP Server.
Saving to: ‘/home//fogDBbackups/fog_sql_1.3.5-RC-10_20170221_110738.sql’
     0K                                                        0.00 =0s
2017-02-21 11:07:39 (0.00 B/s) - ‘/home//fogDBbackups/fog_sql_1.3.5-RC-10_20170221_110738.sql’ saved [0/0]
‘./10secdelay/i386-efi/intel.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/intel.efi’
cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/intel.efi’: No such file or directory
‘./10secdelay/i386-efi/ipxe.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/ipxe.efi’
cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/ipxe.efi’: No such file or directory
‘./10secdelay/i386-efi/realtek.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/realtek.efi’
cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/realtek.efi’: No such file or directory
‘./10secdelay/i386-efi/snp.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/snp.efi’
cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/snp.efi’: No such file or directory
‘./10secdelay/i386-efi/snponly.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/snponly.efi’
cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/snponly.efi’: No such file or directory
‘./10secdelay/ldlinux.c32’ -> ‘/tftpboot/./10secdelay/ldlinux.c32’
‘./10secdelay/libcom32.c32’ -> ‘/tftpboot/./10secdelay/libcom32.c32’
‘./10secdelay/libutil.c32’ -> ‘/tftpboot/./10secdelay/libutil.c32’
‘./10secdelay/memdisk’ -> ‘/tftpboot/./10secdelay/memdisk’
‘./10secdelay/menu.c32’ -> ‘/tftpboot/./10secdelay/menu.c32’
‘./10secdelay/pxelinux.0’ -> ‘/tftpboot/./10secdelay/pxelinux.0’
‘./10secdelay/pxelinux.0.old’ -> ‘/tftpboot/./10secdelay/pxelinux.0.old’
‘./10secdelay/pxelinux.cfg/default’ -> ‘/tftpboot/./10secdelay/pxelinux.cfg/default’
cp: cannot create regular file ‘/tftpboot/./10secdelay/pxelinux.cfg/default’: No such file or directory
‘./10secdelay/vesamenu.c32’ -> ‘/tftpboot/./10secdelay/vesamenu.c32’

[sudburr]

Hmm, 2nd and 3rd time around upgrading RC8 to RC10 I cannot reproduce it.

[Wayne Workman]

That makes no sense at all. I don’t disbelieve you, I just don’t know what’s going on.

[Tom Elliott]

This wasn’t a problem with key sequence or even double entries as originally thought (though that could still cause similar issues).

However it was found and is now fixed.