| *** ralonsoh has joined #openstack-horizon | 06:12 | |
| *** josecastroleon has joined #openstack-horizon | 06:26 | |
| *** lvdombrkr has joined #openstack-horizon | 06:27 | |
| *** vishalmanchanda has joined #openstack-horizon | 06:33 | |
| *** lvdombrkr89 has joined #openstack-horizon | 07:12 | |
| *** lvdombrkr has quit IRC | 07:16 | |
| *** rdopiera has joined #openstack-horizon | 07:54 | |
| amotoki | vishalmanchanda: hi | 09:04 |
|---|---|---|
| vishalmanchanda | amotoki: hi | 09:04 |
| amotoki | vishalmanchanda: regarding OFTC update backports in stable branches, the global redirect has been setup . | 09:05 |
| vishalmanchanda | amotoki: yeah I see, I think we don't require backport anymore. | 09:05 |
| vishalmanchanda | amotoki: beacuse always redirect to master contribution.rst | 09:06 |
| amotoki | vishalmanchanda: I think it is better to keep the current contributor guide in stable branches (w/ your backport optionally), thoguth? | 09:06 |
| vishalmanchanda | amotoki: ohh. | 09:06 |
| amotoki | vishalmanchanda: all access to contributor guide in stable branches will be redirected to the master, but it is nice to see the TOC of the contirbutor guide. | 09:06 |
| amotoki | vishalmanchanda: thought? | 09:06 |
| vishalmanchanda | amotoki: which stable/branches* requires backport? | 09:08 |
| amotoki | vishalmanchanda: actually no branch needs backports. | 09:10 |
| amotoki | vishalmanchanda: I am also okay with backports to some stable branches (perhaps maintained branches) as it potentially provides infomration to who read the document in the repo directly. | 09:10 |
| amotoki | vishalmanchanda: which is your prefernce? | 09:10 |
| vishalmanchanda | amotoki: I mean both options fine for me, I have no stronger opinion on them after this redirect thing. | 09:11 |
| *** whoami-rajat has joined #openstack-horizon | 09:12 | |
| *** jchorin has joined #openstack-horizon | 09:12 | |
| amotoki | vishalmanchanda: okay. as of now, your backports are open. If you would like to land them, I will approve it. that's the main reason I asked it :) | 09:13 |
| jchorin | Hi everyone! I am having an issue with my Horizon setup with TLS support. I get a "Bad Request (400)" every time. The only log I get with Apache is 'GET /horizon HTTP/1.1" 400 5860 "-" "curl/7.68.0"' | 09:14 |
| jchorin | Has anyone seen this already? | 09:14 |
| vishalmanchanda | amotoki: Ok thanks we will keep the current contributor guide in the stable branches. | 09:14 |
| amotoki | jchorin: are you talking about access to horizon over TLS? | 09:17 |
| amotoki | jchorin: or do you mean "access to back-end services over TLS"? | 09:17 |
| jchorin | amotoki: Access to Horizon over TLS. Basically I followed this: https://docs.openstack.org/horizon/wallaby/admin/customize-configure.html#configure-the-dashboard-for-https | 09:19 |
| amotoki | jchorin: the guide assume horizon is configured as the top level of URL. Your logs says you accessed to /horizon. Is it what you expected? | 09:21 |
| jchorin | amotoki: I get the same thing when accessing top level URL: "GET / HTTP/1.1" 400 5853 "-" "curl/7.68.0" | 09:22 |
| jchorin | I also have some deprecation warnings, and "No local_settings file found." | 09:23 |
| jchorin | amotoki: I also have some deprecation warnings, and "No local_settings file found." | 09:23 |
| amotoki | jchorin: I have no good answer or suggestion on 400 error. it is usually caused by misconfiguration of apache server or mod_wsgi (but at the moment I have no time to try it locally) | 09:30 |
| amotoki | jchorin: regarding deprecation warning, I believe they can be ignored. | 09:31 |
| amotoki | jchorin: regarding "No local_settings file found.", it depends on whether you prepared local_settings.py or not. | 09:32 |
| jchorin | amotoki: well I did modify '/etc/openstack-dashboard/local_settings.py' | 09:34 |
| jchorin | amotoki: Ok I guess I should look in the direction of apache then | 09:34 |
| amotoki | jchorin: one possible reason for 400 in apache/wsgi/django situation like horizon is ALLOWED_HOSTS (in local_settings.py). | 09:35 |
| amotoki | jchorin: Loading /etc/openstack-dashboard/local_settings.py seems distribution-specific setting, but perhaps you need to check how local_settings.py is loaded. | 09:36 |
| jchorin | amotoki: thanks, I'll take a look. | 09:37 |
| jchorin | amotoki: regarding allowed hosts, I set it already to "['*']", so it is not the culprit I guess | 09:38 |
| amotoki | jchorin: so a message "local_settings.py file not found" looks important so that ALLOWED_HOSTS is configured properly. | 09:40 |
| amotoki | jchorin: it might help. | 09:40 |
| vmarkov | Hi all. Have a question for discussion. In Admin-System-System Information-Compute Services we have "Last Updated" column, which always shows "0 minutes" because nova returns heartbeat timer on this report. However, documentation for novaclient shows example reports with reasonable update times and these examples haven't updated since 2016. From position of UX, it is reasonable to rename "Last Updated" column or remove it at all, | 09:48 |
| vmarkov | because failed heartbeat anyway raises alert | 09:48 |
| vishalmanchanda | vmarkov: Hi, If I look at "Last Updated" under Admin-System-System Information-Compute Services | 09:53 |
| vishalmanchanda | For me value of shows "Last Updated" =3 days, 20 hours | 09:54 |
| vishalmanchanda | vmarkov: So what you mean by it always shows "0 minutes" and we can remove it. | 09:55 |
| vmarkov | Really interesting. Tried $ openstack compute service list on devstack and on production cluster, and get timestamps several seconds old | 10:19 |
| amotoki | vmarkov: I also tested it in my dev env. I stopped nova-compute almost 2 hours ago (before afk). I checked the dashboard now and see "1 hour, 50 minutes" in "Last Updated" column. | 10:57 |
| amotoki | vmarkov: horizon uses a response of novaclient services.list() and just applies utils_filters.parse_isotime and filters.timesince | 11:00 |
| amotoki | vmarkov: so what I can suggest is to check the response of the corresponding API call (service-list). | 11:01 |
| vmarkov | Anyway, Horizon shows actual response from service-list call in human readable form. But it can be 0 minutes if service alive or some longer time if service failed or turned off. I'm not sure, if "Last Updated" is correct name for it. Probably "Last seen" or smth like it will be more accurate | 11:35 |
| *** tosky has joined #openstack-horizon | 11:59 | |
| vmarkov | Also could you review two patches? | 12:28 |
| vmarkov | https://review.opendev.org/c/openstack/horizon/+/793420 | 12:28 |
| vmarkov | https://review.opendev.org/c/openstack/horizon/+/793970 | 12:28 |
| *** tmazur has joined #openstack-horizon | 13:58 | |
| opendevreview | Radomir Dopieralski proposed openstack/horizon master: Initial test of django sass processor https://review.opendev.org/c/openstack/horizon/+/794809 | 14:23 |
| opendevreview | Oleksandr Kozachenko proposed openstack/horizon master: Add the filter function in c-bak dashboard for both Project & Admin https://review.opendev.org/c/openstack/horizon/+/791532 | 14:30 |
| *** dklyle has joined #openstack-horizon | 14:50 | |
| opendevreview | Oleksandr Kozachenko proposed openstack/horizon stable/victoria: Add the filter function in c-bak dashboard [victoria] https://review.opendev.org/c/openstack/horizon/+/795128 | 15:50 |
| opendevreview | Oleksandr Kozachenko proposed openstack/horizon master: Add the filter function in c-bak dashboard for both Project & Admin https://review.opendev.org/c/openstack/horizon/+/791532 | 16:23 |
| *** rdopiera has quit IRC | 16:32 | |
| *** jchorin has quit IRC | 16:43 | |
| *** ralonsoh has quit IRC | 17:51 | |
| *** vishalmanchanda has quit IRC | 19:12 | |
| *** lvdombrkr89 has quit IRC | 19:46 | |
| *** lvdombrkr has joined #openstack-horizon | 19:49 | |
| *** lvdombrkr has quit IRC | 20:52 | |
| *** tosky has quit IRC | 22:04 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!