Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CA-399643 Use full paths when stopping fairlock on upgrade #708

Merged

Conversation

TimSmithCtx
Copy link
Contributor

Amend the fairlock upgrade scriptlet so that it uses full paths. This prevents it failing unexpectedly. Also, change it from a %posttrans scriptlet to a %post scriptlet so that the new version will have an effect immediately any new version is available.

Amend the fairlock upgrade scriptlet so that it uses full paths. This
prevents it failing unexpectedly. Also, change it from a %posttrans
scriptlet to a %post scriptlet so that the new version will have an
effect immediately any new version is available.

Signed-off-by: Tim Smith <tim.smith@cloud.com>
@@ -237,13 +237,16 @@ Manager and some other packages
%{_unitdir}/fairlock@.service
%{_libexecdir}/fairlock

%posttrans fairlock
%post fairlock
## On upgrade, shut down existing lock services so new ones will
## be started. There should be no locks held during upgrade operations
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What allows to ensure that there's no lock at the time of the RPM update?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The toolstack assures us they do not perform RPM upgrades while simultaneously performing storage management operations. Anyone on the command line who chooses to do an RPM upgrade in the middle of a disk shuffle should expect many more problems than just the odd dropped lock :-)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Is it the fact that the host is disabled during the upgrades which ensures this?

@MarkSymsCtx MarkSymsCtx merged commit 24de268 into xapi-project:master Sep 26, 2024
2 checks passed
@TimSmithCtx TimSmithCtx deleted the private/timsmi/CA-399643 branch October 3, 2024 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants