Adds bugs to 3.10 release notes (#844)

Co-authored-by: Steven Smith <[email protected]>

modules/attributes.adoc

@@ -35,7 +35,7 @@ ifeval::["{productname}" == "Red Hat Quay"]
 :clairnewver: v3.8
 :quayimage: quay-rhel8
 :clairimage: clair-rhel8
-:clairproductminv: 4.9.0
+:clairproductminv: 4.7.2
 :builderimage: quay-builder-rhel8
 :builderqemuimage: quay-builder-qemu-rhcos
 :postgresimage: registry.redhat.io/rhel8/postgresql-13:1-109

modules/disabling-robot-account.adoc

@@ -118,5 +118,6 @@ $ podman login -u="<organization-name/username>+<robot-name>" -p="KETJ6VN0WT8YLL
 +
 [source,terminal]
 ----
-DEBU[0000] error logging into "quay-server.example.com": unable to retrieve auth token: invalid username/password: unauthorized: Robot accounts have been disabled. Please contact your administrator. 
+...
+DEBU[0000] error logging into "quay-server.example.com": unable to retrieve auth token: invalid username/password: unauthorized: Robot accounts have been disabled. Please contact your administrator.
 ----

modules/managing-namespace-auto-pruning-policies.adoc

@@ -2,7 +2,7 @@
 [id="managing-namespace-auto-pruning-policies"]
 = Managing namespace auto-pruning policies using the {productname} UI
 
-Namespace auto-pruning policies are created using the {productname} UI v2. This can be done after you have configured your {productname} `config.yaml` file to enable the auto-pruning feature.
+Namespace auto-pruning policies are created using the {productname} UI v2. This can be done after you have configured your {productname} `config.yaml` file to enable the auto-pruning feature and the v2 UI.
 
 [NOTE]
 ====
@@ -14,14 +14,18 @@ This feature is not available when using the {productname} legacy UI.
 
 Use the following procedure to configure your {productname} `config.yaml` file to enable the namespace auto-pruning feature.
 
+.Prerequisites 
+
+* You have set `FEATURE_UI_V2` to `true` in your `config.yaml` file.
+
 .Procedure 
 
 * In your {productname} `config.yaml` file, add, and set, the `FEATURE_AUTO_PRUNE` environment variable to `True`. For example:
 +
 [source,yaml]
 ----
 # ...
-FEATURE_AUTO_PRUNE: True
+FEATURE_AUTO_PRUNE: true
 # ...
 ----
 
@@ -36,7 +40,7 @@ Use the following procedure to create an auto-prune policy using the {productnam
 
 .Procedure 
 
-. Tag three sample images, for example, `busybox`, that will be pushed to the repository with auto-pruning enabled. For example:
+. Tag four sample images, for example, `busybox`, that will be pushed to the repository with auto-pruning enabled. For example:
 +
 [source,terminal]
 ----
@@ -58,7 +62,7 @@ $ podman tag docker.io/library/busybox <quay-server.example.com>/<quayadmin>/bus
 $ podman tag docker.io/library/busybox <quay-server.example.com>/<quayadmin>/busybox:test4
 ----
 
-. Push the three sample images, for example, `busybox`, to the repository with auto-pruning enabled by entering the following commands:
+. Push the four sample images, for example, `busybox`, to the repository with auto-pruning enabled by entering the following commands:
 +
 [source,terminal]
 ----
@@ -77,7 +81,7 @@ $ podman push <quay-server.example.com>/<quayadmin>/busybox:test3
 +
 [source,terminal]
 ----
-sudo podman push --tls-verify=false <quay-server.example.com>/<quayadmin>/busybox:test4
+$ podman push <quay-server.example.com>/<quayadmin>/busybox:test4
 ----
 
 . Check that there are four tags in your repository. 

modules/red-hat-quay-namespace-auto-pruning-overview.adoc

@@ -12,7 +12,7 @@ Currently, two policies have been added:
 
 After tags are automatically pruned, they go into the {productname} time machine, or the  amount of time, after a tag is deleted, that the tag is accessible before being garbage collected. The expiration time of an image tag is dependent on your organization's settings. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/manage_red_hat_quay/index#garbage-collection[{productname} garbage collection]. 
 
-Users are only have to configure one policy per namespace; this can be done through the {productname} v2 UI. Policies can also be set by using the API endpoints through the command-line interface (CLI). 
+Users can only configure one policy per namespace; this can be done through the {productname} v2 UI. Policies can also be set by using the API endpoints through the command-line interface (CLI). 
 
 [id="prerequisites-limitations-namespace-autopruning"]
 == Prerequisites and limitations for namespace auto-pruning 

modules/rn_3_10_0.adoc

@@ -56,13 +56,13 @@ Alternatively, you can receive the following error if you try to create a robot
 ** Manage or create new team members
 ** Set repository permissions
 ** Search for specific teams 
-* * View teams, members of a team, or collaborators of a team 
+** View teams, members of a team, or collaborators of a team 
 
 * With this update, a *Default permissions* page has be been added to the v2 UI. This page allows {productname} administrators to set repository permissions. 
 
 * With this update, a *Tag History* page has been added to the v2 UI. Additionally, {productname} administrators can add and manage labels for repositories, and set expiration dates for specified tags in a repository. 
 
-For more information on accessing these pages, or enabling these features, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/use_red_hat_quay/index#using-v2-ui[Using the {productname} v2 UI].
+For more information about navigating the v2 UI and enabling, or using, these features, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/use_red_hat_quay/index#using-v2-ui[Using the {productname} v2 UI].
 
 [id="clair-gc-manifests"]
 === Garbage collection of manifests for Clair
@@ -163,22 +163,22 @@ ROBOTS_WHITELIST:
 ----
 +
 For more information, see. . .
-
+////
 
 [id="bug-fixes-310"]
 == {productname} bug fixes
 
-* link:[*PROJQUAY-*]
-* link:[*PROJQUAY-*]
-* link:[*PROJQUAY-*]
-* link:[*PROJQUAY-*]
-* link:[*PROJQUAY-*]
-* link:[*PROJQUAY-*]
-* link:[*PROJQUAY-*]
-* link:[*PROJQUAY-*]
-* link:[*PROJQUAY-*]
-* link:[*PROJQUAY-*]
-////
+* link:https://issues.redhat.com/browse/PROJQUAY-6184[*PROJQUAY-6184*]. Add missing props for Create robot account modal
+* link:https://issues.redhat.com/browse/PROJQUAY-6048[*PROJQUAY-6048*]. Poor UI performance with quotas enabled
+* link:https://issues.redhat.com/browse/PROJQUAY-6010[*PROJQUAY-6010*]. Registry quota total worker fails to start due to import
+* link:https://issues.redhat.com/browse/PROJQUAY-5212[*PROJQUAY-5212*]. Quay 3.8.1 can't mirror OCI images from Docker Hub
+* link:https://issues.redhat.com/browse/PROJQUAY-2462[*PROJQUAY-2462*]. Consider changing the type of the removed_tag_expiration_s from integer to bigint
+* link:https://issues.redhat.com/browse/PROJQUAY-2803[*PROJQUAY-2803*]. Quay should notify Clair when manifests are garbage collected	
+* link:https://issues.redhat.com/browse/PROJQUAY-5598[*PROJQUAY-5598*]. Log auditing tries to write to the database in read-only mode	
+* link:https://issues.redhat.com/browse/PROJQUAY-4126[*PROJQUAY-4126*]. Clair database growing
+* link:https://issues.redhat.com/browse/PROJQUAY-5489[*PROJQUAY-5489*]. Pushing an artifact to Quay with oras binary results in a 502
+* link:https://issues.redhat.com/browse/PROJQUAY-3906[*PROJQUAY-3906*]. Quay can see the push image on Console after push image get error "Quota has been exceeded on namespace"
+* link:https://issues.redhat.com/browse/PROJQUAY-5137[*PROJQUAY-5137*]. 5137
 
 [id="quay-feature-tracker"]
 == {productname} feature tracker

modules/using-v2-ui.adoc

@@ -221,11 +221,11 @@ Use the following procedure to create a new team using the {productname} v2 UI.
 
 . Optional. You can click the one of the following options to reveal more information about teams, members, and collaborators: 
 
-* **Team View*. This menu shows all team names, the number of members, the number of repositories, and the role for each team.
+* **Team View**. This menu shows all team names, the number of members, the number of repositories, and the role for each team.
 
-* **Members View*. This menu shows all usernames of team members, the teams that they are part of, the repository permissions of the user.
+* **Members View**. This menu shows all usernames of team members, the teams that they are part of, the repository permissions of the user.
 
-* **Collaborators View*. This menu shows repository collaborators. Collaborators are users that do not belong to any team in the organization, but who have direct permissions on one or more repositories belonging to the organization.
+* **Collaborators View**. This menu shows repository collaborators. Collaborators are users that do not belong to any team in the organization, but who have direct permissions on one or more repositories belonging to the organization.
 
 [id="creating-robot-account-v2-ui"]
 === Creating a robot account using the {productname} v2 UI
@@ -310,15 +310,15 @@ Use the following procedure to create default permissions using the {productname
 .. If selecting *Anyone*, the following information must be provided:
 +
 * **Applied to**. Search, invite, or add a user/robot/team.
-* **Permission*. Set the permission to one of *Read*, *Write*, or *Admin*.
+* **Permission**. Set the permission to one of *Read*, *Write*, or *Admin*.
 
-.. If select *Specific user*, the following information must be provided:
+.. If selecting *Specific user*, the following information must be provided:
 +
 * **Repository creator**. Provide either a user or robot account. 
 * **Applied to**. Provide a username, robot account, or team name. 
-* **Permission*. Set the permission to one of *Read*, *Write*, or *Admin*.
+* **Permission**. Set the permission to one of *Read*, *Write*, or *Admin*.
 
-. Click *Create default permission*. A confirmation box appears, returning the following alert: *Successfully created default permission for creator:*.
+. Click *Create default permission*. A confirmation box appears, returning the following alert: *Successfully created default permission for creator*.
 
 [id="organization-settings-v2-ui"]
 === Organization settings for the {productname} v2 UI