Skip to content
This repository has been archived by the owner on Feb 11, 2020. It is now read-only.

task failure import-opsmgr-settings #384

Closed
sonmacharius opened this issue Feb 11, 2019 · 5 comments
Closed

task failure import-opsmgr-settings #384

sonmacharius opened this issue Feb 11, 2019 · 5 comments

Comments

@sonmacharius
Copy link

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
Copy link

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
Copy link

nebhale commented Mar 1, 2019

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

@jtarchie
Copy link
Contributor

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
Copy link
Contributor

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}"

jpmcb pushed a commit that referenced this issue May 24, 2019
…psman-settings does not fail #384

Signed-off-by: Kira Boyle <[email protected]>
@kcboyle
Copy link
Contributor

kcboyle commented May 24, 2019

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants