Description of problem: If upgrading to the newest version of Node fails, the LV created to hold the new layer is left on the system. This means that subsequent updates may fail (either because the new LV already exists, or because /etc remediation may copy problematic files from /etc to a newer layer) Version-Release number of selected component (if applicable): Any How reproducible: 100% Steps to Reproduce: 1. Fail an upgrade to a newer version of Node (unmounted but extant /var/crash, for example) Actual results: The new LV is present Expected results: The new LV should be removed on failure Additional info:
Verified Steps: 1. fresh install rhvh-4.2.3-20180531 2. umount /var/crash 3. upgrade to rhvh-4.2-20180815.0 4. upgrade failed Actual results: The new LV should be removed on failure # imgbase w You are on rhvh-4.2.3.1-0.20180531.0+1
(In reply to Ryan Barry from comment #0) > Description of problem: > If upgrading to the newest version of Node fails, the LV created to hold the > new layer is left on the system. > > This means that subsequent updates may fail (either because the new LV > already exists, or because /etc remediation may copy problematic files from > /etc https://bloxdio2.com to a newer layer) > > Version-Release number of selected component (if applicable): > Any > > How reproducible: > 100% > > Steps to Reproduce: > 1. Fail an upgrade to a newer version of Node (unmounted but extant > /var/crash, for example) > > Actual results: > The new LV is present > > Expected results: > The new LV should be removed on failure > > Additional info: Have this bug solved?