-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
devfile/devworkspace-operator
#1521Labels
area/devworkspace-operatorkind/bugOutline of a bug - must adhere to the bug report template.Outline of a bug - must adhere to the bug report template.
Description
Describe the bug
If I start two workspaces containing an endpoint with the same name, the dev workspace controller enters a loop. As a result, both namespaces do not start and remain stuck on "Preparing Service".
sample devfile
schemaVersion: 2.3.0
metadata:
name: endpoints-issue
components:
- name: tools
container:
image: quay.io/devfile/universal-developer-image:ubi8-latest
memoryRequest: 1G
memoryLimit: 4G
cpuRequest: '1'
cpuLimit: '2'
- name: data
volume:
size: 256Mi
- name: postgresql
container:
image: quay.io/fedora/postgresql-12:latest
cpuLimit: "1"
cpuRequest: 50m
memoryLimit: 512Mi
memoryRequest: 64Mi
endpoints:
- exposure: internal
targetPort: 5432
name: postgresql
protocol: tcp
attributes:
discoverable: true
env:
- name: POSTGRESQL_USER
value: user
- name: POSTGRESQL_PASSWORD
value: pass
- name: POSTGRESQL_ROOT_PASSWORD
value: root
- name: POSTGRESQL_DATABASE
value: db
volumeMounts:
- name: data
path: /var/lib/pgsql/dataChe version
7.93@latest
Steps to reproduce
- Create two workspaces with endpoints having the same name.
- Start both workspaces.
- Observe that the dev workspace controller goes into a loop and both namespaces remain stuck on "Preparing Service".
Expected behavior
Both workspaces should start without any issues
Runtime
OpenShift
Screenshots
Installation method
OperatorHub
Environment
other (please specify in additional context)
Eclipse Che Logs
No response
Additional context
Environment:
DevSpaces Version: 3.16.1
DevWorkspaces Operator Version: 0.30.2
Metadata
Metadata
Labels
area/devworkspace-operatorkind/bugOutline of a bug - must adhere to the bug report template.Outline of a bug - must adhere to the bug report template.
Type
Projects
Status
Ready for Review