Do a Sanity Check: Difference between revisions
Line 20: | Line 20: | ||
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. | 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 | Note: This output shows SysV services only and does not include native | ||
Line 28: | Line 28: | ||
livesys 0:off 1:off 2:off 3:on 4:on 5:on 6:off | 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 | livesys-late 0:off 1:off 2:off 3:on 4:on 5:on 6:off | ||
[root@ | [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: | 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: | ||
[root@ | [root@localhost ~]# systemctl list-unit-files | grep enabled | grep service | sort | ||
abrt-ccpp.service enabled | abrt-ccpp.service enabled | ||
abrtd.service enabled | abrtd.service enabled | ||
Line 39: | Line 39: | ||
abrt-xorg.service enabled | abrt-xorg.service enabled | ||
accounts-daemon.service enabled | accounts-daemon.service enabled | ||
autovt@.service enabled | |||
dbus-org.freedesktop.ModemManager1.service enabled | dbus-org.freedesktop.ModemManager1.service enabled | ||
dbus-org.freedesktop.NetworkManager.service enabled | dbus-org.freedesktop.NetworkManager.service enabled | ||
Line 46: | Line 46: | ||
dmraid-activation.service enabled | dmraid-activation.service enabled | ||
getty@.service enabled | getty@.service enabled | ||
hypervfcopyd.service enabled | |||
hypervkvpd.service enabled | |||
hypervvssd.service enabled | |||
irqbalance.service enabled | irqbalance.service enabled | ||
lightdm.service enabled | lightdm.service enabled | ||
lvm2-monitor.service enabled | lvm2-monitor.service enabled | ||
mcelog.service enabled | mcelog.service enabled | ||
ModemManager.service enabled | ModemManager.service enabled | ||
multipathd.service enabled | multipathd.service enabled | ||
Line 58: | Line 59: | ||
NetworkManager-wait-online.service enabled | NetworkManager-wait-online.service enabled | ||
nstboot.service enabled | nstboot.service enabled | ||
nstwui.service enabled | |||
rngd.service enabled | rngd.service enabled | ||
rsyslog.service enabled | rsyslog.service enabled | ||
Line 63: | Line 65: | ||
smartd.service enabled | smartd.service enabled | ||
spice-vdagentd.service enabled | spice-vdagentd.service enabled | ||
sshd.service enabled | |||
syslog.service enabled | syslog.service enabled | ||
udisks2.service enabled | |||
vgauthd.service enabled | |||
vmtoolsd.service enabled | |||
vmtoolsd.service enabled | [root@localhost ~]# | ||
[root@ | |||
== Verify That Documentation Builds == | == Verify That Documentation Builds == |
Revision as of 08:47, 3 July 2016
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.
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. 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:
[root@localhost ~]# systemctl list-unit-files | grep enabled | grep service | sort abrt-ccpp.service enabled abrtd.service enabled abrt-oops.service enabled abrt-vmcore.service enabled abrt-xorg.service enabled accounts-daemon.service enabled autovt@.service enabled dbus-org.freedesktop.ModemManager1.service enabled dbus-org.freedesktop.NetworkManager.service enabled dbus-org.freedesktop.nm-dispatcher.service enabled display-manager.service enabled dmraid-activation.service enabled getty@.service enabled hypervfcopyd.service enabled hypervkvpd.service enabled hypervvssd.service enabled irqbalance.service enabled lightdm.service enabled lvm2-monitor.service enabled mcelog.service enabled ModemManager.service enabled multipathd.service enabled NetworkManager-dispatcher.service enabled NetworkManager.service enabled NetworkManager-wait-online.service enabled nstboot.service enabled nstwui.service enabled rngd.service enabled rsyslog.service enabled rtkit-daemon.service enabled smartd.service enabled spice-vdagentd.service enabled sshd.service enabled syslog.service enabled udisks2.service enabled vgauthd.service enabled vmtoolsd.service enabled [root@localhost ~]#
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.