Skip to content

Common mistakes during deployment

The following sections lists the common mistakes that might occur during deployment of an application.

For additional information, refer to FAQs.

Improper unzipping of "appbinary"

During deployment of an application, consider the following factors:

  • Unzip the "appbinary.zip" file correctly
  • The "path" parameter in the "manifest.yml" file should be as per the folder structure

For example, consider that the "fmtest-1.0.0.zip" file has been downloaded from Operator Cockpit. After unzipping the "fmtest-1.0.0.zip" file, the following files/folders are available:

  • appbinary.zip
  • manifest.yml
  • metadata.json
  • icon.png

Now, unzip the "appbinary.zip" file correctly. After unzipping, make sure that the "path" parameter in the "manifest.yml" file is updated to point to the correct file. For reference, see the following image:

Mainfest file

① Folder path

② Corresponding file path defined in "manifest"

Note

While executing the "cf push" command, the parameter "buildpack" will be automatically changed to "buildpacks" by Cloud Foundry.

Incorrect "manifest" file modifications

After unzipping "appbinary.zip", the following factors should be considered:

  • The "path" parameter in "manifest.yml" should point to the correct file/files.
  • Except for the corresponding files of the application, there should not be any other additional/duplicate files in the folder where the .zip file is extracted.

The following conditions should be met with respect to the parameter names in "manifest" and "metadata" files:

  • "appname" parameter in "manifest" file matches with the "componentname" parameter in "metadata" file.
  • "serviceInstanceName" in the "manifest" file matches with the "instancename" in "metadata" file.
  • For an application, the total number of components that are defined in "manifest.yml" and "metadata.json" files should match.

Last update: January 22, 2024