Thursday, 2022-07-14

opendevreviewVerification of a change to openstack/ironic master failed: Allocation candidates prefer matching name  https://review.opendev.org/c/openstack/ironic/+/84585600:03
opendevreviewMerged openstack/ironic master: Make anaconda non-image deploys sane  https://review.opendev.org/c/openstack/ironic/+/83470901:28
opendevreviewMerged openstack/ironic master: Trivial: log which state the node is in  https://review.opendev.org/c/openstack/ironic/+/84887401:37
opendevreviewVerification of a change to openstack/ironic-python-agent master failed: Drop support for instance netboot  https://review.opendev.org/c/openstack/ironic-python-agent/+/84896901:37
opendevreviewAija Jauntēva proposed openstack/ironic stable/yoga: Fix markup typo in Redfish driver docs  https://review.opendev.org/c/openstack/ironic/+/84981008:32
opendevreviewAija Jauntēva proposed openstack/ironic bugfix/20.2: Fix markup typo in Redfish driver docs  https://review.opendev.org/c/openstack/ironic/+/84981108:32
dtantsurmorning folks09:01
jandersgood morning dtantsur o/09:03
iurygregorygood morning Ironic11:29
timeuHi Ironic, did anybody notice a recent change in the trunk port implementation in the latest OSP 16.2.3 release ? For some reason the subport of the trunk has 'binding:vnic_type': 'normal' instead of 'binding:vnic_type': 'baremetal' which causes our SDN's ML2 driver not to properly bind the port. This worked in a previous OSP (16.2.2) release. 11:32
dtantsurI guess only OSP folks (TheJulia, hjensas, stevebaker[m]) know the diff11:35
timeuI am trying to bisect the changes and see if the issue came via a neutron minor upgrade or an upgrade of our SDN's plugin. 11:43
timeuthe parent port is properly bound but it also has barmetal as vnic_type while the subport has normal. I will dig through the code. 11:44
timeuIn other news the latest sushy 4.2.0 breaks redfish on the Lenovo hardware. I added a comment with the error message here: https://storyboard.openstack.org/#!/story/200968011:45
opendevreviewkamlesh chauvhan proposed openstack/ironic-tempest-plugin master: Add iDRAC RAID cleaning steps tests  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/84160111:47
timeuis there an easy way to find out which RPM version (i.e. openstack-neutron) corresponds to which upstream version ? 11:57
iurygregoryI think you have the information about the commit in the rpm name 12:42
iurygregoryso you could check the branch12:42
TheJuliaOpenstack releases with major and minor12:46
timeuiurygregory: thanks. This is the version that don't work neutron-15.3.5.dev132-py3.6 and this is the version it worked last time: neutron-15.2.1.dev12-py3.6. Not sure if this corresponds to the neutron git tags12:51
timeuIt's also really hard for me right now to figure out what the expected behavior is. Before binding the port the first time to a baremetal node the vnic_type is normal. Once ironic does its thing the vnic_type of the parent bound is set to baremetal. Not sure who should update the vnic_type of the subport ? Is it the trunk service ? ironic or the mechanism driver ? 12:53
iurygregory15.3.5 is probably the latest release from train (train-em tag...)12:53
iurygregoryhttps://opendev.org/openstack/releases/src/branch/master/deliverables/train/neutron.yaml12:53
TheJuliaIronic does the update12:54
timeuah thansk for the link I guess with this I can figure out the commits and see what changed 12:54
timeuok so it might not be a neutron thing but maybe a change in ironic12:54
timeuI will try to compare the 2 versions I have and see what I can figure out. So the last time it worked (at least when I tested it) it was still with OSP 16.1. I tried it now again with OSP 16.2.3 and it didn't. I have to leave for today. Will debug it further tomorrow12:57
TheJuliatimeu: I can look through changes in the packaging, but most likely taking tomorrow off12:59
timeuThanks. that would be great. it's not urgent. We are just testing the feature in our dev environment. One last question is networking-baremetal responsible for updating the port information or ironic itself ?13:00
kaloyanHey guys, I wanted to ask something else. We have this strange setup where we're migrating from an inhouse baremetal provisioning solution to Ironic and OpenStack in general (Nova, Neutron, Cinder). I have a machine with 6 ports on it, all described in Ironic. I've marked a port as PXE capable and configured the switches so that it and the rest of Neutrons' stack are in the13:06
kaloyansame vlan. The provider network is of type "flat" as well as the networking_interface field for that machine. When the machine boots, it loads up cloud-init and talks with Nova to fetch metadata. The network metadata received from Nova contains only one link as well as one network which is expected, since this is the only information Nova knows about. My question is the13:06
kaloyanfollowing: How can I make Nova send information for the remaining ports? Shall I add ports in Neutron that aren't attached to a network? 13:06
kaloyanHmmm, looking at the Ironic driver for Nova, it looks like it it generates a config drive that gets passed to ironic when the spawn method of the driver is called13:11
kaloyanHowever, when booting from volume (using iSCSI) this is no longer the case, as cloud-init would talk to the metadata service which would return network metadata that only Nova knows13:14
TheJuliatimeu: networking-baremetal does not update port info in ironic, it updates physical network mapping daata in neutron and tells port binding for flat networks that it is "successful"13:20
TheJuliatimeu: ironic does the update actions. fwiw, I don't think anything really changed there, but I'm aware of an issue with OVN in the mix that I'm wondering if maybe your encountering. Do you happen to be trying to use OVN?13:21
TheJuliakaloyan: I guess, for our context, the question for us to ask is what would you use the other interfaces for? if my memory is serving me correctly, it matches the mac address in cloud init and configures the interface...13:23
kaloyanWe intend to use them for testing our product (distributed storage software) so it requires networking13:24
TheJuliaso you can issue multiple vif attachments....13:27
TheJuliabut I don't think the metadata gets in nova, since it is for the machine to boot, the other interfaces work via dhcp13:27
* TheJulia checks the docs13:28
TheJuliakaloyan: so you can create an instance with multiple nics on launch13:29
TheJuliaand you'd need to have it's networks in neutron as well of course for that to work13:29
TheJuliaI would assume that the additional ports would be in the cloud-init metadata as well as have been setup configuration wise13:30
kaloyanTheJulia: hmm... I understand. Now, given the fact that Ironic "injects" the rest of the ports in the network metadata when using a config drive (https://opendev.org/openstack/nova/src/commit/de65131f92ba5ba812e33e6ff63be0991687413a/nova/virt/ironic/driver.py#L994) isn't it a good idea to do the same when requesting metadata from Nova?13:41
kaloyanI'm really trying to avoid declaring phantom Neutron networks and ports13:42
TheJuliawell, they aren't really phantom but it is a one or the other sort of thing13:46
TheJuliawe have no means to inject/modify the metadata 13:46
kaloyanI beleive this is a question that the team behind Nova should answer, isn't it?13:47
TheJulialikely13:47
TheJuliahowever, that pattern requires vifs to be registered which are neutron ports13:47
kaloyanyeah, I missed the part of the code that actually13:50
ashinclouds[m]I was reading it and going “wow, that is kind of not clear at a glance”13:51
ashinclouds[m]Err wrong client13:51
TheJulia\o:13:51
TheJuliaGah13:51
TheJuliaI need more coffee13:51
dtantsurhuh, CS9 broken in Bifrost?14:41
iurygregorynew results or something from yesterday?14:58
iurygregoryyesterday there was the problem with tarbals website14:59
dtantsurNo DHCP during iPXE15:00
dtantsur UTF-16 stream does not start with BOM <== has been fixed long ago, no?15:01
dtantsurmmm, yeah, I've got some old IPA in my metal3-dev-env15:04
dtantsuroh, https://images.rdoproject.org/centos8/master/rdo_trunk/current-tripleo/ hasn't been updated since February. oh.15:05
dtantsuranyone looking into the new jsonschema?15:33
dtantsur- Failed: 13415:37
dtantsurOMFG15:37
opendevreviewDmitry Tantsur proposed openstack/ironic master: Fix compatibility with jsonschema>=4.0.0  https://review.opendev.org/c/openstack/ironic/+/84988216:08
TheJuliawow16:37
TheJuliathat is all the wow16:37
* TheJulia goes and gets water to prepare for next call of the day16:42
dtantsuro/17:00
TheJuliagoodnight dtantsur 17:01
opendevreviewMerged openstack/ironic stable/yoga: Update known issue for iDRAC Swift firmware update  https://review.opendev.org/c/openstack/ironic/+/84963417:23
opendevreviewMerged openstack/ironic bugfix/20.2: Update known issue for iDRAC Swift firmware update  https://review.opendev.org/c/openstack/ironic/+/84963317:23
erbarrdoes OCP 4.10 use wallaby or xena?18:36
TheJuliadunno19:20
TheJuliaiurygregory: do you know?19:20
iurygregoryerbarr, none of them =) bugfix branches =)19:37
erbarrok, which one and how do they relate to release branches then? XD19:38
iurygregoryerbarr, for ironic is bugfix/19.019:39
iurygregorybufgix branches we cut them between stable releases19:39
iurygregoryerbarr, dos this answer your question ?19:43
erbarryea, thanks19:44
iurygregoryyw =)19:46
opendevreviewMerged openstack/ironic-python-agent master: Drop support for instance netboot  https://review.opendev.org/c/openstack/ironic-python-agent/+/84896922:00
JayFhttps://review.opendev.org/c/openstack/ironic/+/847136 trivial review of a doc update if someone wants to take a look22:26
opendevreviewVerification of a change to openstack/ironic master failed: Allocation candidates prefer matching name  https://review.opendev.org/c/openstack/ironic/+/84585623:02

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