You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On September 10th, 2018, we released a new version of Apigee Edge for Private Cloud.

> [!NOTE]
> For more information, see the following resources:
>
> - *[Edge for Private Cloud 4.17.09 documentation](https://docs.apigee.com/private-cloud/v4.17.09)*
> - *Questions or issues?* Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
> - *Release notifications* : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications)

## Update procedure

To update your installation, perform the following procedure on the Edge nodes:

1. **On all Edge nodes:**
   1. Clean Yum repos:  

      ```
      sudo yum clean all
      ```
   2. Update the Edge 4.17.09 `bootstrap_4.17.09.sh` file in "/tmp/bootstrap_4.17.09.sh":

      ```
      curl https://software.apigee.com/bootstrap_4.17.09.sh -o /tmp/bootstrap_4.17.09.sh
      ```
   3. Install the Edge 4.17.09 `apigee-service` utility and dependencies:

      ```
      sudo bash /tmp/bootstrap_4.17.09.sh apigeeuser=uName apigeepassword=pWord
      ```

      Where <var translate="no">uName:pWord</var> are the username and password you received from
      Apigee. If you omit <var translate="no">pWord</var>, you will be prompted to enter it.
   4. Update the `apigee-setup` utility:

      ```
      sudo /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
      ```
   5. Execute the contents of the `apigee-service.sh` file by using the `source` command:

      ```
      source /etc/profile.d/apigee-service.sh
      ```
2. On each of your qpid nodes, run the `update` utility:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c qpid -f config_file
   ```
3. On each of your Postgres nodes, run the `update` utility:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c ps -f config_file
   ```
4. On each of your BAAS usergrid nodes, run the `update` utility:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c b -f config_file
   ```

## Bugs fixed

The following table lists the bugs fixed in this release:

| Issue ID | Description | Build Number^\*^ |
|---|---|---|
| 67727814 | **Postgres upgrade failed on 4.17.09** | `apigee-postgresql-9.4.11-0.0.1135` |
| 72173268 | **Upgrade apigee-qpidd on CentOS 7.3 from 17.09 to 18.01 was failing** | `apigee-qpidd-4.17.09-0.0.856` |
| 72651279 | **Upgrade BaaS UI to use reCAPTCHA v2** | `apigee-tomcat-7.0.82-0.0.897 baas-sap-usergrid-2.2.0-0.0.380 baas-usergrid-2.2.0-0.0.37` |

### ^\*^About the build numbers

> [!NOTE]
> The **Build Number** column in the table specifies the earliest version of the component that contains the fix. Use that build number to determine if you already have the fix installed, or if you need to perform an update.
>
> To find out the build number of a currently installed component, use the
> `apigee-service` utility with the following syntax:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-service component version
> ```
>
> Where <var translate="no">component</var> is the name of the component without the build number extension.
> For example:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-service apigee-setup version
> ```
>
> You can get the build number of *all components* with the `apigee-all`
> utility:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-all version
> ```