Do a Sanity Check
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.
Commit
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.
sudo 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 Console target and running nstpasswd.
[root@probe ~]# systemctl list-unit-files | grep "enabled " | grep service | sort abrt-journal-core.service enabled enabled abrt-oops.service enabled enabled abrt-vmcore.service enabled enabled abrt-xorg.service enabled enabled accounts-daemon.service enabled enabled dbus-daemon.service enabled enabled dkms.service enabled enabled getty@.service enabled enabled import-state.service enabled enabled irqbalance.service enabled enabled lightdm.service enabled enabled lvm2-monitor.service enabled enabled mcelog.service enabled enabled ModemManager.service enabled enabled NetworkManager-dispatcher.service enabled enabled NetworkManager.service enabled enabled NetworkManager-wait-online.service enabled enabled nstboot.service enabled enabled nstwui.service enabled disabled ostree-remount.service enabled enabled pmcd.service enabled enabled pmie.service enabled enabled pmlogger.service enabled enabled rsyslog.service enabled enabled rtkit-daemon.service enabled enabled selinux-autorelabel-mark.service enabled enabled smartd.service enabled enabled sshd.service enabled disabled sssd.service enabled enabled switcheroo-control.service enabled enabled systemd-homed-activate.service enabled disabled systemd-homed.service enabled enabled systemd-network-generator.service enabled enabled systemd-pstore.service enabled enabled udisks2.service enabled enabled upower.service enabled enabled vboxservice.service enabled enabled vgauthd.service enabled disabled vmtoolsd.service enabled enabled [root@probe ~]#
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.
