| *** ysandeep|out is now known as ysandeep|rover | 05:08 | |
| ysandeep|rover | good morning everyone o/ | 05:16 |
|---|---|---|
| marios | \o | 05:18 |
| pojadhav | good morning \o | 05:24 |
| bhagyashris | good morning 0/ | 05:35 |
| * ysandeep|rover prays tempest failures please be consistent, I don't mind you failing at all but please be consistent. | 05:46 | |
| marios | ysandeep|rover: :/ i know this feeling | 05:50 |
| ysandeep|rover | :D | 05:51 |
| pojadhav | marios, hey how you resolved this error ?? https://review.opendev.org/c/openstack/tripleo-ci/+/839518/8#message-23c7677c86b0457399ecc41e41ff97834a3f361b | 06:27 |
| pojadhav | could you please guide me too | 06:28 |
| marios | pojadhav: we removed the play since it was unused https://review.opendev.org/c/openstack/tripleo-ci/+/841223 | 06:29 |
| marios | pojadhav: where do you see that? rebase should fix | 06:29 |
| pojadhav | marios, ahh okay. my patch was in merge conflict. I rebased it. | 06:30 |
| pojadhav | marios, thanks! | 06:30 |
| marios | pojadhav: ack np | 06:30 |
| *** ysandeep|rover is now known as ysandeep|rover|lunch | 08:02 | |
| jpodivin | this is awkward, does anyone know what's irc nick of Jakob Meng? | 08:19 |
| jpodivin | Can't seem to find it in the lp | 08:20 |
| Tengu | jpodivin: jm1 iirc | 08:33 |
| marios | Tengu: jpodivin: yes correct | 08:37 |
| jm1 | ysandeep|rover|lunch: o/ | 08:45 |
| jm1 | ysandeep|rover|lunch: sync after lunch? :) | 08:45 |
| jm1 | jpodivin: hey, saw your mail regarding ci in ansible openstack collection. wanna talk about your ci issues tomorrow in tripleo ci community call? | 08:47 |
| jm1 | chandankumar: o/ do you have bitwarden's cli tool installed? | 08:48 |
| akahat | hey folks.. i'm not able to understand why same job is defined in two different places: https://review.rdoproject.org/codesearch/?q=periodic-tripleo-ci-centos-9-scenario010-ovn-provider-standalone-master&i=nope&files=&repos= | 08:51 |
| jpodivin | jm1: sure we can. | 08:52 |
| jpodivin | jm1: although I would rather ask straight away if you don't mind. | 08:52 |
| jm1 | jpodivin: sure | 08:53 |
| chandankumar | jm1: hello | 09:20 |
| chandankumar | jm1: yes | 09:20 |
| jm1 | chandankumar: have you been able to export the vault using the cli? | 09:28 |
| chandankumar | jm1: not yet, need to try that out | 09:32 |
| jm1 | chandankumar: "bw list items" etc. allows us to show all secrets in a collection, "bw get item PUT_ITEM_HERE" is for single items. So "bw list items" allows us to backup our vault, although it is apparently unencrypted without further action. "bw export" does not work, as we expected. | 09:58 |
| chandankumar | jm1: yes list items gives so many data | 09:58 |
| chandankumar | jm1: bm export with organization option also does not work? | 09:59 |
| *** ysandeep|rover|lunch is now known as ysandeep|rover | 10:01 | |
| jm1 | chandankumar: for me it says "Resource not found." | 10:05 |
| jm1 | chandankumar: without orgid it works, but will only return my own vault | 10:05 |
| chandankumar | oh, okay, not useful then | 10:06 |
| chandankumar | jm1: so first solution bw list items sounds good | 10:06 |
| chandankumar | jm1: thank you for looking into that :-) ++ | 10:07 |
| ysandeep|rover | jm1: I am available for sync now but if you want we can meet once rlandy|out is in ~30 mins. | 10:08 |
| ysandeep|rover | reviewbot: please add in review list: https://review.opendev.org/c/openstack/openstack-tempest-skiplist/+/841834 | 10:09 |
| reviewbot | I have added your review to the Review list | 10:09 |
| jm1 | ysandeep|rover: ack, then lets wait for rlandy|out ^^ | 10:11 |
| *** rlandy|out is now known as rlandy | 10:15 | |
| rlandy | jm1: ysandeep|rover: I'm here | 10:15 |
| rlandy | jm1: ysandeep|rover: want to meet? | 10:16 |
| rlandy | jm1: pls nick | 10:16 |
| ysandeep|rover | rlandy, jm1 meet.google.com/cse-yqza-tna | 10:17 |
| ysandeep|rover | rlandy, https://review.opendev.org/c/openstack/openstack-tempest-skiplist/+/841834 | 10:21 |
| ysandeep|rover | jm1: hey you around? | 10:24 |
| rlandy | 2022-05-16 10:07:05 | - Curl error (7): Couldn't connect to server for https://buildlogs.centos.org/centos/9-stream/messaging/x86_64/rabbitmq-38/repodata/repomd.xml [Failed to connect to buildlogs.centos.org port 443: Connection refused] | 10:53 |
| rlandy | 2022-05-16 10:07:05 | Error: Failed to download metadata for repo 'centos9-rabbitmq': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried | 10:53 |
| pojadhav | marios, hello I have question regarding c7 teardown.. | 10:54 |
| *** jm1|ruck is now known as jm1|rover | 10:54 | |
| pojadhav | if c7 job name mentioned occurrence found then in that case what should be done ?? for example https://github.com/rdo-infra/ci-config/blob/0ce33c32ecf54f4df2834e6e147989129d380b15/ci-scripts/infra-setup/roles/rrcockpit/files/mariadb/skiplist.py#L36-L37 | 10:55 |
| marios | pojadhav: looking | 11:03 |
| marios | pojadhav: i am guessing that is not used any more ? (hard coded centos 7 fs 21? ) generally speaking we want to remove all the things. for this one i'd leave it till last, i.e. target zuul.d/ files first in all the places then start following more general cases like this one | 11:04 |
| marios | pojadhav: so for this one, when you get to it dig and see if that is used any where and if you cant find it ask in scrum/reviews call | 11:05 |
| marios | pojadhav: if it is no longer used then remove the whole file | 11:05 |
| marios | pojadhav: if it is used, then update that reference to something other than centos-8 | 11:05 |
| marios | err other than centos-7 | 11:05 |
| pojadhav | marios, ack thank you! | 11:06 |
| chandankumar | cs9 container does not /sbin/init command :-( | 11:06 |
| chandankumar | ubi9 beta image have different weird issue with molecule | 11:06 |
| chandankumar | so use these shiny containers at own risk | 11:07 |
| rlandy | chandankumar: need to chat with you after review time re: new initiatives | 11:07 |
| chandankumar | rlandy: ok | 11:10 |
| chandankumar | Does anyone built an init container on top of centos stream 9 container? | 11:13 |
| *** dviroel|out is now known as dviroel | 11:21 | |
| jm1 | arxcruz, frenzy_friday, rcastillo: have to attend cix call today, so will have to cancel our mtg for today | 11:29 |
| arxcruz | jm1 ack, anyway, i'm updating the patches with latewswt comments | 11:30 |
| arxcruz | latest* | 11:30 |
| arxcruz | also did a round of reviews | 11:30 |
| reviewbot | Do you want me to add your patch to the Review list? Please type something like add to review list <your_patch> so that I can understand. Thanks. | 11:30 |
| frenzy_friday | jm1, no problem for me. I have updated the done cards in miro, will update the will do next cards | 11:30 |
| jm1 | arxcruz: cool :) | 11:32 |
| jm1 | frenzy_friday: oh great, we can still (re)use today's board for our scrum mtg ^^ | 11:33 |
| ysandeep|rover | marios, https://code.engineering.redhat.com/gerrit/c/openstack/tripleo-ci-internal-jobs/+/399683/21/zuul.d/standalone-jobs.yaml#215 | 11:42 |
| *** pojadhav is now known as pojadhav|afk | 12:01 | |
| chandankumar | rlandy: want to meet now? | 12:01 |
| chandankumar | regarding new initiatives | 12:01 |
| rlandy | chandankumar: yes ... https://meet.google.com/vwp-ujai-ysv?pli=1&authuser=0 | 12:01 |
| *** jm1|rover is now known as jm1|ruck | 12:07 | |
| *** jm1|ruck is now known as jm1|rover | 12:07 | |
| ysandeep|rover | rlandy, jm1|rover wohoo we promoted master | 12:10 |
| jm1 | ysandeep|rover: what was the path where you could check the neutron error in c8 wallaby? | 12:10 |
| jm1 | ysandeep|rover: not tempest path but the other path | 12:11 |
| rlandy | ysandeep|rover: jm1: yay - we will also promote rhos-17 on rhel-8 finally | 12:11 |
| ysandeep|rover | jm1: nova logs in compute node - logs/overcloud-novacompute-0/var/log/extra/errors.txt.gz | 12:12 |
| ysandeep|rover | error.txt have grep of all the errors | 12:13 |
| ysandeep|rover | jm1, You will see something like - "Instance failed to spawn: nova.exception.VirtualInterfaceCreateException: Virtual Interface creation failed" | 12:13 |
| ysandeep|rover | jm1: fyi.. https://bugs.launchpad.net/tripleo/+bug/1964940/comments/4 | 12:13 |
| jm1 | ysandeep|rover: am i looking at the wrong pipeline? https://review.rdoproject.org/zuul/builds?pipeline=openstack-periodic-integration-stable1-cs8&skip=0 | 12:14 |
| ysandeep|rover | jm1: that's right, c8 wallaby | 12:15 |
| jm1 | ysandeep|rover: because both fs show other errors than VirtualInterf.. | 12:16 |
| ysandeep|rover | jm1: that virtual interface one is transient - happens sometimes.. We need to check if the latest hash run is failing with other error in consitent way.. /me also checking | 12:17 |
| jm1 | ysandeep|rover: let me check! | 12:23 |
| ysandeep|rover | jm1: for ex. https://trunk.rdoproject.org/api-centos8-wallaby/api/civotes_agg_detail.html?ci_name=periodic-tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset035-wallaby - if we skip fs001 and fs035 - latest hash 5951e9703b6eae17d1d3cf9312ab1eeb will promote. | 12:24 |
| ysandeep|rover | we only have 2 run for the hash 5951e9703b6eae17d1d3cf9312ab1eeb , taking a look at fs035 | 12:24 |
| ysandeep|rover | here - bunch of tempest tests failed: https://logserver.rdoproject.org/openstack-periodic-integration-stable1-cs8/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset035-wallaby/78cd2bc/logs/undercloud/var/log/tempest/failing_tests.log.txt.gz | 12:25 |
| ysandeep|rover | but the earlier run was better: https://logserver.rdoproject.org/openstack-periodic-integration-stable1-cs8/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset035-wallaby/df5d9f9/logs/undercloud/var/log/tempest/failing_tests.log.txt.gz | 12:25 |
| ysandeep|rover | jm1: you are right - we don't see virtual interface creation traceback in https://logserver.rdoproject.org/openstack-periodic-integration-stable1-cs8/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset035-wallaby/df5d9f9/logs/overcloud-novacompute-0/var/log/extra/errors.txt.gz | 12:26 |
| ysandeep|rover | jm1: lately we are seeing lot of tempest random failures, As the latest run only have 2 runs - I would rerun the fs001/fs035 with hash 5951e9703b6eae17d1d3cf9312ab1eeb via testproject to see if those failure are consistent. | 12:29 |
| jm1 | ysandeep|rover: ack | 12:30 |
| jm1 | ysandeep|rover: will run testproject, if non-consistent i will ask you to vote on my criteria patch | 12:30 |
| ysandeep|rover | jm1++ sounds good | 12:31 |
| bhagyashris | rlandy, https://code.engineering.redhat.com/gerrit/c/testproject/+/400570/5#message-ccc3c2bc86cdafc107f61e894ee849e42504889a testproject | 12:36 |
| bhagyashris | https://code.engineering.redhat.com/gerrit/gitweb?p=openstack/tripleo-ci-internal-jobs.git;a=blob;f=zuul.d/standalone-jobs.yaml#l57 | 12:40 |
| ysandeep|rover | rlandy, jm1: 17/rhel-8 promoted as well after a long... \o/ wohoo | 12:40 |
| dviroel | ++ | 12:40 |
| *** ysandeep|rover is now known as ysandeep|rover|afk | 12:45 | |
| jm1 | ysandeep|rover++ | 12:55 |
| soniya29 | chandankumar, rlandy, arxcruz, please review these patches whenever you have time:- https://review.opendev.org/q/topic:tempest_allow_list | 12:56 |
| *** pojadhav|afk is now known as pojadhav | 13:06 | |
| *** ysandeep|rover|afk is now known as ysandeep|rover | 13:11 | |
| chandankumar | soniya29: sure | 13:14 |
| chandankumar | soniya29: can you update this one https://review.opendev.org/c/openstack/tripleo-quickstart/+/839725 ? | 13:15 |
| soniya29 | chandankumar, sure | 13:16 |
| frenzy_friday | hey dpawlik 0/ I added a patch to use cirobot user instead of tripleocirobot. Pls add to your review list when you get some time, thanks! https://review.rdoproject.org/r/c/config/+/42891 | 13:21 |
| reviewbot | I have added your review to the Review list | 13:21 |
| chandankumar | soniya29: pojadhav you might need a rebase https://review.opendev.org/c/openstack/openstack-tempest-skiplist/+/839588 on this, thanks! | 13:22 |
| pojadhav | chandankumar, sure | 13:22 |
| dpawlik | frenzy_friday++ | 13:23 |
| soniya29 | chandankumar, okay | 13:33 |
| rlandy | ysandeep|rover: jm1: ha - looks like victoria will promote | 13:37 |
| ysandeep|rover | rlandy, yes testproject just passed | 13:37 |
| rlandy | way to go today | 13:37 |
| rlandy | jm1 must be the good luck charm :) | 13:37 |
| rlandy | I;m rerunning the one failing job on rhos-17 on rhel-9 so that might promo also | 13:38 |
| rlandy | ysandeep|rover: jm1: and 16.2 should clear promo as well today | 13:51 |
| rlandy | we should have a party | 13:51 |
| ysandeep|rover | good to see all these promotion after fun filled last week :D | 13:52 |
| ysandeep|rover | rlandy, 16.2 only waiting for bm job - its in rerun | 13:53 |
| ysandeep|rover | oh that just passed as well :D | 13:53 |
| ysandeep|rover | that means we promoted everything in last 2 days - except c8 wallaby - which jm1 is tracking now | 13:53 |
| jm1 | ysandeep|rover: c8 wallaby integration is still running, c8 wallaby component tripleo and network are failing | 13:54 |
| rlandy | yep | 13:54 |
| rlandy | ysandeep|rover: finally, right??? | 13:55 |
| ysandeep|rover | random tempest failure is still a cause of concern - not all jobs failing with neutron bug - I will try to dig deeper if there is any service level fault. | 13:56 |
| ysandeep|rover | :) finally yeah - I haven't seen this much green in a while | 13:57 |
| ysandeep|rover | but don't want to jinx it :D fingers crossed | 13:57 |
| jm1 | ysandeep|rover: cant we retrigger wallaby c8 component jobs? used dlrn hash from rr tool and it fails with "The DLRN hash or tag is not recognized. The hash or tag should not contain path slashes" | 13:58 |
| ysandeep|rover | jm1, for component just run the job without hash & force_periodic | 14:00 |
| jm1 | ysandeep|rover: okeeee ^^ | 14:00 |
| marios | rlandy: scrum time | 14:01 |
| marios | o/ | 14:01 |
| marios | folks tripleo-ci | 14:01 |
| marios | scrum time | 14:01 |
| marios | now | 14:01 |
| marios | join | 14:01 |
| dasm|off | o/ | 14:01 |
| marios | please | 14:01 |
| *** dasm|off is now known as dasm | 14:01 | |
| marios | thanks | 14:01 |
| marios | o/ | 14:01 |
| marios | \o | 14:02 |
| dasm | i'm gonna join after srbac | 14:02 |
| dasm | ~o~ | 14:02 |
| bhagyashris | https://code.engineering.redhat.com/gerrit/c/openstack/tripleo-ci-internal-jobs/+/399683/22/zuul.d/component-jobs.yaml#546 | 14:12 |
| dasm | marios: you're right. i should include depends-on for this: https://review.rdoproject.org/r/c/config/+/42619 | 14:27 |
| dasm | dependent patch is already merged. can you revisit your -1, marios? | 14:28 |
| dviroel | https://review.rdoproject.org/r/q/topic:ceph_promotion_pipeline | 14:36 |
| jm1 | akahat: thanks for the shellsheck patches! will have a look at code when i work on my ever growing review backlog again after rr 🙈 | 14:36 |
| jm1 | *shellcheck | 14:37 |
| akahat | jm1, sure. np :) | 14:37 |
| dasm | https://review.rdoproject.org/r/q/topic:pxe_uefi | 14:41 |
| dasm | https://review.opendev.org/q/topic:revive-elastic-recheck | 14:42 |
| ysandeep|rover | rlandy, jm1 fyi.. Victoria and 16.2 promoted as well | 14:49 |
| rlandy | we're having a rocking day | 14:50 |
| akahat | Folks, please review this, imp for OVB job run. https://review.rdoproject.org/r/c/config/+/42899 | 14:54 |
| ysandeep|rover | Tengu: I will miss checkpoint today - components promotions are up to date - updated the doc | 14:55 |
| ysandeep|rover | jm1, rlandy shutdown sequence.. need anything? | 15:00 |
| rlandy | ysandeep|rover: should be fine ... what's the story with wallaby c8? | 15:00 |
| jm1 | rlandy: rerun still in progress | 15:00 |
| akahat | chandankumar, rlandy marios ysandeep|rover please +w above patch ^^ | 15:00 |
| ysandeep|rover | rlandy, last failures were not on neutron bug.. jm1 have rerun the jobs once again | 15:01 |
| rlandy | ysandeep|rover: anything you want me to merge or watch? | 15:01 |
| jm1 | ysandeep|rover: thanks for doing all the work 🙈 | 15:01 |
| rlandy | ok - perfct | 15:01 |
| rlandy | jm1: pls let me know when you are EoD the status | 15:01 |
| rlandy | and if I need to do something about that | 15:01 |
| ysandeep|rover | rlandy: >> anything you want me to merge or watch? no, all good.. | 15:01 |
| ysandeep|rover | akahat, can check first thing tomorrow o/ | 15:02 |
| *** ysandeep|rover is now known as ysandeep|out | 15:02 | |
| ysandeep|out | jm1, see you tomorrow o/ have a good rest of your day | 15:02 |
| jm1 | rlandy: will have a break now while rerun jobs are in progress but will check back later today | 15:10 |
| jm1 | ysandeep|out: have a nice evening :) | 15:10 |
| marios | dasm: it needs rebase | 15:19 |
| dasm | marios: done. | 15:20 |
| dasm | rebased it 1h ago. it needed one more rebase | 15:21 |
| *** dviroel is now known as dviroel|lunch | 15:25 | |
| frenzy_friday | dasm, rlandy, card for ER discussions: https://issues.redhat.com/secure/RapidBoard.jspa?rapidView=11751&view=detail&selectedIssue=TRIPLEOCI-1044 (hackmd link in desc) | 15:28 |
| dasm | frenzy_friday: thx. | 15:28 |
| dasm | frenzy_friday: i'll start adding tasks under this epic to show the progress | 15:29 |
| frenzy_friday | dasm, yep sure. i added one for podman compose, feel free to add your face to it and update | 15:30 |
| dasm | k | 15:30 |
| *** marios is now known as marios|out | 15:37 | |
| rlandy | jm1: ha - fs035 on wallaby c8 is passing in the current run integration line | 15:44 |
| chandankumar | see ya! | 15:45 |
| dasm | rlandy: it sounds like we need to have a better way (automated?) of checking if skiplist is healthy | 15:49 |
| rlandy | dasm: indeed - asked bhagyashris to add an item to the sprint to address this | 15:56 |
| rlandy | per our planning meeting | 15:56 |
| dasm | ack | 15:56 |
| rlandy | dasm: sorry | 16:03 |
| rlandy | how's next week?? | 16:03 |
| rlandy | jm1: so for latest run on w c8 - on fs001 is failing - you can check the tempest hit when it reports | 16:04 |
| rlandy | lunch - brb | 16:05 |
| *** dviroel|lunch is now known as dviroel | 16:24 | |
| jm1 | rlandy: fs001 passed on wallaby c8, but fs35 failed with "failed to reach ACTIVE status" https://review.rdoproject.org/r/c/testproject/+/42888 | 16:24 |
| rlandy | jm1: lol | 16:25 |
| rlandy | different hashes? | 16:25 |
| jm1 | rlandy: so do we stick to our plan, merge the temp criteria patch and revert it once promoted? | 16:25 |
| rlandy | jm1: one sec - checking the hash | 16:25 |
| rlandy | https://trunk.rdoproject.org/api-centos8-wallaby/api/civotes_agg_detail.html?ref_hash=5951e9703b6eae17d1d3cf9312ab1eeb | 16:26 |
| rlandy | jm1: ^^ it should promote on its own | 16:26 |
| jm1 | rlandy: wait, does this mean all individual jobs of this hashed passed at least once? | 16:27 |
| jm1 | rlandy: but never at the same time? | 16:27 |
| rlandy | jm1: it does indeed | 16:27 |
| rlandy | so dlrn will promote | 16:27 |
| jm1 | rlandy: dlrn is happy as soon as each one passed at least once, it is not necessary to pass at the same time? | 16:28 |
| jm1 | rlandy: so we dont have to do anything? | 16:28 |
| rlandy | jm1: you are free | 16:28 |
| jm1 | rlandy: will look at ci degraded next | 16:29 |
| rlandy | jm1: http://promoter.rdoproject.org/promoter_logs/container-push/20220516-154104.log promotion in progress | 16:29 |
| jm1 | rlandy: ah okay i was looking at https://trunk.rdoproject.org/centos8-wallaby/current/, apparently to early ^^ | 16:30 |
| rlandy | jm1: need help with anything? | 16:30 |
| jm1 | rlandy: will have to check the cards first, so nope :) | 16:30 |
| rlandy | jm1: you can always check the promoter | 16:31 |
| rlandy | and you'll be looking to current-tripleo | 16:31 |
| rlandy | not current | 16:31 |
| rlandy | k - ping if needed | 16:31 |
| jm1 | rlandy: sure, thanks :) | 16:33 |
| jm1 | rlandy: c8 wallaby component network is failing in step "oooci-build-images : Remove fwupd-redfish.conf file from overcloud-hardened-uefi-full.qcow2", i think we saw this before a couple of times. but i cannot find a bug report. any idea? | 16:43 |
| rlandy | jm1: we did - it cleared up | 16:47 |
| rlandy | is that consistent | 16:47 |
| dviroel | https://opendev.org/openstack/tripleo-ci/commit/018f3ecf7e2100d873391a354086f17469514ecf | 16:49 |
| dviroel | "Remove fwupd-redfish.conf file from overcloud images" ^ | 16:49 |
| jm1 | dviroel: thanks! this was submitted 4 month ago 🤔 | 16:54 |
| jm1 | rlandy: it failed with same error message on 2022-05-10 and 2022-05-15, but in between it passed sometimes | 16:54 |
| rlandy | jm1: yep - it's transient | 16:55 |
| rlandy | is the network component the only one out? | 16:56 |
| jm1 | rlandy: nope, tripleo as well | 17:03 |
| jm1 | rlandy: since this error is coming again and again (even i saw it, although this is my second shift only) i did this quick hack to reproduce it https://review.rdoproject.org/r/c/testproject/+/42902 | 17:03 |
| jm1 | rlandy: will wait for tripleo component rerun and then see if this is the same error | 17:04 |
| jm1 | rlandy: okay tripleo component just passed 😂 | 17:05 |
| jm1 | rlandy: wallaby c8 tripleo component | 17:05 |
| rlandy | jm1: you've probably seen it often enough to track- I'd be interested to see if it shows up again after we promote this current hash | 17:07 |
| rlandy | because we did not see it in the integration line | 17:07 |
| jm1 | rlandy: we dont get the output of the virt-customize run, so its hard to know what is going on. my little hacky patch above adds debug flags, so hopefully we see some useful info | 17:09 |
| * jm1 brb | 17:12 | |
| rlandy | ok | 17:27 |
| *** rlandy is now known as rlandy|mtg | 18:14 | |
| *** rlandy|mtg is now known as rlandy | 19:30 | |
| dviroel | rlandy: hey o/ | 19:37 |
| rlandy | dviroel: hi | 19:37 |
| dviroel | rlandy: considering refactor container-login to support multiple registries, wdyt? | 19:37 |
| dviroel | this https://github.com/rdo-infra/review.rdoproject.org-config/blob/master/playbooks/tripleo-rdo-base/container-login.yaml | 19:37 |
| dviroel | idea is to create another playbook that do the same thing, but supports multiple registries, and validate it by switch one or two jobs to test | 19:39 |
| rlandy | dviroel: I have been editing the duplicate playbook of that in downstream | 19:39 |
| rlandy | sure | 19:39 |
| rlandy | I have one | 19:39 |
| rlandy | bit I don't think my secret is working out | 19:39 |
| * rlandy gets | 19:39 | |
| rlandy | I need to start work again on that now | 19:39 |
| dviroel | yep, the idea is to work on a loop, and call podman_login jus once | 19:40 |
| dviroel | so we don't need to duplicate things | 19:40 |
| rlandy | dviroel: my hacked version: https://code.engineering.redhat.com/gerrit/gitweb?p=openstack/tripleo-ci-internal-config.git;a=blob;f=playbooks/tripleo-rdo-base/container-login-test.yaml;h=d02963f838b0b821858c9b13d16cef2ca3c2c1ad;hb=HEAD | 19:40 |
| rlandy | open to better ideas | 19:41 |
| rlandy | a role would be better | 19:41 |
| rlandy | so we can reuse | 19:41 |
| dviroel | my idea is to loop over a list of registries and populate 'container_registry_logins' and afte that, call podman_login role just once, since it will iterate over 'container_registry_logins' | 19:43 |
| dviroel | tested on my side alredy ^ | 19:43 |
| dviroel | just need to create a smart way to provide registry + secret info | 19:44 |
| rlandy | dviroel: what do you mean 'smart way' | 19:46 |
| rlandy | in your loop? | 19:47 |
| jm1 | rlandy: instead of debugging this sporadic failures, i will try to revert the initial patch that brought these failures: https://review.opendev.org/c/openstack/tripleo-ci/+/841992 | 19:48 |
| rlandy | if we don;t need it anymore | 19:48 |
| dviroel | rlandy: a way that isn't painfull to provide in our jobs - we have some secrets data hardcoded in our playbook. | 19:48 |
| rlandy | you mean because it | 19:49 |
| rlandy | s config? | 19:49 |
| dviroel | like this: https://github.com/rdo-infra/review.rdoproject.org-config/blob/master/playbooks/tripleo-rdo-base/container-login.yaml#L36 | 19:49 |
| dviroel | the user is hardcoded, and the secret info too | 19:49 |
| jm1 | rlandy: that is what i am trying to find out. according to bz bug it has been fixed 6 days ago | 19:49 |
| rlandy | jm1: ok ... if we have the fix | 19:49 |
| rlandy | dviroel: charming and hard to test config | 19:50 |
| rlandy | we'd have to duplicate a test playbook | 19:50 |
| dviroel | rlandy: yes :) | 19:50 |
| rlandy | and try there | 19:50 |
| jm1 | rlandy: bz bug says it is fixed in c8s for a month. no worry, i will find out | 19:50 |
| rlandy | ok | 19:50 |
| rlandy | dviroel: if you want you can play downstream | 19:51 |
| rlandy | less chance of leaking info | 19:51 |
| rlandy | and fi you do, it's only internal | 19:51 |
| dviroel | rlandy: also a good idea, i can validate with the 2 logins that you need | 19:55 |
| * jm1 started a couple of jobs, will sleep while they are running ;) out for today | 20:08 | |
| rlandy | dviroel: go4it | 20:16 |
| rlandy | dviroel; I want to hold a node now to try confirm the secret and the username | 20:17 |
| rlandy | will let you know | 20:17 |
| dviroel | rlandy: the username is the one with | yet? | 20:20 |
| rlandy | dviroel: ack - I pulled the username out of secret | 20:21 |
| rlandy | so I could pass it in a jobs | 20:21 |
| rlandy | job | 20:21 |
| rlandy | at the point of testing that | 20:22 |
| rlandy | I can pass that test to you if you like | 20:22 |
| dviroel | i have a guess | 20:24 |
| dviroel | on https://code.engineering.redhat.com/gerrit/gitweb?p=openstack/tripleo-ci-internal-config.git;a=blob;f=playbooks/tripleo-rdo-base/container-login-test.yaml;h=d02963f838b0b821858c9b13d16cef2ca3c2c1ad;hb=HEAD#l117 | 20:24 |
| dviroel | you need extra quotes | 20:24 |
| dviroel | like this: "{'{{ quay_login_secret_name.username }}': '{{ quay_login_secret_name.passwd }}'}" | 20:24 |
| dviroel | on my local tests, only work in this way ^ | 20:25 |
| rlandy | dviroel: let me try | 20:26 |
| * rlandy digs up test | 20:28 | |
| dviroel | you may need them another extra quote for username too, since it has | on it, but you can do that on your job var | 20:29 |
| rlandy | dviroel: I tried: https://code.engineering.redhat.com/gerrit/c/testproject/+/200295/257/.zuul.yaml | 20:31 |
| rlandy | which didn't work | 20:31 |
| rlandy | if I add more quotes, idk | 20:31 |
| rlandy | https://code.engineering.redhat.com/gerrit/gitweb?p=openstack/tripleo-ci-internal-config.git;a=blob;f=playbooks/tripleo-rdo-base/container-login-test.yaml;h=d02963f838b0b821858c9b13d16cef2ca3c2c1ad;hb=HEAD#l117 | 20:32 |
| rlandy | so if I added more quotes there?? | 20:32 |
| rlandy | not sure | 20:32 |
| rlandy | dviroel: https://code.engineering.redhat.com/gerrit/gitweb?p=openstack/tripleo-ci-internal-config.git;a=blob;f=playbooks/tripleo-rdo-base/container-login-test.yaml;h=d02963f838b0b821858c9b13d16cef2ca3c2c1ad;hb=HEAD#l22 does not have double quotes | 20:33 |
| rlandy | thoughts? | 20:33 |
| dviroel | rlandy: good question, tested here with a test playbook. The problem is passing a ansible var on user. In this case ^ the user name is hardcoded, so thats why this one works | 20:34 |
| rlandy | let me try one more change one the var on the job | 20:35 |
| rlandy | long shot - but here goes | 20:36 |
| rlandy | dviroel: if you want to take this example to play with, with pleasure :) | 20:38 |
| dviroel | rlandy: yeah, i can work on this, np | 20:38 |
| dviroel | rlandy: without double quotes, tripleo_podman does that "podman login --username={{ dviroel_user }} --password=fake_pass registry2" | 20:39 |
| dviroel | rlandy: will continue with this tomorrow, no worries, i can use downstream to test | 20:51 |
| * dviroel going out | 20:51 | |
| *** dviroel is now known as dviroel|out | 20:51 | |
| rlandy | dviroel|out: thank you | 20:54 |
| rlandy | have a good night | 20:54 |
| dasm | dviroel|out: o/ | 20:55 |
| * dasm goes offline | 21:12 | |
| *** dasm is now known as dasm|off | 21:12 | |
| * rcastillo leaving for today | 21:48 | |
| *** rlandy is now known as rlandy|out | 23:05 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!