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

Delay on settings update #1

Open
abraverm opened this issue Apr 30, 2018 · 2 comments
Open

Delay on settings update #1

abraverm opened this issue Apr 30, 2018 · 2 comments

Comments

@abraverm
Copy link

Hi, first of all, awesome role and module! thank you for creating it.
My current solution uses configure_server_settings.rb tool which updates one setting at a time but the change is immediate. When I used your module it seems to take some time for the change to apply. I tried to add ::Settings.reload! but it didn't help.

Thanks,
Alex

@itewk
Copy link
Collaborator

itewk commented Apr 30, 2018

@abraverm Thank you for the interest in the role and module. As for the module itself, a lot of the design decisions were due to feedback when trying to merge the module into upstream ansible. That conversation can be seen here, ansible/ansible#35182.

I have seen some delays in processing times of settings change, but they are all on the ManageIQ queue/scheduling side. I don't think there is much we can do from the module side to coax along the ManageIQ queue/schedule.

Before I just close this as "not sure what we can do", do you have any ideas on what we could do to force a quicker loading of the settings?

Also, the module shouldn't return until the setting has actually been applied. Are you seeing the module complete and the setting still not being applied?

@abraverm
Copy link
Author

Before I just close this as "not sure what we can do", do you have any ideas on what we could do to force a quicker loading of the settings?

Ruby or cloudforms internals are far from my expertise, I think the difference between the implementations is that the tool updates the server object directly with save! while module is doing it through vmdb::settings which goes to the queue as you said. One option is to refactor the code to update server directly like in the tool.

Also, the module shouldn't return until the setting has actually been applied. Are you seeing the module complete and the setting still not being applied?

Yes, for example I use the module to change authentication settings and it says they are changed but when I check the UI the old settings are still there.

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

No branches or pull requests

2 participants