Bug 2089675 - Could not move Serverless Service without Revision (or while starting?)
Summary: Could not move Serverless Service without Revision (or while starting?)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.11
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.11.0
Assignee: Jeff Phillips
QA Contact: spathak@redhat.com
URL:
Whiteboard:
: 2090193 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-24 08:38 UTC by Christoph Jerolimov
Modified: 2022-08-10 11:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:13:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
could-not-move-service.mp4 (5.54 MB, video/mp4)
2022-05-24 08:43 UTC, Christoph Jerolimov
no flags Details
could-move-service.mp4 (2.04 MB, video/mp4)
2022-05-24 08:44 UTC, Christoph Jerolimov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 11723 0 None open Bug 2089675: Fix for setting position of topology groups with no children 2022-06-16 19:10:55 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:13:54 UTC

Description Christoph Jerolimov 2022-05-24 08:38:27 UTC
Description of problem:
When the user imports a git repository and selects 'Serverless Service', it is impossible to move the Service while the Revision is not created (or it depends on another creating/starting state).

When the revision is created and loaded the Service can be moved again.

Version-Release number of selected component (if applicable):
4.11 (works fine in 4.10)

How reproducible:
Always

Steps to Reproduce:
1. Install OpenShift Serverless operator, create Serving CR
2. Import a component from git, select Serverless Service
3. On the topology try to move the new Serverless Service

Actual results:
I could not move it. After some seconds it's possible again.

Expected results:
Could move it after creating a new service.

Additional info:
Please checkout the recording, sometimes it also moves the wrong Service.

Comment 1 Christoph Jerolimov 2022-05-24 08:43:30 UTC
Created attachment 1882588 [details]
could-not-move-service.mp4

Comment 2 Christoph Jerolimov 2022-05-24 08:44:07 UTC
Created attachment 1882589 [details]
could-move-service.mp4

Comment 3 Jeff Phillips 2022-06-16 19:04:00 UTC
*** Bug 2090193 has been marked as a duplicate of this bug. ***

Comment 4 Christoph Jerolimov 2022-06-20 15:56:56 UTC
Verified on 4.11.0-0.nightly-2022-06-20-084444

Comment 7 errata-xmlrpc 2022-08-10 11:13:36 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069


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