fix AnsibleFailedError: hwclock: Cannot access the Hardware Clock via…#807
Open
fix AnsibleFailedError: hwclock: Cannot access the Hardware Clock via…#807
Conversation
… any known method
djgalloway
reviewed
Feb 18, 2026
Comment on lines
+35
to
+37
| become: true | ||
| become_method: sudo | ||
| become_user: root |
Contributor
There was a problem hiding this comment.
djgalloway
reviewed
Feb 18, 2026
Contributor
There was a problem hiding this comment.
Modifying this file isn't necessary for your stated use case of VMs or containers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In virtual machines or containers, running the
smoketest case can easily lead to failure due to errors like "['hwclock: Cannot access the Hardware Clock via any known method.', 'hwclock: Use the --verbose option to see the details of our search for an access method.']". This is because virtual machines or containers typically lack the necessary permissions to directly execute thehwclockcommand, and such errors are not usually serious and should not cause test case failures. In containers or virtual machines,hwclockerrors should be ignored to allow the test case to continue execution.fix https://tracker.ceph.com/issues/69280