openshift-ansible: Upgrading from OCP 3.3 to 3.4 is missing latest ImageStreams/Templates

Description

After upgrading from 3.3 to 3.4 I was expecting to see the latest IS/Templates released in origin/ocp for php(7), mysql(5.7), ruby/etc/etc

Version

Please put the following version information in the code block indicated below.

  • Your ansible version per ansible --version

If you’re operating from a git clone:

  • The output of git describe

If you’re running from playbooks installed via RPM or atomic-openshift-utils

  • The output of rpm -q atomic-openshift-utils openshift-ansible

Place the output between the code block below:

root@osmaster0p:~:
----> ansible --version
ansible 2.2.0.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = Default w/o overrides

root@osmaster0p:~:
----> rpm -q atomic-openshift-utils openshift-ansible
atomic-openshift-utils-3.4.44-1.git.0.efa61c6.el7.noarch
openshift-ansible-3.4.44-1.git.0.efa61c6.el7.noarch
Steps To Reproduce
  1. upgrade from 3.3.* to 3.4.*
  2. look for latest IS that should be available
Expected Results

Describe what you expected to happen.

Example command and output or error messages
Observed Results

Describe what is actually happening.

Example command and output or error messages

For long output or logs, consider using a gist

Additional Information

Provide any additional information which may help us diagnose the issue.

  • Your operating system and version, ie: RHEL 7.2, Fedora 23 ($ cat /etc/redhat-release)
  • Your inventory file (especially any non-standard configuration parameters)
  • Sample code, etc
Rhel 7.3

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 19 (10 by maintainers)

Most upvoted comments

sure, a release note makes sense to warn people that some of the “latest” tags will be updated to point to new images and they should audit their resources for references to “latest” imagestreamtags.

and unfortunately there’s really nothing we can do about that at this point.

I think at least a Release Note is warranted here, as any application that was deployed pre 3.4 will truly be broken as far as mysql is concerned. We just experienced it by breaking authentication to our production cluster due to the SSO mysql DC getting 5.7 and mangling the data in it, said deployment is a 3.3.x deployment. again, mysql is the only one I can speak outright as it just bit me, but seeing as how there are quite a large number of templates, some sort of a note that changes are happening from :latest to specific version and how to upgrade a legacy DC seem like something to be included in the RN at least or Errata upgrade notes. simple oc edit dc/$somedc (search :latest and replace with current version) pre-upgrade of cluster would have solved the problem had we known it was coming.