overcloud plan container collides with current upload artifacts location

Bug #1620384 reported by Steven Hardy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Steven Hardy

Bug Description

When you use DeployArtifacts, the scripts provided in tripleo-common default to an "overcloud" container to store the tarball:

$ cat ~/.tripleo/environments/puppet-modules-url.yaml
# Heat environment to deploy artifacts via Swift Temp URL(s)
parameter_defaults:
  DeployArtifactURLs:
    - 'http://192.0.2.1:8080/v1/AUTH_36c25109478c4b5a9a159f45bb5edf00/overcloud/puppet-modules.tar.gz?temp_url_sig=6cf6da79bb81df8e34503c8b9fa4886787bebd58&temp_url_expires=1504630707'

This is now deleted every time we delete the overcloud, which is a regression from an operator perspective as now you have to re-upload the tarball every deploy vs only when it changes.

I guess we need to modify the container name in the tripleo-common scripts

Steven Hardy (shardy)
Changed in tripleo:
milestone: none → newton-rc1
status: New → Triaged
importance: Undecided → High
Steven Hardy (shardy)
Changed in tripleo:
assignee: nobody → Steven Hardy (shardy)
Changed in tripleo:
milestone: newton-rc1 → newton-rc2
Revision history for this message
Steven Hardy (shardy) wrote :
Changed in tripleo:
status: Triaged → Fix Released
milestone: newton-rc2 → newton-rc1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.