Bug 1434430

Summary: Confusing warning with 2nd start of container with atomic run
Product: [Fedora] Fedora Reporter: Lukas Slebodnik <lslebodn>
Component: atomicAssignee: Brent Baude <bbaude>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: adimania, amurdaca, dwalsh, fkluknav, lsm5, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: atomic-1.16.5-1.fc26.x86_64 atomic-1.17.1-2.fc25 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-02 23:15:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lukas Slebodnik 2017-03-21 13:41:32 UTC 
Description of problem:
I saw following warning few times when I was executing my containers.
  The '$container_name' container is using an older version of the installed
  '$image_name' container image. If you wish to use the newer image,
  you must either create a new container with a new name or
  ...

Firstly, I thought that atomic was right but after some experiments I can
see such warning even with up to date image.

Version-Release number of selected component (if applicable):
sh$ rpm -q atomic
atomic-1.16.4-1.fc26.x86_64

How reproducible:
Deterministic

Steps to Reproduce:
1. //update image from registry
   docker pull docker.io/fedora:25
2. // run container for first time
   atomic run --name test fedora:25 bash
3. // start image for second time
   atomic run test

Actual results:
sh# atomic run test
The 'test' container is using an older version of the installed
'fedora:25' container image. If you wish to use the newer image,
you must either create a new container with a new name or
uninstall the 'test' container. 

# atomic uninstall --name test fedora:25

and create new container on the fedora:25 image.

# atomic update --force fedora:25s

 removes all containers based on an image.
[root@aed7601fb918 /]#

Expected results:
Shell is returned without any extra warnings
Comment 1 Brent Baude 2017-03-21 14:23:35 UTC 
PR generated -> https://github.com/projectatomic/atomic/pull/945
Comment 2 Fedora Update System 2017-04-20 18:53:04 UTC 
atomic-1.17.1-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e4b118174a
Comment 3 Fedora Update System 2017-04-23 17:20:40 UTC 
atomic-1.17.1-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e4b118174a
Comment 4 Fedora Update System 2017-04-24 15:17:01 UTC 
atomic-1.17.1-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-b9b0f308ed
Comment 5 Fedora Update System 2017-04-25 03:54:45 UTC 
atomic-1.17.1-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-b9b0f308ed
Comment 6 Fedora Update System 2017-05-02 23:15:26 UTC 
atomic-1.17.1-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.