Bug 1734687
| Summary: | 'pcs resource bundle reset' fails if existing port-map and storage-map ids are reused [rhel-7.7.z] | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | RAD team bot copy to z-stream <autobot-eus-copy> | ||||
| Component: | pcs | Assignee: | Ivan Devat <idevat> | ||||
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 7.7 | CC: | aherr, cfeist, cluster-maint, idevat, michele, mjuricek, mlisik, omular, tojeline | ||||
| Target Milestone: | rc | Keywords: | ZStream | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | pcs-0.9.167-3.el7_7.1 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1725849 | Environment: | |||||
| Last Closed: | 2019-09-03 17:41:39 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1725849 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
RAD team bot copy to z-stream
2019-07-31 08:17:48 UTC
Created attachment 1600639 [details]
proposed fix
After fix [kid76 ~] $ rpm -q pcs pcs-0.9.167-3.el7_7.1.x86_64 [kid76 ~] $ pcs resource bundle create B1 container docker image=pcs:new port-map id=PM1 range=4000-4400 storage-map id=SM1 source-dir=/tmp/a target-dir=/tmp/b [kid76 ~] $ pcs resource bundle reset B1 container image=pcs:new port-map id=PM1 range=4000-4400 storage-map id=SM1 source-dir=/tmp/a target-dir=/tmp/b [kid76 ~] $ echo $? 0 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:2604 |