Update documentation as needed

Description

None

Acceptance Criteria

None

Activity

Show:
Liz Nemsick
October 21, 2020, 2:52 PM
Edited

Should the section 'Set svckill::mode to warning' tell the users to set this to warning in the default.yaml file? Otherwise, couldn't there be a negative impact on client nodes that may run puppet agent during the server upgrade process?

Liz Nemsick
October 21, 2020, 3:16 PM
Edited

I think the section on general instructions should tell the user to verify puppetserver and puppetdb are up. When I ran the upgrade on el7, puppetdb was down and the puppet agent run failed. I saw the polkit error when checking the service status using systemctl directly, so that may be worth noting in the SIMP 6.4.0 to 6.5.0 upgrade section. (You won't see the message when you use puppet resource service x, but there is no guarantee the user won't attempt some service command in the middle of the upgrade.)

Liz Nemsick
October 21, 2020, 3:57 PM

In general upgrade instructions replace 'Use the --force option if you get warnings that local changes will get overwritten and you are sure you do not have changes that need saving.' with 'Use the --force option if you get warnings that local changes will get overwritten and you are sure you do not have changes that need to be saved.'

Also, should we mention that the --force option will tell you that it is "Overwriting local modifications" even when there are not local changes being overwritten? We are hitting weird r10k behavior that we may want to let our users know is normal.

Liz Nemsick
October 21, 2020, 4:06 PM

It took two puppet agent runs after the upgrade to get to idempotency. Should the general upgrade instructions tell the users to run puppet until convergence, or is that general puppet knowledge that they should have if they are upgrading a system?

Liz Nemsick
October 21, 2020, 7:39 PM
Edited

unpack_dvd has unexpected consequences in CentOS if you do not specify the -v option (e.g. unpack_dvd SIMP-6.5.0-1.el7-CentOS-7.0-x86_64.iso --unpack-pxe ). It places the OS packages in the existing CentOS-<major version> directory in yum and the OS pxeboot files in the /var/simp/environments/..../linux-install/centos-<major version> directories. Since each of those directories is typically a link to a previous CentOS release directory, it means means {{unpack_dvd} overwrites the files for the previous CentOS release. Our docs should tell the user to use the -v option for CentOS.

Labels

None

Story Points

1

Assignee

Jeanne Greulich

Sprint

Priority

Medium
Configure