Do a Sanity Check: Difference between revisions

From MediaWiki
Jump to navigationJump to search
Line 51: Line 51:
  NetworkManager-wait-online.service          enabled  
  NetworkManager-wait-online.service          enabled  
  nstboot.service                            enabled  
  nstboot.service                            enabled  
open-vm-tools.service                      enabled
  packagekit-offline-update.service          enabled  
  packagekit-offline-update.service          enabled  
  restorecond.service                        enabled  
  restorecond.service                        enabled  

Revision as of 22:17, 16 November 2013

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.

yum 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@dhcp105 ~]# 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@dhcp105 ~]# 

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@probe-eth0 ~]# 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 
acpid.service                               enabled 
dbus-org.freedesktop.NetworkManager.service enabled 
display-manager.service                     enabled 
gdm.service                                 enabled 
getty@.service                              enabled 
irqbalance.service                          enabled 
lvm2-monitor.service                        enabled 
mcelog.service                              enabled 
multipathd.service                          enabled 
NetworkManager.service                      enabled 
NetworkManager-wait-online.service          enabled 
nstboot.service                             enabled 
packagekit-offline-update.service           enabled 
restorecond.service                         enabled 
rngd.service                                enabled 
rsyslog.service                             enabled 
rtkit-daemon.service                        enabled 
smartd.service                              enabled 
spice-vdagentd.service                      enabled 
syslog.service                              enabled 
sysstat.service                             enabled 
systemd-readahead-collect.service           enabled 
systemd-readahead-drop.service              enabled 
systemd-readahead-replay.service            enabled 
vmtoolsd.service                            enabled 
[root@probe-eth0 ~]#

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.