[
https://issues.jboss.org/browse/JBIDE-20257?page=com.atlassian.jira.plugi...
]
Marián Labuda edited comment on JBIDE-20257 at 7/15/15 3:26 AM:
----------------------------------------------------------------
Yeah, this results in same behaviour. It's also non possible to create a new project
via this way from CLI. So the CLI command "oc new-project projectName" do
workaround to achieve creation of a new project?
the JSON should be following (with correct syntax):
{code}
{
"kind": "Project",
"apiVersion": "v1",
"metadata": {
"name": "test"
}
}
{code}
[~jcantrill] and according to cluster scope. That's scope of a super user. Is there
any way to modify json, which is provided to OpenShift server to create a new project, to
be having specified scope, to successfully create a new project? Otherwise I am afraid
Manage Projects is not much of use for us beyond deleting projects.
was (Author: mlabuda):
Yeah, this results in same behaviour. It's also non possible to create a new project
via this way from CLI. So the CLI command "oc new-project projectName" do
workaround to achieve creation of a new project?
the JSON should be following (with correct syntax):
{code}
{
"kind": "Project",
"apiVersion": "v1",
"metadata": {
"name": "test"
}
}
{code}
Cannot create any new project via OpenShift Projects dialog
-----------------------------------------------------------
Key: JBIDE-20257
URL:
https://issues.jboss.org/browse/JBIDE-20257
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta2
Reporter: Marián Labuda
Assignee: Jeff Cantrill
Priority: Blocker
Fix For: 4.3.0.Beta2
In OpenShift Projects dialog opened via context menu of a v3 application, it is not
possible to create a new project. There is a error that project is trying to be created in
cluster scope. See full error description below:
{code}
Could not create project "project01dsa": User "demo" cannot create
projects at the cluster scope
com.openshift.restclient.authorization.ResourceForbiddenException: User "demo"
cannot create projects at the cluster scope
at
com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:393)
at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:185)
at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:169)
at
org.jboss.tools.openshift.core.connection.Connection.createResource(Connection.java:316)
at
org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizardModel.createProject(NewProjectWizardModel.java:55)
at
org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:46)
at
org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
This is happening also on locally running OpenShift v3 and also on staging v3 server.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)