The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
Cloud provisioner attempts to contact the dashboard on port 3000
|Branch:||Affected PE version:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This ticket may be automatically exported to the ENTERPRISE project on JIRA using the button below:
The cloud provisioner attempts to contact the dashboard on the previous port (3000) when running “puppet node classify”, however the Puppet Enterprise Console default port is 443. If installing the cloud provisioner in PE, it should look for the dashboard on port 443 by default. I’m not sure if this is a bug in PE or Cloud Provisioner.
#1 Updated by Daniel Pittman about 2 years ago
- Status changed from Unreviewed to Needs Decision
- Assignee set to Nigel Kersten
This looks like a conflict between FOSS and PE default values; Nigel, can you work out which we should have in the core repositories, and then I assume assign on to Mike to get the packaging updated to modify whatever other version to do the right thing.
#2 Updated by Nigel Kersten about 2 years ago
- Status changed from Needs Decision to Accepted
- Assignee deleted (
This is somewhat complex, as we don’t strictly have a “default port” in the normal sense.
We do try to install on 443 if it’s not in use, but the “default” in the installer is worked out somewhat intelligently by probing the ports to see if they’re in use.
This feels like the sort of thing that is ultimately going to be solved by a centralized store of info that states what port the ENC is running on.
What about us defaulting to 443 if they’ve said they’re using SSL?