openshift/ci-chat-bot

password appears empty when cluster is not ready

sarroutbi opened this issue · 5 comments

From my perspective, it makes no sense to show this message:

image

It should only be shown once it is confirmed there is no error (cluster has been correctly launched). Otherwise, it can be confusing.

Hello. It appears that the main issue here is that the password is not set up correctly. The Cluster Bot sends the message as listed above when the cluster is ready, but the console (which is the web UI) is not. In these cases, the cluster should be ready to be interacted with via the oc tool, but not through a browser.

The password missing is a different issue that we should investigate. The cluster should always have a password by the time this message is sent.

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

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

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-bot: Closing this issue.

In response to this:

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.