search

vmware-archive / pcf-pipelines

PCF Pipelines
Apache License 2.0
158 stars 282 forks source link

task failure import-opsmgr-settings #384

Closed sonmacharius closed 5 years ago

sonmacharius commented 5 years ago

https://github.com/pivotal-cf/pcf-pipelines/blob/40733516f1e961ea5768d7fae1be4a029fda6764/tasks/import-opsmgr-settings/task.sh#L35

--decryption-passphrase "${OPSMAN_PASSPHRASE}" needs to be put in front of import-installation for the om-linux command to execute properly or you will get

could not execute "import-installation": the global decryption-passphrase argument is required for this command

suggest moving line 35 before 33.

cf-gitbot commented 5 years ago

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

nebhale commented 5 years ago

Note that this is the same bug as is PR'd in #376.

jtarchie commented 5 years ago

This is not the same issue as the PR #376. The proposed solution in the PR will not work for the version of om that is currently installed on the docker image.

The issue that this person is experiencing is an issue with om. It has a second issue reported on om.

jtarchie commented 5 years ago

The change that needs to be made to the task.

@@ -31,8 +31,8 @@ function main() {
       --skip-ssl-validation \
       --request-timeout 86400 \
       import-installation \
-      --installation "${cwd}/opsmgr-settings/${OPSMAN_SETTINGS_FILENAME}" \
-      --decryption-passphrase "${OPSMAN_PASSPHRASE}"
+      --decryption-passphrase "${OPSMAN_PASSPHRASE}" \
+      --installation "${cwd}/opsmgr-settings/${OPSMAN_SETTINGS_FILENAME}"
  }

  main "${PWD}"
kcboyle commented 5 years ago

This is being fixed because this is a breaking change for current pipelines.

This will be included in the next (last) release of pcf-pipelines. This feature has not been tested by CI, nor will it be. Use this commit and the corresponding release at your own risk.

In the future, please use platform-automation for all your automation needs. Pivotal Documentation