Difference between revisions of "Do a Sanity Check"

From NST Wiki
Jump to navigationJump to search
(Check Package Links)
(Check Enabled Services)
Line 28: Line 28:
 
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@dhcp106 ~]# chkconfig --list | grep 3:on
+
  [root@dhcp105 ~]# 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 34: Line 34:
 
       systemd configuration.
 
       systemd configuration.
 
   
 
   
cpuspeed      0:off 1:on 2:on 3:on 4:on 5:on 6:off
 
 
  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
lvm2-monitor  0:off 1:on 2:on 3:on 4:on 5:on 6:off
+
  [root@dhcp105 ~]#  
open-vm-tools  0:off 1:off 2:on 3:on 4:on 5:on 6:off
 
sysstat        0:off 1:on 2:on 3:on 4:on 5:on 6:off
 
  [root@dhcp106 ~]#  
 
  
 
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@dhcp106 ~]# systemctl | grep service
+
  [root@dhcp105 ~]# systemctl list-unit-files | grep enabled | grep service | sort
 +
abrt-vmcore.service                        enabled
 +
acpid.service                              enabled
 +
arp-ethers.service                          enabled
 +
dbus-org.freedesktop.NetworkManager.service enabled
 +
getty@.service                              enabled
 +
httpd.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 
 +
open-vm-tools.service                      enabled
 +
rsyslog.service                            enabled
 +
sshd-keygen.service                        enabled
 +
sshd.service                                enabled
 +
systemd-readahead-collect.service          enabled
 +
systemd-readahead-replay.service            enabled
 +
system-setup-keyboard.service              enabled
 +
[root@dhcp105 ~]#
  
 
== Verify That Documentation Builds ==
 
== Verify That Documentation Builds ==

Revision as of 12:33, 27 February 2012

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 Package Links

Check the links on the manifest page (you may want to use the Pinger Firefox add-on as it was recently updated to support Firefox 3.5).

Alternatively, we may want to consider making a "make link-check" target to perform a similar test using the URLs from the "pkginfo.xml" files we define.

Will need to discuss this step with Ron.

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@dhcp105 ~]# systemctl list-unit-files | grep enabled | grep service | sort
abrt-vmcore.service                         enabled 
acpid.service                               enabled 
arp-ethers.service                          enabled 
dbus-org.freedesktop.NetworkManager.service enabled 
getty@.service                              enabled
httpd.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  
open-vm-tools.service                       enabled 
rsyslog.service                             enabled 
sshd-keygen.service                         enabled 
sshd.service                                enabled 
systemd-readahead-collect.service           enabled 
systemd-readahead-replay.service            enabled 
system-setup-keyboard.service               enabled 
[root@dhcp105 ~]#

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 frolloing 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.