Bug 1686151
| Summary: | Cannot update a blueprint component to the latest version | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Terry Bowling <tbowling> | ||||
| Component: | cockpit-composer | Assignee: | jgiardin <jgiardin> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Robert M Williams <rwilliam> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 7.6 | CC: | elpereir, mpitt, xiaofwan | ||||
| Target Milestone: | rc | Keywords: | Extras, Rebase | ||||
| Target Release: | 7.7 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
.Image Builder no longer fails to update a blueprint component to the last version
Previously, Image Builder failed to solve dependencies or create images after a local repository mirror was refreshed.As a consequence, it continued to show the old version of the blueprint components. This update, fixes the problem.
As a result, dependence solving and image composes succeed.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-08-06 17:31:45 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
Terry Bowling
2019-03-06 20:14:32 UTC
Created attachment 1541591 [details]
SAP-HANA-Bare-Metal.toml
SAP-HANA-Bare-Metal.toml for reproducer
This issue should be addressed as part of cockpit-composer 0.1.8 (see description on Releases page: https://github.com/weldr/welder-web/releases. Verified on cockpit-composer v4. Hello, does this Bugzilla could be considered a release note candidates for 7.7? If it does, could you, please, review the Doc Text field or provide the initial content in the feature-reason-result format, so it can be used as the basis for the description. Many thanks in advance 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/RHBA-2019:2388 |