Thursday, 2020-06-25

*** yaawang_ has joined #starlingx00:45
*** born2bake has quit IRC01:03
*** hoonetorg has quit IRC03:02
bwensleyborn2bake - I added a reply in the LP03:04
*** hoonetorg has joined #starlingx03:15
*** riuzen has joined #starlingx04:36
*** sgw has quit IRC04:57
*** riuzen has quit IRC04:57
*** dpanech has quit IRC05:40
*** riuzen has joined #starlingx05:55
*** riuzen has quit IRC05:55
*** hyunsikyang has joined #starlingx06:11
*** hyunsikyang__ has quit IRC06:14
*** pyn38 has joined #starlingx06:42
*** bengates has joined #starlingx06:57
*** zbsarash1 has quit IRC06:58
*** bengates has quit IRC07:10
*** bengates has joined #starlingx07:11
*** sgw1 has quit IRC07:22
*** born2bake has joined #starlingx09:11
*** bengates has quit IRC09:14
*** bengates has joined #starlingx09:15
*** bengates_ has joined #starlingx09:45
*** bengates has quit IRC09:48
*** bengates_ has quit IRC10:03
*** bengates has joined #starlingx10:04
*** pyn38 has quit IRC11:51
*** bengates has quit IRC13:43
*** bengates has joined #starlingx13:47
*** sgw has joined #starlingx13:52
sgwMorning all13:53
*** zbsarash1 has joined #starlingx14:06
*** sgw1 has joined #starlingx14:09
*** dpanech has joined #starlingx14:23
dpanechsgw: looks like I installed docker from https://download.docker.com/linux/centos/docker-ce.repo14:25
dpanechThen:  dnf -y --setopt=docker-ce-stable.module_hotfixes=true install containerd.io docker-ce docker-ce-cli14:37
dpanechsgw: the tb script crates a docker image called $USER-stx-builder:7.4 ... do you know what the 7.4 refers to? It's hard-coded in the script.15:17
dpanechsgw: back to docker... what are the symptoms of your networking problems?16:10
*** yaawang_ has quit IRC16:35
*** bengates has quit IRC16:36
*** bengates has joined #starlingx16:37
born2bakethere is no way I can access kube cluster remotely?16:37
*** bengates has quit IRC16:37
*** bengates has joined #starlingx16:43
*** bengates has quit IRC16:48
*** yaawang_ has joined #starlingx16:55
sgwdpanech: sorry was not checking here, reading16:58
sgwdpanech: so I am using docker-ce.repo also, and my symptoms now seems to be no DNS name resolutions, I can ping 8.8.8.8, but resolving google.com fails17:04
sgwAs for the tb script, the 7.4 refers to CentOS 7.4 which is the version we started out with, you updated it to 7.817:04
dpanechsgw: looks like my Dockerfile commit from last week broke the tb script in master. Please hold off on approving any related code reviews until I fix it.17:11
dpanechsgw: "I can ping 8.8.8.8..." -- from within Docker or from host?17:12
sgwwithin the container17:12
dpanechsgw: not sure if this is related, but docker messes with host's routing table, sometimes in ways that break things.17:13
dpanechsomeone at WR had a problem like that recently17:14
dpanechit creates virtual network devices and assignes semi-random IP addresses to them, that sometimes mask the actual routes on your network17:15
sgwI can run the same centos8 container on other machines (ubuntu and fedora platform OS) in my network with no networking issues, it just seems to be the host that has centos8 as the platform OS17:16
dpanechselinux?17:18
sgwjsomervi1: do we want to have the "fixes" and "cc" tags in that sub-patch?  Will gerrit do something strange?17:18
sgwI am running a generic CentOS-8 with default firewall and selinux (if running by default).17:19
sgwjsomervi1: I am referring to the QAT patch17:20
jsomervi1why, should it?  It's just a file.17:24
dpanechsgw: I'm pretty sure the firewall is required for docker. But I did disable selinux.17:28
sgwAh, let me take a look at selinux settings17:30
jsomervi1sgw see starlingx-3.0.0/cgcs-root/stx/integ/kernel/kernel-std/centos/patches/cpuidle-menu-Avoid-taking-spinlock-for-accessing-QoS.patch for a past example17:30
sgwjsomervi1: just checking, I guess since it's not going through the any kernel process it won't be parsed. thanks for clarification17:31
jsomervi1np17:31
sgw1slittle1: I guess for 4.x, I need to create a set of flock manifests also, not just default.xml18:18
*** rcw has joined #starlingx19:13
sgwslittle1: as I am looking at that code, can you think of why we could commit the modified manifests after tagging vs before?  Don't we want to use repo init with a tag and get the newer manifests?19:47
dpanechsgw: I'm finding multiple issues with stx/tools in both master and 3.0 ... I think Poornima's changes might actually fix things for 3.0, at least for the moment. But they may cause merge conflicts later, because I still can't get my head around the overall strategy for all these pieces.20:33
sgw1Here changes are very targeted obviously, although I am not sure about her change in the tb.sh script, need to look at that more.  I can ask her tonight.20:34
dpanechI think all she did was change the image tag to 7.820:36
sgw1But I am not sure we want that, we want it to stay at 7.4 until container matches 7.820:40
sgw1FROM line in Dockerfile20:41
dpanechI suppose... on the other hand, that container's initial yum repo files point to mirror.centos.org, which is, effectively 7.8 at the moment.20:43
* sgw1 was confused, yes she updated it form master, that's probably one of the problems your seeing20:43
sgw1I thought it was for the 3.x branch20:43
sgw1the 7.4-7.8 change I can +2 for master, that makes sense unless you plan to revert your original change20:44
dpanechyeah ok.20:45
sgw1dpanech: so are you saying let's take poornima's 3.x patches (pin mock only & add 7.8 repos )  And then when you figure out the correct update for the Dockerfile/container you will do that later?20:47
sgw1Short term fix for cves and then a longer term tools update?20:47
dpanechno let's wait till tomorrow at least, I'm still investigating. I think we need another cherry pick for centos 7.7 repo. It's target URL is no longer valid, I think this was fixed in master.20:48
sgw1Ok, we can wait20:51
dpanechsgw: looks like tools/README is not up to date in stx/master. Either that or tb.sh has been broken since build layering introduction. Is there some other document file(s) that describe how to use tb.sh? I don't see any pending reviews for it in gerrit.21:24
dpanechSurprised this has gone unnoticed for so long21:24
sgwI have been using tb.sh with layers no problem21:25
dpanechLiterally following README doesn't work.21:25
sgwRecently no less.  What about following either of the Layer Build docs on starlingx.io?21:26
sgwSounds like readme needs updating then21:26
sgwI think the missing item for layered build would be setting LAYER= in the localrc21:26
dpanechi'm stuck before that on the download_mirror step.21:27
sgwI can actually reuse the container in different projects with LAYER= different layers21:27
sgwtb.sh create failing?21:28
sgwI guess I don't understand where your failing then21:28
dpanechno, under "package mirror creation" it says "cd centos-mirror-tools && docker run -v $PWD:/localdisk ..."; (as root) then run download_mirror.sh inside. Not the volume mount point, its a small subtree of the repo. Not enough to run anything.21:30
dpanech* Not=note21:30
sgwCheck newer/pending documentation: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_83b/733048/11/check/openstack-tox-docs/83b9be4/docs/developer_resources/layered_build_guide.html21:53
dpanechok thanks, I'll try that21:58
sgwdpanech: well i disabled selinux and still have the same issue that can resolve google.com for example.22:35
*** rchurch has quit IRC23:43
*** rchurch has joined #starlingx23:43
*** born2bake has quit IRC23:56

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!