OCP 3.7 Release: Link Fixes

vikram-redhat · vikram-redhat · commit 662692262246 · 2017-11-28T22:28:05.000-05:00
Conflicts:
	install_config/revhistory_install_config.adoc
	release_notes/revhistory_release_notes.adoc
diff --git a/admin_guide/managing_networking.adoc b/admin_guide/managing_networking.adoc
@@ -1112,7 +1112,7 @@ port from pods in the *_same_* namespace, and connections on ports `80` and
 [[admin-guide-networking-networkpolicy-routers]]
 === NetworkPolicy and Routers
 
-When using the *ovs-multitenant* plugin, traffic from the xref:../architecture/topics/routers.adoc[routers] is automatically allowed into all namespaces. This is because the routers are
+When using the *ovs-multitenant* plugin, traffic from the routers is automatically allowed into all namespaces. This is because the routers are
 usually in the _default_ namespace, and all namespaces allow connections from
 pods in that namespace. With the *ovs-networkpolicy* plugin, this does not
 happen automatically. Therefore, if you have a policy that isolates a namespace
diff --git a/admin_guide/managing_projects.adoc b/admin_guide/managing_projects.adoc
@@ -32,8 +32,7 @@ command use this endpoint when a developer xref:../dev_guide/projects.adoc#dev-g
 === Modifying the Template for New Projects
 The API server automatically provisions projects based on the template that is
 identified by the `projectRequestTemplate` parameter of the
-xref:../install_config/master_node_configuration.adoc#master-node-config-project-config
-[*_master-config.yaml_* file]. If the parameter is not defined, the API server
+xref:../install_config/master_node_configuration.adoc#master-node-config-project-config[*_master-config.yaml_* file]. If the parameter is not defined, the API server
 creates a default template that creates a project with the requested name, and
 assigns the requesting user to the "admin" role for that project.
 
diff --git a/apb_devel/writing/getting_started.adoc b/apb_devel/writing/getting_started.adoc
@@ -17,7 +17,7 @@ toc::[]
 In this tutorial, you will walk through the creation of some sample Ansible
 Playbook Bundles (APBs). You will create actions for them to allow provision,
 deprovision, bind, and unbind. You can find more information about the design of
-APBs in the xref:../index.adoc#apb-devel-design[Design] topic. More in-depth
+APBs in the xref:../index.adoc#apb-devel-intro-design[Design] topic. More in-depth
 information about writing APBs is available in the
 xref:reference.adoc#apb-devel-writing-reference[Reference] topic.
 
diff --git a/apb_devel/writing/reference.adoc b/apb_devel/writing/reference.adoc
@@ -111,8 +111,7 @@ link:https://docs.docker.com/engine/reference/commandline/tag/#extended-descript
 |Boolean option of whether or not this APB can be bound to. Accepted fields are `true` or `false`.
 
 |`metadata`
-|Dictionary field declaring relevant metadata information. See
-xref:metadata[metadata] for details.
+|Dictionary field declaring relevant metadata information.
 
 |`plans`
 |A list of plans that can be deployed. See
diff --git a/architecture/networking/routes.adoc b/architecture/networking/routes.adoc
@@ -604,7 +604,7 @@ and "-". The default is the hashed internal key name for the route. |
 |`*haproxy.router.openshift.io/timeout*` | Sets a server-side timeout for the route. xref:time-units[(TimeUnits)] | `ROUTER_DEFAULT_SERVER_TIMEOUT`
 |`*router.openshift.io/haproxy.health.check.interval*`| Sets the interval for the back-end health checks. xref:time-units[(TimeUnits)] | `ROUTER_BACKEND_CHECK_INTERVAL`
 |`*haproxy.router.openshift.io/ip_whitelist*` | Sets a xref:whitelist[whitelist] for the route. |
-|`*haproxy.router.openshift.io/hsts_header*` | Sets a xref:hsts[Strict-Transport-Security] header for the edge terminated or re-encrypt route. |
+|`*haproxy.router.openshift.io/hsts_header*` | Sets a Strict-Transport-Security header for the edge terminated or re-encrypt route. |
 
 |===
 
diff --git a/architecture/service_catalog/ansible_service_broker.adoc b/architecture/service_catalog/ansible_service_broker.adoc
@@ -41,5 +41,5 @@ APBs use a simple directory with named playbooks to perform OSB API actions,
 such as provision and bind. Metadata defined in *_apb.yml_* spec file contains a
 list of required and optional parameters for use during deployment.
 
-See the xref:../../apb_devel/index.adoc#apb-devel-design[APB Development Guide]
+See the xref:../../apb_devel/index.adoc#apb-devel-intro-design[APB Development Guide]
 for details on the overall design and how APBs are written.
diff --git a/install_config/install/rpm_vs_containerized.adoc b/install_config/install/rpm_vs_containerized.adoc
@@ -62,7 +62,7 @@ For the advanced installation method, you can set the Ansible variable
 xref:../../install_config/install/advanced_install.adoc#configuring-ansible[inventory
 file] on a cluster-wide or per host basis.
 
-For the xref:../../install_config/install/disconnected_install.html[disconnected
+For the xref:../../install_config/install/disconnected_install.adoc#install-config-install-disconnected-install[disconnected
 installation method], to install the etcd container, you can set the Ansible
 variable `osm_etcd_image` to be the fully qualified name of the etcd image on
 your local registry, for example, `registry.example.com/rhel7/etcd`.
diff --git a/install_config/revhistory_install_config.adoc b/install_config/revhistory_install_config.adoc
@@ -6,4 +6,4 @@
 :icons:
 :experimental:
 
-// do-release: revhist-tables
+// do-release: revhist-tables
diff --git a/install_config/upgrading/automated_upgrades.adoc b/install_config/upgrading/automated_upgrades.adoc
@@ -208,7 +208,7 @@ start an upgrade.
 
 The quick installer supports upgrading between minor versions of {product-title}
 (one minor version at a time, e.g., 3.5 to 3.6) as well as between
-xref:../../release_notes/ocp_3_6_release_notes.adoc#ocp-36-asynchronous-errata-updates[asynchronous errata updates] within a minor version (e.g., 3.6.z).
+asynchronous errata updates within a minor version (e.g., 3.6.z).
 
 If you have an older format installation configuration file in
 *_~/.config/openshift/installer.cfg.yml_* from an installation of a previous
@@ -231,7 +231,7 @@ To start an upgrade with the quick installer:
 [NOTE]
 ====
 If the quick installer fails, note the error output and check
-xref:upgrading_known_issues.adoc#install-config-upgrading-known-issues[Known Issues] for any additional steps.
+Known Issues for any additional steps.
 ====
 
 include::install_config/upgrading/automated_upgrades.adoc[tag=automated_upgrade_after_reboot]
diff --git a/release_notes/ocp_3_7_release_notes.adoc b/release_notes/ocp_3_7_release_notes.adoc
@@ -912,9 +912,11 @@ You can also automate the configuration of the provider to point to multiple Ope
 [NOTE]
 ====
 The *_/tmp/cp.yml_* file requires some manual configurations to create and use
-it correctly. See
-xref:../install_config/cfme/container_provider.adoc#cfme-container-provider-multiple[Multiple
-Container Providers] for more information.
+it correctly. 
+
+//// Commenting out this section till CFME merges
+See Multiple Container Providers for more information.
+////
 ====
 
 [[ocp-37-diagnostics]]
@@ -1096,7 +1098,7 @@ metrics, and get alerts. Operators can see and query metrics and alerts on the
 Prometheus web dashboard, or bring their own Grafana and hook it up to
 Prometheus.
 
-See xref:../nstall_config/cluster_metrics.adoc#openshift-prometheus[Prometheus
+See xref:../install_config/cluster_metrics.adoc#openshift-prometheus[Prometheus
 on OpenShift] for more information.
 
 [[ocp-37-integrated-approach-to-adding-hosa]]
@@ -1406,7 +1408,7 @@ The {product-title} 3.7 documentation will be updated with more complete
 instructions on deploying CFME 4.6 after it has been released.
 
 [discrete]
-[[updated-installer-support-for-cfme]]
+[[node-authorizer-plugin]]
 === Node Authorizer and Admission Plug-in for Managing Node Permissions
 
 In {product-title} 3.7, the node authorizer and admission plug-in are used to
@@ -2762,7 +2764,7 @@ The following features that were formerly in Technology Preview from a previous
 - xref:../dev_guide/cron_jobs.adoc#dev-guide-cron-jobs[Cron Jobs (formerly called Scheduled Jobs)]
 - xref:../dev_guide/deployments/kubernetes_deployments.adoc#dev-guide-kubernetes-deployments-support[Kubernetes
 Deployments Support]
-- xref:../release_notes/ocp_3_5_release_notes.adoc#ocp-35-statefulsets[`StatefulSets`, formerly known as `PetSets`]
+- `StatefulSets`, formerly known as `PetSets`
 - xref:../admin_guide/quota.adoc#limited-resources-quota[Require Explicit Quota to Consume a Resource]
 - xref:../architecture/additional_concepts/storage.adoc#pv-mount-options[Mount Options]
 - xref:../install_config/install/advanced_install.adoc#advanced-install-configuring-system-containers[Installation of etcd, Docker Daemon, and Ansible Installer as System Containers]
diff --git a/release_notes/revhistory_release_notes.adoc b/release_notes/revhistory_release_notes.adoc
@@ -6,4 +6,4 @@
 :icons:
 :experimental:
 
-// do-release: revhist-tables
+// do-release: revhist-tables
diff --git a/rest_api/index.adoc b/rest_api/index.adoc
@@ -89,7 +89,7 @@ be created and deleted as needed with the appropriate role(s) assigned. See
 xref:../architecture/additional_concepts/authorization.adoc#roles[Authorization]
 in the Architecture documentation for a deeper discussion on roles.
 
-[[rest-api-examples]]
+[[rest-api-index-examples]]
 == Examples
 
 These examples provide a quick reference for making successful REST API calls.
