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.

Sign up for GitHub

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

Jump to bottom

There is no /etc/systemd/timesyncd.conf.d folder by default - Step 2.1.3.1 #62

Closed
arvatoth-vcc opened this issue Aug 21, 2023 · 2 comments
Closed

There is no /etc/systemd/timesyncd.conf.d folder by default - Step 2.1.3.1 #62

arvatoth-vcc opened this issue Aug 21, 2023 · 2 comments
Assignees
@uk-bolly
Labels
bug Something isn't working

Comments

@arvatoth-vcc
Copy link

Describe the Issue
In step 2.1.3.1. copying 50-timesync.conf file to the /etc/systemd/timesyncd.conf.d folder, but this is not exists by default.

Expected Behavior
Need to create folder in a previous task.

Actual Behavior
Error happens, no such directory.

Environment:

  • branch being used: devel
  • Ansible Version: 2.12.0
  • Host Python Version: 3.10.12
  • Ansible Server Python Version: 3.10.12
  • Additional Details: Ubuntu 22.04 in KVM virtual server

Possible Solution
Create folder before copying task.
@arvatoth-vcc arvatoth-vcc added the bug Something isn't working label Aug 21, 2023
@uk-bolly uk-bolly self-assigned this Aug 30, 2023
uk-bolly added a commit that referenced this issue Aug 30, 2023
@uk-bolly
Addressed #62
4144b85 
Signed-off-by: Mark Bolwell <[email protected]>
@uk-bolly uk-bolly mentioned this issue Sep 5, 2023
Merged
uk-bolly added a commit that referenced this issue Sep 6, 2023
@uk-bolly
Merge pull request #66 from ansible-lockdown/issue_#62
2a7c649 
Addressed #62
@uk-bolly uk-bolly mentioned this issue Sep 12, 2023
Merged
@uk-bolly
Copy link
Member

uk-bolly commented Sep 19, 2023 •
edited
Loading

hi @arvatoth-vcc

Thank you for raising this issue. The fix has now been added to the devel branch.
Please let us know if you are still seeing the issue?

Many thanks

uk-bolly

@arvatoth-vcc
Copy link
Author

hi @uk-bolly,

Great, thank you, working perfectly.

@uk-bolly uk-bolly mentioned this issue Sep 26, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@uk-bolly uk-bolly

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arvatoth-vcc @uk-bolly