Bug 1751245
Summary: | [Scale Up] ERROR configuring crond | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | mlammon | ||||
Component: | openstack-tripleo-heat-templates | Assignee: | Emilien Macchi <emacchi> | ||||
Status: | CLOSED ERRATA | QA Contact: | Sasha Smolyak <ssmolyak> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | urgent | ||||||
Version: | 15.0 (Stein) | CC: | apevec, aschultz, bfournie, emacchi, jcoufal, lhh, mburns, michele, ohochman, ramishra, scorcora, shdunne, ssmolyak | ||||
Target Milestone: | rc | Keywords: | Regression, TestBlocker, Triaged | ||||
Target Release: | 15.0 (Stein) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | openstack-tripleo-heat-templates-10.6.1-0.20190909163923.999c846.el8ost | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-09-21 11:24:31 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: | |||||||
Attachments: |
|
Description
mlammon
2019-09-11 13:55:11 UTC
Created attachment 1614110 [details]
overcloud_scale_up_log
what version of podman are you running on the overcloud? [stack@undercloud-0 ~]$ sudo podman --version podman version 1.0.5 I asked on the overcloud nodes, not the undercloud. Please close the bug if you're not using podman version 1.0.5 on the overcloud nodes (again not the undercloud). Apologies, I misread I checked controller node and its 1.0.5 [root@controller-0 ~]# podman -version podman version 1.0.5 Seems that the log message - "run failed after error creating container storage: the container name \"container-puppet-crond\" is already in use by \"de08e0f99bc58991787b216c70ab2171bf56095dc92e6607ccef5002119ed6e9\" " is showing the same issue with container storage leakage as https://bugzilla.redhat.com/show_bug.cgi?id=1747885#c8 (and https://github.com/containers/libpod/issues/3906 as Emilien indicated). Even with podman 1.0.5, which adds the "podman rm --storage" command, don't you have to run that command to mitigate this issue? What openstack-tripleo-heat-templates build were you using? I tested OSP15 scale out withhttps://review.opendev.org/#/c/680623 and it passed. I hit the selinux bug trying to test this one https://bugzilla.redhat.com/show_bug.cgi?id=1751300 I will need to re-test with compose which fixes 1751300 Mistral log is clear after scale up, scale up passed, no errors of crond or any other. Verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:2811 |