Bug #21622
closed
Similarly named Chef Environments are not imported
Description
On our server we have some similarly named Chef Environments:
dev Development
dev-ng Development Next Gen
load Load Testing
load-ng Load Testing Next Gen
etc...
When we click "Import from Chef Server" on the environments page, *-ng environments are seen and the :add action is listed as they do not exist. Clicking import results in a "success" message, but the environments never appear.
Files
Updated by Chris Routh over 7 years ago
- File Screenshot from 2017-11-09 10-40-37.png Screenshot from 2017-11-09 10-40-37.pngScreenshot from 2017-11-09 10-40-37.png added
- File Screenshot from 2017-11-09 10-40-51.png Screenshot from 2017-11-09 10-40-51.pngScreenshot from 2017-11-09 10-40-51.png added
- File Screenshot from 2017-11-09 10-41-31.png Screenshot from 2017-11-09 10-41-31.pngScreenshot from 2017-11-09 10-41-31.png added
Updated by Chris Routh over 7 years ago
- File Screenshot from 2017-11-09 11-20-08.png Screenshot from 2017-11-09 11-20-08.pngScreenshot from 2017-11-09 11-20-08.png added
Thought I'd work around this by adding the environments manually. But we cannot.
This is a flaw in the environments naming standard that either the Chef Gem or Foreman allows for. "must be alphanumeric" - Chef allows for dashes in the name of an environment, so Foreman must also allow this.
Updated by Marek Hulán over 7 years ago
- Status changed from New to Closed
- Assignee set to Marek Hulán
- Translation missing: en.field_release changed from 215 to 216
- Pull request https://github.com/theforeman/foreman_chef/pull/83 added
Thanks for the report and sorry for the delay. I updated the validation according to the docs it can now contain hyphens and underscores.