Do a Sanity Check

From NST Wiki
Jump to navigationJump to search

Prior to creating a release, one should perform the following sanity checks.

Note: In order to perform all of the sanity checks, you will need BOTH your NST development system and a running NST probe.


You should do a commit to ensure that you do not have any outstanding modifications.

svn commit

Build Yum Repository

Run the following from the top level directory to make certain that you can build and update all the RPM files that make up the NST repository.

dnf clean all
make repo-build

Check Enabled Services

Make sure you boot a recent ISO image and verify that the expected services are enabled at boot time. Be aware that the sshd and httpd services will not be enabled or running until the nstpasswd command is run.

[root@localhost ~]# chkconfig --list | grep 3:on

Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overridden by native
      systemd configuration.

      If you want to list systemd services use 'systemctl list-unit-files'.
      To see services enabled on particular target use
      'systemctl list-dependencies [target]'.

livesys        	0:off	1:off	2:off	3:on	4:on	5:on	6:off
livesys-late   	0:off	1:off	2:off	3:on	4:on	5:on	6:off
[root@localhost ~]# 

As noted in the output, the above doesn't show information about native systemd services. To view those services as well, run the following command and review the output produced.NOTE: The output shown below was produced after booting the NST ISO in VirtualBox and selecting the default Graphical Desktop target.

[root@localhost ~]# systemctl list-unit-files | grep enabled | grep service | sort
abrt-journal-core.service                   enabled
abrt-oops.service                           enabled
abrt-vmcore.service                         enabled 
abrt-xorg.service                           enabled
accounts-daemon.service                     enabled
autovt@.service                             enabled
dbus-broker.service                         enabled
dbus-daemon.service                         enabled
dbus-org.freedesktop.ModemManager1.service  enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
dbus-org.freedesktop.timedate1.service      enabled
dbus.service                                enabled
dbxtool.service                             enabled
display-manager.service                     enabled
dkms.service                                enabled
dmraid-activation.service                   enabled
getty@.service                              enabled
import-state.service                        enabled
irqbalance.service                          enabled
lightdm.service                             enabled
lvm2-monitor.service                        enabled
mcelog.service                              enabled
messagebus.service                          enabled
ModemManager.service                        enabled
multipathd.service                          enabled
NetworkManager-dispatcher.service           enabled
NetworkManager.service                      enabled
NetworkManager-wait-online.service          enabled
nstboot.service                             enabled
rngd.service                                enabled
rsyslog.service                             enabled
rtkit-daemon.service                        enabled
selinux-autorelabel-mark.service            enabled
smartd.service                              enabled
sssd.service                                enabled
timedatex.service                           enabled
udisks2.service                             enabled
vboxservice.service                         enabled 
vgauthd.service                             enabled  
vmtoolsd-init.service                       enabled 
vmtoolsd.service                            enabled 
[root@localhost ~]#

You might only see the vboxservice.service entry if you are running under VirtualBox.

Verify That Documentation Builds

Make sure the docs directory builds. This is required to update the on-line version of the man pages for the release:

[root@dev repo]# cd docs
[root@dev docs]# make

Run Automated Tests

Run the following from the top level to perform numerous checks on the running NST probe with the IP address specified.

make probe-check HOST=IP

There will be a LOT of output produced. A copy of the output will be saved to the file: "probe-check.log" which may be viewed using the command: "less -R probe-check.log". Make sure the file looks clean (or like you would expect). Make sure you aren't tempted to skip this step. We thought we were OK and skipped this step during the 1.8.1 release and ended up delivering a ISO image with a broken sym-link.