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

Dvm changes to get external postgres working. #1708

Merged
merged 1 commit into from
Jul 18, 2019

Conversation

PrajaktaPurohit
Copy link
Contributor

@PrajaktaPurohit PrajaktaPurohit commented Jul 18, 2019

Signed-off-by: Prajakta Purohit [email protected]

Currently external-postgresql does not work in the chef-server dvm setup.
Minor changes to fix it.

Output of running chef-server-ctl test and chef-server-ctl status

Finished in 51.44 seconds (files took 3.54 seconds to load)
172 examples, 0 failures, 2 pending

root@api:~# chef-server-ctl status
-------------------
 Internal Services
-------------------
run: bookshelf: (pid 14601) 297s; run: log: (pid 8954) 357s
run: nginx: (pid 14446) 299s; run: log: (pid 9378) 338s
run: oc_bifrost: (pid 14354) 300s; run: log: (pid 8646) 377s
run: oc_id: (pid 14439) 300s; run: log: (pid 8686) 371s
run: opscode-erchef: (pid 14678) 296s; run: log: (pid 9124) 351s
run: opscode-expander: (pid 14499) 297s; run: log: (pid 8816) 361s
run: opscode-solr4: (pid 14466) 298s; run: log: (pid 8751) 365s
run: rabbitmq: (pid 15112) 290s; run: log: (pid 9739) 332s
run: redis_lb: (pid 9288) 342s; run: log: (pid 9287) 342s
-------------------
 External Services
-------------------
The PGconn, PGresult, and PGError constants are deprecated, and will be
removed as of version 1.0.

You should use PG::Connection, PG::Result, and PG::Error instead, respectively.

Called from /opt/opscode/embedded/lib/ruby/gems/2.5.0/gems/chef-server-ctl-1.0.0/bin/chef-server-ctl:123:in `postgresql_connection'
run: postgresql: connected OK to 192.168.33.150:5432

Check List

@PrajaktaPurohit PrajaktaPurohit requested a review from a team July 18, 2019 14:24
dev/defaults.yml Outdated
@@ -7,7 +7,7 @@ vm:
postgresql:
# enable a separate postgres vm but do not use it unless
# use-vm-for-external is set.
start: false
start: true
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please change to false.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes - if you haven't already found, you can set this up in dev/config.yml to override the defaults.

@PrajaktaPurohit PrajaktaPurohit force-pushed the praj/fix_external_postgres_dvm branch from 76c6ce6 to da6f5da Compare July 18, 2019 16:01
@PrajaktaPurohit PrajaktaPurohit merged commit d121d27 into master Jul 18, 2019
@chef-ci chef-ci deleted the praj/fix_external_postgres_dvm branch July 18, 2019 16:33
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

Successfully merging this pull request may close these issues.

2 participants