| Summary: | Upgrade failed when / is on iSCSI | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Alexander Todorov <atodorov> |
| Component: | anaconda | Assignee: | Ales Kozumplik <akozumpl> |
| Status: | CLOSED NOTABUG | QA Contact: | Release Test Team <release-test-team> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.2 | CC: | jzeleny |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-09-19 09:29:38 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 691780 | ||
|
Description
Alexander Todorov
2011-09-15 12:30:50 UTC
Hmm, I found something which is probably my fault but I haven't seen it with older releases IIRC. After the initial install I created another VM which has different MAC address for the nic and then upgraded. ifcfg-eth0 still contained the MAC from the previous VM. This is probably propagated to initrd but I can't find where. ifname=eth0:XXXX on the grub command line also contains the old MAC. After fixing grub and ifcfg-eth0 to contain the correct MAC I hit bug #737479. (In reply to comment #1) > Hmm, I found something which is probably my fault but I haven't seen it with > older releases IIRC. > > After the initial install I created another VM which has different MAC address > for the nic and then upgraded. ifcfg-eth0 still contained the MAC from the > previous VM. This is probably propagated to initrd but I can't find where. Alex can you retest under the standard conditions then? (In reply to comment #3) > Alex can you retest under the standard conditions then? Re-tested and I hit bug #737479. |