RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1686151 - Cannot update a blueprint component to the latest version
Summary: Cannot update a blueprint component to the latest version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit-composer
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.7
Assignee: jgiardin
QA Contact: Robert M Williams
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-06 20:14 UTC by Terry Bowling
Modified: 2019-08-06 17:31 UTC (History)
3 users (show)

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.
Clone Of:
Environment:
Last Closed: 2019-08-06 17:31:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
SAP-HANA-Bare-Metal.toml (4.55 KB, text/plain)
2019-03-06 20:28 UTC, Terry Bowling
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2388 0 None None None 2019-08-06 17:31:47 UTC

Description Terry Bowling 2019-03-06 20:14:32 UTC
Description of problem:

After updating repositories, depsolving fails as described in bz1686146.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. follow steps in bz1686146

2. When I try to edit the blueprint via the Cockpit interface to tell it to manually update the package, it silently fails and continues to show the old version.

3. The only way to resolve it was to save the blueprint via the CLI, manually edit the toml file, and commit it back.  Then the blueprint was satisfied and would use the latest version.


Actual results:
depsolving and image composes fail


Expected results:

Additional info:

Comment 2 Terry Bowling 2019-03-06 20:28:01 UTC
Created attachment 1541591 [details]
SAP-HANA-Bare-Metal.toml

SAP-HANA-Bare-Metal.toml for reproducer

Comment 3 jgiardin 2019-03-18 16:59:55 UTC
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.

Comment 5 Xiaofeng Wang 2019-07-19 02:57:50 UTC
Verified on cockpit-composer v4.

Comment 7 Eliane Ramos Pereira 2019-08-06 09:44:15 UTC
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

Comment 8 errata-xmlrpc 2019-08-06 17:31:45 UTC
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


Note You need to log in before you can comment on or make changes to this bug.