-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
podman PullImage varlink API broken on fedora-29 when the tag specified does not exist #11579
Comments
verify/fedora-29
First occurrence: 2019-04-12T09:07:43.341705 | revision 4c82e3f, logs
First occurrence: 2019-04-15T17:25:46.174671 | revision 1f8ac89
First occurrence: 2019-04-15T19:22:12.487990 | revision 1b90047, logs
First occurrence: 2019-04-15T22:24:12.777459 | revision f1a141f, logs
First occurrence: 2019-04-16T04:16:39.459613 | revision 1f8ac89
First occurrence: 2019-04-16T16:55:04.447456 | revision 294a6d2, logs
First occurrence: 2019-04-16T17:22:29.825632 | revision 0328160, logs
First occurrence: 2019-04-16T18:08:03.888654 | revision 24323f9
First occurrence: 2019-04-16T19:30:50.750944 | revision 8ea303d
First occurrence: 2019-06-11T13:26:38.377037 | revision ed31c98
|
…xisting tag testDownloadImage sometimes fails, because the podman crash causes the UI to get reloaded, causing the expected elements to not be present. However we only check the journal messages for coredumps only for sucessfull tests, so we don't catch the podman crash in this case. Add this second naughty for cockpit-project#11579 which will cover the above mentioned scenario. Known issue cockpit-project#11579
…xisting tag testDownloadImage sometimes fails, because the podman crash causes the UI to get reloaded, causing the expected elements to not be present. However we only check the journal messages for coredumps only for sucessfull tests, so we don't catch the podman crash in this case. Add this second naughty for #11579 which will cover the above mentioned scenario. Known issue #11579 Closes #11622
…xisting tag testDownloadImage sometimes fails, because the podman crash causes the UI to get reloaded, causing the expected elements to not be present. However we only check the journal messages for coredumps only for sucessfull tests, so we don't catch the podman crash in this case. Add this second naughty for cockpit-project#11579 which will cover the above mentioned scenario. Known issue cockpit-project#11579 Closes cockpit-project#11622
verify/fedora-30
First occurrence: 2019-04-19T22:13:04.884740 | revision 08739ac, logs
First occurrence: 2019-04-20T23:04:54.568776 | revision 1f22f53, logs
First occurrence: 2019-04-22T03:20:49.747623 | revision 919dbd4, logs
First occurrence: 2019-04-22T10:34:22.246512 | revision cd4e3ba, logs
First occurrence: 2019-04-22T19:33:35.327518 | revision 9de4d29, logs
First occurrence: 2019-04-22T20:25:00.513920 | revision 35280a3ede517de5359320d5d461e84d1dbd03d7, logs
First occurrence: 2019-04-22T20:53:44.082658 | revision d9d457a, logs
First occurrence: 2019-04-23T20:44:29.540312 | revision 9af9b58fbe2ef5dc6b133944fb1fc43697ab4196, logs
First occurrence: 2019-04-23T21:16:57.039633 | revision 9af9b58fbe2ef5dc6b133944fb1fc43697ab4196, logs
First occurrence: 2019-06-23T14:18:44.539687 | revision dd9341e
|
Issue in libpod project: containers/podman#2860
The text was updated successfully, but these errors were encountered: