Skip to content
This repository has been archived by the owner on Feb 13, 2023. It is now read-only.

'postgresql_packages' is undefined #957

Closed
mgifford opened this issue Nov 1, 2016 · 9 comments
Closed

'postgresql_packages' is undefined #957

mgifford opened this issue Nov 1, 2016 · 9 comments

Comments

@mgifford
Copy link

mgifford commented Nov 1, 2016

I'm not sure why I am getting this error when I run $ vagrant provision:

TASK [geerlingguy.postgresql : Ensure PostgreSQL packages are installed.] ******
fatal: [drupalvm]: FAILED! => {"failed": true, "msg": "'postgresql_packages' is undefined"}

I can't find a solid reference to 'postgresql_packages', but have made sure that postgresql is installed:
$ brew install postgresql

It seems to be running:
$ brew services start postgresql
Service postgresql already started, use brew services restart postgresql to restart.

Where should this be defined?

This is on a Mac (obviously), but not sure where to go from here. It was running find the last time I used DrupalVM. Just did an update and now am rather stuck.

@geerlingguy
Copy link
Owner

@mgifford - This would be inside the VM itself... but there shouldn't be a condition when using Drupal VM where that variable isn't defined—you're using Vagrant and building a VM using one of the geerlingguy/* boxes, correct?

Here's the task in the Ansible role that defines the packages: https://github.com/geerlingguy/ansible-role-postgresql/blob/3cb4aaaa53b32a0a0df113db19777d4a72afcd83/tasks/variables.yml#L11-L14

Do you have something like postgresql_packages: [] in your config.yml?

@mgifford
Copy link
Author

mgifford commented Nov 2, 2016

  1. Thanks again for being amazing.

  2. I'm going to build this again with one of the geerlingguy/* boxes in the morning and will let you know.

  3. This is an older instance I'm building on. I'm pretty sure I haven't added anything special to the config.yml but will look.

@Razunter
Copy link

Razunter commented Nov 2, 2016

Same issue. Upgraded from 3.2 or older version of DrupalVM. Had to figure out how to upgrade Ansible, no mention of that in "breaking changes". But can't find workaround for this issue.

@antonyanimator
Copy link

I have the same issue, running the 14.04 vm

@geerlingguy
Copy link
Owner

@geerlingguy
Copy link
Owner

Fixed upstream, going to fix by updating role deps here.

@mgifford
Copy link
Author

mgifford commented Nov 3, 2016

Progress. I'm getting different errors now.

I ran vagrant box update

I made that ansible is at 2.2.0.0

I've updated the git repo for drupalvm

Finished: success: 7, skipped: 0, failure: 0, total: 7\nLoading composer repositories with package information\nUpdating dependencies (including require-dev)\nYour requirements could not be resolved to an installable set of packages.\n\n  Problem 1\n    - The requested package drupal/devel could not be found in any version, there may be a typo in the package name.\n\nPotential causes:\n - A typo in the package name\n - The package is not available in a stable-enough version according to your minimum-stability setting\n   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.\n\nRead <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.\n\nInstallation failed, reverting ./composer.json to its original content.", "stdout": "", "stdout_lines": [], "warnings": []}
    to retry, use: --limit @/Users/mikegifford/drupal-vm/provisioning/playbook.retry

PLAY RECAP *********************************************************************
drupalvm                   : ok=174  changed=2    unreachable=0    failed=1   

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

GitHub doesn't seem to like the long lines. Full report here - http://pastebin.com/ezBwqzfS

Seems the problem boils down to "The requested package drupal/devel could not be found in any version".

@danepowell
Copy link
Contributor

For anyone looking for a fix to the original problem here... basically the solution is to update DrupalVM to 3.5.1. It doesn't look like there was ever an upstream "fix" to Ansible.

@benjifisher
Copy link
Contributor

GitHub doesn't seem to like the long lines.

I think the long lines are fine, but maybe it is hard to tell because your browser does not show a scrollbar unless you are actively scrolling. Is this a "feature" of recent versions of macOS?

brandonratz pushed a commit to confcats/drupal-vm that referenced this issue Nov 18, 2016
kekkis pushed a commit to kekkis/drupal-vm that referenced this issue Feb 23, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants