For more information, see " Enabling and scheduling maintenance mode." On an instance in a cluster configuration, when a site administrator sets maintenance mode on a single cluster node using ghe-maintenance -s, the utility warns the administrator to use ghe-cluster-maintenance -s to set maintenance mode on all of the clusters nodes. To avoid a failure during a configuration run on a cluster, validation of nf with the ghe-cluster-config-check utility ensures that the consul-datacenter field for each node matches the top-level primary-datacenter field. When the dependency submission API received a submission with one or more dependencies without a version, the dependency graph will now correctly report this fact. On an instance with a GitHub Advanced Security license, if code scanning had been used while running GitHub Enterprise Server 3.4 or earlier, a subsequent upgrade from 3.5 to 3.6 or 3.7 could fail when attempting to add a unique index to a database table.Īn enterprise owner could not enable two-factor authentication (2FA) for an instance if any enterprise owners had not enabled 2FA for their user accounts. The metrics included pre_oids, pre_oids, and. GitHub Enterprise Server published distribution metrics that cannot be processed by collectd. In some cases on an instance with multiple nodes, GitHub Enterprise Server erroneously stopped writing to replica fileservers, causing repository data to fall out of sync. The CSV reports for all users and all active users, available from the site admin dashboard, did not consider recent access using SSH or personal access tokens. On an instance with GitHub Actions enabled, if a user manually triggered a workflow using the REST API but did not specify values for optional booleans, the API failed to validate the request and returned a 422 error. If a repository contained a CODEOWNERS file with check annotations, pull requests "Files changed" tab returned a 500 error and displayed "Oops, something went wrong" in the "Unchanged files with check annotations" section. When a site administrator used ghe-migrator to migrate data to GitHub Enterprise Server, in some cases, nested team relationships would not persist after teams were imported. Responses from the /repositories REST API endpoint erroneously included deleted repositories. On instances configured to use the private beta of SCIM for GitHub Enterprise Server, users' authentication with SSH keys and personal access tokens failed due to an erroneous requirement for authorization.Īfter a user imported a repository with push protection enabled, the repository was not immediately visible in the security overview's "Security Coverage" view. On an instance in a cluster configuration, when a site administrator set maintenance mode using ghe-maintenance -s, a Permission denied error appeared when the utility tried to access /data/user/common/nf.ĭuring configuration of high availability, if a site administrator interrupted the ghe-repl-start utility, the utility erroneously reported that replication was configured, and the instance would not perform expected clean-up operations. ghe-repl-teardown now displays an informational alert and continues the teardown.Īfter an administrator used the /setup/api/start REST API endpoint to upload a license, the configuration run failed with a Connection refused error during the migrations phase. On an instance in a high availability configuration, if an administrator tore down replication from a replica node using ghe-repl-teardown immediately after running ghe-repl-setup, but before ghe-repl-start, an error indicated that the script cannot launch /usr/local/bin/ghe-single-config-apply - run is locked. In some cases, graphs on the Management Console's monitor dashboard failed to render. GitHub Actions ( actions) and Microsoft SQL ( mssql) did not appear in the list of processes within the instances monitor dashboard. In the Management Console's monitor dashboard, the Cached Requests and Served Requests graphs, which are retrieved by the git fetch catching command, did not display metrics for the instance.Īfter a site administrator exempted the user from rate limiting by using the ghe-config -limiting-exempt-users "github-actions" command, running ghe-config-check caused a Validation is-valid-characterset failed warning to appear. On an instance in a high availability configuration, a git push operation could fail if GitHub Enterprise Server was simultaneously creating the repository on a replica node. On an instance with GitHub Actions enabled, nested calls to reusable workflows within a reusable workflow job with a matrix correctly evaluate contexts within expressions, like strategy: $.
0 Comments
Leave a Reply. |