Skip to content

Commit 4d2e5ac

Browse files
travisamartintravisamartin
authored
docs(nim): remove closed "Won’t Fix" issues from Known Issues (#1011)
1 parent d8738d3 commit 4d2e5ac

File tree

1 file changed

+0
-275
lines changed

1 file changed

+0
-275
lines changed

‎content/nim/releases/known-issues.md

Lines changed: 0 additions & 275 deletions
Original file line numberDiff line numberDiff line change
@@ -50,22 +50,6 @@ After the restart you will see the line “loading CVE data from file” in the
5050

5151
---
5252

53-
### {{% icon-bug %}} New warning message when no usage data or report is available {#46022}
54-
55-
{{<bootstrap-table "table table-striped table-bordered">}}
56-
| Issue ID | Status |
57-
|----------------|--------|
58-
| 46022 | Won't be resolved |
59-
{{</bootstrap-table>}}
60-
61-
#### Description
62-
63-
Users now see a warning message when they click the **Send Usage To F5** button if no new usage data or report is available. The message reads:
64-
65-
> "Usage data is not available at the moment. Please try submitting usage details again later."
66-
67-
---
68-
6953

7054
## 2.19.1
7155

@@ -457,44 +441,8 @@ The list of Threat Campaigns will disappear when scrolling down, preventing the
457441
#### Workaround
458442

459443
Threat Campaign versions can be published with the API using the route: `api/platform/v1/security/publish`
460-
461444
---
462445

463-
### {{% icon-bug %}} When upgrading to Instance Manager 2.10, there may be warnings from the Ingestion service {#42133}
464-
465-
{{<bootstrap-table "table table-striped table-bordered">}}
466-
467-
| Issue ID | Status |
468-
|----------------|--------|
469-
| 42133 | Won't be resolved |
470-
471-
{{</bootstrap-table>}}
472-
#### Description
473-
474-
When upgrading to 2.10 you may see a warning like the below message for the NGINX Management Suite Ingestion service. It can be safely ignored.
475-
476-
```none
477-
[WARN] #011/usr/bin/nms-ingestion #011start/start.go:497 #011error checking migrations Mismatched migration version for ClickHouse, expected 39 migrations to be applied, currently have only 44 migrations applied.
478-
```
479-
480-
---
481-
482-
### {{% icon-bug %}} When upgrading to Instance Manager 2.10, the API does not return lastDeploymentDetails for existing configurations {#42119}
483-
484-
{{<bootstrap-table "table table-striped table-bordered">}}
485-
486-
| Issue ID | Status |
487-
|----------------|--------|
488-
| 42119 | Won't be resolved |
489-
490-
{{</bootstrap-table>}}
491-
#### Description
492-
493-
After upgrading to Instance Manager 2.10, the API does not return lastDeploymentDetails for existing configuration blocks. This is then reflected as "Invalid Date" in the UI (See #42108).
494-
495-
#### Workaround
496-
497-
Republish the configuration for the affected configuration blocks.
498446

499447
---
500448

@@ -503,75 +451,11 @@ Republish the configuration for the affected configuration blocks.
503451

504452
November 17, 2022
505453

506-
### {{% icon-bug %}} App Protect Policies page fails when deployed via Helm chart {#38782}
507-
508-
{{<bootstrap-table "table table-striped table-bordered">}}
509-
510-
| Issue ID | Status |
511-
|----------------|--------|
512-
| 38782 | Won't be resolved |
513-
514-
{{</bootstrap-table>}}
515-
#### Description
516-
517-
When installing NGINX Instance Manager on Kubernetes via Helm Chart, the App Protect page shows an error banner, and no default policies are displayed.
518-
519-
---
520-
521-
### {{% icon-bug %}} Config deployment could fail when referencing remote cert inside allowed directories {#38596}
522-
523-
{{<bootstrap-table "table table-striped table-bordered">}}
524-
525-
| Issue ID | Status |
526-
|----------------|--------|
527-
| 38596 | Won't be resolved |
528-
529-
{{</bootstrap-table>}}
530-
#### Description
531-
532-
Deploying NGINX config with references to remote cert that resides in allowed directories could fail, with the following error:
533-
`BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory`.
534-
535-
This can also be diagnosed with log entries in `/var/log/nginx-agent/agent.log`, noting the removal of the referenced certificate.
536-
537-
#### Workaround
538-
539-
- Add the referenced cert to NMS as managed certificate and publish the config again.
540-
- Move the referenced remote certificate to a directory that's not in the allowed directory list.
541-
542454
---
543455

544-
### {{% icon-bug %}} Unreferenced NGINX App Protect policy file in /etc/nms {#38488}
545-
546-
{{<bootstrap-table "table table-striped table-bordered">}}
547-
548-
| Issue ID | Status |
549-
|----------------|--------|
550-
| 38488 | Won't be resolved |
551-
552-
{{</bootstrap-table>}}
553-
#### Description
554-
555-
When using NGINX Instance Manager with App Protect policies, previously referenced policies in the NGINX configuration may not be removed after they are no longer referenced in the NGINX config.
556-
557-
#### Workaround
558-
559-
Unreferenced policy files may be removed manually from /etc/nms.
560456

561457
---
562458

563-
### {{% icon-bug %}} HTTP version schema returns incorrect value in Advanced metrics module {#38041}
564-
565-
{{<bootstrap-table "table table-striped table-bordered">}}
566-
567-
| Issue ID | Status |
568-
|----------------|--------|
569-
| 38041 | Won't be resolved |
570-
571-
{{</bootstrap-table>}}
572-
#### Description
573-
574-
The values currently populated for http.version_schema are incorrect. The response is "4" for HTTP traffic and "6" for HTTPS traffic.
575459

576460
---
577461

@@ -600,50 +484,6 @@ For example, in the NGINX App Protect WAF JSON declarative policy, these referen
600484

601485
October 04, 2022
602486

603-
### {{% icon-bug %}} Aux data fails to upload if the size is greater than 3145728 characters {#37498}
604-
605-
{{<bootstrap-table "table table-striped table-bordered">}}
606-
607-
| Issue ID | Status |
608-
|----------------|--------|
609-
| 37498 | Won't be resolved |
610-
611-
{{</bootstrap-table>}}
612-
#### Description
613-
614-
Updating a config with an aux data file exceeding 3145728 characters fails with a validation error similar to the following example:
615-
616-
Request body has an error: doesn't match the schema: Error at "/auxFiles/files/3/contents": maximum string length is 3145728
617-
618-
---
619-
620-
### {{% icon-bug %}} "Deployment Not Found" error when publishing NGINX config to NATS server {#37437}
621-
622-
{{<bootstrap-table "table table-striped table-bordered">}}
623-
624-
| Issue ID | Status |
625-
|----------------|--------|
626-
| 37437 | Won't be resolved |
627-
628-
{{</bootstrap-table>}}
629-
#### Description
630-
631-
Occasionally, when publishing an NGINX config to a NATS server, the system returns a `Deployment Not Found` error, and the `nms.log` file includes the error `http failure with code '131043': <nil>`.
632-
633-
#### Workaround
634-
635-
Remove the existing NATs working directory and restart the NMS Data Plane Manager (`nms-dpm`) service as root.
636-
637-
{{< call-out "caution" >}}Restarting the `nms-dpm` service is disruptive and may result in the loss of event data. You should schedule a maintenance window for restarting the service.{{< /call-out >}}
638-
639-
```bash
640-
rm -rf /var/lib/nms/streaming
641-
systemctl restart nms-dpm
642-
```
643-
644-
---
645-
646-
647487
## 2.3.0
648488

649489
June 30, 2022
@@ -678,22 +518,6 @@ filterBy=<dimension-name>!= ''
678518
679519
May 25, 2022
680520
681-
### {{% icon-bug %}} Giving long names (255+ characters) to certificates causes internal error {#34185}
682-
683-
{{<bootstrap-table "table table-striped table-bordered">}}
684-
685-
| Issue ID | Status |
686-
|----------------|--------|
687-
| 34185 | Won't be resolved |
688-
689-
{{</bootstrap-table>}}
690-
#### Description
691-
692-
When adding certificates, an internal error (error code: 134018) is returned if the name given for the certificate exceeds 255 characters.
693-
694-
#### Workaround
695-
696-
Use a name that is 255 or fewer characters.
697521
698522
---
699523
@@ -702,71 +526,13 @@ Use a name that is 255 or fewer characters.
702526
703527
April 05, 2022
704528
705-
### {{% icon-bug %}} An unexpected number of instances are shown after upgrading nginx-agent to 2.1.0 {#33307}
706-
707-
{{<bootstrap-table "table table-striped table-bordered">}}
708-
709-
| Issue ID | Status |
710-
|----------------|--------|
711-
| 33307 | Won't be resolved |
712-
713-
{{</bootstrap-table>}}
714-
#### Description
715-
716-
After upgrading to NGINX Instance Manager 2.1.0, and updating nginx-agent from platform packaging, duplicate instances may appear on the Instance overview page. This issue is caused by a change in how the NGINX Agent generates the `system_uid`.
717-
718-
#### Workaround
719-
720-
You can safely delete the older entries or wait for them to expire.
721-
722-
---
723-
724-
### {{% icon-bug %}} “No such process” error occurs when publishing a configuration {#33160}
725-
726-
{{<bootstrap-table "table table-striped table-bordered">}}
727-
728-
| Issue ID | Status |
729-
|----------------|--------|
730-
| 33160 | Won't be resolved |
731-
732-
{{</bootstrap-table>}}
733-
#### Description
734-
735-
When publishing a configuration, you might encounter an error similar to the following example:
736-
737-
``` text
738-
config action failed: Config apply failed (write): no such process
739-
```
740-
741-
This error can occur when there is a desyncronization between the NGINX Agent and NGINX PID, often after manually restarting NGINX when the Agent is running.
742-
743-
#### Workaround
744-
745-
Restart the NGINX Agent:
746-
747-
``` bash
748-
sudo systemctl restart nginx-agent
749-
```
750-
751529
---
752530
753531
754532
## 2.0.0
755533
756534
December 21, 2021
757535
758-
### {{% icon-bug %}} NGINX App Protect WAF blocks NGINX Instance Manager from publishing configurations {#32718}
759-
760-
{{<bootstrap-table "table table-striped table-bordered">}}
761-
762-
| Issue ID | Status |
763-
|----------------|--------|
764-
| 32718 | Won't be resolved |
765-
766-
{{</bootstrap-table>}}
767-
#### Description
768-
769-
NGINX Instance Manager does not currently support managing NGINX App Protect WAF instances. NGINX App Protect WAF may block attempts to publish configurations to NGINX App Protect WAF instances.
770536
771537
---
772538
@@ -787,44 +553,3 @@ In the web interface, when uploading a config file that's larger than 50 MB (max
787553

788554
Keep config files under 50 MB.
789555

790-
---
791-
792-
### {{% icon-bug %}} CentOS 7, RHEL 7, and Amazon Linux 2 package managers allow unsupported NGINX/NGINX Plus versions {#28758}
793-
794-
{{<bootstrap-table "table table-striped table-bordered">}}
795-
796-
| Issue ID | Status |
797-
|----------------|--------|
798-
| 28758 | Won't be resolved |
799-
800-
{{</bootstrap-table>}}
801-
#### Description
802-
803-
When installing on CentOS 7, RHEL 7, and Amazon Linux 2, the package manager doesn't prevent installing NGINX Instance Manager with unsupported versions of NGINX or NGINX Plus. As a consequence, it is possible that `nms-instance-manager` is installed without an NGINX gateway. Resulting in a less than optimal experience.
804-
805-
#### Workaround
806-
807-
Install a supported version of NGINX (v1.18 or later) or NGINX Plus (R22 or later). See the [Technical Specifications]({{< ref "nim/fundamentals/tech-specs.md" >}}) guide for details.
808-
809-
---
810-
811-
### {{% icon-bug %}} gRPC errors occur when starting NGINX Instance Manager {#28683}
812-
813-
{{<bootstrap-table "table table-striped table-bordered">}}
814-
815-
| Issue ID | Status |
816-
|----------------|--------|
817-
| 28683 | Won't be resolved |
818-
819-
{{</bootstrap-table>}}
820-
#### Description
821-
822-
When starting NGINX Instance Manager, you may see errors similar to the following in `/etc/nginx/conf.d/nms-http.conf:227`:
823-
824-
```text
825-
nginx[1234]: nginx: [emerg] unknown directive "grpc_socket_keepalive"
826-
```
827-
828-
#### Workaround
829-
830-
Make sure your version of NGINX is v1.18 or later.

0 commit comments

Comments
 (0)