SM:3.2.1-build21: Provision of Ubuntu Targets does not initilialise with error in "Unable to locate package linux-headers-3.13.0-100-generic"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Won't Fix
|
Critical
|
Dheeraj Gautam | ||
R3.2 |
Fix Committed
|
Critical
|
Ignatious Johnson Christopher | ||
Trunk |
Won't Fix
|
Critical
|
Dheeraj Gautam |
Bug Description
SM:3.2.1-build21: Provision of Ubuntu Targets does not initilialise with error in "Unable to locate package linux-headers-
1) Install SM Package 3.2.1.-build 21
2) Add Ubuntu OS 14-4-5; COntrail Mitaka Package for ubuntu 3.2.1 build 21
3) Add cluster/Server of target which has mention of kernel version 3.13.0-100, and kernel_upgrade set as yes
4) Reiamge the target with OS , observe that reimage goes through successfully (https:/
The above bug is validated and this bug is not seen)
5) Initiate Provision ; Observe that it gets stuck with provision_started with following error on Syslog
Feb 5 21:48:03 nodeh8 puppet-
Feb 5 21:48:03 nodeh8 puppet-
Feb 5 21:48:03 nodeh8 puppet-
Feb 5 21:48:03 nodeh8 puppet-
Feb 5 21:48:03 nodeh8 puppet-
Feb 5 21:48:03 nodeh8 puppet-
Feb 5 21:48:03 nodeh8 puppet-
Feb 5 21:48:03 nodeh8 puppet-
Feb 5 21:48:03 nodeh8 puppet-
Feb 5 21:48:03 nodeh8 puppet-
Feb 5 21:48:03 nodeh8 puppet-
6) Observed that the hieradata populated has correct kernel version, but the kernel fails to get upgrade with kernel 3.13.0-100 and blocks the provision further
7) /var/www/
linux-crashdump
linux-headers-
linux-headers-
linux-headers-
linux-headers-
8) This issue was not seen in 3.2.1 build 19
Seeing the same behavior in Mainline build 3036
tags: | added: blocker sanity |
description: | updated |
description: | updated |
Changed in juniperopenstack: | |
status: | New → Won't Fix |
This issue has not been observed in R3.2-22, so marking as Fix-Committed