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
chef-server-ctl upgrade fails at postgresql migrations (using sqitch) #1037
Comments
The hacky solution is to edit def run_sqitch(target, service, opts = {})
options = default_opts_for_service(service).merge(opts)
command = <<-EOM.gsub(/\s+/," ").strip!
sqitch --engine pg
--db-name #{options[:database]}
--db-host #{Partybus.config.postgres['vip']}
--db-port #{Partybus.config.postgres['port']}
--db-user EXPLICITLY SET USERNAME
--top-dir /opt/opscode/embedded/service/#{options[:path]}
deploy #{target} --verify
EOM
run_command(command, env: {"PGPASSWORD" => EXPLICITLY SET PASSWORD})
end |
From my reading of the code, it looks like what possibly could have been the case is that |
@mathiasjakobsen has this been resolved? 😃 |
@srenatus I actually don't know ¯\(ツ)/¯ As I mentioned above I used a hacky solution to get around the problem, and havn't done an update since. But we can close the issue, and I'll reopen if I encounter it again. |
@mathiasjakobsen thanks for cleaning up! 👍 |
I'm having the exact same issue, but the fix shown above is not working. I assume the user and password and single quoted strings? |
@bucm01 as I recall, the username was not quoted, but the password was double quoted. |
When
chef-server-ctl upgrade
-ing, the following happens in the the[private-chef-upgrade]
step..Trying to run the command manually shows that because no
--db-user
is specified, it reads the next arguments wrong, and interprets the--top-dir
as binaries.When removing
--db-user
, it fails withfe_sendauth: no password supplied
.See here for full log:
The text was updated successfully, but these errors were encountered: