Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1539308 - Delete project fail since could not find a service instance in dao
Delete project fail since could not find a service instance in dao
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.9.0
Unspecified Unspecified
high Severity high
: ---
: 3.9.0
Assigned To: Erik Nelson
Zhang Cheng
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-27 12:35 EST by Zhang Cheng
Modified: 2018-03-28 10:23 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-28 10:23:11 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 None None None 2018-03-28 10:23 EDT

  None (edit)
Comment 5 Zhang Cheng 2018-02-23 02:02:00 EST
Project can be deleted succeed by steps in description, and the unrelated and normal log have been lowered to Info:

[2018-02-23T05:55:58.922Z] [INFO] - Could not find a service instance in dao - 100: Key not found (/service_instance/af202c35-6dea-4e9d-8402-1ea9381445ca) [1194]

Verified in here. And opened another bug to trace "Zombie project issue - while delete a project that contain provision failed instance"
https://bugzilla.redhat.com/show_bug.cgi?id=1548311

Test Version:
ansible-service-broker: 1.1.13
APB registry using stage
Comment 8 errata-xmlrpc 2018-03-28 10:23:11 EDT
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-2018:0489

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