Bug 1300215

Summary: [fork][userinterface_public_576]Always show Creating on next step page
Product: OKD Reporter: Yadan Pei <yapei>
Component: Management ConsoleAssignee: bpeterse
Status: CLOSED CURRENTRELEASE QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.xCC: aos-bugs, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-12 17:11:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
CreatingOnNextStepPage
none
MessageOnOverviewPage
none
HTTPMessageError none

Description Yadan Pei 2016-01-20 09:51:20 UTC
Description of problem:
When create dc and hpa using a template includes different api groups, message "Creating <template_name> in project <project_name>" and "Creating" are always on the next step page. there is no helpful info on next page. When click project name it goes back to project overview, we could find resources are created successfully, but we can't clear the message on overview page
 
Version-Release number of selected component (if applicable):
fork_ami_openshift3_userinterface_public_576_177 

How reproducible:
Always

Steps to Reproduce:
1.cat test-template.yaml
kind: Template
apiVersion: v1
metadata:
  annotations:
    description: This example shows create HPA
    iconClass: icon-ruby
    tags: hpa
  creationTimestamp: null
  name: hpa-scale
objects:
- apiVersion: v1
  kind: DeploymentConfig
  metadata:
    labels:
      run: php-apache
    name: php-apache
  spec:
    replicas: 1
    selector:
      run: php-apache
    template:
      metadata:
        labels:
          run: php-apache
      spec:
        containers:
        - image: gcr.io/google_containers/hpa-example
          imagePullPolicy: IfNotPresent
          name: php-apache
          resources:
            requests:
              cpu: 200m
          securityContext:
            privileged: true
        restartPolicy: Always
        securityContext: {}
        terminationGracePeriodSeconds: 30
    triggers:
    - type: ConfigChange
- apiVersion: extensions/v1beta1
  kind: HorizontalPodAutoscaler
  metadata:
    name: php-apache
  spec:
    scaleRef:
      kind: DeploymentConfig
      name: php-apache
      subresource: scale
    minReplicas: 1
    maxReplicas: 10
    cpuUtilization:
      targetPercentage: 50
2.create template via CLI
# oc create -f test-template.yaml
template "hpa-scale" created
3. create hpa and dc from template on web console

Actual results:
"Creating" message are showing all the time, no other useful info, message on overview page could not be cleared(see attachment)

Expected results:
Should create dc and hpa successfully, show instructions of CLI and link to overview page

Additional info:
create resource from template via command line succeed
# oc create -f test-template.yaml
template "hpa-scale" created
# oc process hpa-scale | oc create -f -
deploymentconfig "php-apache" created
horizontalpodautoscaler "php-apache" created

Comment 1 Yadan Pei 2016-01-20 09:52:49 UTC
Created attachment 1116561 [details]
CreatingOnNextStepPage

Comment 2 Yadan Pei 2016-01-20 09:53:24 UTC
Created attachment 1116564 [details]
MessageOnOverviewPage

Comment 3 Yadan Pei 2016-01-20 10:00:47 UTC
Created attachment 1116568 [details]
HTTPMessageError

Comment 4 bpeterse 2016-01-22 18:53:59 UTC
I have not been able to reproduce this. Is there any missing information in your #3 creating hpa and dc from template on web console?  Please elaborate, thanks!

Comment 5 bpeterse 2016-01-22 20:37:30 UTC
needed to adjust to the following:
oc create -f test-template.yaml -n openshift 

to create the template in the openshift namespace.

Comment 6 bpeterse 2016-01-22 20:38:20 UTC
I believe this is resolved.  I will be creating a new fork_ami, comment will be on the trello card.

Comment 7 Yadan Pei 2016-01-24 12:14:43 UTC

(In reply to bpeterse from comment #5)
> needed to adjust to the following:
> oc create -f test-template.yaml -n openshift 
> 
> to create the template in the openshift namespace.

create template in other namespace also reproduce this issue, anyway since this has been resolved, I will verify in new fork_ami

Comment 8 Yadan Pei 2016-01-26 01:48:36 UTC
tested on fork_ami_openshift3_userinterface_public_576_193, resources in test-template.yaml are all created successfully