New features, enhancements, resolved issues, and known issues for Puppet Discovery 1.x release series.
Released 28 February 2019
Role-based access control (RBAC). Puppet Discovery supports the admin and the viewer user role, each with specific permissions. For more information, see Managing access.
Microsoft Azure and OpenStack dashboard cards. Displayed on each dashboard card is the total number of hosts discovered running on your Microsoft Azure and OpenStack accounts. For more information, see Dashboard cards.
- Microsoft Azure host summary page. Listed on the host summary page are the discovered hosts and specific host attributes, such as subscription ID, resource groups, and key names. For more information, see Azure .
OpenStack host summary page. Listed on the host summary page are the discovered hosts and specific host attributes, such as flavors, security groups, and key names. For more information, see OpenStack .
Contextual tasks. Depending on which summary or details page you are viewing, Puppet Discovery offers specific tasks to run on the listed hosts, host instances, or packages. For more information, see Running tasks on hosts.
Refreshing the dashboard. You can automatically or manually refresh the Puppet Discovery dashboard. For more information, see Dashboard.
Updating from 1.7.0, or lower, returns an error. When updating to 1.9.0 from 1.7.0, or lower, the
puppet-discovery statuscommand returns an error message relating to the pdp service not starting. To resolve this issue, see Updating Discovery.
Initialization errors. After starting Puppet Discovery, you may receive initialization errors relating to
v1/sys/init. To resolve this issue, run the
puppet-discovery resetcommand. This will erase all configured sources and credentials.
Duplicate hosts discovered. Puppet Discovery does not deduplicate discovered hosts that have
Released 18 December 2018
Amazon Web Services and VMware dashboard cards. The Amazon Web Services (AWS) and the VMware dashboard cards display the total number of discovered hosts running on your each of your accounts. For more information, see Dashboard cards.
AWS host summary page. The AWS host summary page lists the discovered hosts and specific host attributes, such as the instance types, security groups, and tags. For more information, see Amazon Web Services.
VMware VSphere host summary page. The VMware host summary page lists the discovered hosts and specific host attributes, such as the instance types, tags, annotations, and states. For more information, see VMware vSphere.
Improved logging for the pd_edge container. View each discovery transaction log by setting the
edge.loglevelconfiguration override to INFO. For more information, see Configuration overides.
Offline update. Using the offline mode, Puppet Discovery supports updating installations on air-gapped machines. For detailed instructions, see Updating Discovery.
Case insensitive filtering. When filtering resources on any of the host, package, or container pages, all filter operators support case-insensitivity.
pd-gopdp and pd_storage containers. The
pd-gopdpcontainer, which replaces the
pd_pdpcontainer, provides a new implementation of the ingest service that processes discovered data, and the storage layer for discovered data is separated out into its own container,
pd_storage. For more information, see Puppet Discovery architecture.
Containers used an inconsistent restart policy. When restarting the Docker daemon, some of the Discovery containers also restarted.
The offline command returned an unknown flag error. When installing Discovery using the offline mode, the
--offlinecommand returned the
unknown flag: --offlineerror.
puppet-discovery restartcommand did not support the
The pdp service doesn't start. After updating to 1.8.0, the
puppet-discovery statuscommand returns an error message relating to the pdp service not starting. Ignore this error message as the
pd_pdpcontainer is no longer used and will eventually be removed.
Delay in the dashboard populating. After updating from 1.6.0, or lower, the dashboard does not populate until after the first discovery run. The default setting, which can be modified, for each Discovery run is every 30 minutes. For more information, see Configuration overides.
Browser refresh required after updating. If you have Puppet Discovery open in a browser and update to the 1.8.0 release, you must refresh your browser to be able to sign in.
Released 27 November 2018
Export discovered resources to a CSV file. To export summary data relating to discovered hosts, packages, or containers to a CSV file, click Export on each summary page. For detailed instructions, see Filtering and exporting resources.
Multi-criteria filtering on target hosts. When configuring a task, create a custom filter to view target hosts based on multiple criteria that you specify. For more information, see Filtering and exporting resources.
Customize table columns. On each resource summary page, customize the table by hiding or showing columns to display data that is most relevant to you. For detailed instructions, see Filtering and exporting resources.
Progress bar displayed when configuring a task. A progress bar guides you through the process of running a task on target hosts; select a task, choose your target hosts, select host credentials, and review your task details.
Inaccessible hosts dashboard card. Due to invalid credentials or configuration issues, the new dashboard card displays the total number of hosts that are not accessible to discover resources on. For more information, see Viewing resources.
Select all option affected by a race condition. When applying the Select all option on the list of target hosts to run a task on, a slow network connection and a large number of target hosts resulted in not all of the hosts being selected.
Containers were not discovered on hosts that had OpenSSH 6.7, or lower, configured. To discover containers, the version of curl running on each host had to support the
Containers were not discovered on hosts that had OpenSSH 7.4 configured. To discover containers, your SSH credentials had to be for a non-root account that was also a member of the Docker group.
Updating to 1.7.0. After updating from 1.6.0, you may receive an error message that volumes relating to pdp-go are still in use. For more information, see Updating Discovery.
Host and package data not discovered on hosts. Data relating to services, uptime, and packages are not discovered on Oracle Linux hosts running versions greater than 7.2.
Unable to sign out. During the first-time user workflow, you are unable to sign out of Puppet Discovery.
Resources discovered when a source is removed. When a source is deleted during the discovery process, resources relating to the source are still discovered.
Released 9 October 2018
OpenStack. Add your OpenStack credentials to discover the host instances running on each of your OpenStack accounts. In addition to this, add SSH and WinRM authentication credentials to discover resources running on each host. For more information, see Adding sources and Adding host credentials.
Multi-criteria filteringon hosts, packages, and containers. Filter the list of discovered hosts, packages, or containers on each summary page by creating a custom filter to view resources based on multiple criteria that you specify. For more information, see Filter hosts, containers, or packages on summary pages.
Manage packages on target hosts. Run the manage package task to install, upgrade, or uninstall packages on discovered Linux and Windows hosts without installing an agent. For more information, see Running tasks on target hosts.
Run commands on target hosts. Run the execute command task to run arbitrary shell commands on discovered Linux and Windows hosts without installing an agent. For more information, see Running tasks on target hosts.
First-time user workflow. A redesigned first-time run guides you through adding sources and host credentials, to viewing discovered resources on the Puppet Discovery dashboard.
Japanese support. The Puppet Discovery UI is available in Japanese and internationalized for the future addition of other languages. A Japanese version of the documentation is also available.
curl --unix requirement. To discover containers, the version of curl running on each target host required the
--unix-socketparameter. This dependency has now been removed.
Discovery fails to start after an update. When updating from 1.4.0, or lower, the
puppet-discovery startcommand fails to start the application. To update from 1.4.0, or lower, see Updating Puppet Discovery.
Sources and credentials must be added after updating an offline installation. To update an offline installation, you must install Discovery using the offline mode, and enter your sources and credentials again. For more information, see Installing in offline mode.
Containers not discovered on hosts that have OpenSSH 6.7, or lower, configured. To discover containers, the version of curl running on each host must support the
Containers not discovered on hosts that have OpenSSH 7.4 configured . To discover containers, your SSH credentials must be for a non-root account that is also a member of the Docker group.
The cumulative total number of packages displayed on dashboard card. The packages dashboard card displays the cumulative total number of packages discovered across all hosts, whereas the packages summary page lists the total amount of unique packages.
Select all option may not select all hosts. When applying the Select all option on the list of target hosts to run a task on, a slow network connection and a large number of target hosts can result in not all of the hosts being selected.
Released 19 September 2018
Offline installation. Using the offline mode, Puppet Discovery supports installations on air-gapped machines. For detailed instructions, see Installing in offline mode.
Incorrect localized timestamps. When the browser language setting was not set to English, Japanese localized timestamps were displayed.
Released 23 August 2018
Pseudo-translation library. The pseudo translation library was enabled in error.
Released 22 August 2018
Privilege escalation for SSH credentials. SSH credentials for the root account are required to run tasks on a target hosts, whether installing a Puppet agent or managing a system service. When adding SSH credentials, the option to escalate
non-rootuser account privileges to
rootis available. See Adding host credentials.
Discovery and tasks scopes support per host credential. When adding host credentials, each SSH and WinRM credential can be assigned both the discover data on hosts scope, and the run tasks on targets hosts scope. See Adding host credentials.
TLS server certificate generation. Puppet Discovery generates a new TLS server certificate during each installation and during a reset.
Extended session security flag not sent in request headers. When strict NTLM server versions were enabled, WinRM requests failed due to the extended session security flag not being sent in request headers. The correct NTLM flags are now set to support extended session security.
Released 25 July 2018
New in this release:
OS family of unsupported operating systems. When Puppet Discovery authenticates with hosts running unsupported operating systems, it discovers the OS family of each operating system. For a list of supported operating systems to discover data on, see System requirements.
Double quotes displayed in the operating system value for Ubuntu 14. On the hosts list page, the operating system value for Ubuntu 14 displayed leading doube quotes.
Inconsistent highlighting displayed in the select task menu. On the Select a task page, the mouse over highlight did not display when selecting the first task option in the list.
SSH connections to upsupported AIX hosts did not terminate cleanly. SSH connections to unsupported AIX hosts did not terminate cleanly and left zombie processes running.
Blocked SSH connections did not timeout. Blocked SSH connections did not time out or terminate the connection.
Puppet Discovery exercised the halt service on Cisco virtual machines. During a discovery run, the halt service was inadvertently exercised on Cisco virtual machines resulting in shutdowns.
Leading digits in the bar chart y-axis were truncated. On the Puppet Discovery dashboard, numbers displayed on the bar chart y-axis were slightly truncated.
Released 2 July 2018
Authentication options for WinRM credentials. To address CVE-2018-11746, Puppet Discovery uses NTLM authentication over HTTPS. When adding your WinRM credentials, you can now enable a fallback to use NTLM authentication over HTTP. The fallback occurs when the default NTLM authentication over HTTPS fails. To enable this option, see WinRM credentials.
Inconsistent number of facets returned during discovery. A race condition introduced as part of the 1.1.0 release, meant that an inconsistent number of facets were returned during a discovery run.
When a parent path was not set on a facet, the edge stopped working. When no parent path was set on the facet produced by the provider, the edge stopped working.
CLI didn't use the environment proxy. The CLI did not use the
http_proxyenvironment variable, resulting in failures when starting or updating Puppet Discovery. This release fixes this issue. The
no_proxyenvironment variables are now used during each CLI HTTP request.
Hostname and IP address were not displayed in the pd_edge log. The pd_edge error log did not display a hostname or an IP address.
When host credentials were not entered, requests for each facet continued. When no host credentials were entered, the request to the provider for the initial facet resulted in an error message. Discovery continued to send requests to the same provider for subsequent facets, resulting in multiple error messages.
Google Cloud Platform source could not be added when using Firefox version 60.0.2. When using Firefox 60.0.2, the Google Cloud Platform source could not be added during the first time user flow.
The availability zone rather than the region was displayed for Amazon Web Services sources. The Amazon Web Services provider was reporting the availability zone rather than the region.
CLI commands failed for users with no internet access. The
versionCLI commands failed for users with no internet access. This was due to Puppet Discovery automatically checking for an updated version when running each command.
Source name was missing in the activity feed table. In some instances, the source name was not populated in the activity feed table.
Released 30 May 2018
WinRM required unencrypted and basic auth configuration settings. WinRM connections over HTTPS were previously not supported.
No notification for Windows users to enable Linux containers. Windows users were not notified to enable Linux containers for their docker daemon.
Using escalated privileges for non-root users, Discovery didn't automatically retry failed task runs. Task runs were failing due to Discovery not automatically escalating non-root credentials to root privileges.
Expired bearer tokens didn't refresh. When the user's bearer token expired, the user interface didn't request a new bearer token.
Windows discovery returns all group objects in the entire domain. When ran on a domain controller, the Windows discovery command to enumerate groups returns every group object in the entire domain.
Windows discovery returns all user objects in the entire domain. When ran on a domain controller, the Windows discovery command to enumerate users returns every user object in the entire domain.
WinRM discovery keeps TCP connections alive. After each activity, WinRM connections are kept open for 2 minutes. During this time, TCP keepalives are sent each second causing excessive network traffic.
Released 14 May 2018
Filter was ignored when running a task. When Select all was applied to the list of available hosts or credentials to run a task on, the user defined filter was ignored. This resulted in a large number of hosts and credentials being inadvertently selected to run the task on. This release fixes this issue.
Released 8 May 2018
This is the initial release of Puppet Discovery.