Bug #36076
kernel_untar_build.sh: bison: command not found
% Done:
0%
Source:
Q/A
Tags:
Backport:
mimic, luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
powercycle
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
2018-09-15T17:04:57.202 INFO:tasks.workunit.client.0.smithi192.stdout: YACC scripts/kconfig/zconf.tab.c 2018-09-15T17:04:57.203 INFO:tasks.workunit.client.0.smithi192.stderr:/bin/sh: bison: command not found 2018-09-15T17:04:57.203 INFO:tasks.workunit.client.0.smithi192.stderr:make[1]: *** [scripts/kconfig/zconf.tab.c] Error 127 2018-09-15T17:04:57.203 INFO:tasks.workunit.client.0.smithi192.stderr:make: *** [defconfig] Error 2 2018-09-15T17:04:57.204 INFO:tasks.workunit:Stopping ['kernel_untar_build.sh'] on client.0...
Related issues
History
#1 Updated by Neha Ojha over 5 years ago
/a/yuriw-2018-09-15_16:05:18-powercycle-mimic-distro-basic-smithi/3026999/
#2 Updated by Yuri Weinstein over 5 years ago
- Related to Bug #36039: "/bin/sh: 1: bison: not found" in krbd knfs added
#3 Updated by Neha Ojha over 5 years ago
- Status changed from New to Fix Under Review
#4 Updated by Patrick Donnelly over 5 years ago
- Status changed from Fix Under Review to Pending Backport
- Assignee set to Neha Ojha
- Target version set to v14.0.0
- Source set to Q/A
#5 Updated by Nathan Cutler over 5 years ago
- Copied to Backport #36121: mimic: kernel_untar_build.sh: bison: command not found added
#6 Updated by Nathan Cutler over 5 years ago
- Status changed from Pending Backport to Resolved
#7 Updated by Yuri Weinstein about 4 years ago
#8 Updated by Nathan Cutler about 4 years ago
- Status changed from Resolved to Pending Backport
- Target version deleted (
v14.0.0) - Backport changed from mimic to mimic, luminous
#9 Updated by Nathan Cutler about 4 years ago
- Copied to Backport #43926: luminous: kernel_untar_build.sh: bison: command not found added
#10 Updated by Nathan Cutler about 4 years ago
- Pull request ID set to 24185
#11 Updated by Nathan Cutler about 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".