syndesisio / syndesis

This project is archived. A flexible, customizable, open source platform that provides core integration capabilities as a service.
https://syndesis.io/
Apache License 2.0
597 stars 203 forks source link

Console URL doesn't seem to be correctly set when installed via 'syndesis install' #3076

Closed gashcrumb closed 3 years ago

gashcrumb commented 6 years ago

This is a...


[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Documentation issue or request

The problem

Seems like the 'open log in openshift' link and the 'logs' link don't work properly out of the box on openshift, with a little digging we found that the consoleUrl setting in the UI's config.json file seems to be empty or can often be the wrong URL.

Expected behavior

Ideally this URL should be set correctly when running syndesis install

@dhirajsb FYI

As a workaround this can be fixed by editing the syndesis-ui-config ConfigMap. Also with #3072 yarn start:minishift will set up the dev instance with the right console URL at least via minishift.

gashcrumb commented 6 years ago

Note in the consoleUrl you need to include /console as part of the URL as well, there's #2730 discussing the need for that.

phantomjinx commented 6 years ago

Current status of this is holding, pending an upstream exposure of the console url via their API. Until then, there is little reliable that can be accomplished. See this PR for more details.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

gashcrumb commented 5 years ago

https://github.com/openshift/origin/issues/20447#issuecomment-511042444

In our current architecture this would need to be re-exposed by the server in some fashion.

zregvart commented 5 years ago

@paoloantinori why is this a p0 now the issue has been open for a year unaddressed?

paoloantinori commented 5 years ago

Because it's still present and broken in 7.4.

On Mon, 29 Jul 2019, 20:14 Zoran Regvart, notifications@github.com wrote:

@paoloantinori https://github.com/paoloantinori why is this a p0 now the issue has been open for a year unaddressed?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/syndesisio/syndesis/issues/3076?email_source=notifications&email_token=AALTHWS57ZDKDR7NTLDNTJTQB4XRLA5CNFSM4FJ5SJZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3BR4AA#issuecomment-516103680, or mute the thread https://github.com/notifications/unsubscribe-auth/AALTHWUN2VLVGQTWVN5J2SLQB4XRLANCNFSM4FJ5SJZA .

zregvart commented 5 years ago

@paoloantinori I guess I assumed that this is blocking 7.4 release. Did you mean to signal that this is priority work for 7.5?

paoloantinori commented 5 years ago

yes, it's for 7.5.

I just wanted to raise it's a priority since the beginning of the dev Sprint to be sure we won't forget to look at this.

I do mistakes often with GH classification and it's good that you have double checked, but luckily I didn't this time and I confirm that the 7.5 release target is the correct one.

Screenshot from 2019-07-30 11-50-38