odo project create stuck inconsistently

Created on 9 May 2019  ·  15Comments  ·  Source: openshift/odo

[kind/bug]

What versions of software are you using?

  • Operating System: macOS
  • Output of odo version: master

How did you run odo exactly?

$odo login -u <username> -p <password>
$ odo project create test1 -w
 ◐  Waiting for project to come up

Actual behavior

$odo login -u <username> -p <password>
✓  Login successful.

You have access to the following projects and can switch between them with 'odo project <project-name>':

  * default
    kube-public
    kube-system
    myproject
[...]

$ odo project create test1 -w
 ◐  Waiting for project to come up

Expected behavior

Should not stuck

Any logs, error output, etc?

kinbug prioritHigh

All 15 comments

/kind bug

@kadel @mohammedzee1000 Can you please check on your aws cluster

oc i am using:

$ oc version
Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.0+21f1917-94-dirty", GitCommit:"21f1917", GitTreeState:"dirty", BuildDate:"2019-05-08T04:30:13Z", GoVersion:"go1.11.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+21f1917", GitCommit:"21f1917", GitTreeState:"clean", BuildDate:"2019-05-08T04:27:15Z", GoVersion:"go1.11.8", Compiler:"gc", Platform:"linux/amd64"}

I can also see the same issue on 3.11 too

------------------------------
odoCmpSubE2e Test odo push with --source and --config flags when using project flag(--project) and current directory 
  create local nodejs component and push source and code separately
  /home/travis/gopath/src/github.com/openshift/odo/tests/integration/component.go:134
Created dir: /tmp/332880534
Creating a new project: gkhmzeodob
Running odo with args: [project create gkhmzeodob -w] 
[odo]  •  Waiting for project to come up  ...
Setting current dir to: 
Deleting project: kjddnulrrn
Running odo with args: [project delete kjddnulrrn -f] 
[odo]  ✗  The project kjddnulrrn does not exist. Please check the list of projects using `odo project list`
• Failure in Spec Setup (JustBeforeEach) [600.356 seconds]
odoCmpSubE2e
/home/travis/gopath/src/github.com/openshift/odo/tests/integration/cmp_sub_test.go:13
  Test odo push with --source and --config flags
  /home/travis/gopath/src/github.com/openshift/odo/tests/integration/component.go:112
    when using project flag(--project) and current directory
    /home/travis/gopath/src/github.com/openshift/odo/tests/integration/component.go:123
      create local nodejs component and push source and code separately [JustBeforeEach]
      /home/travis/gopath/src/github.com/openshift/odo/tests/integration/component.go:134
      Timed out after 600.000s.
      Expected process to exit.  It did not.
      /home/travis/gopath/src/github.com/openshift/odo/tests/helper/helper_run.go:29

Details log - https://travis-ci.org/openshift/odo/jobs/530179092

@amitkrout , working for me though

$ odo project create test1 -w
 ✓  Waiting for project to come up
 ✓  Project 'test1' is ready for use
 ✓  New project created and now using project : test1

maybe some flake

I saw it a couple of time also. There is definitely something fishy going on.

It is happening during odo project create and also in odo push during "Creating project ..." sometimes it hangs directly after this message.

It looks like it is something in project.Create function. It keeps waiting for the project even when it was already created (checked using oc)

/milestone 1.0

Found on travis too (oc 3.11.0) - https://travis-ci.org/openshift/odo/jobs/533311923

odo generic when .odoignore file exists 
  should be able to push changes while showing logging
  /home/travis/gopath/src/github.com/openshift/odo/tests/integration/generic_test.go:107
Creating a new project: lynepdgscs
Running odo with args: [project create lynepdgscs -w] 
[odo]  •  Waiting for project to come up  ...
Deleting project: fbyhalarqp
Running odo with args: [project delete fbyhalarqp -f] 
[odo]  ✗  The project fbyhalarqp does not exist. Please check the list of projects using `odo project list`

another occurrence on https://github.com/openshift/odo/pull/1741#issuecomment-493102041

------------------------------
odoWatchE2e when component is in the current directory when --project flag is used 
  odo watch fail when component not pushed
  /home/travis/gopath/src/github.com/openshift/odo/tests/integration/watch_test.go:54
Creating a new project: vjivqocqvj
Running odo with args: [project create vjivqocqvj -w] 
[odo]  •  Waiting for project to come up  ...
Deleting project: 
Running odo with args: [project delete  -f] 
[odo]  ✗  The project  does not exist. Please check the list of projects using `odo project list`
• Failure in Spec Setup (BeforeEach) [600.165 seconds]
odoWatchE2e
/home/travis/gopath/src/github.com/openshift/odo/tests/integration/watch_test.go:13
  when component is in the current directory [BeforeEach]
  /home/travis/gopath/src/github.com/openshift/odo/tests/integration/watch_test.go:39
    when --project flag is used
    /home/travis/gopath/src/github.com/openshift/odo/tests/integration/watch_test.go:53
      odo watch fail when component not pushed
      /home/travis/gopath/src/github.com/openshift/odo/tests/integration/watch_test.go:54
      Timed out after 600.000s.
      Expected process to exit.  It did not.
      /home/travis/gopath/src/github.com/openshift/odo/tests/helper/helper_run.go:29
------------------------------

/priority high
/priority-remove medium

@kadel , @amitkrout , it is hard to reproduce it locally, instead I would like to add -v 4 in all odo project create in tests to see how it is reacting ?
WDYT ?

only verbose flag was added in the PR https://github.com/openshift/odo/pull/1754/files
This is still an issue.

/reopen

@kadel: Reopened this issue.

In response to this:

only verbose flag was added in the PR https://github.com/openshift/odo/pull/1754/files
This is still an issue.

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kadel: Reopened this issue.

In response to this:

only verbose flag was added in the PR https://github.com/openshift/odo/pull/1754/files
This is still an issue.

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@surajnarwade i found the same failure one of my pr on trivis.

Running odo with args: [project create cgellxakwu -w -v4] 
[odo] I0528 09:34:13.961021   16958 preference.go:116] The configFile is /home/travis/.odo/config.yaml
[odo] I0528 09:34:13.961058   16958 occlient.go:452] Trying to connect to server 127.0.0.1:8443
[odo] I0528 09:34:13.961488   16958 occlient.go:459] Server https://127.0.0.1:8443 is up
[odo] I0528 09:34:13.978368   16958 occlient.go:382] isLoggedIn err:  <nil> 
[odo]  output: "developer"
[odo] I0528 09:34:13.978401   16958 context.go:342] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: context
[odo] I0528 09:34:13.978409   16958 context.go:342] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: context
[odo] I0528 09:34:13.978539   16958 context.go:342] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: project
[odo] I0528 09:34:13.978549   16958 context.go:342] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: app
[odo] I0528 09:34:13.978556   16958 context.go:342] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: project
[odo]  •  Waiting for project to come up  ...
[odo] I0528 09:34:13.986062   16958 context.go:342] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: app
[odo] I0528 09:34:13.986086   16958 context.go:342] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: output
[odo] I0528 09:34:13.986093   16958 context.go:342] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: component

This is getting more and more annoying? Do we have any clue what is happening there?

/assign
/unassign @surajnarwade

Was this page helpful?
0 / 5 - 0 ratings