summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix: make Intel CNA hardware manager none genericstein-eolstein-em3.6.5stable/steinQianbiao.NG2020-10-123-35/+35
| | | | | | | | | | | | | | Currently, IntelCnaHardwareManager inherits GenericHardwareManager which makes it a new "GenericHardwareManager" with "MAINLINE" priority. This causes all other hardware-managers with lower priority than "MAINLINE" never be used. To fix this, make IntelCnaHardwareManager inherit basic HardwareManager. Change-Id: I28b665d8841b0b2e83b132e1f25df95e03e7ba10 Story: 2008142 Task: 40882 (cherry picked from commit dc63d2f240698148e1de6c43251b89c7e5cfdf33) (cherry picked from commit fad38ee376b8fe7679f54c6ddfe984cd8f5ae6b7)
* Merge "Prevent un-needed iscsi cleanup" into stable/steinZuul2020-08-096-2/+22
|\
| * Prevent un-needed iscsi cleanupJulia Kreger2020-07-286-2/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we added software raid support, we started calling bootloader installation. As time went on, we ehnanced that code path for non RAID cases in order to ensure that UEFI nvram was setup for the instance to boot properly. Somewhere in this process, we missed a possible failure case where the iscsi client tgtadm may return failures. Obviously, the correct path is to not call iscsi teardown if we don't need to. Since it was always semi-opportunistic teardown, we can't blindly catch any error, and if we started iSCSI and failed to tear the connection down, we might want to still fail, so this change moves the logic over to use a flag on the agent object which one extension to set the flag and the other to read it and take action based upon that. Change-Id: Id3b1ae5e59282f4109f6246d5614d44c93aefa7c Story: 2007937 Task: 40395 (cherry picked from commit 2a56ee03b6ffb2d8c8f5ff553e90ecf6ee07f9af) (cherry picked from commit 4746f09b3dfa765684e6e20cf4b9742e1bb3bd62)
* | Merge "Fix TypeError on agent lookup failure" into stable/steinZuul2020-08-093-4/+84
|\ \
| * | Fix TypeError on agent lookup failureJulia Kreger2020-08-073-4/+84
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Agent lookups can fail as we presently use logging.exception, better known in our code as LOG.exception, which can also generate other fun issues on journald based systems where additional errors could be raised resulting in us being unable to troubleshoot the the actual issue. Because of the mis-use of LOG.exception and the default behavior of the backoff retry handler, the retry logic was also not functional as any error no matter how small caused IPA to just exit. Change-Id: Ic4608b7c6ff9773d1403926efb3d59869c71343b Story: 2007968 Task: 40465 (cherry picked from commit 5eab9bced63b2b9a6753cbbf594dda7ef9d03a3a) (cherry picked from commit e45ee3f64221962ad243f7df8bc123510c632935)
* | | Merge "improve error messages during node lookup failures" into stable/steinZuul2020-08-091-4/+15
|\ \ \ | |/ /
| * | improve error messages during node lookup failuresDoug Hellmann2020-07-301-4/+15
| |/ | | | | | | | | | | | | | | | | | | The error messages reported on the console when the agent can't find its node do not give enough information to debug the cause of the failure. This change adds some basic details like the URL of the API server and the addresses of the node being sought there. Change-Id: Ia54faf05c80159d1d5fde0b222627c673f1cffe3 (cherry picked from commit f7740c7919584389e907f66bdfa1b4f31c75ead1)
* | Pin Ironic Tempest PluginIury Gregory Melo Ferreira2020-08-032-1/+4
|/ | | | | | | Pin the ironic-tempest-plugin to an old version, so we don't run the net set of tests with wholedisk+partition Change-Id: Ib01db7f578b1b666b339bb7954529d0ee7225b1e
* Rescan devices before performing uefi checks3.6.4Julia Kreger2020-03-183-16/+59
| | | | | | | | | | | | | | | | With the fix to the uefi code path so secure boot works properly and is not accidently stomped on, we forgot to rescan the device and force the partition table to update, which is vital for iscsi based deploys. Conflicts: ironic_python_agent/extensions/image.py Depends-On: https://review.opendev.org/706960 Change-Id: Ic2f338be075e93a2ce8c76c706d37db9bf8792ea Story: 2007276 Task: 38713 (cherry picked from commit 6f1f9c7f6ed55689f5e738e7b6f01a5c789099e5)
* Skip read-only devices with metadata erase3.6.3Julia Kreger2020-02-053-0/+75
| | | | | | | | | | | | | | | | | | | | | | | | | HPE "Virtual Install Devices" appear as read-only block devices, and may... or may not be visible depending on the bios configuration state. These devices can no longer be disabled from the bios settings so the simplest course of action seems to be that we should handle the existence of a read-only device. In the event of secure erase, this is treated as a hard failure case and a driver_internal_info flag has been added to enable a future bypass method for knowledgable operators. Backport note: the unit tests have been modified to account for Python 2 Conflicts: ironic_python_agent/hardware.py ironic_python_agent/tests/unit/test_hardware.py Change-Id: Ief8b360d11e654d8fae3a04a2a9f8d474a06e167 Story: 2007229 Task: 38502 (cherry picked from commit cd7b2693f873bde72706f8b6ab8c1f21e68f0fd1)
* Avoid grub2-install when on UEFI boot modeIury Gregory Melo Ferreira2020-01-226-13/+569
| | | | | | | | | | | | | | | | | | This patch changes the workflow for whole disk images when using uefi. If we can identify the bootloader and it's valid we can update using efibootmgr since grub2-install have problems specially on secure boot mode. We also updated the regex to search for the uefi partition on the disk, since in some cases the parted command output can be without the FS for the partition with esp Flag. Adds the efibootmgr and efivar to tinyipa (since ipa-builder is not used in stable/train) Change-Id: I7167e71e5d2352a045565289b200e5530d0ba11d Story: #2006847 Task: #37435 (cherry picked from commit b6210be196fea271b2c49f89d3e1638517c1198c)
* Search for efi partitionIury Gregory Melo Ferreira2020-01-222-0/+70
| | | | | | | | | | | | | | This patch adds a function that will be responsible to identify the efi partition on a give device, this is necessary on the Software Raid scenario and when installing bootloader. Conflicts: ironic_python_agent/tests/unit/test_utils.py ironic_python_agent/utils.py Change-Id: I5f326db2d37b2a15090ec84e477e63f7d92e7447 Co-Authored-By: Raphael Glon <raphael.glon@corp.ovh.com> (cherry picked from commit 966356e58c786fab1b176767615c481d449076a2)
* Fix IPA execution issues due to lack of entropyPierre Riteau2019-11-223-1/+16
| | | | | | | | | | | | | | | | | | | | | | | | | While running TinyIPA stable/stein images in KVM virtual machines with Tenks, we noticed that IPA would start but not execute further, which appeared to be caused by a lack of entropy. This patch installs haveged, a simple entropy daemon [1], into the tinyipa ramdisk and starts it on boot, which resolves the issue. We first applied this change in ironic-python-agent-builder for master and stable/train with I7d47b7828733cc03c1ed6c370c451465a6d492b6 [2]. We still build stable/stein images from the ironic-python-agent repository, so we can't directly backport the commit. Additionally, we install haveged from source, because a Tiny Core extension is available only for x86, not for x86_64 [3]. We use version 1.9.4 as newer versions require a more recent GNU Automake. [1] http://www.issihosts.com/haveged/ [2] https://review.opendev.org/#/c/695080/ [3] http://tinycorelinux.net/8.x/x86_64/tcz/ Change-Id: I7d47b7828733cc03c1ed6c370c451465a6d492b6 Story: 2006911 Task: 37554
* Fix tox.ini to correctly test lower-constraintsDmitry Tantsur2019-10-011-2/+6
| | | | | | | | | Due to the way we currently define install_command, all test targets are using upper-constraints, including the lower-constraints one. This patch fixes it and adds standard things like passing proxy settings. Change-Id: I61c3b45ae591ea44688f29598cb8b802bb094423 (cherry picked from commit 91ed55678ee662df36794bf1f79153e6585023d6)
* Fix compatibility with Pint 0.5Dmitry Tantsur2019-09-252-1/+6
| | | | | | | Conversion from Quantity to int/long was added only in 0.5.2. Change-Id: I23f93d29a0624b77f4624c6af530971eb6a4c01b (cherry picked from commit 386654f602c86495515811dd741652a3b0292fd3)
* CI: stop using pyghmi from git masterDmitry Tantsur2019-07-315-5/+0
| | | | | Change-Id: I855e6e02a33bcf146497089319445d76652f0691 (cherry picked from commit e1b630dd841363d1e1d322628ce667705f309467)
* Merge "Stop logging lshw output, collect it with other logs instead" into ↵3.6.2Zuul2019-07-034-5/+13
|\ | | | | | | stable/stein
| * Stop logging lshw output, collect it with other logs insteadDmitry Tantsur2019-06-184-5/+13
| | | | | | | | | | | | | | | | | | | | The lshw output is huge even on virtual machines, and it pollutes the debug logging. This change silences it. Instead, the lshw output is collected as part of the ramdisk logs. Depends-On: https://review.opendev.org/#/c/665635/ Change-Id: I6a3015b2d8d09f6f48b5cbd39dc84bd75b72f909 (cherry picked from commit 94048fe97e93af3ad6902c3c1aa4ec5d92b41747)
* | Correct formatting of a warning when lshw cannot be runDmitry Tantsur2019-06-271-1/+1
|/ | | | | Change-Id: I7c55aee4b3b52cb414a595cf548e1f22e954f619 (cherry picked from commit 69064a8610134f7e6777083375487f15f7dbbc7b)
* Merge "Add more channel number for detecting BMC IP address" into stable/stein3.6.1Zuul2019-05-212-3/+11
|\
| * Add more channel number for detecting BMC IP addressDongcan Ye2019-05-082-3/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | IPMI SPEC[1] assignment channel number 1-11 for vendors implementation(We an search "Channel Numbers" in section 6.3). We met an baremetal product, like H3C, use number 8 as LAN channel. Current code limit channel number to 1~7, I think this can increase to 1~11. [1] https://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/ipmi-second-gen-interface-spec-v2-rev1-1.pdf Change-Id: I63a6ff91d702b990ef09da13e6e2e269e7274cce Task: 30654 Story: 2005528 (cherry picked from commit 66d3c8e453a58c01740581079045e9b4368c4bde)
* | Merge "Do not use metadata checksums with ext4" into stable/steinZuul2019-05-211-0/+5
|\ \
| * | Do not use metadata checksums with ext4Riccardo Pittau2019-05-151-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove metadata_csum option when creating filesystems since cirros doesn't support it. This option was added in Debian stretch and Ubuntu bionic as default and it breaks compatibility with filesystems created with older versions. (cherry picked from commit 4e086f9f0fa2cfdd215994c76025bdb7954e3610) Change-Id: I6772e455f5d1ee7587c2dc43203b02e5e54cb714
* | | Merge "Ironic python agent does not extract correct available memory" into ↵Zuul2019-05-173-12/+231
|\ \ \ | |/ / |/| | | | | stable/stein
| * | Ironic python agent does not extract correct available memoryUros Orozel2019-04-163-12/+231
| | | | | | | | | | | | | | | | | | | | | | | | | | | This patch fixes parsing of memory class output of lshw output. Task: 30201 Story: 2005308 Change-Id: I0e7ff9f86a266d2f798457136fed0100c78569e2 (cherry picked from commit d8018b9f35172b22475984a921fadd439c5239cc)
* | | Merge "Bind mount /run into chroot when installing grub" into stable/steinZuul2019-05-083-1/+21
|\ \ \ | |_|/ |/| |
| * | Bind mount /run into chroot when installing grubDerek Higgins2019-05-023-1/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | grub-mkconfig runs a lvs command that attempts to access /run/lvm once for each block device, currently it times out after 10 seconds for each device and moves on. Multiple 10 second delays become a problem (causing IPA API timeouts) when multiple block devices are present. Bind mounting in /run avoids the delay and the timeouts. Task: 30616 Story: 2005507 Change-Id: Iae8b7808a35bff121f64971aadd4bd36b5f5bb71 (cherry picked from commit 9c35f0279209ce233a7562f2d9310ded1e0edba5)
* | | Merge "Fix download upper constraints" into stable/steinZuul2019-04-301-1/+1
|\ \ \
| * | | Fix download upper constraintsRiccardo Pittau2019-04-251-1/+1
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We use the url from tox.ini to download the upper constraints and recently that has changed to a redirect and curl doesn't correctly follows redirects by default but stops at the first page. Adding -L option to curl command makes curl follows the redirect until the final location is found and should allow the correct file to be downloaded. Change-Id: I25c724ffe189d414643c910be0ef61c550f802b7 (cherry picked from commit a88e61959bc41a10de5f58f8a1ffc34ae6f1e822)
* | | Merge "Fetch upper constraints from opendev.org" into stable/steinZuul2019-04-291-1/+1
|\ \ \
| * | | Fetch upper constraints from opendev.orgPavlo Shchelokovskyy2019-04-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the imagebuild/common/generate_upper_constraints.sh is currently failing as the curl command in this file does not handle redirects. Instead of allowing redirects, use the proper current link to the upper constraints file. Change-Id: I92c5bfa65ba149687f61172c2a89ff38660a58cf (cherry picked from commit 93dae93d52c8eec10d4e94f16b460443075ec129)
* | | | Merge "Switch to Debian Stretch for building CoreOS images" into stable/steinZuul2019-04-261-7/+3
|\ \ \ \ | |_|/ / |/| | |
| * | | Switch to Debian Stretch for building CoreOS imagesDmitry Tantsur2019-04-171-7/+3
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | It seems that Jessie is no longer supported, and its backports repo is no longer available, hence all CoreOS jobs fail. Also install setuptools into the environment explicitly, since some dependencies fail to install without it. Change-Id: I751522209d07caa26422a75b108f8c8baf782028 (cherry picked from commit ac4904ed960dabe94a4b6a3ceff9b4038e61f24f)
* | | OpenDev Migration PatchOpenDev Sysadmins2019-04-199-31/+31
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
* | Replace openstack.org git:// URLs with https://Ian Wienand2019-03-245-9/+9
|/ | | | | | | | | | | | | | | | | This is a mechanically generated change to replace openstack.org git:// URLs with https:// equivalents. This is in aid of a planned future move of the git hosting infrastructure to a self-hosted instance of gitea (https://gitea.io), which does not support the git wire protocol at this stage. This update should result in no functional change. For more information see the thread at http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html Change-Id: I8cb21cd82c61069b73db6ecbdfe5ca427cefcb97
* Update UPPER_CONSTRAINTS_FILE for stable/steinOpenStack Release Bot2019-03-201-1/+1
| | | | | | | | | | | | Update the URL to the upper-constraints file to point to the redirect rule on releases.openstack.org so that anyone working on this branch will switch to the correct upper-constraints list automatically when the requirements repository branches. Until the requirements repository has as stable/stein branch, tests will continue to use the upper-constraints list on master. Change-Id: Id873c61b2c9becd7920855ae10aa31aa2e3a5bf0
* Update .gitreview for stable/steinOpenStack Release Bot2019-03-201-0/+1
| | | | Change-Id: I6e507e5d948c10721d9c4b9d6736f5799787d92b
* Update release notes3.6.0Dmitry Tantsur2019-03-186-18/+15
| | | | Change-Id: I409379f72c8bb42b73e0f3aef8226904975d06ff
* Correct clean_build command according to MakefileCandy Tsai2019-03-121-1/+1
| | | | | | | The Makefile's command to clean only the tinyipa ramdisk build is `make clean_build`, adjust the name according to the Makefile. Change-Id: Icb9f2b7213de4be1eda71d92150f76e5efd72887
* Merge "Update python-hardware requirement for py3"Zuul2019-03-081-1/+2
|\
| * Update python-hardware requirement for py3Julia Kreger2019-03-081-1/+2
| | | | | | | | Change-Id: I8528a8738ce54fe2af04244cbe917422eb78fca7
* | Replace ZUUL_REFNAME for zuul.branchIury Gregory Melo Ferreira2019-03-051-3/+2
| | | | | | | | | | | | | | Replace `ZUUL_REFNAME` in favor of `zuul.branch` to get the correct branch name when building images. Change-Id: I6fe33b2f17c742d57d19985169cd9800007b5768
* | Run the imagebuild post playbook on all hostsDmitry Tantsur2019-03-011-1/+1
| | | | | | | | | | | | | | | | The "primary" host is an artifact of legacy playbooks. It does not exist in new zuul v3 jobs, and thus the publish does not happen. We probably need to rework the whole job again one day, but for now use hosts:all. Change-Id: I398e3b2b36795c7773afc27ead08d70eee0069ed
* | Update path for publish jobsIury Gregory Melo Ferreira2019-03-012-7/+7
| | | | | | | | | | | | | | - Use `src/git.openstack.org/openstack/<project>` instead of `src/<project>` Change-Id: Idd92d33e82abc9d4946c71e45f68e9e1713a0b95
* | Allow image checksum to be a URLDmitry Tantsur2019-02-254-34/+186
| | | | | | | | | | | | | | | | | | We allow image_source to be a URL, let us also support URLs for checksums. This change copies handling of multi-file checksum files from metalsmith. Change-Id: Ie4d7e5c79b76bdd72d50eeb384cf10519278a80c Story: #2005061 Task: #29605
* | Merge "Move to zuulv3"Zuul2019-02-216-283/+43
|\ \
| * | Move to zuulv3Iury Gregory Melo Ferreira2019-02-086-283/+43
| | | | | | | | | | | | | | | Depends-On: https://review.openstack.org/#/c/630100/ Change-Id: I69edcd2c0356bc1577e2a5974b004585b37469ca
* | | Merge "Add secondary sorting by name when guessing root disk"Zuul2019-02-134-6/+81
|\ \ \
| * | | Add secondary sorting by name when guessing root diskArne Wiebalck2019-02-114-6/+81
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As some BIOSes try to boot only from the "first" disk, Ironic should order potential disks not only by size, but also by name. This patch proposes to add secondary sorting by device name when identifying the root disk. Change-Id: I4017c839eeb9d00d2b4ad5b90e4e9b65b74296c7 Story: #2004976 Task: #29434
* | | | Merge "Building tinyipa with python3 by default"Zuul2019-02-093-2/+11
|\ \ \ \
View Lorry Controller Status