Monday, 2022-06-06

opendevreviewIan Wienand proposed opendev/base-jobs master: DNM: trying to fail job  https://review.opendev.org/c/opendev/base-jobs/+/84475400:52
ianwthat df thing has got me a few times too.  interestingly it worked for ^ 00:59
ianwi grepped all the executor logs, and didn't find any current instances where it seemed to fail01:03
opendevreviewIan Wienand proposed opendev/base-jobs master: DNM: trying to fail job  https://review.opendev.org/c/opendev/base-jobs/+/84475401:12
opendevreviewIan Wienand proposed opendev/base-jobs master: DNM: trying to fail job  https://review.opendev.org/c/opendev/base-jobs/+/84475401:39
opendevreviewIan Wienand proposed opendev/base-jobs master: DNM: trying to fail job  https://review.opendev.org/c/opendev/base-jobs/+/84475403:25
ianwinteresting, timing out the job and also filling up the disk during execution don't appear to trigger this behaviour03:49
opendevreviewIan Wienand proposed opendev/base-jobs master: DNM: trying to fail job  https://review.opendev.org/c/opendev/base-jobs/+/84475404:01
*** gibi is now known as gibi_summit06:01
StutiArya[m]Hi, I am trying to push my stable branch changes to master branch, whenever I try to push I get below error :... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/JjcFancgqWYvHlvuLFZqMCrF)07:20
Clark[m]Stuti Arya: can you share what repository you are working with and what command you are running?07:21
fungifwiw, that doesn't look like an error from git-review itself07:25
StutiArya[m]I have made changes to stable/xena branch in x/networking-infoblox, then did... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/tntgCQhDTjFNdbuNVFnTGmcX)07:26
fungiStutiArya[m]: make sure you're following https://docs.opendev.org/opendev/infra-manual/latest/gettingstarted.html#getting-started for setting up your account and tools correctly07:28
StutiArya[m]fungi: yes, I am following this Document 07:29
Clark[m]Stuti Arya: the issue is that `git push` takes a remote as the first argument. In this case there is no git remote named master. But generally our docs won't recommend pushing directly07:30
Clark[m]the expectation is that all changes are pushed for review to special gerrit refs (something that git-review does for you automatically) and not directly to the branch07:30
fungihttps://docs.opendev.org/opendev/infra-manual/latest/gettingstarted.html#proposing-a-change07:30
fungi(note nowhere does it tell you to use `git push`)07:31
fungiStutiArya[m]: can you be more specific about what you mean by "push my stable branch changes to master branch"? are you using git cherry-pick to pick those changes to the other branch?07:33
fungithe exact commands you're running and the repository you're running them on will be necessary for us to be able to provide better guidance07:33
Clark[m]fungi: the steps are in one of the previous messages which may have been truncated by irc with a link to them07:33
fungioh, i missed the second message, yes07:34
StutiArya[m]fungi: I am running below cmds:... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/QBCeKGhBVzeQijRAWjsPJOYZ)07:34
fungiokay, so you're trying to push a merge commit, it sounds like?07:35
*** ysandeep is now known as ysandeep|lunch07:36
StutiArya[m]> <@sarya009:matrix.org> fungi: I am running below cmds:... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/QsYWMUnwftYNVDrNTLzGVECd)07:36
fungianyway, `git review master` will override the branch detection from the stable branch .gitreview file, but you're probably better off cherry-picking those commits to master and then `git review` in master should pick the correct branch and create new changes07:36
fungialso, your `git merge stable` is overwriting the master branch .gitreview file, which is a bad idea07:39
fungithose files need to be branch-specific07:39
clarkblooking at the POST_FAILURES monasca-common fails due to the git cross user permissions error in a post run playbook. I think we can ignore that set of failures07:43
clarkbkolla has an error with a read timeout pushing to quay.io. Can also ignor ethat one07:44
clarkbglance failed devstack which prevented glance from being installed which broke some post-run play that runs glance commands07:45
clarkbthe more I look at not OSA the more I think the OSA problems may be OSA specific07:45
fungiseems that way, yes07:46
fungilemme see if the autohold from last night caught anything yet07:46
fungiyeah, 104.239.175.148 looks like one. that was for node request 300-0018332716 associated with build https://zuul.opendev.org/t/openstack/build/4b0e0c1d64c0471f8b1ac330d21b6e22 which was a stable/wallaby periodic pipeline job which ended in a normal FAILURE result due to what looks like it broke when trying to start some nova services07:56
funginoonedeadpunk: i'm guessing that's not useful, so i'm going to release it and reset the autohold07:56
fungiif you want it scoped to a specific change you're rechecking in order to try to reproduce the problem, that may help narrow it a bit07:56
fungianyway, i've got a general autohold for --project=openstack/openstack-ansible --tenant=openstack --job=openstack-ansible-deploy-aio_lxc-ubuntu-focal at the moment07:58
clarkbhttps://github.com/jwilk/python-syntax-errors is an interesting idea08:03
fungii agree, it's an awesome idea... but no license declared for any of it?08:15
fungii would feel weird reusing those08:15
StutiArya[m]<fungi> "anyway, `git review master` will..." <- is there any other method than cherry pick?08:19
fungiStutiArya[m]: updating your project's gerrit acl to allow pushing merge commits08:20
fungibut those are very hard to review and can create a mess if you're not extremely careful08:21
StutiArya[m]> <@_oftc_fungi:matrix.org> anyway, `git review master` will override the branch detection from the stable branch .gitreview file, but you're probably better off cherry-picking those commits to master and then `git review` in master should pick the correct branch and create new changes08:21
StutiArya[m] * is there any other method than cherry pick?08:21
StutiArya[m]I am getting version compatibility error with master, but originally stable/xena was created from master08:21
fungifor example, messes like just merging to master without being careful to omit the .gitreview file08:21
fungii don't understand what "getting version compatibility error with master" means08:22
fungiplease reference specific error messages and specific commands which are resulting in them08:23
StutiArya[m]https://review.opendev.org/c/x/networking-infoblox/+/84349808:23
fungi"ERROR: Cannot install Babel==2.9.1 because these package versions have conflicting dependencies" https://zuul.opendev.org/t/openstack/build/489d7839fc8f4d95904eab1eb1d1c340/log/job-output.txt#63608:26
fungithat looks like a python packaging version mismatch08:26
StutiArya[m]why this is not working with master branch and working with stable branch08:27
StutiArya[m]if I will go and change stable/branch maybe I will get new version mismatch errors08:27
StutiArya[m]Is there any solution for this?08:28
fungiyou could try to reproduce it locally and compare `tox -e pep8` output between stable/xena and master08:30
StutiArya[m]fungi: https://zuul.opendev.org/t/openstack/build/0d93b1396ced40ab8634dba987ef108708:44
StutiArya[m] * fungi: https://zuul.opendev.org/t/openstack/build/0d93b1396ced40ab8634dba987ef108708:45
StutiArya[m]I am getting this error now- ERROR: Cannot install Babel==2.10.1 because these package versions have conflicting dependencies08:45
fungipep8 installdeps: -c/home/zuul/src/opendev.org/openstack/requirements/upper-constraints.txt, -r/home/zuul/src/opendev.org/x/networking-infoblox/requirements.txt, -r/home/zuul/src/opendev.org/x/networking-infoblox/test-requirements.txt08:48
fungihttps://opendev.org/openstack/requirements/src/branch/master/upper-constraints.txt#L55908:49
StutiArya[m]what rebase does ?08:52
fungioh, this is on stable/xena not master08:53
StutiArya[m]fungi: yes08:53
fungihttps://opendev.org/x/networking-infoblox/src/branch/stable/xena/requirements.txt#L5 and https://opendev.org/openstack/requirements/src/branch/stable/xena/upper-constraints.txt#L559 disagree, which is the reason for your error08:55
fungithis has nothing to do with opendev, this is an openstack-related software development problem you're having08:56
StutiArya[m]How can I resolve this?09:01
fungiavoid using specific version pins in your requirements files if you're also going to use pinned constraints09:04
fungiyour master branch does "Babel>=1.3" which is fine in combination with the "Babel===2.10.1" constraint in the openstack/requirements master branch09:06
fungibut on stable/xena you have "Babel==2.9.1" which conflicts with the "Babel===2.9.1" constraint in the stable/xena branch of openstack/requirements09:07
fungier, no that's the same version isn't it09:08
* fungi looks closer09:08
clarkbit might be a python version problem09:08
clarkblooks like maybe 3.6 or newer is required09:09
fungioh, that's coming from your proposed change: https://review.opendev.org/c/x/networking-infoblox/+/844789/1/requirements.txt09:09
clarkboh thats for latest babel09:09
clarkb2.9.1 does python2.7 and 3.4 or newer09:09
fungiso the error message is quite straightforward. your change updates requirements.txt to "Babel==2.10.1" which conflicts with the "Babel===2.9.1" in stable/xena of openstack/requirements09:10
*** ysandeep|lunch is now known as ysandeep09:15
*** jpena|off is now known as jpena09:37
opendevreviewClark Boylan proposed zuul/zuul-jobs master: Add thhe post-reboot-tasks role  https://review.opendev.org/c/zuul/zuul-jobs/+/84470409:41
opendevreviewClark Boylan proposed zuul/zuul-jobs master: Add the post-reboot-tasks role  https://review.opendev.org/c/zuul/zuul-jobs/+/84470410:03
clarkbI'm not sure why the linter is failing on that now. It seems like it is angry about things in othe rfiles which might indicate a new version of the linter however I recognize some of those rules as being old ? I dunno10:04
clarkbwe skip experimental so maybe those rules moved from experimental to not experimental10:08
opendevreviewClark Boylan proposed zuul/zuul-jobs master: Add the post-reboot-tasks role  https://review.opendev.org/c/zuul/zuul-jobs/+/84470410:13
clarkbif you look at the diff between those two patchsets please don't laugh at me. I blame jet la10:15
*** pojadhav is now known as pojadhav|afk11:14
*** ysandeep is now known as ysandeep|break11:39
opendevreviewClark Boylan proposed zuul/zuul-jobs master: Add the post-reboot-tasks role  https://review.opendev.org/c/zuul/zuul-jobs/+/84470411:45
*** dviroel|out is now known as dviroel11:51
opendevreviewClark Boylan proposed zuul/zuul-jobs master: Add the post-reboot-tasks role  https://review.opendev.org/c/zuul/zuul-jobs/+/84470411:56
*** ysandeep|break is now known as ysandeep12:46
*** pojadhav|afk is now known as pojadhav13:18
*** ysandeep is now known as ysandeep|brb14:25
*** ysandeep|brb is now known as ysandeep14:33
*** dviroel is now known as dviroel|lunch15:12
johnsomIs there a way that I am missing for a core to remove the "Work In Progress" flag in gerrit that someone else pressed? Not the "-1" WIP vote, but the new "Mark as work in progress" option? Someone set this on a patch because another patch needed to land first (yes, I know) then went on vacation. This seems to be blocking the +W on that patch.15:20
johnsomhttps://review.opendev.org/c/openstack/designate/+/84415215:20
johnsomUpdates to the patch don't seem to clear it either.15:21
Clark[m]johnsom: not currently. That is the main reason we haven't dropped the -W vote system15:27
Clark[m]I think an admin can unset it but I'm not sure of the details on that15:27
johnsomOk, thanks. I don' think this is critical, but was wondering if I was missing something.15:28
fungiyeah, right now there's no acl to control it, so it's only possible for the change owner or admins to set/remove15:43
*** marios is now known as marios|out15:45
*** ysandeep is now known as ysandeep|out15:53
*** dviroel|lunch is now known as dviroel16:22
*** jpena is now known as jpena|off17:15
opendevreviewMerged openstack/project-config master: grafana ceph: add nova stable/(xena|yoga) branches  https://review.opendev.org/c/openstack/project-config/+/83551418:54
*** mnasiadka_ is now known as mnasiadka19:53
*** dviroel is now known as dviroel|afk19:57
code_bleuhello21:22
code_bleuwell poo.. I guess this client isn't working...no one saying anything. if you do see this, I'd appreciate the acknowledgement that it works...and won't bug you anymore.21:25
BlaisePabon[m]LGTM21:26
BlaisePabon[m]code_bleu: Di you have a specific question?21:27
code_bleuBlaisePabon[m]  thanks...now I know it works at least21:27
code_bleuyes21:27
code_bleuI've been struggling to find the right path to get policy.yaml file to work.  I have the config in nova.conf setup with policy_dirs and policy_file...I used the oslopolicy-sample-generator  --namespace nova to create the policy.yaml file.  For testing, I'm trying to get a non-admin user be able to do an 'openstack host list', but nothing is working21:27
fungicode_bleu: that sounds like an openstack project question. the #opendev channel is where we discuss our source code hosting, collaboration and test automation platform, per the /topic22:09
fungiyou probably want the #openstack channel, or to post on the openstack-discuss@lists.openstack.org mailing list22:10
opendevreviewMerged openstack/diskimage-builder master: Remove py 3.6 support and update jobs  https://review.opendev.org/c/openstack/diskimage-builder/+/83622923:18

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