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

proxy_mysql_server needs a default for status in order for the insert to succeed #33

Merged
merged 1 commit into from
Aug 3, 2017

Conversation

mcrauwel
Copy link
Member

@mcrauwel mcrauwel commented Aug 3, 2017

No description provided.

@alexjfisher alexjfisher changed the title proxy_mysql_server needs a default for status in order for the insert to succeeed... proxy_mysql_server needs a default for status in order for the insert to succeed Aug 3, 2017
@alexjfisher alexjfisher added the bug Something isn't working label Aug 3, 2017
@alexjfisher
Copy link
Member

Should the default go in here instead?

@mcrauwel
Copy link
Member Author

mcrauwel commented Aug 3, 2017

No we don't want to force a default if the field is not managed by puppet, we just need a default to be able to insert it and then we don't need to manage it further.

This field is often managed by external scripts like the proxysql_galera_checker and adding the default to the type will result the galera_checker and puppet to fight...

See also: http://www.proxysql.com/blog/galera-awareness-and-proxysql-scheduler

@mcrauwel
Copy link
Member Author

mcrauwel commented Aug 3, 2017

this bug was caused by the fix for #25

@alexjfisher alexjfisher merged commit 00eb033 into voxpupuli:master Aug 3, 2017
@mcrauwel mcrauwel deleted the fix_default_value branch September 10, 2018 09:08
cegeka-jenkins pushed a commit to cegeka/puppet-proxysql that referenced this pull request Aug 22, 2023
proxy_mysql_server needs a default for status in order for the insert to succeed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants