| airship-irc-bot | <sidney.shiba> PS https://review.opendev.org/c/airship/treasuremap/+/778728 merged so next is https://review.opendev.org/c/airship/treasuremap/+/779413. | 00:00 |
|---|---|---|
| airship-irc-bot | <mattmceuen> The timeout bump for airshipctl's gate failed zuul for what looks like an unrelated reason. We have a few airshipctl patches that we could WF+1 or retest, and I think this would be a good candidate: https://review.opendev.org/c/airship/airshipctl/+/783125 | 00:17 |
| airship-irc-bot | <mattmceuen> Looks like we have 4 airshipctl checks & 4 airshipctl gates going now, so maybe once some of those pass | 00:18 |
| airship-irc-bot | <raliev> I bet none of them will pass again lol | 00:24 |
| airship-irc-bot | <sidney.shiba> PS https://review.opendev.org/c/airship/treasuremap/+/779413 just merged | 00:50 |
| airship-irc-bot | <mattmceuen> Don't jinx it @raliev :slightly_smiling_face: | 00:50 |
| airship-irc-bot | <kk6740> I have no doubts in TM as it has no tests :) | 00:51 |
| airship-irc-bot | <mattmceuen> problem solved | 00:51 |
| airship-irc-bot | <kk6740> As easy as that :) | 00:52 |
| airship-irc-bot | <raliev> it’s culmination right now - if 780500 passes the most unpredictable script 30 then there are good chances it will be merged, as well as the other ones :slightly_smiling_face: | 00:53 |
| airship-irc-bot | <kk6740> I am concerned that two jobs in a row failed to at the same place. target node is not getting up. and console logs are empty. | 01:09 |
| airship-irc-bot | <raliev> look like it gets up | 01:13 |
| airship-irc-bot | <raliev> https://zuul.openstack.org/stream/e32dc993fe0f444c834577ba2d7a64d0?logfile=console.log | 01:13 |
| airship-irc-bot | <sreejith.punnapuzha> Can i get review on this... https://review.opendev.org/c/airship/airshipctl/+/783718 finally got +1 from gates | 01:33 |
| *** uzumaki has quit IRC | 02:13 | |
| *** uzumaki has joined #airshipit | 05:39 | |
| *** uzumaki has quit IRC | 06:53 | |
| *** mugsie__ is now known as mugsie | 11:01 | |
| *** uzumaki has joined #airshipit | 11:17 | |
| *** uzumaki has quit IRC | 11:19 | |
| airship-irc-bot | <mattmceuen> Happy merging morning :slightly_smiling_face: good things come to those who wait (and occasionally recheck) | 12:27 |
| airship-irc-bot | <mattmceuen> @james.gu I put in a treasuremap change to update the airshipctl pin to include the (now merged) change to add your script, and rebased you TM change on top of it https://review.opendev.org/c/airship/treasuremap/+/783911 | 12:28 |
| airship-irc-bot | <ak3216> @mattmceuen or @sreejith.punnapuzha with 783718 merging, should https://review.opendev.org/c/airship/airshipctl/+/774251 be rerun now as it was dependent on it? | 12:55 |
| airship-irc-bot | <mattmceuen> I think so @ak3216, & looks like Sreejith is trying, but I see this error which makes me thing there's some mismatch between the merged function and the template that needs it: `template: tmpl:29: function "genSSHKeyPair" not definedtemplate: tmpl:29: function "genSSHKeyPair" not definedcouldn't execute function: exit status 1` | 13:15 |
| airship-irc-bot | <ak3216> @raliev with https://review.opendev.org/783910 merging, can we go ahead & close https://github.com/airshipit/airshipctl/issues/348? Thanks! | 13:24 |
| airship-irc-bot | <ak3216> @niha.twinkle with https://review.opendev.org/c/airship/airshipctl/+/776472 merging, can we close out https://github.com/airshipit/airshipctl/issues/323? Thanks! | 13:25 |
| airship-irc-bot | <mattmceuen> @sreejith.punnapuzha It looks like the secret gen is failing because the template is looking for quay.io/airshipit/templater:v2, and that tag was last updated 7 days ago. The new templater version is tagged by git commit & latest, but not by v2 | 13:37 |
| airship-irc-bot | <mattmceuen> I just updated the v2 tag manually, and will kick off a recheck | 13:37 |
| airship-irc-bot | <sreejith.punnapuzha> Sure thanks | 13:38 |
| airship-irc-bot | <mattmceuen> We'll still need to get to the bottom of why that tag isn't getting updated by the image build/push job | 13:38 |
| airship-irc-bot | <sreejith.punnapuzha> image publish job is only pushing latest and commit sha as image tags as far as i know. there is not playbook task to push v2 tag | 13:41 |
| airship-irc-bot | <mattmceuen> @sean.eagan did we decide to go with v2 tags for the krm functions, or v1? I forget | 13:41 |
| airship-irc-bot | <mattmceuen> replacement-transformer isn't pushing v1 or v2 tags either, but the difference is our manifests are using replacement-transformer:latest | 13:43 |
| airship-irc-bot | <sean.eagan> i think the decision was to use v2 for all Airship 2 projects, so I went with that | 13:44 |
| airship-irc-bot | <sean.eagan> https://review.opendev.org/c/airship/airshipctl/+/767179 | 13:44 |
| airship-irc-bot | <mattmceuen> ok. is the process for the krm functions going to be 1. pin to :v2 in master, and it's a moving pin (more like what we'd discussed before) 2. pin to :lastest in master, and make :v2.x a static pin, which we only pin against in v2 branch (more like what we're doing with the rest of the release) 3. or something in between :slightly_smiling_face: | 13:45 |
| airship-irc-bot | <mattmceuen> we could discuss that in upcoming flight plan if you think that would help | 13:48 |
| airship-irc-bot | <sean.eagan> yeah we can discuss there. the goal of the moving v2 tag was to be an "in between" solution where we can avoid breaking changes but still include non-breaking changes without having to update references. | 13:50 |
| airship-irc-bot | <mattmceuen> yeah, and that's where I'm wondering whether latest *might* now fit the bill, *if* we do per-minor-release pinning of krm functions as part of the release process. But I'm not sure. | 13:51 |
| *** rpioso is now known as rpioso|afk | 13:55 | |
| airship-irc-bot | <sean.eagan> also the intention is to not manually update the v2 tag in quay but rather push a e.g. v2.0.1 git tag and have the automation push the v2 (major), v2.0 (minor), and v2.0.1 (patch) tags to quay | 14:02 |
| airship-irc-bot | <raliev> basically, yes, we can close it | 14:05 |
| airship-irc-bot | <ak3216> Great, thanks. I just took care of it. | 14:05 |
| *** SRao has joined #airshipit | 15:00 | |
| airship-irc-bot | <mattmceuen> Ah I see the treasuremap-airshipctl-pin-update validation error that roman_g was referring to: `error validating data: [ValidationError(VersionsCatalogue.spec.images.grafana.repository): invalid type for org.airshipit.v1alpha1.VersionsCatalogue.spec.images: got "string", expected "map", ValidationError(VersionsCatalogue.spec.images.grafana.tag)` | 15:25 |
| airship-irc-bot | <mattmceuen> @mf4192 looks like grafana's versions catalogue contents need to be trued up to new schema right? I will try to fix & put it in my pin update | 15:25 |
| *** muhaha has joined #airshipit | 15:26 | |
| airship-irc-bot | <mf4192> Exactly, I’m looking over it now with James | 15:28 |
| airship-irc-bot | <mattmceuen> Ok awesome - if you can please push it to my pin patchset then that would be better :slightly_smiling_face: | 15:28 |
| airship-irc-bot | <mf4192> Looks like the images are using a mixture of formats | 15:29 |
| airship-irc-bot | <mattmceuen> You're ahead of me and I need to get on top of something else urgent | 15:29 |
| airship-irc-bot | <james.gu> are you saying tis is not urgent? :slightly_smiling_face: | 15:29 |
| airship-irc-bot | <mattmceuen> No it is for sure :slightly_smiling_face: | 15:29 |
| airship-irc-bot | <mattmceuen> Just can only do one urgent thing at at time, sadly | 15:29 |
| airship-irc-bot | <james.gu> treasuremap images version and airshipctl images version are using different formats | 15:30 |
| airship-irc-bot | <mf4716> URGENT: Airshipctl Core reviews & WF needed for v2.0 GA PS https://review.opendev.org/c/airship/airshipctl/+/774251 | 15:40 |
| *** rpioso|afk is now known as rpioso | 16:00 | |
| airship-irc-bot | <niha.twinkle> Yes , thanks for closing the issue. | 16:08 |
| airship-irc-bot | <niha.twinkle> @ak3216 Yes , thanks for closing the issue. | 16:09 |
| airship-irc-bot | <mf4192> @james.gu @mattmceuen Unfortunately the fix for the schema validation errors isn’t going to be as straight-forward as I was hoping. Lots of these are for images going into HelmReleases, which get plugged directly into the chart’s `values.image` block which is expecting to have `repository` and `tag` keys | 16:34 |
| airship-irc-bot | <mf4192> But then there are others like SIP that have the repo and tag / hash as a single string, which is what the schema is expecting and how all of the replacements work in airshipctl | 16:35 |
| airship-irc-bot | <mattmceuen> @mf4192 would the simplest thing to do be to just disassociate the existing versions-treasuremap from `kind: versionsCatalogu` ? | 16:38 |
| airship-irc-bot | <mattmceuen> Just make it a VariableCatalogue for now (no change needed for substitution rules etc) and then sort it out for 2.1? | 16:39 |
| airship-irc-bot | <mf4192> Yep, that’s probably the easiest for now since all the replacement rules work. The only other thing I would have suggested in the sort term is a small change to the schema to allow either version of the `image` object | 16:40 |
| airship-irc-bot | <mf4192> But I think your suggestion makes more sense | 16:40 |
| airship-irc-bot | <james.gu> I think either relaxing the schema or escape the validation by changing kind will work | 16:47 |
| airship-irc-bot | <james.gu> The latter is quick for sure | 16:47 |
| airship-irc-bot | <mf4192> Yep, I’m working on those changes now. I’ll push up a new PS to Matt’s pin change after I’ve had a chance to test locally | 16:50 |
| airship-irc-bot | <mattmceuen> awesome, thanks Matt | 17:02 |
| airship-irc-bot | <mf4192> PS updated, working its way through gates now | 17:28 |
| *** SRao has quit IRC | 17:34 | |
| airship-irc-bot | <james.gu> @mattmceuen https://review.opendev.org/c/airship/docs/+/745974 needs to go to the v2 branch as well I think? | 18:25 |
| airship-irc-bot | <mattmceuen> Do you mean we should branch (or tag) the docs project James? Or something different? | 18:26 |
| airship-irc-bot | <james.gu> somehow docs repo is already branched with v2 (with the new source tree) | 18:27 |
| airship-irc-bot | <james.gu> all the goodies are on the v2 branch | 18:27 |
| airship-irc-bot | <mattmceuen> Why do we have a v2 branch for docs in the first place? | 18:30 |
| airship-irc-bot | <mattmceuen> Maybe we discussed it but if so I've forgotten -- I had it in my head that maybe we'd tag it, but a branch seems like overkill in our situation for docs (to me at least) | 18:31 |
| airship-irc-bot | <mattmceuen> Is the idea for docs v2 to swap and become master, like treasuremap? In any case we want our v2 documentation in master, one way or another, after we release v2.0 | 18:33 |
| airship-irc-bot | <dwalt> There was an email thread awhile back with the team is working on documentation. They requested it since they are redoing the entire toctree, and it would be disruptive to the current documentation, so I created it | 18:35 |
| airship-irc-bot | <dwalt> Anything we are adding in the short term would probably be easier to add to master | 18:35 |
| airship-irc-bot | <mattmceuen> "Anything we are adding in the short term would probably be easier to add to master" - sorry Drew could you rephrase that for me? I didn't catch it | 18:37 |
| airship-irc-bot | <mattmceuen> Did we take out Airship 1 documentation in the v2 branch? | 18:37 |
| airship-irc-bot | <james.gu> I don't have the history of the docs v2 branch discussion that I can remember | 18:37 |
| airship-irc-bot | <dwalt> For the v2 release that we are working on at the moment. The toctree project is a ways out | 18:37 |
| airship-irc-bot | <james.gu> Matt, looks like the v2 was created when the new v2 doc tree was created. https://review.opendev.org/plugins/gitiles/airship/docs/+/refs/heads/v2 | 18:42 |
| airship-irc-bot | <mattmceuen> James, just chatted briefly w/ Drew to get me up to speed. We're thinking that the safest/simplest path forward would be to move the airship-in-a-pod.rst and the site authoring guide patchsets over to master. Because: the branch was really created for disruptive toctree work that is not yet complete (correct me if that's not right) | 18:51 |
| airship-irc-bot | <mattmceuen> And we want those two docs in master for the v2.0 release | 18:51 |
| airship-irc-bot | <mattmceuen> then when the v2 branch toctree stuff is ready, that can be merged back into master | 18:52 |
| airship-irc-bot | <mattmceuen> does that sound right to you? | 18:52 |
| airship-irc-bot | <james.gu> just chatting with Mike in the zodiac dsu (if you want to join), the idea is to merge v2 back to master for the release. yes, I agree with Drew the toctree change is disruptive. | 18:53 |
| airship-irc-bot | <sidney.shiba> Hi team, I am trying to deploy a `capz` (Azure operator) target cluster for a PoC and getting context related errors with `airshipctl` during clusterinit phase. Rishabh tried with `capd` (Docker operator) and similar errors but during control plane deployment phase. This is the sequence of commands I run: 1. Create ephemeral cluster: `airshipctl/tools/document/start_kind.sh` 2. Setting context: `kubectl config set-context | 19:46 |
| airship-irc-bot | ephemeral-cluster --cluster kind-ephemeral-cluster --user kind-ephemeral-cluster --kubeconfig $KUBECONFIG` 3. Clusterinit Ephemeral cluster: `airshipctl phase run clusterctl-init-ephemeral –debug` Not sure what I need to do to get this working. Can anybody help? `$ *airshipctl phase run clusterctl-init-ephemeral --debug*` `[airshipctl] 2021/03/30 16:46:24 opendev.org/airship/airshipctl/pkg/k8s/kubeconfig/builder.go:120: Getting site | 19:46 |
| airship-irc-bot | kubeconfig` `[airshipctl] 2021/03/30 16:46:24 opendev.org/airship/airshipctl/pkg/k8s/kubeconfig/builder.go:122: Getting kubeconfig for cluster 'ephemeral-cluster' to build site kubeconfig` `{"Message":"starting clusterctl init executor","Operation":"ClusterctlInitStart","Timestamp":"2021-03-30T16:46:24.498447711-05:00","Type":"ClusterctlEvent"}` `[airshipctl] 2021/03/30 16:46:24 opendev.org/airship/airshipctl/pkg/k8s/kubeconfig/builder.go:248: | 19:46 |
| airship-irc-bot | Received error when extacting context, ignoring kubeconfig. Error: failed merging kubeconfig: source context 'ephemeral-cluster' does not exist in source kubeconfig` `[airshipctl] 2021/03/30 16:46:24 opendev.org/airship/airshipctl/pkg/k8s/kubeconfig/builder.go:126: All kubeconfig sources failed for cluster 'ephemeral-cluster', error 'all kubeconfig sources failed for cluster 'ephemeral-cluster'', skipping it` `[airshipctl] 2021/03/30 16:46:24 | 19:46 |
| airship-irc-bot | opendev.org/airship/airshipctl/pkg/k8s/kubeconfig/builder.go:122: Getting kubeconfig for cluster 'target-cluster' to build site kubeconfig` `[airshipctl] 2021/03/30 16:46:24 opendev.org/airship/airshipctl/pkg/k8s/kubeconfig/builder.go:248: Received error when extacting context, ignoring kubeconfig. Error: failed merging kubeconfig: source context 'target-cluster' does not exist in source kubeconfig` `[airshipctl] 2021/03/30 16:46:24 | 19:46 |
| airship-irc-bot | opendev.org/airship/airshipctl/pkg/k8s/kubeconfig/builder.go:126: All kubeconfig sources failed for cluster 'target-cluster', error 'all kubeconfig sources failed for cluster 'target-cluster'', skipping it` `[airshipctl] 2021/03/30 16:46:24 opendev.org/airship/airshipctl/pkg/clusterctl/client/client.go:104: Starting cluster-api initiation` `[airshipctl] 2021/03/30 16:46:24 opendev.org/airship/airshipctl/pkg/events/processor.go:60: Received | 19:46 |
| airship-irc-bot | error on event channel {context "ephemeral-cluster" does not exist}` `Error events received on channel, errors are:` `[context "ephemeral-cluster" does not exist]` Executing `kubectl` finds the `ephemeral-cluster` context but not `airshipctl`. See below. What else needs to be configured? `$ *echo $KUBECONFIG*` `/home/sx3394/.airship/kubeconfig` `$ *kubectl --kubeconfig /home/sx3394/.airship/kubeconfig --context ephemeral-cluster get pods | 19:46 |
| airship-irc-bot | -A*` `NAMESPACE           NAME                                                     READY  STATUS   RESTARTS  AGE` `kube-system         coredns-74ff55c5b-77qfw                                  1/1    Running  0         133m` `kube-system         coredns-74ff55c5b-zffk7                     | 19:46 |
| airship-irc-bot | `kube-system kindnet-vs745 1/1 Running 0 133m` `kube-system kube-apiserver-ephemeral-cluster-control-plane 1/1 Running 0 133m` `kube-system kube-controller-manager-ephemeral-cluster-control-plane 1/1 Running 0 | 19:46 |
| airship-irc-bot | `kube-system kube-scheduler-ephemeral-cluster-control-plane 1/1 Running 0 133m` `local-path-storage local-path-provisioner-78776bfc44-dkrnz 1/1 Running 0 133m` | 19:46 |
| airship-irc-bot | <kk6740> Can u show ur airship config? | 20:32 |
| airship-irc-bot | <kk6740> and also run `airshipctl phase render -s config -k ClusterMap | 20:41 |
| airship-irc-bot | <mattmceuen> @sreejith.punnapuzha your helm-chart-collator fix to airshipctl got a gate failure, but it was a timeout and I'm not sure what caused it: https://review.opendev.org/c/airship/airshipctl/+/784122 | 20:42 |
| airship-irc-bot | <sreejith.punnapuzha> seems like zuul is down. i cant access the url | 20:42 |
| airship-irc-bot | <mattmceuen> ( I think it was a timeout, just because that's what roman mentioned could cause missing logs) | 20:43 |
| airship-irc-bot | <mattmceuen> I got one issue accessing the logs through zuul, but retrying got them up for me | 20:43 |
| airship-irc-bot | <kk6740> i think recheck will help | 20:46 |
| airship-irc-bot | <mattmceuen> it certainly can't hurt :slightly_smiling_face: - done | 20:48 |
| airship-irc-bot | <mattmceuen> between that and yeseterday's "zuul reboot"... ugh bad timing | 20:48 |
| airship-irc-bot | <mattmceuen> the other two changes we're waiting on for branching have a dependency on Sreejith's | 20:49 |
| airship-irc-bot | <kk6740> @sidney.shiba do u still need help with the azure? | 21:03 |
| *** muhaha has quit IRC | 21:56 | |
| airship-irc-bot | <mattmceuen> Sreejith's change got a -1 from Jenkins due to a timeout, but it had previously passed, so I think the change is probably fine. The zuul gate just kicked off, so that should confirm. | 22:28 |
| airship-irc-bot | <ao129q> <here> Airship now has it's own project type at https://www.stackalytics.io/?project_type=airship-type | 22:43 |
| airship-irc-bot | <mattmceuen> oh nice! | 22:53 |
| airship-irc-bot | <sidney.shiba> @kk6740 I moved forward a bit but when initializing the ephemeral cluster with CAPI and CAPZ components, respective pods fails as it is not able to pull images. | 23:58 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!