Bug #27484
closed
foreman-installer broken with postgres
Description
Environment:
- Fresh install in CentOS 7 (AWS instance)
- Default instructions for 1.22.0 and 1.21.3
After following all installation steps the foreman is up and running but no environments are imported. Using the installer with --foreman-db-type=mysql works as expected.
Not sure if it related to #27315 as in my case no errors were reported.
Files
Updated by Ewoud Kohl van Wijngaarden almost 5 years ago
Do you have anything like an installer log (from /var/log/foreman-installer)?
Updated by Fabrício Cabeça almost 5 years ago
Ewoud Kohl van Wijngaarden wrote:
Do you have anything like an installer log (from /var/log/foreman-installer)?
Unfortunately I've terminated the machine that would have a clean log, when I can I will run another instance to grab these, it was 100% reproducible...
Updated by Fabrício Cabeça almost 5 years ago
- File foreman.log foreman.log added
- File foreman.1.log foreman.1.log added
Ewoud Kohl van Wijngaarden wrote:
Do you have anything like an installer log (from /var/log/foreman-installer)?
Updated by Ewoud Kohl van Wijngaarden almost 5 years ago
I don't see any error. Can you describe how it's broken?
Updated by Fabrício Cabeça almost 5 years ago
Ewoud Kohl van Wijngaarden wrote:
I don't see any error. Can you describe how it's broken?
It doesn't import the production environment, of course I did add the puppet ntp class as described in the installation instructions right after the quickstart guide as suggested, and I also ran the foreman-rake command to import this class, classes imported, no environment.
Updated by Ewoud Kohl van Wijngaarden almost 5 years ago
Are you sure the environment has the correct taxonomies? I think we've seen a bug where it's not assigned any so not visible. You can try to select Any organizations and Any locations in the top menu, go to environments overview. If you then see it, edit it to assign the taxonomies.
Updated by Fabrício Cabeça almost 5 years ago
Ewoud Kohl van Wijngaarden wrote:
Are you sure the environment has the correct taxonomies? I think we've seen a bug where it's not assigned any so not visible. You can try to select Any organizations and Any locations in the top menu, go to environments overview. If you then see it, edit it to assign the taxonomies.
You saved my day ! I thought it was fixed when I saw the environment after importing the puppet classes but it was still broken elsewhere. Assigning the taxonomies using the "fix mismatches" button fixed everything. Thanks !
Updated by Fabrício Cabeça almost 5 years ago
- Status changed from New to Resolved