search

openshift / assisted-installer

Apache License 2.0
69 stars 98 forks source link

serious bug with SNO? #349

Closed hetzbh closed 2 years ago

hetzbh commented 3 years ago

Hi, I've reinstalled SNO on a VM today from scratch. Installation went without a problem.

However, I see 2 weird things compared to yesterday:

  1. When trying to deploy any sample app (sample Python basic for example), I get the following in the log stream:

    Cloning "https://github.com/elsony/devfile-sample-python-basic.git" ...
error: fatal: unable to access 'https://github.com/elsony/devfile-sample-python-basic.git/': SSL certificate problem: self signed certificate in certificate chain

  2. Clicking on "add" and selecting "All services" - I only get 4 services (Basic NodeJS, Basic Python, Basic Quarkus, Basic Spring boot) and only Devfile type. There are no other items in the catalog.

Should I open a bug in BZ about it?

eranco74 commented 3 years ago

Unsure what went wrong, I just tried it myself and it seems to be working. I see 14 sample apps, and the python-basic example is running: Build log:

 Cloning "https://github.com/elsony/devfile-sample-python-basic.git" ...
    Commit: de421f7a7fdcde306415a71ed7d719fb0f7bf8ee (Optimze build)
    Author: eyuen <eyuen@redhat.com>
    Date:   Fri Apr 30 15:30:14 2021 -0400
time="2021-09-09T13:22:44Z" level=info msg="Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled"
I0909 13:22:44.226242       1 defaults.go:102] Defaulting to storage driver "overlay" with options [mountopt=metacopy=on].
Caching blobs under "/var/cache/blobs".

Pulling image python:slim ...

Successfully pushed image-registry.openshift-image-registry.svc:5000/new/python-basic@sha256:ca028d9efb88e3e189e3ad28bf15ab0e2a0e0188ded6853092203c01c7b9492d
Push successful

Pod logs: INFO:waitress:Serving on http://0.0.0.0:8081

openshift-bot commented 2 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 2 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 2 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci[bot] commented 2 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/assisted-installer/issues/349#issuecomment-1030870442): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.