From e18f9779ab00fee7f31dd1ad9002dd7b799657a8 Mon Sep 17 00:00:00 2001 From: Stanislaw Kardach Date: Sat, 14 May 2016 23:55:11 -0700 Subject: Fix improperly exported patches Signed-off-by: Stanislaw Kardach --- ...Ubuntu-Blacklist-rtc-efi-if-not-supported.patch | 35 ---------------------- ...Ubuntu-Blacklist-rtc-efi-if-not-supported.patch | 35 ++++++++++++++++++++++ ...rease-maximum-shell-command-timeout-to-2h.patch | 33 ++++++++++++++++++++ ...01-Increase-maximum-shell-command-timeout.patch | 33 -------------------- ...E-Disable-amd64-Liberty-on-Ubuntu-for-now.patch | 2 +- ...configuration-item-for-WSREP-SST-provider.patch | 2 +- 6 files changed, 70 insertions(+), 70 deletions(-) delete mode 100644 patches/fuel-agent/0010-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch create mode 100644 patches/fuel-agent/0011-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch create mode 100644 patches/fuel-astute/0001-Increase-maximum-shell-command-timeout-to-2h.patch delete mode 100644 patches/fuel-astute/0001-Increase-maximum-shell-command-timeout.patch (limited to 'patches') diff --git a/patches/fuel-agent/0010-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch b/patches/fuel-agent/0010-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch deleted file mode 100644 index b0c32f4f..00000000 --- a/patches/fuel-agent/0010-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch +++ /dev/null @@ -1,35 +0,0 @@ -From: Alexandru Avadanii -Date: Mon, 9 May 2016 21:46:51 +0200 -Subject: [PATCH] target Ubuntu: Blacklist rtc-efi if not supported. - -Older ThunderX and possibly other UEFI-enabled targets do not support -rtc-efi properly, so they end up filling dmesg with useless -complaints about not being able to read system time. - -Target OS (Ubuntu) deployment already has a snippet that blacklists -i2c_piix4 in certain scenarios, so provide a similar test for rtc_efi. ---- - cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2 | 10 ++++++++-- - 1 file changed, 8 insertions(+), 2 deletions(-) - -diff --git a/cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2 b/cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2 -index 253be2d..9758376 100644 ---- a/cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2 -+++ b/cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2 -@@ -49,8 +49,14 @@ cloud-init-per instance resolv_conf_head_nameserver /bin/sh -c 'echo nameserver - # configure black module lists - # virt-what should be installed - if [ ! -f /etc/modprobe.d/blacklist-i2c_piix4.conf ]; then -- ( (virt-what | fgrep -q "virtualbox") && echo "blacklist i2c_piix4" >> /etc/modprobe.d/blacklist-i2c_piix4.conf || :) && update-initramfs -u -k all -- modprobe -r i2c_piix4 -+ ( (virt-what | fgrep -q "virtualbox") && \ -+ ( echo "blacklist i2c_piix4" >> /etc/modprobe.d/blacklist-i2c_piix4.conf && \ -+ update-initramfs -u -k all && modprobe -r i2c_piix4 ) || :) -+fi -+if [ ! -f /etc/modprobe.d/blacklist-rtc_efi.conf ]; then -+ ( /bin/cat /sys/class/rtc/rtc0/time > /dev/null 2>&1 ) || \ -+ ( echo "blacklist rtc_efi" >> /target/etc/modprobe.d/blacklist-rtc_efi.conf && \ -+ update-initramfs -u -k all && modprobe -r rtc_efi ) - fi - - cloud-init-per instance conntrack_ipv4 /bin/sh -c 'echo nf_conntrack_ipv4 | tee -a /etc/modules' diff --git a/patches/fuel-agent/0011-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch b/patches/fuel-agent/0011-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch new file mode 100644 index 00000000..b0c32f4f --- /dev/null +++ b/patches/fuel-agent/0011-target-Ubuntu-Blacklist-rtc-efi-if-not-supported.patch @@ -0,0 +1,35 @@ +From: Alexandru Avadanii +Date: Mon, 9 May 2016 21:46:51 +0200 +Subject: [PATCH] target Ubuntu: Blacklist rtc-efi if not supported. + +Older ThunderX and possibly other UEFI-enabled targets do not support +rtc-efi properly, so they end up filling dmesg with useless +complaints about not being able to read system time. + +Target OS (Ubuntu) deployment already has a snippet that blacklists +i2c_piix4 in certain scenarios, so provide a similar test for rtc_efi. +--- + cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2 | 10 ++++++++-- + 1 file changed, 8 insertions(+), 2 deletions(-) + +diff --git a/cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2 b/cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2 +index 253be2d..9758376 100644 +--- a/cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2 ++++ b/cloud-init-templates/boothook_fuel_7.0_ubuntu.jinja2 +@@ -49,8 +49,14 @@ cloud-init-per instance resolv_conf_head_nameserver /bin/sh -c 'echo nameserver + # configure black module lists + # virt-what should be installed + if [ ! -f /etc/modprobe.d/blacklist-i2c_piix4.conf ]; then +- ( (virt-what | fgrep -q "virtualbox") && echo "blacklist i2c_piix4" >> /etc/modprobe.d/blacklist-i2c_piix4.conf || :) && update-initramfs -u -k all +- modprobe -r i2c_piix4 ++ ( (virt-what | fgrep -q "virtualbox") && \ ++ ( echo "blacklist i2c_piix4" >> /etc/modprobe.d/blacklist-i2c_piix4.conf && \ ++ update-initramfs -u -k all && modprobe -r i2c_piix4 ) || :) ++fi ++if [ ! -f /etc/modprobe.d/blacklist-rtc_efi.conf ]; then ++ ( /bin/cat /sys/class/rtc/rtc0/time > /dev/null 2>&1 ) || \ ++ ( echo "blacklist rtc_efi" >> /target/etc/modprobe.d/blacklist-rtc_efi.conf && \ ++ update-initramfs -u -k all && modprobe -r rtc_efi ) + fi + + cloud-init-per instance conntrack_ipv4 /bin/sh -c 'echo nf_conntrack_ipv4 | tee -a /etc/modules' diff --git a/patches/fuel-astute/0001-Increase-maximum-shell-command-timeout-to-2h.patch b/patches/fuel-astute/0001-Increase-maximum-shell-command-timeout-to-2h.patch new file mode 100644 index 00000000..d7048954 --- /dev/null +++ b/patches/fuel-astute/0001-Increase-maximum-shell-command-timeout-to-2h.patch @@ -0,0 +1,33 @@ +From: Stanislaw Kardach +Date: Mon, 9 May 2016 18:54:33 -0700 +Subject: [PATCH] Increase maximum shell command timeout to 2h + +Since `execute_shell_command` mcagent is used for building the target +image and the timeout provided in the astute task is just respected on +the Astute level (on mcollective level this timeout is actually a +minumum between value provided and ddl value) we need to increase it +for Armband operation. + +Because Armband builds the target image via `qemu-debootstrap`, it can +take more than 1 hour to finish the building. Therefore aside of +increasing the timeout in the Astute task, the maximum timeout value +for mcagent has to be increased. + +Signed-off-by: Stanislaw Kardach +--- + mcagents/execute_shell_command.ddl | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/mcagents/execute_shell_command.ddl b/mcagents/execute_shell_command.ddl +index 0480be7..ad58046 100644 +--- a/mcagents/execute_shell_command.ddl ++++ b/mcagents/execute_shell_command.ddl +@@ -4,7 +4,7 @@ metadata :name => "Execute shell command", + :license => "Apache License 2.0", + :version => "8.0.0", + :url => "http://mirantis.com", +- :timeout => 3600 ++ :timeout => 7200 + + action "execute", :description => "Execute shell command" do + diff --git a/patches/fuel-astute/0001-Increase-maximum-shell-command-timeout.patch b/patches/fuel-astute/0001-Increase-maximum-shell-command-timeout.patch deleted file mode 100644 index d7048954..00000000 --- a/patches/fuel-astute/0001-Increase-maximum-shell-command-timeout.patch +++ /dev/null @@ -1,33 +0,0 @@ -From: Stanislaw Kardach -Date: Mon, 9 May 2016 18:54:33 -0700 -Subject: [PATCH] Increase maximum shell command timeout to 2h - -Since `execute_shell_command` mcagent is used for building the target -image and the timeout provided in the astute task is just respected on -the Astute level (on mcollective level this timeout is actually a -minumum between value provided and ddl value) we need to increase it -for Armband operation. - -Because Armband builds the target image via `qemu-debootstrap`, it can -take more than 1 hour to finish the building. Therefore aside of -increasing the timeout in the Astute task, the maximum timeout value -for mcagent has to be increased. - -Signed-off-by: Stanislaw Kardach ---- - mcagents/execute_shell_command.ddl | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/mcagents/execute_shell_command.ddl b/mcagents/execute_shell_command.ddl -index 0480be7..ad58046 100644 ---- a/mcagents/execute_shell_command.ddl -+++ b/mcagents/execute_shell_command.ddl -@@ -4,7 +4,7 @@ metadata :name => "Execute shell command", - :license => "Apache License 2.0", - :version => "8.0.0", - :url => "http://mirantis.com", -- :timeout => 3600 -+ :timeout => 7200 - - action "execute", :description => "Execute shell command" do - diff --git a/patches/fuel-web/0005-FIXME-Disable-amd64-Liberty-on-Ubuntu-for-now.patch b/patches/fuel-web/0005-FIXME-Disable-amd64-Liberty-on-Ubuntu-for-now.patch index 243d9c85..da231cb4 100644 --- a/patches/fuel-web/0005-FIXME-Disable-amd64-Liberty-on-Ubuntu-for-now.patch +++ b/patches/fuel-web/0005-FIXME-Disable-amd64-Liberty-on-Ubuntu-for-now.patch @@ -11,7 +11,7 @@ TODO: maybe rename above fixture to include arch in name. 1 file changed, 1 insertion(+) diff --git a/nailgun/nailgun/fixtures/openstack.yaml b/nailgun/nailgun/fixtures/openstack.yaml -index 4979fb5..037ceba 100644 +index 9da1346..f798830 100644 --- a/nailgun/nailgun/fixtures/openstack.yaml +++ b/nailgun/nailgun/fixtures/openstack.yaml @@ -1986,6 +1986,7 @@ diff --git a/patches/fuel-web/0006-Add-configuration-item-for-WSREP-SST-provider.patch b/patches/fuel-web/0006-Add-configuration-item-for-WSREP-SST-provider.patch index dacb26de..dc6c4b3e 100644 --- a/patches/fuel-web/0006-Add-configuration-item-for-WSREP-SST-provider.patch +++ b/patches/fuel-web/0006-Add-configuration-item-for-WSREP-SST-provider.patch @@ -12,7 +12,7 @@ Signed-off-by: Stanislaw Kardach 1 file changed, 21 insertions(+) diff --git a/nailgun/nailgun/fixtures/openstack.yaml b/nailgun/nailgun/fixtures/openstack.yaml -index 037ceba..598cf77 100644 +index f798830..c99e91a 100644 --- a/nailgun/nailgun/fixtures/openstack.yaml +++ b/nailgun/nailgun/fixtures/openstack.yaml @@ -856,6 +856,27 @@ -- cgit 1.2.3-korg